I've had this phone for about 2 weeks now and I'm starting to have this weird problem. The phone is not rooted and nothing has been done to it. Every time I place a call, the phone will go black and it'll stay like that even after the person hangs up. I can't press the home button or power button! So I tried some things! I downloaded watchdog to see if any of my apps were causing this, didn't work. Next thing I did was install the XXKI3 (2.3.5) upgrade with ODIN, went smoothly but problem still occurs. Then lastly I factory restored the phone and it went fine but it the problem still occurs...
I don't know if this could be the problem but I went to a Ghost Armor kiosk and had them install a screen protector for me (yesterday). The phone worked fine before I had it installed!
Another thing, when I place the call, my sensor turns red and it stays like that.
PhiChong said:
I've had this phone for about 2 weeks now and I'm starting to have this weird problem. The phone is not rooted and nothing has been done to it. Every time I place a call, the phone will go black and it'll stay like that even after the person hangs up. I can't press the home button or power button! So I tried some things! I downloaded watchdog to see if any of my apps were causing this, didn't work. Next thing I did was install the XXKI3 (2.3.5) upgrade with ODIN, went smoothly but problem still occurs. Then lastly I factory restored the phone and it went fine but it the problem still occurs...
I don't know if this could be the problem but I went to a Ghost Armor kiosk and had them install a screen protector for me (yesterday). The phone worked fine before I had it installed!
Another thing, when I place the call, my sensor turns red and it stays like that.
Click to expand...
Click to collapse
the screen protector might be interfering with your proximity sensor making the phone think you still have it held to your head.
PhiChong said:
I've had this phone for about 2 weeks now and I'm starting to have this weird problem. The phone is not rooted and nothing has been done to it. Every time I place a call, the phone will go black and it'll stay like that even after the person hangs up. I can't press the home button or power button! So I tried some things! I downloaded watchdog to see if any of my apps were causing this, didn't work. Next thing I did was install the XXKI3 (2.3.5) upgrade with ODIN, went smoothly but problem still occurs. Then lastly I factory restored the phone and it went fine but it the problem still occurs...
I don't know if this could be the problem but I went to a Ghost Armor kiosk and had them install a screen protector for me (yesterday). The phone worked fine before I had it installed!
Another thing, when I place the call, my sensor turns red and it stays like that.
Click to expand...
Click to collapse
Hi,
It has to be firmware issue. but its really weird.. ...indeed
When the proximity sensors turns red - it means that it is activated (operational). If it stays red all the time - something is wrong. I would recommend turning the proximity sensor off (in settings/call). And as a final fix i would consider flashing another firmware. If you want to stay in official FW, see this: http://forum.xda-developers.com/showthread.php?t=1075278. Pick a FW of your choice and flash it using few easy steps. When you follow the steps carefully - nothing wrong will happen ;-) I can recommend XWKI4 official firmware. its better than stock 2.3.5 so far.
---------- Post added at 03:15 PM ---------- Previous post was at 03:10 PM ----------
damn it... sorry for my previous post ;-) I was not reading carefully ... you know... noobs ;-) But the last sentence about recommended official FW is nothing but true ;-)
Thanks guys! I found the issue. It wasn't the firmware (thanks for helping though), it is actually the screen protector! I took off the Ghost Armor screen protector and bam it worked, lol. What a waste of money..$20 bucks for the screen protector and it serves no purpose but a hindrance to my phone. I slapped on a cheap screen protector I got from my phone case and it covers the sensor but the material doesn't block the sensor.
Related
Hi all!
My friend loved my mozart, so decided to get himself one!
BUT, annoyingly, there seems to be a problem with the screen...
Sometimes it just wont detect that you are touching it etc.
Sometimes it will work for a little while, or even just a split second and think your pressing instead of sliding your finger.
i HAVE already replaced the screen thinking this would solve it, but its EXACTLY the same
Is there anything else i could try, or is it just a screwed unit?
Cheers
Keith
BUMPZ!!!
anyone???
you got a screen protector on it? before i got my screen protector on it, it worked good. but after then it sometimes didnt respond to touches. sometimes especially when it was hot
ive answered this 2 times alread, try to search
flash the previous firmware back and itll work, its worked for mine
Well I did it... Broke the screen a couple of weekends ago. Ordered and received a new one. (No problem and not too bad price-wise) Then I ordered the correct screwdriver. That came in yesterday and I followed a couple of tutorials online to take the thing apart. Not too bad despite the teeny-tiny parts. I got it back together and lo-it worked! Actually it took a couple of tries and I reflashed it but then it booted right up. All the apps seemed responsive and life was good once again...
Until I tried to make a call. Then the screen went dark and it appeared that the phone froze up. Called myself from the house phone and discovered that the Aria was dialing, connecting, and sending voice but that I couldn't hear anything on the Aria.
Disassembled, re-set the earpiece, reassembled, called myself again, and I could hear. The screen came on and stayed on, but the touchscreen would not function.
Disassembled, checked all the connections, and reassembled again. The phone appears to work correctly in all aspects until I try to make or receive calls. At that point the screen shuts down and the only way to disconnect a call (or get the screen back) is to pull the battery and reboot.
I tried reflashing the ROM and that didn't work. I'm afraid the transceiver is shorting the screen out somehow but have reached the limits of my expertise.
Any suggestions?
Thanks,
Jerry
I have never had to replace my digitizer so only speaking from what i have read but it sounds like the very small rubber piece that covers the proximity sensor. I have read that if missing or not placed correctly people have had the same problem as you. Just my thoughts
I've replaced my digitizer and I have had the exact same problem. E.Cardo is correct, it is the small rubber piece on the proximity sensor not positioned correctly or not present at all.
Thanks to both of you. The proximity sensor is supposed to be right behind the ATT logo, correct?
I can't wait to get home and try this. I really don't like the backup Cliq Xt... I'll post once I've messed with it.
gdgeorge said:
The proximity sensor is supposed to be right behind the ATT logo, correct?
Click to expand...
Click to collapse
It's hard to see them exactly so I took a picture to show exactly where they are:
http://imgur.com/a/36h8t#ayQhv
It's actually just above the & in the at&t logo, although if you have a replacement digitizer, it might not have the at&t logo on it. If you have trouble seeing it, try looking at it in the sunlight.
To add to what drumist said there as small black rubber piece that goes around the proximity sensor that prevents light seepage and allot of people discard it by mistake when disassembling the phone.
Sent From Deep Within The Rabbit-Hole
Why did you have to reflash? The new screen didn't worked?.
My aria's screen is broken too. I boutgh a new one but It doesn't work. Do you resolve this reflashing? (that's mean applying the new rom version from ATT)
Thanks for your response.
javierarenas said:
Why did you have to reflash? The new screen didn't worked?.
My aria's screen is broken too. I boutgh a new one but It doesn't work. Do you resolve this reflashing? (that's mean applying the new rom version from ATT)
Thanks for your response.
Click to expand...
Click to collapse
The screen or digitizer are hardware they should have nothing to do with the rom. The op only tried flashing the phone to illuminate it is a possible source of the problem. It sounds like you did not install the new screen or digitizer correctly you may need to disassemble and make sure everything is connected correctly and securely. Flashing your phone will most likely not correct your problem.
Sent From Deep Within The Rabbit-Hole
Maybe, just maybe, there are new drivers for the touchscreen included in the rom. I am using cyanogen 7.0.3 without problems, and it works nice with the old screen.
Or the new screen is defective.
I am pretty sure I installed correctly the new screen. Of course the old one is working fine right now.
I requested a new screen so I will wait...
Thanks again.
I'm brand new to HTC devices so I'm unsure if the dialer is sense or if this is a ICS dialer were dealing with. (My old phone was a Droidx, so my exp is with blur and asop 2.3 from liberty).
Either way though i seem to have come across an interesting "bug" or at least unusual behavior.
I've noticed on almost every other call, weather it's incoming or outgoing, the MOMENT you dial/answer the screen goes dark. Now i can press the power button to wake it up again and it will stay on for exactly 5 seconds before going dark again. If i flip on speaker phone the screen will stay on, however the moment i turn off speaker phone it goes dark again.
Whats really annoying is if i go back to the home screen it still goes dark after 5 seconds but now when i wake it up it's at the lock screen. If i try to unlock it the moment i touch the screen it goes dark. No matter where i touch the screen the phone is now perma locked until the call is finished.
Now like i said this happens every other call so far in the 6 times I've tested this, which i thought was really odd. The other times the screen stays on and acts completely normal no matter what i do while a call is active. Fresh reboot makes no difference. I haven't done a factory reset yet as I'm trying avoid that.
What i have done so far is unlocked the bootloader, Flashed recovery, and the root from con247's thread in the dev section. I don't think that has anything to do with it though since i noticed the screen going black during a call before i started messing with bootloaders/recovery/root. I just didn't test it as well before doing those things cuz i didn't think anything of it.
Is anyone else seeing this behavior and does anyone have any suggestions?
Void4ever
void4ever said:
I'm brand new to HTC devices so I'm unsure if the dialer is sense or if this is a ICS dialer were dealing with. (My old phone was a Droidx, so my exp is with blur and asop 2.3 from liberty).
Either way though i seem to have come across an interesting "bug" or at least unusual behavior.
I've noticed on almost every other call, weather it's incoming or outgoing, the MOMENT you dial/answer the screen goes dark. Now i can press the power button to wake it up again and it will stay on for exactly 5 seconds before going dark again. If i flip on speaker phone the screen will stay on, however the moment i turn off speaker phone it goes dark again.
Whats really annoying is if i go back to the home screen it still goes dark after 5 seconds but now when i wake it up it's at the lock screen. If i try to unlock it the moment i touch the screen it goes dark. No matter where i touch the screen the phone is now perma locked until the call is finished.
Now like i said this happens every other call so far in the 6 times I've tested this, which i thought was really odd. The other times the screen stays on and acts completely normal no matter what i do while a call is active. Fresh reboot makes no difference. I haven't done a factory reset yet as I'm trying avoid that.
What i have done so far is unlocked the bootloader, Flashed recovery, and the root from con247's thread in the dev section. I don't think that has anything to do with it though since i noticed the screen going black during a call before i started messing with bootloaders/recovery/root. I just didn't test it as well before doing those things cuz i didn't think anything of it.
Is anyone else seeing this behavior and does anyone have any suggestions?
Void4ever
Click to expand...
Click to collapse
Sounds like the proximity sensor is going wonky. You might try a factory reset and without installing anything else see if you get the same issue. Also, make sure that any programs you have installed are not affecting it for some reason.
blazingwolf said:
Sounds like the proximity sensor is going wonky. You might try a factory reset and without installing anything else see if you get the same issue. Also, make sure that any programs you have installed are not affecting it for some reason.
Click to expand...
Click to collapse
Just factory reset it, skipped setup completely and started making calls, same issue. You maybe right about the sensor though. The first call acted up like i explained. The second call the screen was staying on like i expected, but once i switched speaker phone off and then back on the screen shut off and started acting like call one again.
I just got this phone 6 hours ago i wonder how hard it will be to convince verizon there's a hardware fault. I guess i'd better unroot it and remove recovery so i can call in the morning.
Void4ever
I just wanted to make sure i understand this before i do it.
To remove the root i need to install the RUU for the phone, which i found at http://themikmik.com/showthread.php?13550-Asian-Shooter-goes-ICS-and-a-VZW-Fireball-RUU (second link i assume).
I haven't downloaded it yet, but it's an exe. Will it flash the phone via USB, or does it just extract something i can use recovery to flash with?
Once i get the root removed i just need to flash back the original recovery and i should be good to go right?
Void4ever
void4ever said:
I just wanted to make sure i understand this before i do it.
To remove the root i need to install the RUU for the phone, which i found at http://themikmik.com/showthread.php?13550-Asian-Shooter-goes-ICS-and-a-VZW-Fireball-RUU (second link i assume).
I haven't downloaded it yet, but it's an exe. Will it flash the phone via USB, or does it just extract something i can use recovery to flash with?
Once i get the root removed i just need to flash back the original recovery and i should be good to go right?
Void4ever
Click to expand...
Click to collapse
There are directions in the RUU that will explain all of the steps. You will connect your phone with the USB cable.
It shouldn't be to hard to convince them. Just show them the steps you did to reproduce the issue. Good luck.
On the phone right now and the guy is setting up overnight sat delivery to my house. We are a fairly large business account so i'm glad they are going that extra mile.
Just to note I've noticed the sensor doesn't shut off after a call is complete. In fact it stayed on last night for around 6 hours before finally turning off. I did another test this morning and once again the sensor is stuck on, so good call. Thanks so much for your help, i never would have thought sensor, it seemed like a software issue to me!
Void4ever
void4ever said:
On the phone right now and the guy is setting up overnight sat delivery to my house. We are a fairly large business account so i'm glad they are going that extra mile.
Just to note I've noticed the sensor doesn't shut off after a call is complete. In fact it stayed on last night for around 6 hours before finally turning off. I did another test this morning and once again the sensor is stuck on, so good call. Thanks so much for your help, i never would have thought sensor, it seemed like a software issue to me!
Void4ever
Click to expand...
Click to collapse
No problem. Glad you got a new one coming.
replacement came today and it works like a dream now, got custom recovery and root going! It was def a bad prox sensor on the other one. Thanks again for your help wolf!
Void4ever
Good to hear man. Enjoy that puppy.
void4ever said:
replacement came today and it works like a dream now, got custom recovery and root going! It was def a bad prox sensor on the other one. Thanks again for your help wolf!
Void4ever
Click to expand...
Click to collapse
Awesome.
Sent from my ADR6410LVW using Tapatalk 2
Ok, so my girlfriend dropped her phone and cracked the screen, I ordered a new LCD/Digitizer assembly and everything seemed fine. She then realized that it had a dead line while playing Draw Something. I sent back and just received a new assembly and installed it. Ever since I installed it the screen will occasionally black out and lock up. It takes forever for screen to come back up and seems very random in how long. I try powering off and on to no avail. Once it does come back I get an error log in the notification pull down saying it just rebooted form an unexpected reboot error and I have sent this notification 3 or 4 times.
Things I have tried.
Taking apart and checking all connections as well as cleaning screen on inside and out where proximity sensor goes. I am seriously at a loss, it seems to work for a while on a fresh(actual battery pull) and work fine until it just freezes no button push except power button which shuts off screen and then never comes back except for the captivate buttons on the bottom. I have searched for answers but haven't found anyhing like before.
Thoughts?
Thanks,
Kevin
I know that feel bro.
KKellett said:
Ok, so my girlfriend dropped her phone and cracked the screen, I ordered a new LCD/Digitizer assembly and everything seemed fine. She then realized that it had a dead line while playing Draw Something. I sent back and just received a new assembly and installed it. Ever since I installed it the screen will occasionally black out and lock up. It takes forever for screen to come back up and seems very random in how long. I try powering off and on to no avail. Once it does come back I get an error log in the notification pull down saying it just rebooted form an unexpected reboot error and I have sent this notification 3 or 4 times.
Things I have tried.
Taking apart and checking all connections as well as cleaning screen on inside and out where proximity sensor goes. I am seriously at a loss, it seems to work for a while on a fresh(actual battery pull) and work fine until it just freezes no button push except power button which shuts off screen and then never comes back except for the captivate buttons on the bottom. I have searched for answers but haven't found anyhing like before.
Thoughts?
Thanks,
Kevin
Click to expand...
Click to collapse
I've actually had this exact same problem with my phone. I haven't replaced the screen but ever since the update my phone will do what hers does. It will freeze after a bit of use and I cannot do anything with it but do a simpull and then it will work again for a bit. I haven't been able to fix it. I have done factory resets, had the store reflash the software and yadda yadda yadda. I'm havinh my phone replaced now but it's frustrating not being able to figure out how to fix it when I feel like it should be fixable since it literally didn't even start until minutes after I installed the update.
It sucks.
Hi everyone,
I acquired a Galaxy S4 that apparently worked but had a broken screen. I replaced the screen and initially seemed to work but quickly noticed it keeps crashing and restarting. It seems to happen after it has been on about 20 minutes, it can work fine, I tested with youtube videos and the longest it worked for was 30 minutes before freezing. Sometimes it can crash even as it is starting up.
Most times it crashes the screen will freeze and completely lock up the device for a few seconds, then turn off, vibrate and restart. Rarely but sometimes, the graphics on the screen will turn different colours and show lines just before restarting.
I have updated the firmware via Odin using a stock rom from sammobile, I have not tried doing anything to the kernell.
The last thing I tried is to clean the motherboard PCB with some PCB cleaner and did a low temperature (about 200degC) attempt at a reflow, but I don't think I did anything long enough to solve any potentially dry or cracked joints as I was worried I would just damage the motherboard all together.
I suspect it would be a dry joint but I have no idea.
I would absolutely love to have this phone working, can anyone offer any advice?
many thanks,
Graham
I'm sure it's not helpful at all, but it sounds like an overheating issue. Does the device get hot before it reboots?
My old Galaxy Nexus experienced these issues after I flashed and overclocked it, and changed the governor. It would get so hot it was almost uncomfortable to touch. Then it would reboot and would be fine for about an hour. Rinse and repeat.
Just as a test, Liquid stable just released, so maybe try flashing that through goo manager and then use performance control to underclock the processor. See if the amount of time between reboots increases?
citenx said:
I'm sure it's not helpful at all, but it sounds like an overheating issue. Does the device get hot before it reboots?
My old Galaxy Nexus experienced these issues after I flashed and overclocked it, and changed the governor. It would get so hot it was almost uncomfortable to touch. Then it would reboot and would be fine for about an hour. Rinse and repeat.
Just as a test, Liquid stable just released, so maybe try flashing that through goo manager and then use performance control to underclock the processor. See if the amount of time between reboots increases?
Click to expand...
Click to collapse
Thank you, it does not get hot at all before freezing. I will give liquid stable a go when I finish work, can't hurt to try!
citenx said:
I'm sure it's not helpful at all, but it sounds like an overheating issue. Does the device get hot before it reboots?
My old Galaxy Nexus experienced these issues after I flashed and overclocked it, and changed the governor. It would get so hot it was almost uncomfortable to touch. Then it would reboot and would be fine for about an hour. Rinse and repeat.
Just as a test, Liquid stable just released, so maybe try flashing that through goo manager and then use performance control to underclock the processor. See if the amount of time between reboots increases?
Click to expand...
Click to collapse
Just as a side note, GPS is buggy and handsfree headphones won't work for me. If you decide to flash, turn off wifi locationing and then GPS will work.
citenx said:
Just as a side note, GPS is buggy and handsfree headphones won't work for me. If you decide to flash, turn off wifi locationing and then GPS will work.
Click to expand...
Click to collapse
I just tried to put liquid stable on my phone, did not try via goomanager since I don't have it, but sent it as an adb sideload while in cwm recovery, it failed to install and now my phone does not turn on, just stuck on Samsung logo, so now I am reflashing stock rom again.
thanks
I have it turning on again now, but most times it actually freezes on the loading screen and half way through the welcome noise. I will test how long it can survive in recovery mode.
When it did turn on I went into camera and started recording to see how long it would last. Strangely enough it crashed during recording but the camera itself was still working and the screen was updating with the camera, however all buttons were unresponsive, the home and return buttons wouldn't even light up, and the recorder time was stuck on 4 seconds. I had to turn it off by holding the power button for about 10 seconds.. maybe this could be useful information for someone to diagnose?
graham0122 said:
I just tried to put liquid stable on my phone, did not try via goomanager since I don't have it, but sent it as an adb sideload while in cwm recovery, it failed to install and now my phone does not turn on, just stuck on Samsung logo, so now I am reflashing stock rom again.
thanks
Click to expand...
Click to collapse
I just noticed from a different post on the Liquid 2.4 thread that the original post was for GSIII (WTF?). If you feel lucky and want to try again, here's the link off of goo and the MD5 is 72b3e6cc79f298f85b8e21f99a990b90.
---------- Post added at 02:34 PM ---------- Previous post was at 02:19 PM ----------
graham0122 said:
I have it turning on again now, but most times it actually freezes on the loading screen and half way through the welcome noise. I will test how long it can survive in recovery mode.
When it did turn on I went into camera and started recording to see how long it would last. Strangely enough it crashed during recording but the camera itself was still working and the screen was updating with the camera, however all buttons were unresponsive, the home and return buttons wouldn't even light up, and the recorder time was stuck on 4 seconds. I had to turn it off by holding the power button for about 10 seconds.. maybe this could be useful information for someone to diagnose?
Click to expand...
Click to collapse
And the only thing wrong with it was the screen? Two days after I got my S4 I went hiking and got it wet (shame on me) but the unresponsiveness sounds just like water damage. Are any of the moisture sensors tripped?
citenx said:
I just noticed from a different post on the Liquid 2.4 thread that the original post was for GSIII (WTF?). If you feel lucky and want to try again, here's the link off of goo and the MD5 is 72b3e6cc79f298f85b8e21f99a990b90.
---------- Post added at 02:34 PM ---------- Previous post was at 02:19 PM ----------
And the only thing wrong with it was the screen? Two days after I got my S4 I went hiking and got it wet (shame on me) but the unresponsiveness sounds just like water damage. Are any of the moisture sensors tripped?
Click to expand...
Click to collapse
The screen is perfect, no moisture sensors tripped. I know the screen was a working one, and as far as I am aware the only problem with this phone is the screen was smashed. I have checked the motherboard and it doesn't seem to be damaged. But if it was I would expect it not to work at all?
The crashing doesn't seem to be due to holding it or moving it, it just happens regardless if its resting untouched etc.
It has now restarted about 10 times in the past few minutes, sometimes as soon as I hear the vibrate to signal it is turning on, because it vibrates 2 or 3 times in the space of a few seconds.
It definitely seems to be getting worse!
It seems to sit in recovery mode as long as it likes though..