Hi i have unrooted Nexus 4 with paranoid android and recently i experienced some problems with sensor responsible for blacking screen when calling someone so i have a few questions. Firstly can i send them unrooted device or it cancel warranty totally no matter what kind of problem it is? Secondly, if no, is there maybe possibility to lock it again so its looks like fabric one etc? Or maybe some know if it maight not be a problem with sensor itself but something else, i already change rom from to cyanogenmod to see if it would help but it didn't.
WIEWIR1107 said:
Hi i have unrooted Nexus 4 with paranoid android and recently i experienced some problems with sensor responsible for blacking screen when calling someone so i have a few questions. Firstly can i send them unrooted device or it cancel warranty totally no matter what kind of problem it is? Secondly, if no, is there maybe possibility to lock it again so its looks like fabric one etc? Or maybe some know if it maight not be a problem with sensor itself but something else, i already change rom from to cyanogenmod to see if it would help but it didn't.
Click to expand...
Click to collapse
First, no you have to unroot in order to send back for warranty(every root guide here will warn you of this)
Second, yes you can relock bootloader and unroot so it appears untouched to the manufacturers.
Third, it might be a battery issue on your part, if your warranty is still valid,you might want to unroot, relock bootloader and send back.
WIEWIR1107 said:
Hi i have unrooted Nexus 4 with paranoid android and recently i experienced some problems with sensor responsible for blacking screen when calling someone so i have a few questions. Firstly can i send them unrooted device or it cancel warranty totally no matter what kind of problem it is? Secondly, if no, is there maybe possibility to lock it again so its looks like fabric one etc? Or maybe some know if it maight not be a problem with sensor itself but something else, i already change rom from to cyanogenmod to see if it would help but it didn't.
Click to expand...
Click to collapse
Off-topic: Check if the screen protector is covering the proximity sensor,many users (including me) have faced the same problem due to the screen guard covering the proximity sensor
Related
OK, now I have a problem.
If I turn my xoom off and then on again the touchscreen will not respond to any input, only hardware buttons work.
If I hold volume up and power button to restart, it restarts and everything works OK. I can but it to sleep and wake it up and still everything works. Everything works until I turn it off and on again, then the problem returns and I need to hold volume up and power button to restart it again to get the touch screen working.
I searched the net but didn't find anything similar.
Any ideas?
is it still stock or you rooted / update kernel ?
errevi said:
is it still stock or you rooted / update kernel ?
Click to expand...
Click to collapse
Its complitly stock wifi only Xoom, bought from US about two weeks old.
I tried Factory reset, it didn't change anything.
Strange thing is that volume up and power reset fixes it every time. And it works fine until i turn it off again. What does this volume up and power button command do exactly, soft reset? If soft reset fixes it, it can't be a hardware problem or can it?
If I were you I would return it cuz to me that sounds like a defect with your xoom. But if u messed with it (rooting/unlocking) they won't even touch it.
Motive101 said:
If I were you I would return it cuz to me that sounds like a defect with your xoom. But if u messed with it (rooting/unlocking) they won't even touch it.
Click to expand...
Click to collapse
Like i already said, i haven't messed with it, it's completely stock.
About returning it... The problem is that i'm in Europe and i bought my Xoom from US, so i'm not really excited about sending it back.
Is it somehow possible to install the current android 3.0.1 rom again? Without unlocking and rooting?
I do not know if it works on the xoom but other tablets have a calibration ini file that you can place on the root of your SD card and reboot letting it recalibrate the touch screen? Let me know and I can send that to you?
poisike said:
Like i already said, i haven't messed with it, it's completely stock.
About returning it... The problem is that i'm in Europe and i bought my Xoom from US, so i'm not really excited about sending it back.
Is it somehow possible to install the current android 3.0.1 rom again? Without unlocking and rooting?
Click to expand...
Click to collapse
gysgtusmc said:
I do not know if it works on the xoom but other tablets have a calibration ini file that you can place on the root of your SD card and reboot letting it recalibrate the touch screen? Let me know and I can send that to you?
Click to expand...
Click to collapse
Thanks for trying to help! I'm not sure i want to mess with this yet. I talked to Motorola about my problem and the seemed very interested in my problem, so i will wait and see what they suggest.
Any news from there? I have a similar situation here (malfunctioning touchscreen, and I'm from Europe).
You can read my story here http://forum.xda-developers.com/showthread.php?t=1036009
My malfunctioning is slightly different from yours, but I'm interested in what Motorola says for a problem like this.
Ieracos said:
Any news from there? I have a similar situation here (malfunctioning touchscreen, and I'm from Europe).
You can read my story here http://forum.xda-developers.com/showthread.php?t=1036009
My malfunctioning is slightly different from yours, but I'm interested in what Motorola says for a problem like this.
Click to expand...
Click to collapse
They are still thinking how they can help me, there is no solution yet, I will let you know when I get a solution from them.
And yes, my problem seems different from you. No one have reported anything similar to my problem.
I have seen a few threads similar to your problem.
poisike said:
And yes, my problem seems different from you. No one have reported anything similar to my problem.
I have seen a few threads similar to your problem.
Click to expand...
Click to collapse
Really? I haven't seen anything like my problem in forums, and everyone told me that my problem is "strange" :S
However, just in case, have you thought about how to return the Xoom from Europe to US? Or are you directly talking with Motorola to file a RMA practice? After all, we should have one year of international warranty by Motorola, isn't it?
Ieracos said:
Really? I haven't seen anything like my problem in forums, and everyone told me that my problem is "strange" :S
However, just in case, have you thought about how to return the Xoom from Europe to US? Or are you directly talking with Motorola to file a RMA practice? After all, we should have one year of international warranty by Motorola, isn't it?
Click to expand...
Click to collapse
In fact someone from Motorola US contacted me and offered help, so I can't really say anything bad about Motorola, they are really friendly and helpful. They offered to replace my Xoom, but later discovered that i'm not in US and suggested that I should be able to get a replacement from europe.
Before I was contacted by Motorola US, I sent a email to Motorola UK and they also apologized for the problems I had and offered to replace my Xoom, only problem is that they don't have any in stock at the moment, so I have to wait about two weeks.
As my Xoom works great after I force reboot it, it's not a problem for me to wait, I can use my Xoom until I get a replacement.
I would like to thank Motorola for the great support that they have offered me and I will update this thread when my issue is resolved.
But back to your problem, I suggest that you contact your nearest Motorola office, i'm sure they will try to help you.
poisike said:
But back to your problem, I suggest that you contact your nearest Motorola office, i'm sure they will try to help you.
Click to expand...
Click to collapse
I'm trying to do it right now
A little update.
I have been using my faulty Xoom for over two weeks now. I didn't turn it off so it worked until today. Today i tried to install a app from Market and My apps crashed, so i tried to stop it and this caused Launcer to FC (Does Launcer FC cause a automatic reboot?). The screen went black and in about 20 seconds it did show me the lock screen and i had no touch screen control. So i force rebooted it and now it doesn't even start up anymore, it's stuck on boot animation.
So it's starting to get really frustrating... I'm even considering to buy another Xoom, but this really isn't a solution, i have no use for two (if i ever get a replacement).
Has anyone any ideas? Why is it now stuck on boot animation, doesn't this look like a software problem? Is there any way to push clean images to it without unlocking? I understand that unlocking will void my warranty?
Is it possible to flash the official stock images without unlocking?
Ok, i got it to boot up again. I did Wipe data/factory reset and now it boots up again, but still no touch control.
And it seems that i have confirmed that doing too many force reboots will mess up the system.
BTW, there is a way to get into Android recovery on WIFI only Xoom, i wish i had known this before, "adb reboot recovery" works.
Can someone please answer my question, is it possible to flash the official stock images without unlocking? Maybe that will fix my touch screen control problem...
I've having this same issue but mine is worse.. the touchscreen is not working AT ALL.. only the power button works..
I can restart the xoom with the volume up power button but after it restarts still no response from the touchscreen!
What can I do to fix this?
Any help would be appreciated..
Hey guys
Apologies if this is supposed to be in general but I figured it would make more sense here.
Basically my brother's phone just got the sense 3.0 update the other day and now whenever he tries to end the call the phone 'switches off. ' I figured it might be something to do with the proximity sensor. So I got the app proximity sensor finder and covered the proximity sensor. When I took my finger off it said that I was still covering it.
Could it be something to do with the update? The phone is not rooted or S-OFF'ed and I don't really want to do it unless I have to. It just seems a little tedious installing a custom rom and then having to make it s-on again if I have to send it back.
Sent from my HTC Desire S using xda premium
Hi guys
I have a fault with my camera on my desire s. The phone is unrooted and on stock gingerbread, waiting for ICS........ But the thing is when I open up the camera all I get is a blank screen and sometimes it flickers on and goes off. Iv done hard reset, soft reset.... The camcorder or 3rd party camera apps dont also work so have any of you guys expereinced the same problem?/ But odly after the hard reset the mirror application sometimes works but very rarely. If you can help please help?/ I have contacted HTC but i really dont wanna send it back for repair!! So some please help me. Thanks Amolak
amolak1999 said:
Hi guys
I have a fault with my camera on my desire s. The phone is unrooted and on stock gingerbread, waiting for ICS........ But the thing is when I open up the camera all I get is a blank screen and sometimes it flickers on and goes off. Iv done hard reset, soft reset.... The camcorder or 3rd party camera apps dont also work so have any of you guys expereinced the same problem?/ But odly after the hard reset the mirror application sometimes works but very rarely. If you can help please help?/ I have contacted HTC but i really dont wanna send it back for repair!! So some please help me. Thanks Amolak
Click to expand...
Click to collapse
If the phone is unrooted, stock and under warranty then don't even consider screwing around with it. This sounds like 99.9% hardware fault, so just send it back to get it fixed.
SimonTS said:
If the phone is unrooted, stock and under warranty then don't even consider screwing around with it. This sounds like 99.9% hardware fault, so just send it back to get it fixed.
Click to expand...
Click to collapse
thanks mate its under warranty just didnt want the hassle of going through the repairs as it could take a while
amolak1999 said:
thanks mate its under warranty just didnt want the hassle of going through the repairs as it could take a while
Click to expand...
Click to collapse
Yep - but a lot less time (and certainly a lot less money) than attempting to fix it yourself, invalidating your warranty and maybe destroying it totally. I have stripped my DS to the guts on several occasions, to replace LCD and digitiser, but I chose to invalidate my warranty when I bought the phone as I wanted to root it. In your position I wouldn't hesitate to send it back officially.
Ok will do thanks
Sent from my HTC Desire S using xda app-developers app
hi. i've a beautiful htc one s black. i've unlocked and rooted the phone and flashed the viperones rom after the update to 2.31. yesterday i noticed that the vibration doesn't work. or better, work sometimes!! doesn't work both the softkeys that vibration on call. i think that the only solution is assistance (fu*k!). have you others solutions??
Try the hard reset and other roms, 2.21 based. Don't change the kernel... For me, the vibration works all time, strange too...
juniorxdb said:
Try the hard reset and other roms, 2.21 based. Don't change the kernel... For me, the vibration works all time, strange too...
Click to expand...
Click to collapse
it's only a my problem. nobody that has flashed the viper rom has this problem....
has the phone been exposed to any kind of moisture? sweat? rain? anything? i run into this all the time at my job. 9 times out of 10 it's a small amount of corrosion built up on the connection to the motherboard. but it could also be a factory defect that has just recently surfaced and even though it's rooted, since it is a hardware issue (most likely) htc will still warranty it
HidaKureku said:
has the phone been exposed to any kind of moisture? sweat? rain? anything? i run into this all the time at my job. 9 times out of 10 it's a small amount of corrosion built up on the connection to the motherboard. but it could also be a factory defect that has just recently surfaced and even though it's rooted, since it is a hardware issue (most likely) htc will still warranty it
Click to expand...
Click to collapse
i talked with a chat center of htc and the operator said to me that the phone is out of warranty and that i pay if i want repair the problem (damn!)...
if you have any experience with hardware repairs on cell phones, you could attempt to disassemble the phone and check the connections for corrosion, damage, etc. if you do, post a picture of the motherboard and a close up of the vibrate connections
HidaKureku said:
if you have any experience with hardware repairs on cell phones, you could attempt to disassemble the phone and check the connections for corrosion, damage, etc. if you do, post a picture of the motherboard and a close up of the vibrate connections
Click to expand...
Click to collapse
no no no. i don't have any experience in disassemble the phone... but the strange thing is that I turned off my phone and it worked, when I turned on no longer worked.
Try flashing a custom kernel. It sounds like it might be software related
Sent from my HTC One S
HidaKureku said:
Try flashing a custom kernel. It sounds like it might be software related
Sent from my HTC One S
Click to expand...
Click to collapse
i tried with the fusion ultimate 2.1 and the viper 'stock'. the problem persist.... :crying:
Then it sounds like hardware to me. You might wanna find a reputable cell phone repair store in your area and let them check it out
Sent from my HTC One S
Hello, so i had my OnePlus one for a while and just recently i dropped it lucky the screen didn't crack and opens up just fine but the touch stopped working is there a fix for this? And how do i go about it.. I'm currently in Egypt so there isn't really any replacements and anyone who knows much about this device to be able to repair it at a decent price. I would like to fix it on my own, and i honestly hope its just a wire unplugged or something..
Thanks.
Rexee said:
Hello, so i had my OnePlus one for a while and just recently i dropped it lucky the screen didn't crack and opens up just fine but the touch stopped working is there a fix for this? And how do i go about it.. I'm currently in Egypt so there isn't really any replacements and anyone who knows much about this device to be able to repair it at a decent price. I would like to fix it on my own, and i honestly hope its just a wire unplugged or something..
Thanks.
Click to expand...
Click to collapse
hi firstly tell me what trouble shooting have you done and secondly what rom are you on is it stock or custom
kallum7 said:
hi firstly tell me what trouble shooting have you done and secondly what rom are you on is it stock or custom
Click to expand...
Click to collapse
I was on a Custom rom i forgot the name but i think it was Tuga its been a while since i last used the phone due to the issue. But the touch screen didn't work in recovery either.
Rexee said:
I was on a Custom rom i forgot the name but i think it was Tuga its been a while since i last used the phone due to the issue. But the touch screen didn't work in recovery either.
Click to expand...
Click to collapse
please follow this https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 and when it says it is only for hard bricks a=only still use it
Rexee said:
Hello, so i had my OnePlus one for a while and just recently i dropped it lucky the screen didn't crack and opens up just fine but the touch stopped working is there a fix for this? And how do i go about it.. I'm currently in Egypt so there isn't really any replacements and anyone who knows much about this device to be able to repair it at a decent price. I would like to fix it on my own, and i honestly hope its just a wire unplugged or something..
Thanks.
Click to expand...
Click to collapse
If you're screen stopped working after dropping it, it is most likely damaged. Dropping it will not cause any rom to malfunction and stop touch from working. It may be a loose connection, or if you got the device used from somewhere, the screen may have once been replaced and the replacement may not be as good as the original (which by no means was perfect either).
It happened to me. Open your opo, disconnect and then reconnect the screen.