Sometimes the screen of my Galaxy Nexus freaks out; it behaves as if I'm touching the screen repeatedly while I'm not. It does not happen a lot, but I think it mostly occurs after pulling down the notification menu and touching a notification message there.
I have tried to reproduce this behavior (camera ready so I can video the screen of my GN), so far no luck. Anybody else experienced this?
Of course, as soon as I'm in bed and have put my camera away I experienced the issue again.
Will try again this evening.
That really sounds like a faulty screen I'm sorry to say. I had a similar issue with my HD2 two years ago, had to send it for replacement.
Hmmm I hope not. Since it's very hard to reproduce I doubt I can prove it in order to get a replacement.
It happens to me only when I'm charging the device. Do you use custom ROM? I'm suspecting that right now.
Nope, stock rom. I haven't even rooted it yet.
Finally caught it on video! It's not very focused but it clearly shows my problem.
http://www.youtube.com/watch?v=Z5_tUcosrtQ&feature=youtu.be
I don't think its a hardware problem because I'm mostly experiencing this problem at home. Today at work I used the phone the whole day without encountering this behavior. I'm 15 minutes home and the problem pops up again. Difference? At home the phone is connected to my WiFi. Any thoughts?
Does it happen when you're not holding the phone? I've had anomalies happen before when the phone is on table and not in my hand before. Or could be faulty driver for touchscreen chip.
Sent from my Galaxy Nexus using xda premium
@rbiter said:
Does it happen when you're not holding the phone? I've had anomalies happen before when the phone is on table and not in my hand before. Or could be faulty driver for touchscreen chip.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
No, it does not happen spontaneously. I happens when I'm using the phone.
I've read some threads for other devices concerning exact the same issue. There were opinions that it could be due to the static charge that gathers on the sensor.
Possible solution could be:
1) discharge the phone
2) remove the battery and wait for about 10-12 hours.
Try it may be it ill help you.
stopdogs said:
I've read some threads for other devices concerning exact the same issue. There were opinions that it could be due to the static charge that gathers on the sensor.
Possible solution could be:
1) discharge the phone
2) remove the battery and wait for about 10-12 hours.
Try it may be it ill help you.
Click to expand...
Click to collapse
Sounds like a longshot, but I will try it anyway. Thanks!
Reflash the phone with stock images and do a wipe if it still persits exchange it asap
Sent from my Galaxy Nexus using Tapatalk
noobdeagle said:
Reflash the phone with stock images and do a wipe if it still persits exchange it asap
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
The phone has a stock image. Also it's not rooted and I haven't touched the bootloader either.
Related
Hello, I have a CDMA GNex running build 36. At random points through the day I find my screen turning on because my phone thinks it is changing. The odd thing is its is not even plugged in. I just was wondering if you guys think it is a hardware issue or if it's just my ROM or Kernel. Any Tips on how to fix this issue are appreciated.
Thanks
Sent from my Galaxy Nexus using XDA
*UPDATE* Found that a battery pull solved the problem on my phone (or at least for now), never reverted back to stock. I had it charge for 20 or so minutes then unplugged the charger and it seemed to recognize it was no longer charging, thanks for the help again guys. If at first the battery pull doesn't work, wait a day and try it again (i pulled it 2 different days)
Any takers? If it is a hardware issue i want to fix it ASAP before my warranty is up!
I have it too, wipe doesn't help. I will try flash a stock rom..
dymex said:
I have it too, wipe doesn't help. I will try flash a stock rom..
Click to expand...
Click to collapse
i've found myself at 99% when it's plugged in and it won't charge anymore. not sure if it's a hardware thing or a rom thing. it's intermittent though... haven't found a fix yet...
Please share what you find out after you revert back!
Sent from my Galaxy Nexus using XDA
When the screen comes on, does it say "Charging"? I am using Text Plus for my messaging, and I had to uncheck a setting to turn on the screen when I received a notification. Are you sure it isn't an app that is turning the screen on?
tokuzumi said:
When the screen comes on, does it say "Charging"? I am using Text Plus for my messaging, and I had to uncheck a setting to turn on the screen when I received a notification. Are you sure it isn't an app that is turning the screen on?
Click to expand...
Click to collapse
Absolutely positive, when going into the battery stats, on the lock screen, and the icon on the top all show that the phone is charging, I seemed to notice it after I flashed the paranoid android ROM. Since then I have reverted back to AOKP and the issue is still there. I may restore stock, and if it persists I'll delete superuser APK. and run it over to Verizon while I still have the warranty. If anyone can tell me if is a hardware or software problem it would help me figure out the problem.
Sent from my Galaxy Nexus using XDA
Hydera5 said:
Absolutely positive, when going into the battery stats, on the lock screen, and the icon on the top all show that the phone is charging, I seemed to notice it after I flashed the paranoid android ROM. Since then I have reverted back to AOKP and the issue is still there. I may restore stock, and if it persists I'll delete superuser APK. and run it over to Verizon while I still have the warranty. If anyone can tell me if is a hardware or software problem it would help me figure out the problem.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I've seen a similar issue where the device will not charge while connected to power. A reboot will resolve the issue but, for obvious reasons, this is less than optimal.
Is there any way to identify what application (since this only changed recently) might be causing the issue?
Thanks!
M
Oh come on!! Don't people use the search function anymore!?!? See http://forum.xda-developers.com/showthread.php?t=1676711 or the other 20-30 threads regarding this issue.
Basically, you need to replace your USB charging board, and Samsung will claim water damage and make you pay for the whole repair...
Let's say for just a second that I didn't run any searches (which I did, not only here but Google as well) and have misinterpreted issue (where the device stops charging after a few moments, but only when the OS is running) and it is actually a hardware issue, how does being condescending help or encourage others to post here?
Sorry, I'm not targeting you. I'm just not okay with people creating new threads instead of contributing in existing threads regarding the exact same issues.
MJMcMahon said:
Let's say for just a second that I didn't run any searches (which I did, not only here but Google as well) and have misinterpreted issue (where the device stops charging after a few moments, but only when the OS is running) and it is actually a hardware issue, how does being condescending help or encourage others to post here?
Click to expand...
Click to collapse
Problem solved (sorta) i called customer care and they said that it was a "common problem" and usually was a result of using a charger other than the one that came with the phone... Long story short they are sending me a new one, new post here if you are still in the helping mood (;
http://forum.xda-developers.com/showthread.php?p=26729008#post26729008
This issue just started happening on my Galaxy Nexus last week. I just called Verizon and explained what was going. I told the rep I hard reset the phone and it still occurs. He said it was a known issue and overnight ed a replacement. If you're having this issue Verizon seems very aware of it.
I had the same issue .... for me it went away with the newer CM builds [VZW].
Hydera5 said:
Hello, I have a CDMA GNex running build 36. At random points through the day I find my screen turning on because my phone thinks it is changing. The odd thing is its is not even plugged in. I just was wondering if you guys think it is a hardware issue or if it's just my ROM or Kernel. Any Tips on how to fix this issue are appreciated.
Thanks
Sent from my Galaxy Nexus using XDA
*UPDATE* Found that a battery pull solved the problem on my phone (or at least for now), never reverted back to stock. I had it charge for 20 or so minutes then unplugged the charger and it seemed to recognize it was no longer charging, thanks for the help again guys. If at first the battery pull doesn't work, wait a day and try it again (i pulled it 2 different days)
Click to expand...
Click to collapse
Mine just started doing this yesterday. Tried a couple of battery pulls but it still seems to think it's constantly charging. When it starts flopping back and forth between charging and discharging the phone becomes unusable. I'm just wondering if the battery pull was a permanent fix for you or did you have to send it in eventually?
hi everyone
last night i was just using my gnexus as usual, then all of a sudden the device just freezes and then proceed to emit a loud noise, like a "buuuzzz" nonstop..i coundt turn it off through the pwer button so i decided to remove the battery..reinsert it, and then can't turn it on again..
tried to conect to pc, the device is not recognized..
cant power on with the charger plugged in..tried another charger, no success
meanwhile i'm trying to put the battery on an external charger to see if its an issue with the battery itself..
i'm starting to think that my nexus is dead..
please if someone cound help me, it would be much appreciated. thx in advance!!!
sorry for my broken english, i'm from brazil
So it doesn't vibrate or anything? You can't get into bootloader? No Odin?
If no, then try OMAP flashing. I never did it, so I don't quite know about it, but apparently this saved some good amount of people with the hard bricking.
Do you have the ability to give it a try with another battery?
Manatee Burger said:
Do you have the ability to give it a try with another battery?
Click to expand...
Click to collapse
Not in the moment, but the battery just runs fine with an external charger. But i'll try to find another one available..
The thing that really bothers me is the no response when plugged to the pc. Am i mistaken, or it should beep when connected through usb(without the battery)?
have the device for TWO months..wow...
kyokeun1234 said:
So it doesn't vibrate or anything? You can't get into bootloader? No Odin?
If no, then try OMAP flashing. I never did it, so I don't quite know about it, but apparently this saved some good amount of people with the hard bricking.
Click to expand...
Click to collapse
no vibration at all
tried to get into bootloader, again no success
I had Similar issue with another phone. It was hardware related. Were you overclocked? Running custom Rom?
Are you under warranty?
Sent from my Galaxy Nexus using xda app-developers app
http://forum.xda-developers.com/showthread.php?t=1760787
This is relevant to your interests...
Yeah I recently had something similar happen. Taking the battery out and plugging it into the computer did the trick and it booted back up. Something to try anyway.
gagb1967 said:
I had Similar issue with another phone. It was hardware related. Were you overclocked? Running custom Rom?
Are you under warranty?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Never messed with the clockspeed, however yes i'm using a custom Rom. Actually i've been using this for 3 days, no problems whatsoever. until now..do u think that's the cause? The phone is literally dead by now. Thats REALLY depressing. and the loud noise when it froze before it completely stopped working.. unbelievable
Jubakuba said:
http://forum.xda-developers.com/showthread.php?t=1760787
This is relevant to your interests...
Click to expand...
Click to collapse
thanks for the link, although nothing happens when i plug the phone to the computer.
If it's dead go ahead and exchange of in warranty. The buzzing sound is a chip frying.
Sent from my Galaxy Nexus using xda app-developers app
thx for the reply everyone!
So the strangest thing happened. i left the battery in the external charger for a full day..when a took it off and put it in the phone, pressed the pwr button with no sucess...nothing again...tried a couple of times..and yet nothing
five minutes later ,on a last ditch effort, pushed the pwer button once more and..FINALLY ! the thing wakes up..booted normaly, like nothing happened.
today when the battery runs out again(on about 2 %) i turned it off and connected the usb cable to charge in my work's pc..now again the same thing happens, phone is dead again. tried with 2 different cables..battery is already in the external charger, gonna try again tomorrow..
starting to think the problem is in the usb connector or the battery itself..but at least my biggest fear(fried phone) seems less likely
This link might (or might not) have relevance to your situation. Thought I'd post it on the chance that it does, and because the information seems unique and unavailable elsewhere.
http://forum.xda-developers.com/showthread.php?t=1756097
Real Cause of The Galaxy Nexus turning itself off at random
strumcat said:
This link might (or might not) have relevance to your situation. Thought I'd post it on the chance that it does, and because the information seems unique and unavailable elsewhere.
http://forum.xda-developers.com/showthread.php?t=1756097
Real Cause of The Galaxy Nexus turning itself off at random
Click to expand...
Click to collapse
thx for the link mate
Yeah, this really apears to be the most logical source of the issue..such a shame, i was really having a great time with this phone.
Re-inserted the battery fully charged and it's not turning on, tried 50x times alrealdy.
gonna call samsung later and see what will unfold..i'´ll post an update as soon as this situation is sorted out.
I recently bought a new note 2, and everything was good and I love it!
But yesterday I was on the phone to a friend and initially I tried putting him on speaker phone, but the screen wouldn't turn on, only the soft touch keys at the bottom lit up. I thought nothing of it and continued my phone call.
It wasn't until he hung up I noticed i still coudn't the damn thing on. So i removed the battery and re inserted it. Here's where things get interesting though, now whenever i try to power it up, i get a little red light in my proximity sensor (i think) that flashes for about half a second.
I've tried soft rest, which does the same thing ( makes the proximity sensor light up for half a second)
Hard reset which does the same thing.
I haven't rooted the phone or anything. Luckily its still under manufacture warranty and I'll get samsung to have a look at it, but any thoughts on what it could be?
soljakid said:
I recently bought a new note 2, and everything was good and I love it!
But yesterday I was on the phone to a friend and initially I tried putting him on speaker phone, but the screen wouldn't turn on, only the soft touch keys at the bottom lit up. I thought nothing of it and continued my phone call.
It wasn't until he hung up I noticed i still coudn't the damn thing on. So i removed the battery and re inserted it. Here's where things get interesting though, now whenever i try to power it up, i get a little red light in my proximity sensor (i think) that flashes for about half a second.
I've tried soft rest, which does the same thing ( makes the proximity sensor light up for half a second)
Hard reset which does the same thing.
I haven't rooted the phone or anything. Luckily its still under manufacture warranty and I'll get samsung to have a look at it, but any thoughts on what it could be?
Click to expand...
Click to collapse
Well, I can tell the that the red light is normal, I get that too and its just because its booting up, when you turn your phone on, what happens exactly?
Thanks for the reply. When I press the power button, around a second later the red light blips for half a second and turns off, but the OS doesn't boot up and nothing happens.
soljakid said:
Thanks for the reply. When I press the power button, around a second later the red light blips for half a second and turns off, but the OS doesn't boot up and nothing happens.
Click to expand...
Click to collapse
Hmmm, This is the first time I heard of a situation like this... Try searching on the site or probably wait for someone to reply....
http://forum.xda-developers.com/showthread.php?t=2065626
Maybe you too.... Sorry that sucks.
This PSA was sent Flow style from my Note 2 N-7100
Now i am really getting worriyng about this, does note2 has started SDS ?
atleast 3-4 cases are reported with same symptoms.
Anyway can you tell
You were on which ROM when this happened?
Are you getting to reboot in recovery/download mod?
@dingokevin I had a read over the thread you linked, and I fear the worst has happened to my note 2. This seems like a serious issue and even a flaw with the motherboard perhaps? Thank the lord it is still under warranty. R.I.P old friend.
@dr.ketan Im not sure what SDS stands for... Yeah I was running stock touchwiz 4.1.1 I think. No modifications and no root what so ever, and nope :/ I tried holding down volume down key + home button + power but no cigar, just the proximity light flashes briefly.
SDS - sudden death syndrome
And if you are unable to get into download/recovery mode then nothing can be done except send it to service station. it highly suggests sudden death which is very known issue for SGS3.
Replying to your query at other thread, you will get motherboard replacement if it is under warranty.
Ahh thats probably whats happened then. Thanks guys, I'll send it off to samsung and have a word or two with them to see why this is happening to many people!
If possible share outcome here too.
Regards
dr.ketan said:
If possible share outcome here too.
Regards
Click to expand...
Click to collapse
Yeah defiantly will do. (Y) cheers
Same thing happened to my friends note 2 and some other people. Is sds happening to the note 2 also now ?? I am very worried
Sent from my GT-N7100 using xda premium
Or could be that screen was damaged somehow.
Sds bug generally happened due to long time in sleep mode.
It happened to him during call
Sent from my GT-N7100 using xda app-developers app
UtkarshGupta said:
Or could be that screen was damaged somehow.
Sds bug generally happened due to long time in sleep mode.
It happened to him during call
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
I was just reading up on some possible causes here on XDA with peoples S3's and someone suggested corrupted NAND memory.. I think this maybe the case because before the phone call I had installed Gangster Rio (which i honestly did purchase off the play store, hand on heart) and after playing it for a while decided to un install it and get a refund. Could me doing this have caused the NAND memory to corrupt? The game is a pretty large file...
No imao no
Sent from my GT-N7100 using xda app-developers app
UtkarshGupta said:
No imao no
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
I highly doubt it was screen damage, imho. I only received the phone last friday and have been cradling it like a fragile little baby, Its never been out of my sight lool.
Maybe i just got really unlucky and ended up with a faulty device.
If screen fault then in such case usually you can hear boot up sound. It seems your case very well fits to sds category only.
Sent from my GT-N7100 using xda premium
dr.ketan said:
If screen fault then in such case usually you can hear boot up sound. It seems your case very well fits to sds category only.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Thank you good Dr. =P
dr.ketan said:
If possible share outcome here too.
Regards
Click to expand...
Click to collapse
Hi Guys,
Got up this morning having left my Note 2 turned on and on charge overnight to discover this same fault -
slow flashing Red light and phone totally dead.
Unable to do anything to rectify the situation.
Still under warranty of course, phone only released in October 2012.
Is this a fault with the phone which necessitates replacement or just a battery problem?
Would be grateful for any advice / guidance / help.
Thanks,
Mike Longley.
MJLONGLEY said:
Hi Guys,
Got up this morning having left my Note 2 turned on and on charge overnight to discover this same fault -
slow flashing Red light and phone totally dead.
Unable to do anything to rectify the situation.
Still under warranty of course, phone only released in October 2012.
Is this a fault with the phone which necessitates replacement or just a battery problem?
Would be grateful for any advice / guidance / help.
Thanks,
Mike Longley.
Click to expand...
Click to collapse
It seems also like SDS send it to Repair AFAIK is a chip problem, not battery so you can't do anything to repair it. If it is under warranty and with counter at 0 send it. They must repair it.
Enviat des del meu GT-N7100
Hey everybody,
I rooted my phone a couple weeks ago and one day it just pooped out. I researched a bunch on google etc and found some things to try but so far no solutions.
Model: SGH-T999 T-mobile s3 (Used CF-Auto-Root and Odin for rooting)
Problem: After the phone pooped out, I was unable to enter recovery mode. I could enter dl mode however it crashes at variable intervals. So I bought a jig figuring maybe that would help but it still crashes in dl about 5 seconds later. Any suggestions?
Everything that I have found on the internet has been were people can usually get it into dl mode and keep it there or they cant get there at all even with a jig. Any help would be appreciated. Thanks!
If you were running stock it's probably a hardware problem. If not what Rom are you on? What/when/how was your most recent flashes?
Have you tried kAsp3rd's brick fix in dev section?
Sent from my SCH-I535 using Tapatalk 4
DocHoliday77 said:
If you were running stock it's probably a hardware problem. If not what Rom are you on? What/when/how was your most recent flashes?
Have you tried kAsp3rd's brick fix in dev section?
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I just tried the kasperd brick fix and it didnt work. It still crashes at variable times and I cannot get it into download mode long enough to do anything. I tried a jig and it also still crashes. Any help would be great. Thanks!
Does it turn off? Reboot? Freeze?
Sent from my SGH-T999L using Tapatalk 4
DocHoliday77 said:
Does it turn off? Reboot? Freeze?
Sent from my SGH-T999L using Tapatalk 4
Click to expand...
Click to collapse
It starts and then crashes. After awhile it might make it to the animation with the blue wave forming around the words samsung, but usually it crashes on the Samsung Galaxy SIII logo in the beginning. Also when I put it into download mode it crashes anywhere from 1-5 seconds after. When I try to get into recovery mode it crashes almost right away when the blue words are at the top left of the screen.
Also when I put the battery in it tries to boot on its own without me pressing power button, and sometimes it tries to reboot after it crashes and turns off without me pressing anything. Also after it crashes I usually cannot just press the power button to try and power it up again so I have to take the battery out and put it back in.
When I was doing the Kasperd brick fix I used the T999 debrick image. How do I know if I have a different variant of the T999. I saw that some people had T999v and T999N. What are those?
Look under the battery for your model. Sounds like a power button issue. All I can say is try fiddling with it a bit. May have to open to see if it is physically always in contact, or it could be a deeper issue on the board. Hard to say.
Sent from my SGH-T999L using Tapatalk 4
DocHoliday77 said:
Look under the battery for your model. Sounds like a power button issue. All I can say is try fiddling with it a bit. May have to open to see if it is physically always in contact, or it could be a deeper issue on the board. Hard to say.
Sent from my SGH-T999L using Tapatalk 4
Click to expand...
Click to collapse
Ok I just see T999 on the label.
How can it be a hardware issue when I never dropped the phone or anything. I was just thinking it was because I rooted the phone because it happened about a week after I rooted it. It was working one minute and then a couple hours later when I took it out of my pocket it was off and I tried turning it on and all that stuff started happening. I will definitely check the power button though. Thanks for the help.
Also another piece of info to add. When I plug it in to charge both the battery charging symbol and red light will sometimes turn on and then it crashes/goes black similar to what happens when trying to power up the phone. Not sure if that helps at all. Thanks!
If my phone was hard bricked I wouldnt be able to turn it on at all correct? Im trying to figure out if I will need to get this thing jtagged or something in order to get it working again.
phillycheese917 said:
How can it be a hardware issue when I never dropped the phone or anything.
Click to expand...
Click to collapse
Physical damage is not a prerequisite of hardware failure. Ever have a hard drive go bad? Did you drop it first?
Aerowinder said:
Physical damage is not a prerequisite of hardware failure. Ever have a hard drive go bad? Did you drop it first?
Click to expand...
Click to collapse
True, however I just find it odd that I rooted the phone and a week later it happened. That is why I am leading towards an issue involving that and not hardware damage.
If it was a problem with rooting, it would have gone south right away. Many people are having these button issues recently. And you don't have to drop it, like aerowinder said, but you do use the button right? Moving parts wear out. Hardware fails. That's really all there is to it. While I could be wrong in my diagnosis, I don't think that will prove to be the case here.
Sent from my SGH-T999L using Tapatalk 4
It does most certainly sound like a hardware issue in the power button. I read another thread very similar to this same thing on the T999.
KAsp3rd said:
It does most certainly sound like a hardware issue in the power button. I read another thread very similar to this same thing on the T999.
Click to expand...
Click to collapse
Any suggestions on what to do from here? I dont think the phone is under warranty anymore.
I took the back casing off to see if the button is getting stuck or anything, but all the mechanics look normal.
phillycheese917 said:
Any suggestions on what to do from here? I dont think the phone is under warranty anymore.
Click to expand...
Click to collapse
I would recommend searching around for others who have had the same issue and seeing what their resolutions were. I've not seen many on here but google turned up quite a few.
KAsp3rd said:
I would recommend searching around for others who have had the same issue and seeing what their resolutions were. I've not seen many on here but google turned up quite a few.
Click to expand...
Click to collapse
Thanks guys! I found a good thread on here about the S3 sudden death thread. Im going to read up on that and see what I can do. It was just tough to find since I was thinking it was bricked but the descriptions for this power button sudden death thing sound spot on. Hopefully I will be able to get everything back in working order.
When I boot up my SGH-I467 (Galaxy Note 8 AT&T LTE) it nearly always displays a screen that looks as though its damaged – just horizontal coloured lines or blocks of colour across the screen with no hint of any image. It only boots up correctly about 1 time in 20 or 30. Once it does boot up correctly everything works fine and there’s no hint of anything wrong with the screen itself. It’s also OK if I just turn the screen off between sessions. However, after recharging the tablet the problem recurs when I switch on. Its on firmware version 4.1.2 which appears to be the latest available for this AT&T version. Any ideas on what's happening and a fix?
Boot up problem - pictures added
erbc said:
When I boot up my SGH-I467 (Galaxy Note 8 AT&T LTE) it nearly always displays a screen that looks as though its damaged – just horizontal coloured lines or blocks of colour across the screen with no hint of any image. It only boots up correctly about 1 time in 20 or 30. Once it does boot up correctly everything works fine and there’s no hint of anything wrong with the screen itself. It’s also OK if I just turn the screen off between sessions. However, after recharging the tablet the problem recurs when I switch on. Its on firmware version 4.1.2 which appears to be the latest available for this AT&T version. Any ideas on what's happening and a fix?
Click to expand...
Click to collapse
I'm very disappointed that my post has had 118 views but no replies so I've added two photos of the screen showing what usually happens when I boot up. Note that about 1 time in 20 or 30 it boots up fine and operates perfectly in every respect and I've then been able to use it for hours continuously without any problem whatever.
Does any one know whether this is likely to be a screen/digitizer problem or something else?
erbc said:
I'm very disappointed that my post has had 118 views but no replies so I've added two photos of the screen showing what usually happens when I boot up. Note that about 1 time in 20 or 30 it boots up fine and operates perfectly in every respect and I've then been able to use it for hours continuously without any problem whatever.
Does any one know whether this is likely to be a screen/digitizer problem or something else?
Click to expand...
Click to collapse
I have never seen this and I have the same model. It sounds like whatever it is, you should be able to take it in for warranty service.
I'd say probably the screen and not the digitizer
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app
Boot up problem
esoh said:
I have never seen this and I have the same model. It sounds like whatever it is, you should be able to take it in for warranty service.
Click to expand...
Click to collapse
Thanks for comments. Although its only about 3 months old it was a gift from the US and I live in UK so warranty service probably isn't an option.
erbc said:
Thanks for comments. Although its only about 3 months old it was a gift from the US and I live in UK so warranty service probably isn't an option.
Click to expand...
Click to collapse
There's a post in this forum about screen replacement and I think that he does them as well. If you can't find a solution, then it may be the best way to go. Also, try asking Samsung themselves. If you explain the situation, they might be able to help you.
esoh said:
There's a post in this forum about screen replacement and I think that he does them as well. If you can't find a solution, then it may be the best way to go. Also, try asking Samsung themselves. If you explain the situation, they might be able to help you.
Click to expand...
Click to collapse
I'm hesitant in attributing this to a screen problem. I normally swich off the device between sessions of use but then have the problem booting up to a good screen. However, I thought it would be easier just to leave it running and the screen has perfomed fne for the last 72 hours with me just fully dimming screen between sessions of using the tablet. Is there anything else that might cause this?
The only things that i could think to suggest would be
1) Have you tried wiping the cache?
2) Have you tried a factory reset?
I'm no expert, but if it were my device I would try both of these before sending the device in for warranty service.
Not saying either is a sure fix, but thats what I would do.
Sent from my SAMSUNG-SGH-I467 using XDA Premium 4 mobile app
dandroid7 said:
The only things that i could think to suggest would be
1) Have you tried wiping the cache?
2) Have you tried a factory reset?
I'm no expert, but if it were my device I would try both of these before sending the device in for warranty service.
Not saying either is a sure fix, but thats what I would do.
Sent from my SAMSUNG-SGH-I467 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry for long delay in responding to your suggestions. I'd already tried a factory resent but not wiping the cache. I did both of these after your suggestion but no change to the fault.