Related
I had my Gtablet for a week and after the update, it works fine. Today, when I power up the tablet, the screen just went blank (white screen). I am a novice thus I did not mod the tablet. What happens? I hate to return the tablet since I was starting to enjoy it. PLease advise.
You might try to reload a working firmware. If you have clockworkmod, and a saved image, restore it and see what happens, perhaps a driver got corrupt somehow. If that does not work, it may very well be hardware failure. Take it back to Sears a white screen is just that. Not useable.
Thanks. Guess I need to run over to sears again for another exchange.......This was my second one. The first one just doesn't boot up and this one was working fine until now.
I am having this white screen of death issue. I'm hoping that getting the battery completely drained will reset something and allow me to see the birds again...never thought I'd be wanting to see those birds, but here I am.
Has anyone ever had the blank white screen of death and gotten their gtab to work again?
damn it, same thing just happened to me. I left it unused for 2 weeks, now I turn it on and white screen! not nice
Bump for the sake of my gtab? anyone??
Sent from my PC36100 using Tapatalk
and bump again? anyone?
White screen follow-up
I believe that this "white screen" is the equivalent of when you see a "No Signal" notification on your HDTV. I'm pretty sure that the tablet is running fine, it's just not outputting video to the LCD. I didn't have a dock to do video out to verify this, but I am fairly certain that's what was happening here.
I had to RMA mine. If anyone has other results/info, please let me know.
The first gtab I bought when it started had a white screen that you could hardly see anything and it blinked. I took it back to office depot and got a new one.
Follow-up White Screen (more info), using HDMI output
Have the same problem with my second GTablet. However, I bought an external dock that has an HDMI output for the GTablet. With the working GTablet, when I plug it into my television, the television mirrors the output of the screen perfectly. With the white-screen tablet, only the television shows something. As I am a basic hardware guy, I guess there are two reasons for this:
1. The flex cable between the display and the computer is loose/broken.
2. Something in the electronics is wrong.
I have received an RMA number for this problem from Viewsonic, although they may just look at it and send it back to me. Any other experiments that people want me to try while I can still see on the external?
Otherwise, I'm just gonna send it to Viewsonic in a couple of days and wait 15-20 business days.
G Tablet White Screen
I have had this lately too. Once in a while when i turn my Gtab on the screen is white. When it first happened, i assumed it was bricked. I tried doing a update.zip back to stock...nothing...just white screen. Then when i was in the process of doing the update.zip flash again, i bumped the bottom, right corner of the tab on my desk and the screen all of a sudden when back to normal, showing the home screen. Now, if it does this white screen business, a simple tap on the right side usually brings it back to normal. I would also assume this is a loose connection of some sort. Anyone cracked the gtab open and been able to find where the screen connection is located? I bought my gtab Jan 14 2011 so it is out of the return window to Sears, and i haven't called Viewsonic for assistance yet as i fear i won't get very far with them. Any help is greatly appreciated!
Triple Love Tap Fix on Bottom Right Corner for White Screen Fix ... Back to Normal
After reading the last post, I tried a triple love tap on the bottom right corner on a white-screened g-Tablet, and voila. It's working again. The Internet is a grand thing. This love-tap thing is clearly undocumented Viewsonic security feature.
As for reference, I did break it open and tried to figure out where the flex cable went, but it's a pretty tight SoC design and when I removed the cover, the connection seemed to be sandwiched between the motherboard and the touchscreen itself. Not wanting to remove the 5 various cables and 3-4 various buttons floating around, I gave up at this point.
If I have to periodically do a love-tap, well so be it. At least, I'm not spending $600 for Motorola Xoom. Thus is the fate of cheap bastards like myself who like to play Fruit Ninja on the cheap.
I can't believe this worked!! "Love Tap" to the right corner brought my white screen back as well.
Bump really works, thanx!
i can't believe the bump worked. I took it apart and looked inside at every connection. I was about to throw it away and then i found this post. I did the bump and it's back to normal.
Another "love bump" success!
Just had it happen to mine this morning -- blank white screen. I did a love bump as suggested, and the screen is back! Definitely sounds like a connection issue, but I don't recall bumping it before it blanked out. I'll just keep fingers crossed that it doesn't happen again.
BTW, for anyone else who needs to do this -- it's definitely a "bump" compared to a "tap". I had to give it enough oomph that I could have craked a walnut with my palm under the same force. Not a "whack" but a "bump" compared to "tap"
WTF WITH VIEWSONIC/USMERCHANTS! I Live in Mexico, I sent (paid..) my tablet to the US for warranty (white screen, the tapping doesnt seem to work with me..) they recieved it, send it back to a friend in the US and he sent it back to mexico (PAID AGAIN).
Just recieved my gtablet, turn on, white screen, nice they didnt even touch the friggin thing!
WHAT THE F...
Ok, bumping this thread again, and letting you know.
Since I was pissed, I opened up my gtablet! Well to letting you know, the CONNECTOR that goes FROM the motherboard to the LCD...was completely loose and not completely connected. This has to be a factory fault, since well, its almost impossible for it to disconnect! Anyway, My tablet is working just fine now, (after 4 months ¬¬)....I will try to get my shipping money back from US Merchants, bastards.
RAWR!
[REQUEST] A permanent solution than periodic love "tap/bumps"
Can you post a picture of the connector? I broke open my tablet before, but I was unable to locate this loose connection. Although I find the current solution very amusing/charming , I would like to have a permanent solution on this thread.
For long term care of the tablet, I've had to do this solution about once every 2-3 months on my 6 year old son's tablet. He had the tablet with the original problem and he may occasionally drop/jostle the thing more than I. So, for the lifetime of this product, the love tap/bump may be an acceptable solution. However, it is clearly a loose connection problem, and more information on your solution would be very helpful to the community.
pmcnano said:
Ok, bumping this thread again, and letting you know.
Since I was pissed, I opened up my gtablet! Well to letting you know, the CONNECTOR that goes FROM the motherboard to the LCD...was completely loose and not completely connected. This has to be a factory fault, since well, its almost impossible for it to disconnect! Anyway, My tablet is working just fine now, (after 4 months ¬¬)....I will try to get my shipping money back from US Merchants, bastards.
RAWR!
Click to expand...
Click to collapse
My solution to the white screen!
I though how stupid I was since I didnt took pictures, but let me explain.
Using the hardware breakdown pics.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I draw a Red Square in the "affected part".
In the top of the square is one end of the cable, in my case this was correct. The other end is underneath the motherboard, so you have to take out all the screws for the motherboard to check the other end, this was completely off.
I dont know if this will help everybody, because I gotta say for myself, the bumping in the bottom right didnt worked for me, not even once and I SMASHED the thing really hard!
Cheers
Paul
edit:
BTW, US MERCHANTS warranty told me someone screwed up on their side, I should have gotten a new tablet ¬¬. Anyways, I'm trying to make a deal with them, since I paid like 50 dls for shipment (I live in Mexico..) and they didnt do anything. Will let you know maybe I get a free dock!!!
Noticed that sometimes no matter how careful i was about swyping the correct word, it would come out wrong.
I checked "show complete trace" in swypes settings to see where i was messing up, and i noticed something much worse than my own mistakes.
Sometimes, my swype sensor goes nuts for no reason. You can see the trace jumping all over even though my finger is moving in a straight line. Heres a screenshot of just moving my finger left and right to see how the trace jumps everywhere:
normal trace
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
crazy trace
Sometimes its worse, but it makes swyping very frustrating. Im wondering if this is a touchscreen issue, and not just confined to swype. I have had trouble in the past moving desktop icons around, and it seemed like something was just off.....
anyone else have this problem?
lourivellini said:
Sometimes its worse, but it makes swyping very frustrating. Im wondering if this is a touchscreen issue, and not just confined to swype. I have had trouble in the past moving desktop icons around, and it seemed like something was just off.....
anyone else have this problem?
Click to expand...
Click to collapse
My screen seems to be 'off' every so often. Most often near the top quarter of my screen when in portrait. Even in landscape it's stays off. So I know it's not software.
Swype messed up for me too a couple times. More jagged than even what you posted. Though it cleared up after an evening or so. Though most times I use SwiftKey. So it could still be doing that.
Sent from my páhhōniē
gr8hairy1 said:
My screen seems to be 'off' every so often. Most often near the top quarter of my screen when in portrait. Even in landscape it's stays off. So I know it's not software.
Swype messed up for me too a couple times. More jagged than even what you posted. Though it cleared up after an evening or so. Though most times I use SwiftKey. So it could still be doing that.
Sent from my páhhōniē
Click to expand...
Click to collapse
thank god im not the only one. Im starting to think i might just have a bad phone. This did this to me on cm and stock. And yes ive had super jagged lines too, i just couldnt replicate it for the screenshot.
What other issues have u had with your device (battery), and is your screen abnormally dim?
Just that screen issue. I exchanged the phone once, only because of screen issues. Dead pixel and touch was off by a bit on the top and bottom of the screen.
I feel bad with all the issues you're having with yours. Mine has been great on nearly everything.
Hopefully you'll get yours figured out. I'm regularly on here as I'm recovering from surgery. Literally nothing else to do. Feel free to message me if you have a minor issue that isn't quite thread worthy. Gives me something to do.
Sent from my páhhōniē
swype sensor?
tell me, is it plugged in when it is messing up? or does it become worse when plugged in. i found that i had a defective charger and the "cursor" or where it was registering y input would jump erratically around the screen! eventually my phone died and i had o get it replaced.
Nope, plugged in or not it doesn't mess up anymore. Hopefully my phone won't die 0.o
Sent from my páhhōniē
tmckenn2 said:
swype sensor?
tell me, is it plugged in when it is messing up? or does it become worse when plugged in. i found that i had a defective charger and the "cursor" or where it was registering y input would jump erratically around the screen! eventually my phone died and i had o get it replaced.
Click to expand...
Click to collapse
gr8hairy1 said:
Nope, plugged in or not it doesn't mess up anymore. Hopefully my phone won't die 0.o
Sent from my páhhōniē
Click to expand...
Click to collapse
Think I've finally got some issues straightened out. Battery life is now incredible (literally the best ive ever seen on a phone) running cm7, and havent had issues with swype since last night.
Will report back if it happens again/my phone craps out. Fingers crossed!
spoke too soon. got home and while typing while the phone was charging i got this:
it seemed really bad, but what ive noticed is sometimes its worse than others, so its not just good or bad, but varying degrees of bad.
Battery life seems fixed, but i cant learn to live with this either. I might try to swap it at radioshack before by 14 (or 30 days) is up.
im telling you, its the charger. im actually using my old moto charger an i havent had any problems
for me it does it when my phone is plugged in charging
agree with some now. Ive only noticed it when plugged in.
Is this rom specific, or does it happen to every rom? I sill have a month to exchange if i need to.
Im using the newest CM7 KANG build btw
This generally happens with non original chargers, feeding the wrong current and driving the touch sensor insane, is what I've heard... That explanation worked for me. No erratic behaviour with original charger, but crazy behaviour with the blackberry charger...
Sent from my SAMSUNG-SGH-I777 using XDA App
Can also occur with the original charger if plugged into noisy power.
I almost thought my Infuse was defective when I first got it because I tried to charge it using the factory charger on an inverter - that combo made the touchscreen VERY unhappy (as in, unusable, you couldn't even unlock the phone)
Factory charger in a real wall outlet was fine.
I've had the same kind of problem before when I was using my cousin's droid x charger(probably wasn't the best idea any way). It would cause swype to get really unhappy, even worse than yours. I have not experienced it with the stock charger but then again I rarely use my phone while it is plugged in.
hmmmm, well currently using my captivate wall charger/usb cord. Ill have to try it with the original when i get a chance to switch them.
They looked exactly the same to me.
If this does end up being the case, where can i buy a stock usb cord, if i need extras?
Mine does it while plugged in with the stock charger. its almost impossible to text sometimes while its plugged in.
anyone considering returning phone? Is this cause for concern? Do all phones do this?
My Atrix was even worse at that...
Sent from my SAMSUNG-SGH-I777 using XDA App
It may be more of a function of how "clean" your wall power is.
As I said - mine works fine on the stock charger at home, but it basically froze the touchscreen when connecting the stock charger to an inverter.
Entropy512 said:
Can also occur with the original charger if plugged into noisy power.
I almost thought my Infuse was defective when I first got it because I tried to charge it using the factory charger on an inverter - that combo made the touchscreen VERY unhappy (as in, unusable, you couldn't even unlock the phone)
Factory charger in a real wall outlet was fine.
Click to expand...
Click to collapse
I had the exact experience with my GSII. Took it out of the box on the way home with it, plugged it into an inverter while I fired it up the first time, and thought I had gotten a defective phone. Touching the screen to slide off the stock lockscreen it looked like I was shaking all over the place. Typing was impossible. The stock charger did the same. I also got no in call audio, but that could have been from the touch screen being freaked out by any slight touch. Unplugged the phone and it was perfectly fine.
I later found one of my old USB chargers did the same thing on wall power. I'm now using a USB lighter plug charger on the go and it works fine. The inverter I have is an older black and decker 400watt and it tests out to be as good as it ever was. Must be something in samsung phones that really dislikes anything but a nice clean sine wave power output.
my s2 has gone mental tonight.
i charged it up to 100% before i left. then tonight for some reason it kept showing this when the charger wasnt plugged in
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
so i kept restarting and taking out the battery til it stopped.
you can see the charging period didnt seem to show up on the graph. the charging period shown there i was not charging but the phone seemed to think it was. so as i was restarting it a few times it went from about 70 to 49 to 17 to 49 again
and also i havent been able to get a phone signal for ages and then when i can it wont let me register a network.
my phone is now basically just a wifi web browsing device until i get it sorted :crying:
Sounds like a battery failure.. Not sure tho.
Sent From My Sexy Sensation Running Aokp.
oh ive just seen this
http://www.dailymail.co.uk/news/art...unable-make-calls-text.html?ito=feeds-newsxml
thats a relief. o2 is down nationwide
EVERY single time I've heard of this issue (and there are a TON of threads all over XDA about this, not to mention all over other forums - seriously, just google "i9100 charging paused voltage too high", and watch how many results you get), it is due to a dirty or failing USB port.
Steps to take.
-clean USB port with a clean, dry brush. (don't be TOO rough)
-if that doesn't work, take out the battery, and with a q-tip and small amount of isopropyl alcohol, clean the USB port. Let it dry, then replace the battery.
-if THAT doesn't work, you'll probably have to get the part for the USB port replaced.
---------- Post added at 04:52 PM ---------- Previous post was at 04:52 PM ----------
elquango said:
oh ive just seen this
http://www.dailymail.co.uk/news/art...unable-make-calls-text.html?ito=feeds-newsxml
thats a relief. o2 is down nationwide
Click to expand...
Click to collapse
This has nothing to do with what you posted...
yeah i know. i had both things happen at the same time so initially i thought it was my phone on the fritz and they were related
so i tried those things and it still having problems.
I bought this replacement in Nov off Ebay. After i lost my original one. Do you think I can still take it anywhere to be repaired?
will the o2 store look at it for me?
such a hassle. im gonna have to unroot it and stuff
oh great and now it keeps randomly vibrating and going to this screen and then back to my home screen
elquango said:
so i tried those things and it still having problems.
I bought this replacement in Nov off Ebay. After i lost my original one. Do you think I can still take it anywhere to be repaired?
will the o2 store look at it for me?
such a hassle. im gonna have to unroot it and stuff
oh great and now it keeps randomly vibrating and going to this screen and then back to my home screen
Click to expand...
Click to collapse
By "those things" I'm guessing you didn't actually replace the part for the USB port. Just the cleaning steps?
That image is "desk clock" mode. It gets activated when certain pins in the USB port are shorted with a specific resistance. If you thoroughly cleaned the port as best you could, and are getting random desk clock mode and still randomly getting the charging paused message, then I'd say your USB port is dying a slow death. You'll need to get the part replaced.
From what I hear the part itself is pretty cheap (like $15) and not hard to replace. I don't know if O2 will do it for you though, since you didn't actually buy the phone from them. You can try... but I doubt it, since it was a second hand purchase. Or just take it to a local cellular repair shop.
My phone is also having a similar experience. I running an AOKP rom so it keeps charging instead. How long will the usb port work for. It's being sent back to Samsung to have the screen replace and have notified them about this. So will the usb port work till next week or could it die in hours or days?
imlgl said:
My phone is also having a similar experience. I running an AOKP rom so it keeps charging instead. How long will the usb port work for. It's being sent back to Samsung to have the screen replace and have notified them about this. So will the usb port work till next week or could it die in hours or days?
Click to expand...
Click to collapse
I'm not sure how someone on a different continent than you can possibly answer a question about the state of the USB port on your phone and how long it will last.
ctomgee said:
By "those things" I'm guessing you didn't actually replace the part for the USB port. Just the cleaning steps?
That image is "desk clock" mode. It gets activated when certain pins in the USB port are shorted with a specific resistance. If you thoroughly cleaned the port as best you could, and are getting random desk clock mode and still randomly getting the charging paused message, then I'd say your USB port is dying a slow death. You'll need to get the part replaced.
From what I hear the part itself is pretty cheap (like $15) and not hard to replace. I don't know if O2 will do it for you though, since you didn't actually buy the phone from them. You can try... but I doubt it, since it was a second hand purchase. Or just take it to a local cellular repair shop.
Click to expand...
Click to collapse
hmm i'll have to look into it then. no idea where to start buying parts and where to take it to repair.
will have to do some research
It can by caused by humidity too in my opinion. Had this problem few times. My friend had too. It was gone after putting out battery for few hours in warm place. Even when I was keeping my phone in locker at roofed swimming pool it was happening.
Sent from my Sgs2 via Xda Premium. Helped? Click thanks button!
ctomgee said:
I'm not sure how someone on a different continent than you can possibly answer a question about the state of the USB port on your phone and how long it will last.
Click to expand...
Click to collapse
I'm going on average, like how long would be last. Roughly. Mine's been doing it for the past 3 days.
imlgl said:
I'm going on average, like how long would be last. Roughly. Mine's been doing it for the past 3 days.
Click to expand...
Click to collapse
It depends on the severity of the damage specific to your phone. If it's damaged more severely, then not long. If it's not damaged so severely, then longer. How long it's been doing it doesn't mean anything.
ctomgee said:
It depends on the severity of the damage specific to your phone. If it's damaged more severely, then not long. If it's not damaged so severely, then longer. How long it's been doing it doesn't mean anything.
Click to expand...
Click to collapse
Well it's still charging but my pc no longer recognises it so I don't thin it's going to last too long.
ok its getting worse now. ive requested a repair from samsung.
before i send it off should i remove all my google and facebook accounts or should it be ok to leave that kind of stuff on there?
As long as it's unrooted, running stock firmware, has the flash counter reset if necessary, why would you need to remove stuff like that first ? I probably wouldn't.
Always remove personal data. Fully wipe your phone. You never know who works in service and what will di with your personal stuff. Thats my opinion.
Sent from my Sgs2 via Xda Premium. Helped? Click thanks button!
MistahBungle said:
As long as it's unrooted, running stock firmware, has the flash counter reset if necessary, why would you need to remove stuff like that first ? I probably wouldn't.
Click to expand...
Click to collapse
what are they gonna do if its rooted?
i dont have warranty anway so im gonna have to pay for the repair
look how mental the battery is being.
having to back up things through airdroid cos i cant use the usb now
If rooted they CAN cancel warranty.
Sent from my Sgs2 via Xda Premium. Helped? Click thanks button!
I got a brand new s2 two and a half weeks ago, 1 week ago when unplugging my charger it sort of went crazy bringing up the car mode, desk clock, charging when it wasn't and the voltage too high popup every 30 seconds. I took it back and they exchanged it straightaway however i have had this one for 3 days and its done exactly the same thing. I rooted and installed a custom rom on the first but left the second totally stock. It also happened to the girlfriends note too.....
Luckily i haven't had the phone for a month yet so i'm still entitled to an exchange but this has put me off samsung and i'm thinking of an alternative if they'll allow me to take a different handset.
Sent from my GT-I9100 using xda premium
First of all, sorry on my bad english.
I have my X10 for almost two years and since I upgraded to 2.3.3 I have lots of problems. The worst problem is with touchscreen. A year ago it started for the first time. Touchscreen just went crazy; when I press, for example, letter a, it writes all other letters except a, or sometimes I press a and it writes aaaaaaaaa. It gets stucked between two home screens and while having that problems, it's almost impossible to unlock screen or answer on a call.
I took it to a service, it was under warranty and they replaced touchscreen (and the whole front mask) and reinstalled software and it was working fine till one month ago. It started doing it again but it lasted just for one day. I left it charging the whole night and other day it was working like new. I had warranty till the end of this year but 2 days ago I rooted it (and losted my warranty) and today it started doing it again.
It's almost impossible that it's touchscreen's fault again! I think that it's this piece of crap x10's official gingerbread (the worst software that exist for a smartphone) fault for this problems because this is just one of lots other problems (GPS, audio stuttering etc.).
Anyone has the same problems? Should I try to put ICS, or turn back to perfectly-working 2.1 or is there a fix for that? I rooted it to install audio stuttering fix and this fix works like a charm so is there any similar fix for that touchscreen?
And I forgot to mention that I found lots of similar threads on internet about that so I can't be the only one.
do you touch the screen with wet hands
nikhil18 said:
do you touch the screen with wet hands
Click to expand...
Click to collapse
No. The screen sometimes gets muggy or greasy but I wipe it and everything works as it should (of course it doesn't respond well when it's muggy). But I'm 80% sure that this is a software related problem, because once it ocurs, lasts for, at least, one day, regardless to conditions (if the screen is clean and other). Sometimes it helps to pull out the battery for 10 minutes, but sometimes it can last for days.
Currently, everything is fine but it's just a matter of time when this issue will ocur again.
Thanks
EDIT: did you mean if I touch the screen with wet hands when the problems ocurs or in general? Could a little of water damage touch screen? A couple of times the screen got a little wet from my hair (when I'm sweaty or when I get out of the water to answer a call) but nothing badly. And the issue didn't ocured after this. But it's interesting that the issue ocured again a month ago, after the summer. We are at the beach every day and I always take my X10 with me for listening to music, taking pictures etc.
But from the other side, if touchscreen module is damaged, the issue would be present all the time.
xplod2841 said:
No. The screen sometimes gets muggy or greasy but I wipe it and everything works as it should (of course it doesn't respond well when it's muggy). But I'm 80% sure that this is a software related problem, because once it ocurs, lasts for, at least, one day, regardless to conditions (if the screen is clean and other). Sometimes it helps to pull out the battery for 10 minutes, but sometimes it can last for days.
Currently, everything is fine but it's just a matter of time when this issue will ocur again.
Thanks
EDIT: did you mean if I touch the screen with wet hands when the problems ocurs or in general? Could a little of water damage touch screen? A couple of times the screen got a little wet from my hair (when I'm sweaty or when I get out of the water to answer a call) but nothing badly. And the issue didn't ocured after this. But it's interesting that the issue ocured again a month ago, after the summer. We are at the beach every day and I always take my X10 with me for listening to music, taking pictures etc.
But from the other side, if touchscreen module is damaged, the issue would be present all the time.
Click to expand...
Click to collapse
Have you ever rooted or changed your rom or do a factory reset?
Sent from my X10i using xda app-developers app
romorsH Spaniards
brenty108 said:
Have you ever rooted or changed your rom or do a factory reset?
Sent from my X10i using xda app-developers app
Click to expand...
Click to collapse
I rooted it a few days ago, and it still has factory gingerbread on it. I'm planing to put ICS on it these days.
I was doing factory reset almost every month, because, as I said, I had lots of problems with stock gingerbread.
whenever i touch my x10 with wet hands the screen becomes unresponsive like while scrolling the phone gets stuck on one place one day i was playing asphalt 5 i changed the controls to screen tap when i played it with wet hands the car was turning on the left side only.
then i put a screen guard then this problem was considerably reduced
Problem started occuring again, on a daily basis. I will smash it into wall :/ Most of the time it works, and at the moment when I have to send an important message, or e-mail or something other important, it goes crazy. Everytime I try to record it with a camcorder and show here, it works just fine. "He" is obviously trolling me. I was sure that it has to do with stock kernel since most of times the problem occured I was on stock kernel, but no. Today I flashed DoomKernel (version without OC) and DonutHD 2.2.9 and it's still occuring.
Touch screen was once replaced so I don't think that the problem lays there. Nor lays in the software/kernel/rom. What else could be? Do you think that screen guard can help me? Despite this, I often have problems when it's too cold outside and the screen gets cold and a little wet from coldness, I can't use it as well... Does screen guard helps in these cases?
Please help! Somebody must know something
Sent from my X10i using Tapatalk 2
It could be a number of things really. The digitizer could be damaged, it could not be inserted in main board right. Since stock and software is not the problem it has to be hardware. You said the screen was changed, the digitizer or the front panel?
Sent from my Xperia X10 using xda app-developers app
brenty108 said:
It could be a number of things really. The digitizer could be damaged, it could not be inserted in main board right. Since stock and software is not the problem it has to be hardware. You said the screen was changed, the digitizer or the front panel?
Sent from my Xperia X10 using xda app-developers app
Click to expand...
Click to collapse
Can the problem be with stock based ROM? Because, as you can see in my signature, I'm using a stock based ROM with DoomKernel. But I don't think neither that the problem is with software. Lots of people are using everything stock and lot of people are using doomkernel and donuthd with no problems.
My mistake, the screen wasn't changed. The front panel was changed, with the digitizer on it. What should I do now? I ordered screen guard but I don't think that this will fix the problem. I can try to order the tools for taking apart my phone to try to connect it better with main board and to clean the dust inside. But it's weird that this problem appeared again.
I asked in a repair service what they could do; they would first try with software (which I've done already) and they can re-solder the whole board but there is no guarantee that the phone will work after that and it would be probably expensive.
Now I started thinking about getting myself a new phone, probably SIII. But I'm sorry to leave my X10 after only 2 years of use and now when I've found a perfect ROM and Kernel
EDIT: I'm still new to all that and don't know the differences. But can it be due to firmware? I changed only ROMs and Kernels but never touched firmware (I don't know if the firmware comes with kernel or rom). Here is my SS of phone info with donuthd on stock kernel:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and with donuthd on doomkernel:
And here is my history:
- everything stock till september, the issue occured 2-3 times but didn't last for a longer period... it was the first time since my digitizer was changed
- first time rooted in september to apply sound stuttering fix
- a few weeks later installed this ROM, had problems with kernel due to installing from recovery, but it worked, issue occured a few times but again, just shortly
- somewhere in october I repaired and returned everything to stock, rooted and installed this ROM, the issue occured only once while using this ROM
- in december returned to stock, root, first time unlock BL, installed DonutHD on stock kernel... issue started occuring again..
- in the same month, tried this ROM only for one day and then again repair, root, unlock BL, doomkernel, donut hd... issue started occuring on a daily basis
The funny thing is that it started occuring when I need it the most... I send a stupid message something like "kfgifskosd " already twice to the same man when I had to reply to an important message from him. I started tiping and the phone went crazy putting random letters and 12-15 smileys and it clicked itself on Send and the message was sent without me even touching the phone. I couldn't even call him to apologise because when I clicked on Contacts it went crazy again.
It seems that the problem was due to my fingers or the "glass" itself I have the screen protector (guard) for more than a month now and the problem didn't appeared even once! Now it's working perfectly and this protector can't get muggy or greasy. I tried with wet and greasy fingers and it's always working.
And today I tried something on my dad's X10 (which doesn't have screen guard) and I had a hard time just to unlock it :laugh: X10 doesn't like my fingers
well i`ve this problem too ,so i`ll try a screen guard,it sometimes occur (specially when i`m messeging) i have to shut the screen off and turn it on again to make it work.
So...my problem is as follows :
ISSUE :
For 3 weeks or so my nexus 9 has been doing some weird stuff :
Randomly, the whole screen starts to flicker and the tablet becomes unresponsive, the only solution left for me being to force reboot by holding down the power button for several second. If I'm watching youtube or just playing some songs, it occasionally starts to make an unbearable noise (much like the old TVs do when don't have the tv-cable in them and you watch the "snowflakes") .
Sometimes, even if I reboot it after the flicker "episode", it would flicker the bootanimation and freeze, thus making me force reboot over and over, until I manage to boot up the tablet properly.
***If I'm lucky, the tablet would just freeze (and then self-reboot after a minute or so)...without the screen flickering
I have also included some pictures of the tablet while it had its "episode". Hope they're helpful !
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
POSSIBLE CAUSES :
1)Over-heating
2)Hardware failure
3)I suspect this is from the kernel, because this has been happening since I tried a no-force encryption kernel (using nexus toolkit), then changed to stock kernel (using nexus root toolkit again), then flashing the stock image (=system, boot, cache, vendor...etc) (using nexus root toolkit again), and then factory reset.
(Also....this issue with screen flickering was present in the early 10-15 nightlies of cm12 when my tablet's battery level was dropping below 15-20%)
SOFTWARE :
Stock ROM : 5.0.1
Build : LRX22C
Current Kernel : stock kernel(flashed with nexus root toolkit)
Root status : ROOTED - using Chainfire's SuperSu app along side with Busybox (free)
Bootloader Status : UNLOCKED (I never locked it back since when i firstly unlocked it)
RESOLVING POINT : THE QUESTIONS
1)Is it possible to resolve this issue with just a change of kernel ?
2)If i change ROMs do i have at least a chance that the flickering won't happen ?
3)If it's a hardware failure, can it be easily resolved or do i need to send back the tablet for repairs/replacement ?
I'll wait for your responses !
Thanks in advance !
If it were me, I would try putting everything completely back to stock (as in the way it came out of the box) and doing a factory reset to see if that fixes all your issues. If it still persists, I would exchange the unit. If not, you can go ahead and unlock and root again after you're satisfied the issue has cleared up.
Thanks for the reply !
I will try that this weekend since i don't have a lot time right now and probably later I'll flash CyanogenMod. I noticed that it flickers only when it gets hot...and if I power it down a little and let it cool...the issue is temporary resolve. I hope things will get better with the 5.1 update.
Until then...any other replies are welcomed and appreciated.
Sent from my Nexus 9 using XDA Free mobile app
mihaicristian said:
Thanks for the reply !
I will try that this weekend since i don't have a lot time right now and probably later I'll flash CyanogenMod. I noticed that it flickers only when it gets hot...and if I power it down a little and let it cool...the issue is temporary resolve. I hope things will get better with the 5.1 update.
Until then...any other replies are welcomed and appreciated.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
It's looks like you have a few cracks or marks on your screen. YMMV on getting google or HTC to replace it with that on it.
inick73376 said:
It's looks like you have a few cracks or marks on your screen. YMMV on getting google or HTC to replace it with that on it.
Click to expand...
Click to collapse
No...luckily it's my tempered glass that has the cracks. My main issue is that I bought this tablet with Amazon in December, not directly from Google or HTC
Mine has done this a couple times and got really bad yesterday freezing, garbled, and rebooting over and over. I went back stock, had been on elementalX (not saying it was the kernel), and have put it through the paces with benchmarks and its been fine so far but I'm still afraid of it. First sign of issues and its off to HTC, amazon purchase as well. I think heat/hardware issue most likely.
I had the screen flickering as well, right out of the box. If memory serves me right, I turned off auto brightness and haven't had flickering since. I am completely stock however. Hope that helps.
I noted that it usually flickered when the battery got under 15-16%...Then, I forced reboot, followed by the powering off of the tablet (from fastboot mode). Finally, I put the N9 to charge (without booting it up).
I tried to turn off the auto-brightness....I hope it will solve the issue, though I doubt it.
Sent from my Nexus 9 using XDA Free mobile app
So...after doing a full factory reset and after flashing the images manually, the issue still persisted (though, it was in a reasonable ammount)
I have discovered that if I put the tablet to charge and force reboot it, the issue is fixed as long as it's charging.
Anyways, now I have done a factory reset again and installed CyanogenMod and Gapps. I'll get back with the results after 24h of use. Wish me luck !
Something similar happened to me with the tablet, in my case it is a 16GB WiFi HTC Nexus September and since I have tried two one based on AOSP 5.0.2 (Simple ROM) with KernelMOD ElementalX and the other based on 5.1 (Lollipopalooza) with Kernel Stock and both happened to me that problem, and I know that
1) It is not by temperature as it passes this on a NORMAL temperature range around 58 degrees Celsius in the CPU ..
2) Not the Kernel as such these two compilations or any modification to why I tried that detail.
Now this in my Tablet has a competition and it happens when in a level of less than 50% charged battery, and always happens when the game is, digase Asphalt 8 Airborne or Clash of Clans, is played if more above that level HAPPENS no charge, sometimes at 20% load vecez other 40% is in order, so I think to do is try a CustomROM CM12 is based on the AICP and look as if no re comportao the stock of Google and look if it happens, if it happens again I hope the 5.1 official Google thing that I think is a hardware problem promptly which can only guarantee remeasure, so will give you time to Google it pleases removing the Firmware 5.1 and the amount and if you stop not happen then, because I feel TERRIBLE guarantee that HTC and Google, as costs provide a team with such problems, and it should be emphasized that BEFORE not happened to me, it came to pass after almost 7 MONTHS ..
PD: That sorry for my English but not my original language, use Google translator.
juandiegofx said:
Something similar happened to me with the tablet, in my case it is a 16GB WiFi HTC Nexus September and since I have tried two one based on AOSP 5.0.2 (Simple ROM) with KernelMOD ElementalX and the other based on 5.1 (Lollipopalooza) with Kernel Stock and both happened to me that problem, and I know that
1) It is not by temperature as it passes this on a NORMAL temperature range around 58 degrees Celsius in the CPU ..
2) Not the Kernel as such these two compilations or any modification to why I tried that detail.
Now this in my Tablet has a competition and it happens when in a level of less than 50% charged battery, and always happens when the game is, digase Asphalt 8 Airborne or Clash of Clans, is played if more above that level HAPPENS no charge, sometimes at 20% load vecez other 40% is in order, so I think to do is try a CustomROM CM12 is based on the AICP and look as if no re comportao the stock of Google and look if it happens, if it happens again I hope the 5.1 official Google thing that I think is a hardware problem promptly which can only guarantee remeasure, so will give you time to Google it pleases removing the Firmware 5.1 and the amount and if you stop not happen then, because I feel TERRIBLE guarantee that HTC and Google, as costs provide a team with such problems, and it should be emphasized that BEFORE not happened to me, it came to pass after almost 7 MONTHS ..
PD: That sorry for my English but not my original language, use Google translator.
Click to expand...
Click to collapse
Those are exactly the circumstances in which my tablet flickers !!!!
Anyways,...everybody just listen and hope this solves your problems too !
The main story :
I installer cm12...and it still flickered....so as a final resolution, I took off the back-cover.
During the removal, I made sure that the camera won't go off, BUT the important thing is that I accidentally unplugged a little-little cable found on the right upside of the tablet (when facing screen down = in the other corner from where the camera is found AND the tablet was held in portrait)
So...after re-plugging that tiny cable back on its port (I think that's what that little whole was named) and playing a little bit with the copper thingy..... I turned on the tablet (without the cover being attached) and it lit up with no problems or whatsoever. After that, I power it off (just to avoid any sort of short-circuit damages ) and put the back-cover.
I have to mention that I heard some sort of click in the up-center of the tablet while I was pressing it to make sure everything was reattached as initially (I think that maybe was the NFC antenna)
Finally, I powered the tablet on....and after charging it to 100% and installing all my apps, I ran Antutu benchmark just to make sure everything was ok. Surprisingly, it passed on without even the slightest sign of flickering.
To sum up : I think the problem was the NFC antenna, somehow interfering with the tablet OR it was that little cable I disconnected, but then reconnected back on.
Now, it's been 7-9 hours and no sign of flickering yet. I really hope this solved my problems as well as yours too.
I'll get back with the results of this "fix" after 24-48h, just to confirm that everything is Ok !
Sent from my Nexus 9 using XDA Free mobile app
Sorry, I accidentally double posted .
mihaicristian said:
Those are exactly the circumstances in which my tablet flickers !!!!
Anyways,...everybody just listen and hope this solves your problems too !
The main story :
I installer cm12...and it still flickered....so as a final resolution, I took off the back-cover.
During the removal, I made sure that the camera won't go off, BUT the important thing is that I accidentally unplugged a little-little cable found on the right upside of the tablet (when facing screen down = in the other corner from where the camera is found AND the tablet was held in portrait)
So...after re-plugging that tiny cable back on its port (I think that's what that little whole was named) and playing a little bit with the copper thingy..... I turned on the tablet (without the cover being attached) and it lit up with no problems or whatsoever. After that, I power it off (just to avoid any sort of short-circuit damages ) and put the back-cover.
I have to mention that I heard some sort of click in the up-center of the tablet while I was pressing it to make sure everything was reattached as initially (I think that maybe was the NFC antenna)
Finally, I powered the tablet on....and after charging it to 100% and installing all my apps, I ran Antutu benchmark just to make sure everything was ok. Surprisingly, it passed on without even the slightest sign of flickering.
To sum up : I think the problem was the NFC antenna, somehow interfering with the tablet OR it was that little cable I disconnected, but then reconnected back on.
Now, it's been 7-9 hours and no sign of flickering yet. I really hope this solved my problems as well as yours too.
I'll get back with the results of this "fix" after 24-48h, just to confirm that everything is Ok !
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I understand, the thing is that did not happen before and now if, which I think is HORRIBLE from HTC and Google to do that, I'll try the Stock and AICP be like going because I go back and repeat, I happen to be bloquela picture completely, is color WHITE or BLUE entire screen and then a super annoying SOUND, which only the button OFF let it down for 6 seconds passed, and then it goes but the crowd as he said it while riding levels low battery at 60% levels up does not, and at first either wrong, and ever since I've been dropped or the like.
So I'll be testing with a logcat to watch that event happens when the system be FROZEN, although I think it's hardware because it is illogical that in no battery HIGH levels and LOW pass if ..
juandiegofx said:
I understand, the thing is that did not happen before and now if, which I think is HORRIBLE from HTC and Google to do that, I'll try the Stock and AICP be like going because I go back and repeat, I happen to be bloquela picture completely, is color WHITE or BLUE entire screen and then a super annoying SOUND, which only the button OFF let it down for 6 seconds passed, and then it goes but the crowd as he said it while riding levels low battery at 60% levels up does not, and at first either wrong, and ever since I've been dropped or the like.
So I'll be testing with a logcat to watch that event happens when the system be FROZEN, although I think it's hardware because it is illogical that in no battery HIGH levels and LOW pass if ..
Click to expand...
Click to collapse
Please do so ! And for the record, my N9 had the same symptoms !
Well I've been back on stock for a week and all was going well, but I came home today to the boot lock screen. It had froze and rebooted at some point all on its own. It also had a lot of trouble booting back up. Slow, laggy, and proceeded to reboot 3-5 more times before ever getting back in to the home screen past the initial boot lock screen. At this point I have no idea what the problem could be (bad storage?) but its definitely a hardware issue and I will be talking to HTC about replacement soon.
juandiegofx said:
I understand, the thing is that did not happen before and now if, which I think is HORRIBLE from HTC and Google to do that, I'll try the Stock and AICP be like going because I go back and repeat, I happen to be bloquela picture completely, is color WHITE or BLUE entire screen and then a super annoying SOUND, which only the button OFF let it down for 6 seconds passed, and then it goes but the crowd as he said it while riding levels low battery at 60% levels up does not, and at first either wrong, and ever since I've been dropped or the like.
So I'll be testing with a logcat to watch that event happens when the system be FROZEN, although I think it's hardware because it is illogical that in no battery HIGH levels and LOW pass if ..
Click to expand...
Click to collapse
So..., the issue still persists, ALTHOUGH it is much more manageable on CM than on stock ROM. I think I'll wipe the device and try again with the back-cover, since that sort of settled things down a little.
Sent from my Nexus 9 using XDA Free mobile app
mihaicristian said:
So..., the issue still persists, ALTHOUGH it is much more manageable on CM than on stock ROM. I think I'll wipe the device and try again with the back-cover, since that sort of settled things down a little.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I am on stock ROM and I have the same issues! Did you find a way to fix it?
anx.go said:
I am on stock ROM and I have the same issues! Did you find a way to fix it?
Click to expand...
Click to collapse
Unfortunately not. I'm waiting for @juandiegofx to reply back to this thread and tell us if he could find something with logcat. I'll try logcat too during this weekend. Maybe I'll find something. I really hope it's not a big hardware issue (apparently, all the tracks lead to some sort of hardware problems).
Sent from my Nexus 9 using XDA Free mobile app
mihaicristian said:
Unfortunately not. I'm waiting for @juandiegofx to reply back to this thread and tell us if he could find something with logcat. I'll try logcat too during this weekend. Maybe I'll find something. I really hope it's not a big hardware issue (apparently, all the tracks lead to some sort of hardware problems).
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Mate, I have not flashing to the original firmware Nexus 9 or any CM12, because I been trying to SimpleAOSP yet, have you conrruencias see and then as now not returned happen to me, I have not seen reason but as I said always happens when I have less than 50% of battery and has started some relatively heavy title, I put my son play and as active logcat to identify hardware ... but everything points, discupa not report me before.
>3 days without flickering !!!
I took off the backcover again...played a litiile with thr battery cable this time.....and that's really all i did. Also I stayed on CyanogenMod and dirty flashed almost every nightly.
To sum up, my issue seems resolved. I'll get back here if something goes wrong
Sent from my Nexus 9 using XDA Free mobile app