After flashing the DeFrost series of ROMS (I am not saying they are the cause of this issue..) from 0.8 to 1.0 ---
I've got an issue where the screen switches itself off during a phone call and never turns on again, unless I pull out the battery and reboot it.
I've just tried flashing Pays BS and RS ROMs and they still to have this issue?
Could it be a problem during flashing just screwed over soomething inside the phone? (Prox. sensor maybe?)
Thanks for your help.
*****EDIT****
I've just found out that if i place the handset (whilst during a call) in very bright sunlight or bright artificial light --- then the screen does re-display.
It's strange however, I'm outside during midday and the screen still is off whilst placing a call. It only registers that the phone is away from my face near a very bright light source.
I've found this issue is faced by many people usually after ROOTing their device(s).
A 'USB-Brick' like issue possibly? (Proxy-Brick lol)
I will attempt to hand in my now HBOOT 0.80 ROOT'd desire to Telstra for warranty tomorrow.
I am now pretty sure that this problem is random and occurs when rooting/flashing a cust. ROM through recovery.
Related
My five month old artemis started apparently randomly freezing a few weeks ago. Usually it just freezes with the screen off, you can tell that there's power to it as there's a slight glow apparent round the edges of the screen in low light, although it does sometimes freeze with the screen and backlight on.
I've tried several of the WM6 roms including the 02 official WM6 rom and it seems to do the same thing. (I was getting the boot screen freeze on the BB4.0 rom though).
It seems to freeze more when I have it in my pocket than when it's sat around on a table and doesn't seem to be related to software installed.
Any ideas whether I am looking at a hardware problem, dodgy contacts etc?
thanks
Update: I've just noticed that if you press gently on the front of the phone, at the left-hand surround round the screen about two-thirds of the way down it makes the phone freeze. Explains why it freezes in the pocket and not on the table - Looks like it's a hardware fault...
fishes234 said:
My five month old artemis started apparently randomly freezing a few weeks ago. Usually it just freezes with the screen off, you can tell that there's power to it as there's a slight glow apparent round the edges of the screen in low light, although it does sometimes freeze with the screen and backlight on.
I've tried several of the WM6 roms including the 02 official WM6 rom and it seems to do the same thing. (I was getting the boot screen freeze on the BB4.0 rom though).
It seems to freeze more when I have it in my pocket than when it's sat around on a table and doesn't seem to be related to software installed.
Any ideas whether I am looking at a hardware problem, dodgy contacts etc?
thanks
Click to expand...
Click to collapse
Hello my friend,
I guess you are not the first nor the last to have the same problems. Mine was freezing too, in the same ways you describe here, but take some time to check this thread as well: http://forum.xda-developers.com/showthread.php?t=320922
In Greece where I come from, it seems that many of us are experiencing the same problems and the company service is changing the motherboard (in my case the first time I sent it, they just upgraded the operating system and worked only a couple of days before it starts the same again), so I think we should start worrying about technical imperfections on our device.
ROM: LeeDroid v1.3 i think
Recovery: Clockwork
Over the week I've noticed my screen been playing up abit. The display sometimes went dim (though it was natural due to my auto brightness).
Today, I cannot see my screen at all. Did the obvious troubleshooting steps.
- take out battery, simcard, sdcard,
- insert battery, enter to recovery mode
nothing, I can feel the phone vibrate on bootup, still no display.
Was thinking sending it away for warranty, but the phone has been rooted.
Will this cause any issues?
I suppose it will cause issues. Except if they swap it instantly in service.
The only thing you can do is to run a 1, 32 ruu and than if it does not fix going blindly and try to revert ENG s-off if you had.
Sent from my LeeDroided Desire HD
I was haa similar issue. The lockscreen would show for like 2 seconds after boot but then the screen would go black and the backlight would still be on It was like my phone had frozen with the screen off. I flashed the rom again but without wiping so i could backup everything then done a full wipe.
Leedroid 1.4.1
K Dotty said:
I was haa similar issue. The lockscreen would show for like 2 seconds after boot but then the screen would go black and the backlight would still be on It was like my phone had frozen with the screen off. I flashed the rom again but without wiping so i could backup everything then done a full wipe.
Leedroid 1.4.1
Click to expand...
Click to collapse
I would like to reflash with a newer rom, can't I can't even see my screen.
Can't get into recovery because screen has no display.
Phone as good as a paperweight, not even a torch
Will have to send away for warranty replacement
iamkuza said:
Was thinking sending it away for warranty, but the phone has been rooted.
Will this cause any issues?
Click to expand...
Click to collapse
To be honest, I was reading the Limited Warranty pamphlet that was in the phone's box last night.
It explicitly states that ONLY hardware components is covered by the limited warranty and specifically excluded software and accessories from the limited warranty. (Sorry, dont have the exact wording now, but it is noted in point 4)
So if there is no warranty on software, how can modifying the software that does not alter the function of the hardware void your warranty?
I am no lawyer, but this sounds pretty straight forward to me.
I highly doubt it will hold up in court, if tested.
If they do contest it. Tell them to put on the default stock ROM and see if the problem still persist.
Hi Guys,
Yesterday I was having trouble with "E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory)" error, I managed to solve this problem but ever since my calls keep dropping, oddly enough the call seems to stay connected the other end.
When I make a call it connects then drops looking at the screen for a few moments the signal has completely gone but then mysteriously comes back almost immediately, if I call my partners phone the call drops after 10-20 seconds, and if I call again the first call to her stays connected at her end, if she picks up the second call the other call goes on hold and the second call drops exactly the same.
Following the cant mount error I flashed back to Reflex 2.0.1, I didnt have the problem earlier with Reflex 2.0.0 which I did a nand with even restoring this the problem remains, I've tried insertcoin rom problems remains and also tried apps2d+ rom instead of cm7 and still problem remains.
Can anyone help?
Should flash a rooted stock froyo rom and start s-off again?
this problem was solved by fixing usb brick
heres my post fixing the problem
http://forum.xda-developers.com/showthread.php?t=1070863
I have fixed the sd card problem, its dropping calls now
I got similar error once after I flashed a align ext4 patch. I had to repartitioned the SD card to fix it.
I have repartitioned several times and tried different sd cards the dropping calls does not appear to be a sd card problem
Jonnibravo said:
I have repartitioned several times and tried different sd cards the dropping calls does not appear to be a sd card problem
Click to expand...
Click to collapse
Are you on orange by the chance? And what rom/radio are you using?
I am on T-mobile uk, I have the 32.56.00.32U 5.17.05.08, I was running Reflex 2.0.1 but I have tried stock froyo insertcoin and backed up reflex 2.0.0 which I did not have a problem with, so I think this could be because I flashed the Beta sensation rom sense 3.0, its definatley nothing to do with the sdcard, also I have usb brick and I cannoit seem to recover it with the usb brick fix, not sure if I have done it correctly though as my cid is t-mob005 not sure if thats correct.
In addition when I tried the fastboot oem boot command it rebooted the phone and siad failed status read failed too many links
Ok, I flashed a old backup of a miui rom I had and have since made a phone call for 2:30 seconds without any problems.
Can anyone help me to explain why this is happening and how I can get back to reflex without calls dropping?
ther may be a problem with the proximity sensor on the fone could be hardware/software
i was having a look over at htc forums and i found this
"
Posted by andyc120 on 15 Aug 2010 2:15 PM
After more research I was able to fix the problem on my Desire. I have a screen protector which had the smallest tiniest mark on it in the top left. The proximity sensor is two small dots at the top left of the front of the phone in the black area above the screen (you can actually just about see them when holding the screen up to the sun or a bright light).
A lot of people apparantly have had this problem when using screen protectors, or cases (I know you said you are not using a case) that cover the proximity sensor. Once I peeled off my screen protector it started working fine again.
There is an app I used to check when the proximity sensor was detecting something and when it wasn't - the app is called ProxyLightTest. Download that then mess around holding your hand over the proximity sensor and see if it has problems. I am guessing you might be using a screen protector or there might be a slight scratch on your screen over the proximity sensor that is messing with your signal. if not then maybe you'll have to send it back.
Hope this helps! Good luck."
Thanks guys I solved the problem thanks to the above poster, seems the radio is affected by the usb brick as soon as that was fixed all the problems stopped
Very good day
I have a query, I have a HTC Touch PRO 2 RHOD300
The phone is counting on the next problem happens when you try to turn the screen by pressing the button on top that will not start and if you take the pen side of the phone just turn on the lights in the lower keys where this call, Windows key, Back and Finish. The phone returns to regain normal when a call comes in after the returns to be shut down and locked and not back on the screen.
In other cases there is the disadvantage that remains off, open the phone to expand and to use the qwerty keyboard and this light comes on but no screen and if you call the phone number that shows no signs of life with this call More on the other side of where you are calling is heard that he was calling.
My question is whether they have a patch for the solution and if someone else had already reported this fault, this problem is being presented to several phone numbers of friends and wanted to see whether if they had a patch to fix what they could afford to apply it to the phones have this fault.
If in case anyone has a solution for this above I would appreciate very much.
Funny... I have been experiencing this same problem just recently. I have another identical phone and replace the sim card in it with the same results. It doesnt appear to happen to the phone when the sim card is not installed. I have tried hard reset, selectively installing programs, thinking it was a programing problem with one or another, but nothing I tried seems to change the problem. Any help is appreciated.
Thanks.
KC
Note that for my part I've been trying to give solution to the problem and have identified the following place your sim but the connections do not let my ISP leaves your network connection as my job to your phone so you do not use the 3G data network, thus the problem will not happen.
To me this is what happens, the phone went dead, but if you remove the stylus from the side, the lower lights are lit but not the screen, but if you make a phone call to your cell this and respond, but entering Idle this again locked again.
HTC have written to me but these have not been resolved.
I am in Guatemala and I used 2 different companies and the problem persists.
You friend in that country is, and have only confirmed this problem also began to give you on Friday May 20? because that was the time when many telephones HTC Touch Pro2 here began to have these symptoms.
Yes. Friday would be correct.
So if the issue is global, it is the end of the world of mobile
This doesn't appear to be a new problem though. If you search on "Screen of Death", it is quite common. However, I have tried several of the solutions that I have come across, with no go. It is complicated by the fact that we started experiencing the problem at the same time.
KC
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?
:/