I apologize if this has already been hashed out, but I have combed through the archives and didn't find any solutions.
I got my Tab last July. Right out of the box, it had some sort of screen issue... if I move it physically at all, the screen freezes and the touchscreen is unresponsive. I have to hit the power button off/on to get things moving again. It happens all the time, and basically makes it unpleasant to use.
This unit is unrooted, and has all the stock updates. Do you think rooting and trying a new ROM might fix my problem?
I've been trying to submit a repair request through Samsung, and it will not recognize my serial number.
We also have a Viewsonic G-Tab and a Nook Color, both rooted. It's frustrating when the tablets that cost half of what mine did work so much better...
Thanks so much for any and all help; I'm kind of at a loss these days.
Have you factory reset it? No success? If so, take it back to where you purchased it if you can. That's likely sounds hardware related.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Looks like its hardware issue, the sensors arent reading your touch
Related
Last month, buy a ViewPad 10s. Great device. Thanks to this forum I can install the market and install many things. Until one day, after seeing a movie (Mobo player) I started missing the touch screen. I could not even unlock it!. I turned it off and set aside. The next day started as if nothing had happened. But with the passing of a few days, began to fail often, and not resolved by switching off. Until today that is totally screwed. Not react as it should, and I can not access at all to any of the functions. Here's a short video of what I'm telling you.
(search in youtube "viewpad 10s touch screen problem", the one from chgalvez user)
I've tried calibrate.ini, and almost all .apk calibration apps that are in the forum. I've try as last chance to upgrade with an official rom from viewsonic(1.09), but dont' work neither.
Anyway I think I can't prove anything more as the touchscreen almost no response at all.
Anyone have an idea if there a method to calibrate from the outside, with a USB cable or something?
thanks in advance and sorry for my english...
Wish I could help, but you are posting in the VPAD7 forum - the hardware & firmware are different - you need to go to the Viewsonic Gtablets forum (10" screen size) as folks over there should be better able to help you.
Assuming you are running unrooted device & stock/OEM ROM's - correct?
Best of luck !
Oh, OK, thanks! the device is rooted( z4root method, OK in 1st chance, no problems) and the Fw is an original upgrade from viewsonic....
Sent from my MB525 using XDA App
hi guys.
I *Believe* I have a faulty touchscreen on my S2.
Symptoms:
- mostly on resume, but sometimes in use screen becomes choppy
- apps are not particularly slow to load
- no pattern to it
- I ran *#0*# and did the touch test, and indeed touches are detected all over the place or not in a straight line if running finger down the glass.
- problem solves itself.
today I captured using ADB what kmsg said, listed below. I just bought a jig, so hopefully samsung should accept a return on it if needed. pls advise if you see something, could not find anything on the interweb.
thanks a lot.
interestingly, firmware version shows: 0x16 0x16, and touch key fw shows 0x4 0x7. I think these are errors?
this was an ebay purchase, so is there a chance they've been screwed up in some way before I got the phone? thanks so much.
getting desperate, so have run TSP firmware update, and watching the results on ADB.
there is immediate differences, and the TSP is not suffering the repeated re-cal's...
monitoring now.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
not fixed
ordered jig from ebay, going to get it repaired under warranty I hope.
just followup. With a little coercement the service centre changed the screen and it works beautifully now.
I fell briefly in love with nitr8's insanity ii ROM. However, after plugging in my phone to Wall charger overnight, I woke up to find my phone was OFF. Power button did turn things back on.
Searching the forums for other's similar pain scenarios leads to some generic domains of possible cause:
Buggy Kernel
Bad Apps
Wrong Modem
Bad HW (RAM)
I briefly became excited about the prospect of running logcat, then saw several 'random re-boot' related posts where the logcat trail goes cold after a hard power down.
Surely, there must be some diagnostic procedures that can point to a root cause.
Is there a RAM HW diagnostic utility...get that question out of the way, for example. (I don't think doing the standard *#0*# test covers RAM ;-) )
I have read through nitr8's entire insanity ii thread and I haven't found any posts about random reboots or power-down there.
I would have posted my query and offer to recompense any blatant stupidity with vast sums of beer, however forum rules require that I ask my 10 stupid questions in the non-developer area first.
I don't expect a free lunch. I'm happy to work for an answer. If somebody can point me to a guide or reference / process that I've missed, I'll be very happy to read up and hang my 'suck at teh search' head in shame.
What I can say from the sampling of Galaxy S2 folks where random rebooting is the source of pain and frustration, is that no clear process was arrived at for determining root cause...mostly luck and re-flashing the double flash Dalvik type responses...or try this modem or that kernel....
I've restored my phone using CWM to the pre-insanity ii state because it hasn't re-booted or powered down (yet) with that build. The attachment reflects where its at right now...in case this is of interest.
v.vibrate(ANNOY said:
I fell briefly in love with nitr8's insanity ii ROM. However, after plugging in my phone to Wall charger overnight, I woke up to find my phone was OFF. Power button did turn things back on.
Searching the forums for other's similar pain scenarios leads to some generic domains of possible cause:
Buggy Kernel
Bad Apps
Wrong Modem
Bad HW (RAM)
I briefly became excited about the prospect of running logcat, then saw several 'random re-boot' related posts where the logcat trail goes cold after a hard power down.
Surely, there must be some diagnostic procedures that can point to a root cause.
Is there a RAM HW diagnostic utility...get that question out of the way, for example. (I don't think doing the standard *#0*# test covers RAM ;-) )
I have read through nitr8's entire insanity ii thread and I haven't found any posts about random reboots or power-down there.
I would have posted my query and offer to recompense any blatant stupidity with vast sums of beer, however forum rules require that I ask my 10 stupid questions in the non-developer area first.
I don't expect a free lunch. I'm happy to work for an answer. If somebody can point me to a guide or reference / process that I've missed, I'll be very happy to read up and hang my 'suck at teh search' head in shame.
What I can say from the sampling of Galaxy S2 folks where random rebooting is the source of pain and frustration, is that no clear process was arrived at for determining root cause...mostly luck and re-flashing the double flash Dalvik type responses...or try this modem or that kernel....
I've restored my phone using CWM to the pre-insanity ii state because it hasn't re-booted or powered down (yet) with that build. The attachment reflects where its at right now...in case this is of interest.
Click to expand...
Click to collapse
Morning v.vibrate(ANNOY, 0),
The way I would take it is in stages,
a) do you have random reboots on other roms? i guess answer is no as you stated that above
b) flash ROM with insanity, restore just contacts and verify there are no random reboots
c) if no reboots go ahead and install your apps
d) if no reboots go ahead and restore all your settings
Report back as to where your reboots start.
I wold also need to know what kernel you on because 99% of the time i have seen this issue its kernel related.
Good morning. Thank you for responding to my query.
I will follow your recommendation to the letter and report back.
In the interest of providing some more background information, I did have a previous configuration that was rebooting prior to insanity ii.
I had been running VillainROM 3.0 with Ninphetamine 2.0.5 and Modem XXKI4. I experienced more than 1 random reboot that way. After that, I re-flashed the kernel to the speedmod one you can see in my previous post attachment and the phone has not had a re-boot with that configuration.
The configuration in the attachment has had 5 days total time (spread over non-contiguous intervals), so it's hard to say for certain. However, the experience I've had so far with swapping out the kernel tends to agree with the idea that re-boots / power down are mostly kernel related.
Finally, in the case of insanity ii, I ran with the 'stock' kernel that came with version 049. I cannot recall the name of that one...but it was cyanogen-based.
Thanks again for your reply and I will endeavour to be systematic and clear about symptoms and prior actions taken.
I really want this ROM to work for me...it's like they say, once you've had it you cannot go back! ;-)
np, start off with this:
Flash latest kernel - Latest Kernel
Flash latest rom - insanity ii cm 051
Monitor
So far, so good.
OK, so I followed your first two instructions to the letter. Flash Kernel, Install ROM. No problem.
Still no problem. I have not had 1 reboot or power down since yesterday evening at 18:00 GMT.
No, I must confess that in an orgy of non-compliance, I've installed many many things. I will try to attach list of screen shots.
I am not sure I expect this to be very helpful or useful. Perhaps I am hoping you may say something like "ooooh, be careful with that dog...it will bite you..." or some such thing.
I will also add that should the power-off come back, I'll start from 0 as instructed and blame myself for wasting time.
On a final note, I think it's been covered before, but trying to use the Video camera is an almost instant FC.
Also, not much to do with your stuff, but I had some troubles with O2 and the KI4 modem:
http://forum.xda-developers.com/showthread.php?p=18994781#post18994781
If I discover any meaningful or useful information, I'll pass that along. I'm sorry if this has been a bit time wasting at present.
Well another day and still no lockup or power-down or any other malfunction.
v.vibrate(ANNOY said:
Well another day and still no lockup or power-down or any other malfunction.
Click to expand...
Click to collapse
Cool glad its sorted
Random Screen Shot of Homescreen...Stolen from Demvil
And it still runs stable...despite the theft and abuse. ;-)
v.vibrate(ANNOY said:
And it still runs stable...despite the theft and abuse. ;-)
Click to expand...
Click to collapse
looking good
Hey now.
I currently have an HTC Desire Z. I rooted it and have had several roms on it. Currently it's running the ICS rom Mexidroid Fried Icecream 3. It's great and I love it. It runs all the apps I use smooth, the keyboard rocks, the battery life is good enough and it basically does everything I want from a phone.
The problem is that the phone is shutting itself off at totally random times. It sometimes happens when I'm doing something, sometimes it happens when it's just laying on my desk. It seems 100% random. It just shuts off without warning and doesn't auto re-start itself. This happens with any rom installed. I tried all the the basic things like full wipe, format SD card etc, but it keeps happening.
Sometimes it happens 3 times in an hour, sometimes it doesn't happen for a week. When it works, it works great and I love it, but I can't really rely on it anymore which is a bit of a deal breaker.
Unless one of you fellas has one last golden tip for me (which I secretly hope because I'm still very happy with this phone), It looks like I'm in the market for a new phone.
My requirements are pretty simple:
Full QWERTY keyboard
Similar sized screen or bigger (3.7")
At least a dual core
Rootable
Compatible with GSM (I live in the Netherlands)
The Droid 4 seems pretty much the only realistic option for me. *edit* scratch that. Just found out it's not a GSM phone...
I saw in another thread here that there isn't much on the horizon in terms of new QWERTY phones, with is a bummer.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Sorry 'bout that, mods.
Anyone got any advice?
Advice
Sechzman said:
Anyone got any advice?
Click to expand...
Click to collapse
Sell it to someone without telling about auto shutdown and pray it goes off once in a week
My handset has been freezing for the past 3 weeks, it's gone back for repair twice and the freezing got worse and worse. The shop agreed to order me a refurb replacement - in the week and a half since I've been waiting the phone has slowly stopped freezing to the point where it just never happens any more. I think this was what some people referred to as the SDS freezing bug. I let the freezes continue without rebooting my phone and that seems to be what's fixed it.
My replacement is due on Wednesday. It seems to me highly unusual that a phone can fix itself (it's been reflashed loads and factory reset even more) - do you think my phone could be considered reliable now or should I go for the replacement. Of course, I'm just curious as to what you personally would do in my situation.
questions go in the questions section.
go for the replacement
Replacement... But still it's only a refurbishment be careful try and get a device without the dodgy emmc
Sent from my GT-I9300 using Tapatalk 2
Please read forum rules before posting!
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator