as said above. my 4 soft buttons backlight are always on even when i shut off the phone.
im using arhd 6.8.0. when phone is off, a dim light is shown in the soft buttons. when i first installed the rom its very smooth. i tried hard resetting the phone but it still doesnt fix the problem.
its very annoying as it drains the battery even when phone is off. sometimes the backlight flickers adjusting the intensity of the light. help pls. thanks
rainversion13 said:
as said above. my 4 soft buttons backlight are always on even when i shut off the phone.
im using arhd 6.8.0. when phone is off, a dim light is shown in the soft buttons. when i first installed the rom its very smooth. i tried hard resetting the phone but it still doesnt fix the problem.
its very annoying as it drains the battery even when phone is off. sometimes the backlight flickers adjusting the intensity of the light. help pls. thanks
Click to expand...
Click to collapse
wats yo kernel? n hboot version n status?
------------------------------------------------
PRESS THE PRETTY "THANKS" BUTTON IF I HELPED
Sent from a shaked up HTC Sensation XE using xda premium
ashkan-khatar said:
wats yo kernel? n hboot version n status?
------------------------------------------------
PRESS THE PRETTY "THANKS" BUTTON IF I HELPED
Sent from a shaked up HTC Sensation XE using xda premium
Click to expand...
Click to collapse
im using sebastianFM kernel and 1.27 hboot. do you think if i backup to official ics, would it fix the problem.
help pls. thanks
up
rainversion13 said:
im using sebastianFM kernel and 1.27 hboot. do you think if i backup to official ics, would it fix the problem.
help pls. thanks
Click to expand...
Click to collapse
actually try a different kernel
see how it goes
but do first a nandroid backup just in case
rzr86 said:
actually try a different kernel
see how it goes
but do first a nandroid backup just in case
Click to expand...
Click to collapse
ok ill try that. but here's the thing. whatever app i use to turn off the backlight of the soft keys. it only dims it to the lowest level and doesnt completely turn it off.
when you look at your phone in a different angle, you can still see a very small light emitting in the soft keys part even when you shut off the phone. i tried reinserting the battery hut it doesnt fix the problem.
rainversion13 said:
ok ill try that. but here's the thing. whatever app i use to turn off the backlight of the soft keys. it only dims it to the lowest level and doesnt completely turn it off.
when you look at your phone in a different angle, you can still see a very small light emitting in the soft keys part even when you shut off the phone. i tried reinserting the battery hut it doesnt fix the problem.
Click to expand...
Click to collapse
Make a backup, do a full wipe in recovery, and reinstall the ROM you want fresh. If the propblem goes away then something is just screwy in your current ROm install and you may just have to set up a fresh install of it.
Skipjacks said:
Make a backup, do a full wipe in recovery, and reinstall the ROM you want fresh. If the propblem goes away then something is just screwy in your current ROm install and you may just have to set up a fresh install of it.
Click to expand...
Click to collapse
i hope your right that its just a rom problem because sometimes out of nowhere, all of a sudden when i shut off the phone, the backlights were completely gone(which is what i want to happen).
I'll post the results later. thanks.
by the way, when i used cpu spy it doesnt turn into deep sleep when the screen is off even if there is no apps running.
i left the phone for 6 hours screen off and charging. and only 8 minutes it turn into deep sleep state. the other remaining comes from my lowest speed which is 384. so im joping its just a rom problem.
rainversion13 said:
by the way, when i used cpu spy it doesnt turn into deep sleep when the screen is off even if there is no apps running.
i left the phone for 6 hours screen off and charging. and only 8 minutes it turn into deep sleep state. the other remaining comes from my lowest speed which is 384. so im joping its just a rom problem.
Click to expand...
Click to collapse
update! i tried installing another rom. it fixes one thing. when the phone is shut off, the backlight is completely gone. but when the phone is in sleep mode, it still has a very dim backlight on the 4 soft buttons. what seems to be the problem?
need help pls. anyone experiencing this same annoying issue?
rainversion13 said:
update! i tried installing another rom. it fixes one thing. when the phone is shut off, the backlight is completely gone. but when the phone is in sleep mode, it still has a very dim backlight on the 4 soft buttons. what seems to be the problem?
need help pls. anyone experiencing this same annoying issue?
Click to expand...
Click to collapse
Wait a minute...when you said the backlight stays on even when you shut off the phone I thought you meant like when you turn the screen off. Do you mean when you physically power off the device?
That's really screwy. If so, something is really REALLY messed up.
Try the following 3 things in this order from easiest to hardest.
1) Remove the SD card. Reboot the phone. See if the problem persists. If it goes away without the SD card, copy your files to a computer, format the SD card, and copy your files back. I give this a 10% chance of working but its quick to test it so why not try?
2) Do a full wipe. Flash a bone stock Sense ROM. Seen if the problem goes away. If it does, wipe again and install whatever you want.
3) Run a full ruu and return to completely stock. If the problem is still there your hardware is broken. If the problem goes away you will have to restart the rooting process. You will have to redo s off, redo superuser, etc. Then flat whatever ROM you want.
Try doing an full ruu back to bone stock. Reroot, and start over with a new ROM. You will have to go through the whole s off process again. But it might fix this. And form the sound of it you have somehow borked things that shouldn't have ever been touched.
Sent from my GT-P5110 using xda app-developers app
Skipjacks said:
Wait a minute...when you said the backlight stays on even when you shut off the phone I thought you meant like when you turn the screen off. Do you mean when you physically power off the device?
That's really screwy. If so, something is really REALLY messed up.
Try the following 3 things in this order from easiest to hardest.
1) Remove the SD card. Reboot the phone. See if the problem persists. If it goes away without the SD card, copy your files to a computer, format the SD card, and copy your files back. I give this a 10% chance of working but its quick to test it so why not try?
2) Do a full wipe. Flash a bone stock Sense ROM. Seen if the problem goes away. If it does, wipe again and install whatever you want.
3) Run a full ruu and return to completely stock. If the problem is still there your hardware is broken. If the problem goes away you will have to restart the rooting process. You will have to redo s off, redo superuser, etc. Then flat whatever ROM you want.
Try doing an full ruu back to bone stock. Reroot, and start over with a new ROM. You will have to go through the whole s off process again. But it might fix this. And form the sound of it you have somehow borked things that shouldn't have ever been touched.
Sent from my GT-P5110 using xda app-developers app
Click to expand...
Click to collapse
Well, when the phone is off, the backlight is already gone. So its ok now. The CPU spy also states that when I turn my screen off, it turns into deep sleep. That one is fixed too. But when I charge the phone and let my screen off, it doesn't go into deep sleep but it consumes the least frequency of the processor which is 192mhz I don't know if that is normal.
I think I have a hardware problem since I sent my phone to replace its microphone flex which includes the lights coming from the buttons. I'll try to send it back to the center since it still has warranty.
Thanks. I'll update you.
rainversion13 said:
Well, when the phone is off, the backlight is already gone. So its ok now. The CPU spy also states that when I turn my screen off, it turns into deep sleep. That one is fixed too. But when I charge the phone and let my screen off, it doesn't go into deep sleep but it consumes the least frequency of the processor which is 192mhz I don't know if that is normal.
I think I have a hardware problem since I sent my phone to replace its microphone flex which includes the lights coming from the buttons. I'll try to send it back to the center since it still has warranty.
Thanks. I'll update you.
Click to expand...
Click to collapse
Any update on this issue? My wife's phone has many screen problems, but one of the primary symptoms is that the backlight is almost always on in the lower left corner, even after removing the battery and reinserting it, before booting. When I charge it, the backlight gets brighter and I see dark pixelation across the screen. At times the screen has crapped out completely, and it usually appears dark, has some light flickering, blotching, and vertical lines. I'm wondering whether this is an LCD/backlight issue at all or another hardware issue. Don't want to buy an LCD if that won't fix anything. Some LCD/digitizer assemblies have a mic cable, though, so I'm curious about what you found out about that. Thanks
Related
turned on the tablet and the screen appeared red color on the place of black. what can be reason for this? or is there any way to make it as it was before?
zgogilava said:
turned on the tablet and the screen appeared red color on the place of black. what can be reason for this? or is there any way to make it as it was before?
Click to expand...
Click to collapse
Not only is some places red instead of black, a number are also blue instead of white.
Perhaps the GPU/SOC is overheating or going bad? I really doubt a cable to the LCD is put in properly or loose, simply because it would be a consistent color (either red/blue/green) that would be off. Try playing an intensive game and seeing what happens. I'd be willing to bet it will either crash or something similar. Probably time to do an RMA.....
darkhawkff said:
Not only is some places red instead of black, a number are also blue instead of white.
Perhaps the GPU/SOC is overheating or going bad? I really doubt a cable to the LCD is put in properly or loose, simply because it would be a consistent color (either red/blue/green) that would be off. Try playing an intensive game and seeing what happens. I'd be willing to bet it will either crash or something similar. Probably time to do an RMA.....
Click to expand...
Click to collapse
reset to factory settings, and after some time turned it on. everything was ok.
that often happens on computors anyways when you overclock the gpu/cpu too much so maby if you keep the voltages low it wont happen again
zgogilava said:
reset to factory settings, and after some time turned it on. everything was ok.
Click to expand...
Click to collapse
hi how exactly you do to reset and wait few hours before turn on? i got the same problem and nothing work so far. thank you
emanoy said:
hi how exactly you do to reset and wait few hours before turn on? i got the same problem and nothing work so far. thank you
Click to expand...
Click to collapse
Boot on recovery (CWM) hold Power + Volume(-)... etc. And do a "factory reset/wipe".
But if the problem comes from an OC heat, I think you will have to install also a rom/kernel without OC. Then wait some hours to start it up.
hope it helps.
Hi,
I had a G2X which had its LCD screen and the touchscreen digitizer broken about 8 months ago. At that time, the phone would turn on, I could see some colors and through the broken LCD screen I could see that the phone would also go to recovery (I was trying to wipe data if I wanted to sell it for parts).
Now, I tried to turn it on (after charging battery) nothing happened. I could feel the phone and the battery get hot but no screen flickering or anything.
I decided if there is something I can do or try before I just toss it out.
So obviously, I don't have a screen to see whats going on and the only indicators that phone responds is the LCD backlight coming on.
I tried to recover via : One Click ClockworkMod (http://forum.xda-developers.com/showthread.php?t=1056847). Computer indicated everything went smooth. However screen wouldn't still show any signs of life.
I followed up by searching the forum. Found this: http://forum.xda-developers.com/showthread.php?t=2015830, and proceeded to do what was prescribed here: http://forum.xda-developers.com/showthread.php?t=1590523
No life in the phone once again.
I finally tried : http://forum.xda-developers.com/showthread.php?t=1248644 (Computer indicates it was a success, the broken LCD screen was on while the "magic" was happening, followed by 2 flashes (each lasting about 2 seconds) and then nothing. )
I tried to turn it on with battery in: nothing happens.
However when I take the battery out and plug in the USB into the computer, Press Vol- and Power simultaneously: the screen comes on for about 5 seconds then turns off, followed by a single flash of the home and menu keys.
I'm not sure if its a software issue or a hardware issue. I would like an expert opinion from people here in the forum. Should I purchase a replacement screen and a digitizer? to try and see what happens next? or should I just stop tinkering with things I dont fully understand and get rid of the device?
Thanks for any advice or comments
cellphoneman said:
Hi,
I had a G2X which had its LCD screen and the touchscreen digitizer broken about 8 months ago. At that time, the phone would turn on, I could see some colors and through the broken LCD screen I could see that the phone would also go to recovery (I was trying to wipe data if I wanted to sell it for parts).
Now, I tried to turn it on (after charging battery) nothing happened. I could feel the phone and the battery get hot but no screen flickering or anything.
I decided if there is something I can do or try before I just toss it out.
So obviously, I don't have a screen to see whats going on and the only indicators that phone responds is the LCD backlight coming on.
I tried to recover via : One Click ClockworkMod (http://forum.xda-developers.com/showthread.php?t=1056847). Computer indicated everything went smooth. However screen wouldn't still show any signs of life.
I followed up by searching the forum. Found this: http://forum.xda-developers.com/showthread.php?t=2015830, and proceeded to do what was prescribed here: http://forum.xda-developers.com/showthread.php?t=1590523
No life in the phone once again.
I finally tried : http://forum.xda-developers.com/showthread.php?t=1248644 (Computer indicates it was a success, the broken LCD screen was on while the "magic" was happening, followed by 2 flashes (each lasting about 2 seconds) and then nothing. )
I tried to turn it on with battery in: nothing happens.
However when I take the battery out and plug in the USB into the computer, Press Vol- and Power simultaneously: the screen comes on for about 5 seconds then turns off, followed by a single flash of the home and menu keys.
I'm not sure if its a software issue or a hardware issue. I would like an expert opinion from people here in the forum. Should I purchase a replacement screen and a digitizer? to try and see what happens next? or should I just stop tinkering with things I dont fully understand and get rid of the device?
Thanks for any advice or comments
Click to expand...
Click to collapse
Any help or advice would be greatly appreciated.
ya
your screen is shot
replace
G2x-CM7 Nightly 11/25/12 Build, Trinity ELP Kernel
Thank you for the response.
Do you think that would suffice? Or additional measures would be required?
Thanks once again.
Sent from my Nexus 4 using xda app-developers app
cellphoneman said:
Thank you for the response.
Do you think that would suffice? Or additional measures would be required?
Thanks once again.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Well if it were me, your going to have to open it up anyways, so pull up a disassemble tutorial video on YouTube, open it up and give everything an inspection for any physical damage.
I'd use a magnifying glass and look for any signs of hairline cracks in the motherboard.
It really does soumd like the screen finally died and that the motherboard is functioning.
G2x-CM7 Nightly 12/09/12 Build, Trinity ELP Kernel
So my phone has been fine until yesterday. Everything seems to be working except the screen won't show anything. I can feel the vibration from unlocking as if it was showing and I can still hear sounds and the buttons at the bottom and the keyboard all light up but nothing shows on the screen. If I take the battery out and put it back in most of the time it fixes the issue. Sometimes it doesn't even show the splash screen though. Its kind of hit or miss.
I replaced the ROM I had on and put the original battery back in (I have an extended battery) to make sure it was neither of those issues. My guess is something is going out on it. Anyone else have this happen/have a fix?
erebus860 said:
So my phone has been fine until yesterday. Everything seems to be working except the screen won't show anything. I can feel the vibration from unlocking as if it was showing and I can still hear sounds and the buttons at the bottom and the keyboard all light up but nothing shows on the screen. If I take the battery out and put it back in most of the time it fixes the issue. Sometimes it doesn't even show the splash screen though. Its kind of hit or miss.
I replaced the ROM I had on and put the original battery back in (I have an extended battery) to make sure it was neither of those issues. My guess is something is going out on it. Anyone else have this happen/have a fix?
Click to expand...
Click to collapse
Also forgot to mention this doesn't happen if I boot into recovery.
Are you using a custom ROM? If it doesn't happen on recovery then sounds like a kernel issue to me... Since the only difference between recovery and normal mode is the kernel they're using is different.
Riyal said:
Are you using a custom ROM? If it doesn't happen on recovery then sounds like a kernel issue to me... Since the only difference between recovery and normal mode is the kernel they're using is different.
Click to expand...
Click to collapse
I am, yeah. I ended up going into recovery and formatting everything, it was still acting up for a bit after that but then started working fine. My guess is I had some sort of corruption. Thanks
Same thing was happening to me when I went ham on my kernel tweaking the hell out of it :silly:
Well I mostly fixed it. Still happens randomly when sliding out. If I slowly slide in or out again that fixes it though. Still, kinda of a weird problem.
Sent from my myTouch_4G_Slide using xda app-developers app
Hi. I have been running pacman v22.0.1 for quite some time now and I could quite easily make and receive calls with no problems, the rom was fast and battery life was great. But quite recently, I received a call and answered it spoke but when it came to ending it, I couldn't get the screen to turn on and all that happened was the button backlights were flashing like mad! So I left it for a while and came back to the phone which had dropped from 84% battery to 41% and it was running very slow. Later when I tried making a call, I couldn't hear anything and I couldn't end the call which led to a charge of £5 which isn't too much money I'm not too fussed with that. But I switched to another rom then wiped everything and flashed pacman again but still had the same problem. Is there anybody who is facing the same problem or has a solution? I have tried on 4 different 4.2 roms now and have experienced the same problem with all.
Just uploaded a very, very long log cat if you are a dev or have knowledge of logs, please read!
Problem solved, it was my screen protector which was covering my proximity sensor and jelly beans behaviour with the proximity sensor caused it to stay off. When buying a screen protector always make sure it has a hole or gap of some sort for the proximity sensor. The bug in the log cat was something else which was fixed by a build.prop tweak.
My radio is 3831.19.00.110
ifti786 said:
I couldn't get the screen to turn on and all that happened was the button backlights were flashing like mad! So I left it for a while and came back to the phone which had dropped from 84% battery to 41% and it was running very slow. Later when I tried making a call, I couldn't hear anything and I couldn't end the call which led to a charge of £5 which isn't too much money I'm not too fussed with that.
Click to expand...
Click to collapse
Were you rapidly pressing the power button? Occasionally, I find my phone lags when turning the screen on, I press the power button once and the buttons light up, then I don't press it again and wait for the screen to turn on. If it is pressed a second time, it means "turn the screen off again", so you never see it turn on.
paulie-uk said:
Were you rapidly pressing the power button? Occasionally, I find my phone lags when turning the screen on, I press the power button once and the buttons light up, then I don't press it again and wait for the screen to turn on. If it is pressed a second time, it means "turn the screen off again", so you never see it turn on.
Click to expand...
Click to collapse
That could just be it: the reason for my problem is my impatience! Still need to check though...
No, that didn't fix it. I think it might have something to do with my proximity sensor because on vipersaga, it used to turn the screen on when I moved my phone from my ear but now it doesn't so I have to press the power button.
Also have the same problem on jelly bean fire
Sent from my HTC Desire S
Please help because I really want Jelly Bean 4.2 but at the current moment, it looks like my desire s is incapable of running it!
I flashed the ROM this morning and everything is well except of GPS (or is it just invisible?) and no weather on the cLock widget (btw any ideas here anybody?). I had issues of the screen keeping black with backlightes hardware buttons (and some others) with v21. But I never tried to use the phone for calling somebody with that, cause it was merely a stage facing the best ROM for me.
Did you do full wipe and Dalvik cache wipe? I found it is very useful to do so, cause it eliminates uncertainties the kind of "where does this come from?".
sanilii said:
I flashed the ROM this morning and everything is well except of GPS (or is it just invisible?) and no weather on the cLock widget (btw any ideas here anybody?). I had issues of the screen keeping black with backlightes hardware buttons (and some others) with v21. But I never tried to use the phone for calling somebody with that, cause it was merely a stage facing the best ROM for me.
Did you do full wipe and Dalvik cache wipe? I found it is very useful to do so, cause it eliminates uncertainties the kind of "where does this come from?".
Click to expand...
Click to collapse
Wipe all partitions except sd card AMD done this on pacman v22.0.1, JellyFireBean, JellyTime, flinny cm10.1 and AOKP redefined. I have just flashed a new radio and will check if that fixed it
Flashing a new radio did not fix the problem please somebody help!
ifti786 said:
Flashing a new radio did not fix the problem please somebody help!
Click to expand...
Click to collapse
I've got the same problem. My screen won't turn on after I move the phone away from my head after a call, altho I can turn it on with the powerbutton somehow. Happens on all JB ROMs for me aswell.
I tried Proximity Sensor Finder app from play store and it says 9cm when theres nothing infront of the sensor, then goes to 0cm when there is something, but doesn't go back to 9cm when the sensor is free again. It only goes back to 0cm when I restart the app.
I don't know whats the problem, but I think its software related.
Is the s2w turned on? If so, it could be the problem. BTW, the problem with black screen but capacitive button lights turned on, also have I. I see it, when I turn off the screen and try to turn it on after 5-10 seconds. But waiting a little helps.
Running Pacman 22.0.1
NVardan said:
Is the s2w turned on? If so, it could be the problem. BTW, the problem with black screen but capacitive button lights turned on, also have I. I see it, when I turn off the screen and try to turn it on after 5-10 seconds. But waiting a little helps.
Running Pacman 22.0.1
Click to expand...
Click to collapse
S2w is off, tried waiting too and that didn't help. I took a log cat of what happened and can upload it if wanted. My friend is taking a look at it for me to see whether there's a bug. It could have something to do with the build.prop.
ifti786 said:
S2w is off, tried waiting too and that didn't help. I took a log cat of what happened and can upload it if wanted. My friend is taking a look at it for me to see whether there's a bug. It could have something to do with the build.prop.
Click to expand...
Click to collapse
Maybe you should upload the logcat in the PACman thread.
Ok will do that now
Sent from my HTC Desire S
NVardan said:
Maybe you should upload the logcat in the PACman thread.
Click to expand...
Click to collapse
The log cat is waaaaaaay too long, I've sent you a message, anybody else who wants the log cat, ill pm you.
ifti786 said:
The log cat is waaaaaaay too long, I've sent you a message, anybody else who wants the log cat, ill pm you.
Click to expand...
Click to collapse
Unfortunately I am NOT a developer so I can't help you.
You must copy-paste your logcat in a .txt file and upload it in the PACman thread.
Sent from my Desire S using Tapatalk 2
I'm having the same problem with JellyFireBean v2. I ended up leaving a few voicemails without knowing, and it cost me 10$ from abroad...
I installed an app that gives information about all the sensors (sensor kinetics). When I start the test it shows a distance of 9cm, then I put my hand over the phone and it shows 0 cm, but then I remove my hand and it stays at 0, exactly like when I make a call.
sarcome said:
I'm having the same problem with JellyFireBean v2. I ended up leaving a few voicemails without knowing, and it cost me 10$ from abroad...
I installed an app that gives information about all the sensors (sensor kinetics). When I start the test it shows a distance of 9cm, then I put my hand over the phone and it shows 0 cm, but then I remove my hand and it stays at 0, exactly like when I make a call.
Click to expand...
Click to collapse
Right, I've just had a look through the logcat and i've found a bug. I'm going to try some build.prop tweaks and see what the results are. I will let you know but please bear in mind that it might take some time as I am having some very important exams coming up so I'm going to be revising in most of my free time.
sarcome said:
I'm having the same problem with JellyFireBean v2. I ended up leaving a few voicemails without knowing, and it cost me 10$ from abroad...
I installed an app that gives information about all the sensors (sensor kinetics). When I start the test it shows a distance of 9cm, then I put my hand over the phone and it shows 0 cm, but then I remove my hand and it stays at 0, exactly like when I make a call.
Click to expand...
Click to collapse
Do you have a screen protector on your phone by any chance?
If this is a duplicate issue, my apologies. My husband's phone has locked and the touch screen is unresponsive. Pulling the battery and restarting the phone does not correct this issue. It is locked when the phone turns on. He cannot answer calls. The only way to turn the phone off is by removing the battery. Help?
maruba79 said:
If this is a duplicate issue, my apologies. My husband's phone has locked and the touch screen is unresponsive. Pulling the battery and restarting the phone does not correct this issue. It is locked when the phone turns on. He cannot answer calls. The only way to turn the phone off is by removing the battery. Help?
Click to expand...
Click to collapse
Has he modified the software in anyway? Has he installed a custom rom or a different radio or the phone is fully stock?
glevitan said:
Has he modified the software in anyway? Has he installed a custom rom or a different radio or the phone is fully stock?
Click to expand...
Click to collapse
Fully stock. I'm thinking he may have dropped it and won't fess up....it was working intermittently, but now it has been frozen for a day and a half, and I'm at a loss.
maruba79 said:
Fully stock. I'm thinking he may have dropped it and won't fess up....it was working intermittently, but now it has been frozen for a day and a half, and I'm at a loss.
Click to expand...
Click to collapse
Then it seems to be a hardware issue more than a software one. However, you can try to re install the stock rom and see what happens. You can go to hboot and do a factory reset, you will lose data but it will install everything again.
Do you know how to do that?..
Power off the device
Press volume down + power
When you get to the white screen with androids, you can navigate with the volume rocker and choose with the power volume. Choose to factory reset the device and see what happens.
glevitan said:
Then it seems to be a hardware issue more than a software one. However, you can try to re install the stock rom and see what happens. You can go to hboot and do a factory reset, you will lose data but it will install everything again.
Do you know how to do that?..
Power off the device
Press volume down + power
When you get to the white screen with androids, you can navigate with the volume rocker and choose with the power volume. Choose to factory reset the device and see what happens.
Click to expand...
Click to collapse
Thank you so much! I'm doing that now! I have this same phone (this is my 2nd one) and have no problems. I love my phone...but I also take care of it!
So that didn't change anything except the wallpaper. Am I pretty well SOL?
maruba79 said:
So that didn't change anything except the wallpaper. Am I pretty well SOL?
Click to expand...
Click to collapse
it seems so. Maybe something got broken...that is why it sounded like a software issue. I am sorry but I guess that your best bet is a service centre
Same thing happened to mine, never dropped it either. I had to replace the digitizer which was a pain.
nsmith4 said:
Same thing happened to mine, never dropped it either. I had to replace the digitizer which was a pain.
Click to expand...
Click to collapse
The hubs took it by a repair shop this morning. The digitizer had come unplugged. :victory: