If your slow on this freshly official installed froyo do this trick. Its a bit buried on this forum so its a bonus for those who haven't come acroos it.
Switching from landscape to portrait takes about 5 senconds. Heres the fix. Its not my find so don't bite my head off! (ducks)
Go to settings, display. Scroll all the way down to "Horizontal Calibration". Place your phone on a level surface that has a ledge. I used my window ledge on my room. Place the phone flat on its face. Lcd screen facing the surface. You should be looking at the battery cover. Not place it so the bottom half of the screen sticks out a bit from the ledge so u can hit the calibration button on the screen. Once it does its calibration, DONE! Fixed gsensor 5 second lag!
MOD EDIT: Added credits for you. Next time, do it yourself!
Original credits to abrognlie here: http://forum.xda-developers.com/showpost.php?p=11552644&postcount=163
and styckx here: http://forum.xda-developers.com/showthread.php?t=964866
Awesome, never knew that and it does work. Thanks!
Thanks. Just tried it and it works.
Sent from my SPH-D700 using XDA App
totally works!!!! but edit ur post cuz it says NOT instead of NOW lol
betterment66 said:
totally works!!!! but edit ur post cuz it says NOT instead of NOW lol
Click to expand...
Click to collapse
Done. Swipe suk0rs. But its the best. Lol.
Lol! Thats why I ducked. I knew I was going to get chewed up for not posting the credits.
Worked great, thanks.
Sent from my SPH-D700 using XDA App
you know, I think I just figured something out. A while back when the first leaks of froyos came out, some people were having gsensor lags while others were not. I was one who did have a bad laggy gsensor. And I noticed that my windows xp machine would sometimes detect my phone with odin and other times it would not. Then one day when I was going to flash, my pc did not detect it. I grabbed the phone while still being connected to the usb line and flipped it to remove the battery cover. When I flipped it to remove the battery cover my pc made a ding noise and "walla!" , odin detected my phone again. Then I assumed my epic had a bad wiggly usb port on my epic. But it wasnt! When I removed the battery cover and flipped it over lcd screen up, odin dropped the connection. I noticed the pattern right there and then.I was successfully able to make odin detect and not detect my epic by just flipping the phone screen facing up and then screen facing down. That explains why some people are flashing and then have a working gsensor while others, it's broken after a flash. The gsensor has some relationship with the hardware and software in the flashing process. In such a way that it gets calibrated after a flash depending on how the phone is laid down while its being flashed.
Everyone, do this simple test. Next time you odin or use the new samsung tool to flash, lay the phone down with the screen facing the surface and battery door facing up towards your view. Let it flash and see if your gsensor works flawlessly. I bet it will.
So in a nutshell. Flashing screen facing down gives you a good working gsensor. Flashing screen facing up gives you a broken laggy gsensor.
abduljaffar said:
you know, I think I just figured something out. A while back when three first leaks of froyos came out, some people were having gsensoe lags while others were not. I was one who had it. And I noticed that my windows xp machine would sometimes detect my phone with odin and other times it would not. Then one day when I was going to flash, my pc did not detect it again. I graded the phone and still connected to the usb line, I flipped it to remove the vary cover. And my pc made a ding noise and "walla!" , odin detected my phone again. Then I figured its a bad wiggly usb port on my epic. But it wasnt! I flipped it over lcd screen up and odin dropped the connection. I was successfully was able to make odin detect and not detect my epic by just flipping the phone screen facing up and then screen facing down. That explains why some people are being a working gsensor while others it's broken after a flash. The gsensor has some relationship with the hardware in such a way that it gets mia calibrated after a flash depending on how the phone is laid down.
Everyone, do this simple test. Next time you odin or use the new samsung tool to flash, lay the phone down with the screen facing the surface and battery door facing up to your view. Let it flash and see if your gsensor works flawlessly. I bet it will.
So in a nutshell. Flashing screen facing down gives you a good working gsensor. Flashing screen facing up gives you a broken laggy gsensor.
Click to expand...
Click to collapse
You know this actually does make alot of sense.
I calibrated mine face down and it is fine now, but I hope somebody else can give this a shot for you.
and mine refuses to work, switches to landscape when face down and leaves me in landscape mode when facing straight up. Tried to do it with auto rotate off and it wont switch to landscape now. Starting to hate this phone.
tenaciousj said:
and mine refuses to work, switches to landscape when face down and leaves me in landscape mode when facing straight up. Tried to do it with auto rotate off and it wont switch to landscape now. Starting to hate this phone.
Click to expand...
Click to collapse
If you are rooted you can use a terminal to run:
/system/bin/sensorcalibutil_yamaha
You have to do it as su though.
bjhill2112 said:
If you are rooted you can use a terminal to run:
/system/bin/sensorcalibutil_yamaha
You have to do it as su though.
Click to expand...
Click to collapse
Just did it, seems snappier but not really fast by no means.
bjhill2112 said:
If you are rooted you can use a terminal to run:
/system/bin/sensorcalibutil_yamaha
You have to do it as su though.
Click to expand...
Click to collapse
for some reason my terminal program isn't asking for superuser permission. what terminal do you use?
The face down horizontal calibration worked for me, on stock EB13. Rotates in less than half a second, it's pretty quick.
The terminal trick stopped working for me for some reason :/ I've always used connectbot, once you su the first time it doesn't ask for root anymore after that.
murso74 said:
for some reason my terminal program isn't asking for superuser permission. what terminal do you use?
Click to expand...
Click to collapse
I used connectbot
murso74 said:
for some reason my terminal program isn't asking for superuser permission. what terminal do you use?
Click to expand...
Click to collapse
Just type "su" at the console
If the upside down calibration dont work, root and do the command line stated above a few post.
Related
Hello all, im still having issues with my touchscreen being i guess mapped incorrectly or sometimes hardly working at all. The more i think about it the more i have to think it can be fixed and also i think about anything that could have happened to the phone b4 it started acting up and there was nothing, not a drop or hit. The only thing i can put on the same timeline is right after i installed lockbot is when it started acting up, is this by chance only or is there a chance lockbot modifies a file that could affect the touchscreen? Any help with this or even ideas would be great. Thanks, veritas
Ps...also after searching google for a few days i noticed a good bit of people posting that they had diff issues after installing a couple diff lockscreen apps, the only issue is that they are all only open post with zero responses to point in the right direction. Thanks
This happened to me too after installing lockbot.
I'm gonna try to reinstall the firmware and will get back with the result.
Currently it just comes and goes .. mostrly comes.. The bottom part of the screen doesn't work at all, and the sliding seems to work harder. Also, when I type a message in landscape, I press a key, and another one is actually shown to be pressed.
I also tryed different versions of lockbot, 1.8 and 1.13 before the touchscreen sarted to have problems, but when it actually happened, I had version 1.8 installed and it froze when I was using it.
Just reinstalled originial firmware, and problem didn't go away.. this is starting to get serious..
i seriously doubt it's related to lockbot. many people use it with no issue.
yeah.. lockbot might have been a coincidence.. I realized that I was using a different charger (not the original one) when using the phone when this problem appeared, and this seems to be consistent with the problem.
Actually I was charging the phone from the usb port of the computer, using also an USB extender.
I'll take the phone to waranty .. I tryed removing the battery and not using it for a day, leaving it to use up all the battery.. no success.
I think that there may be some wild static running through the phone from when I charged it off the usb.
If I play with the phone a lot now, sometimes the bottom part works bot not the top part.. and sometimes, I can press something on the screen just by hovering the thumb over it.
I'm getting the same problem! I press at the bottom of the screen and it selects something in the middle or nothing at all and at the home screen I won't even touch the scrren just hover my thumb over and the screen responds like its trying to go to the next screen but then gets stuck in the middle.
I called t mobile and they said to soft reset or hard reset, did both and no fix.
-------------------------------------
Sent via the XDA Tapatalk App
It's definetly a hardware issue.. it's sad that these touchscreens are so sensitive to the charging currents..
I would have imagined that they would have added some protection for this ..
btw, it's not just a htc hero problem, the web is full with all types of touchscreen phones being afected when using non original charger.
Paticakeman said:
I'm getting the same problem! I press at the bottom of the screen and it selects something in the middle or nothing at all and at the home screen I won't even touch the scrren just hover my thumb over and the screen responds like its trying to go to the next screen but then gets stuck in the middle.
I called t mobile and they said to soft reset or hard reset, did both and no fix.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
That's ALL T-Mobile knows how to do. Reboot your phone or reset your phone. If that doesn't work, they tell you its broke. Anyone could do that job.
alex_g_cl said:
It's definetly a hardware issue.. it's sad that these touchscreens are so sensitive to the charging currents..
I would have imagined that they would have added some protection for this ..
btw, it's not just a htc hero problem, the web is full with all types of touchscreen phones being afected when using non original charger.
Click to expand...
Click to collapse
ANY phone gets affected when using a different charger. People don't stop and look at the voltage of the new charger and leave their phone on it for 10 hours even though it's charged.
You can't protect from stupidity. Not saying any of YOU are stupid, but seriously, don't give your phone 100 volts when its made to receive 12.
I quess that ppl that use non-original chargers would read the voltage output..
Like I said above.. I just used the usb port from the computer to charge, if this is wrong, maibe they should have disabled it
It's definetly a hardware issue.. it's sad that these touchscreens are so sensitive to the charging currents..
I would have imagined that they would have added some protection for this ..
btw, it's not just a htc hero problem, the web is full with all types of touchscreen phones being afected when using non original charger.
Click to expand...
Click to collapse
I was saying here that other parts of the phone are just fine.. if there is a problem with the charger, why doesn't the whole thing brake.
I have a developer unlocked Focus that is currently running 7004. It was dropped in water and I assumed it did not work as all it would give on boot is the connect to PC icon.
Earlier today I was thinking "Hey I should get a second battery" Well I remembered that other 'broken' Focus and I plugged it in. Mistakenly I was holding the camera button as it took a picture and brought me to the camera screen. This allowed me to exit and browse through the phone as normal. Everything worked as normal (Aside from there being no SIM) I could even browse the marketplace.
I decided to test the apps to see if they'd work first Facebook (no good couldn't update stuff even though I was on WiFi) and twitter. After writing a tweet the phone locked up and reverted to the connect to PC screen. Now the hardware buttons do not respond (Back, Home, Search, Camera will focus but won't take picture)
Short version:Now whenever I boot up it goes to the connect to PC screen. If I connect the phone to a PC it just keeps rebooting itself. The hardware buttons do not respond if I do the reset command. (Back, Home, Search, Camera will focus but won't take picture)
Question: Is it possible to fix this issue of infinite boot and have a normal phone again?
Phone specs
Unlocked
ATT Focus
No MicroSD
Version is 7004
If the hardware hasn't been affected you can try a reflash with one of these ROMs. If you can still do that. Plus a hard reset.
From what you have described, I can't tell for sure what is wrong (soft, hard or both). Hopefully none.
The fact that the phone worked, suggests that part of the software is working. The hardware seems ok, so if you're lucky enough the phone might work with a reflash.
What I recommend, before you reflash, considering it was dropped in water, is make really sure it's dry. I hope you removed the battery quick enough as that usually damages the phone if left in, afterwards.
I've heard various methods, and I know 2 that work:
- remove the battery and the cover and find a warm/hotter and dry place (not too hot) and put the phone there, over a towel and in between the phone and the towel, kitchen towel. The idea is to heat the phone slightly. DO NOT use a microwave or a blow dryer or fire. A good example is over an electric blanket, at lowest power (+towel, +paper towel).
- dry rice. immerse the phone completely in dry rice (batt/cover removed) and leave for 24h
So when I flash the device it comes up with a connect to PC screen. However the flash does complete the entire process. Zune then starts running but says restoration fails.
EDIT: I don't think this phone is good to work anymore.
Picture of Zune error: http://imageshack.us/photo/my-images/98/erroron.jpg
Mister Locke said:
So when I flash the device it comes up with a connect to PC screen. However the flash does complete the entire process. Zune then starts running but says restoration fails.
EDIT: I don't think this phone is good to work anymore.
Picture of Zune error: http://imageshack.us/photo/my-images/98/erroron.jpg
Click to expand...
Click to collapse
Did you re-flash the firmware or you only tried to restore from Zune?
The flash process doesn't involve Zune...
I reflashed the phone and then it reboots itself. First with the screen with the red arrow. Which is supposed to happen. Then it reboots itself again and Zune boots up, giving me that error. It then returns to the connect to PC screen once again no matter how many times it is rebooted.
EDIT: Would it matter which AT&T ROM I used to flash it with?
Mister Locke said:
I reflashed the phone and then it reboots itself. First with the screen with the red arrow. Which is supposed to happen. Then it reboots itself again and Zune boots up, giving me that error. It then returns to the connect to PC screen once again no matter how many times it is rebooted.
EDIT: Would it matter which AT&T ROM I used to flash it with?
Click to expand...
Click to collapse
Hmmm.
Here's an Omnia 7 guide, but should apply to the Focus as well (evidently, with Focus ROM/binaries from Samsung-i917-Focus-firmware-UCJK2-ATT-USA.exe)
I suppose you followed it. If that's the case then your hw might be affected...
Yeah I followed that exactly. I'm guessing the hardware is affected and can't be used anymore. Guess the one time I used it was a fluke. XD Oh well. So much for having two Samsung Focuses.
Mister Locke said:
Yeah I followed that exactly. I'm guessing the hardware is affected and can't be used anymore. Guess the one time I used it was a fluke. XD Oh well. So much for having two Samsung Focuses.
Click to expand...
Click to collapse
I think you should ask Heathcliff74 (PM him), maybe the problem is that one of the steps just doesn't complete and maybe there's a way to force that, or there might be more you can try.
Anyone has this problem? When I put my finger on the touchscreen, screen moves up and down like crazy. It gets worse when I move my finger to the side of the screen.
I tried different roms, different kernels, nothing fix this.
Only when using the touchsentivity app and changing the value to any value and clicking apply makes this behaviour disappear for a moment.... after locking the phone and awake it, same thing happens again.
It drives me crazy because I always put my finger on the screen when reading something.. or in some apps or games when I need my finger stay on the screen it gets annoying. .
VIDEO
http://www.youtube.com/watch?v=dMffYq8styM
This isn't normal. If you can't solve this problem with a factory reset, get your phone exchanged or repaired.
Sent from my Desire HD using XDA App
That's what my HD2 used to do. Couldn't type anything on it to save my life. Think I'm gonna have to check my SG2 now I've seen your vid.
Thats probably because the custom kernel your using has a different value for it and the app is setting up 5, try it with a stock kernel and perform a factory reset and see if the issue still occurs w/o changing the TSP value.
I got the same problem. I do that sometimes too.. scrolling up and read while holding my finger down, it just jitters or something.
You're not the only one, but not sure how widespread this problem is or if it is normal or not..
Mine is also jerking when holding the finger out at the edge lol, looks retarded
Sent from my GT-I9100 using Tapatalk
Interesting...so if I disable the touchscreen fix the problem goes away. If I reinstall it, no matter what the settings are, I get the jittering effect at the very corner of the screen.
Tri3Dent said:
I got the same problem. I do that sometimes too.. scrolling up and read while holding my finger down, it just jitters or something.
You're not the only one, but not sure how widespread this problem is or if it is normal or not..
Click to expand...
Click to collapse
Yep I got same problem, when reading and holding down on the screen it does the same.
On Litening Rom 1.5 cant remember if it happened on stock rom though
I get this too, my SGS did it as well.
I tried this multiple times on the edge and it does not jitter at least on the phone that I have.
Mine did this when it was plugged into the mains (using a non-samsung) charger. Does not do it when plugged in via USB or on battery.
Is yours plugged in?
So some have it, some not?
I always had this thing, since KE1.. now on KG5. Stock kernel, custom kernel, rooted or not rooted doesn't matter.
Also, it has nothing to do with the touchsentivity app. The app even fixes it temporary when applying a new value, but it re-appears when locking-awaking the phone. (I tried to enable the service option on the app, so it will apply the value everytime I awake the phone, but this does not work)
I just tried it when plugged in in the changer, it seems to do the opposite... when plugged in I don't have this effect anymore. Once plugged out it starts again.
I also have SGS1.. this does not happen.
gusoldier said:
So some have it, some not?
I always had this thing, since KE1.. now on KG5. Stock kernel, custom kernel, rooted or not rooted doesn't matter.
Also, it has nothing to do with the touchsentivity app. The app even fixes it temporary when applying a new value, but it re-appears when locking-awaking the phone. (I tried to enable the service option on the app, so it will apply the value everytime I awake the phone, but this does not work)
I just tried it when plugged in in the changer, it seems to do the opposite... when plugged in I don't have this effect anymore. Once plugged out it starts again.
I also have SGS1.. this does not happen.
Click to expand...
Click to collapse
So how has this worked out for you? I have this too but just a little bit less. It also stops for me when plugged in. I wen't back to the store with it but saw that the shop model had the problem too so I decided to not return it. How about you?
I checked and it appers that i have i too. Didnt notice it till now.
It is occuring only on the left side when holding my finger.
I did not notice it too...and yes, mine is "Jerky" too...
Mine is fine, so looks faulty to me.
Sent from my GT-I9100 using Tapatalk
weird left side
I have to say this happens to me too but only when at the VERY edge of the screen,on the left.
There is something very weird about the left side of the phone.
1. the touch issue
2. the yellow tint
3. the glass is more raised than the right side(check it out) its like there is less bezel showing on the lower left part of the phone than the right side. I've checked 3 s2s and they all had it.
I have this all over the screen but not as bad as on the left side. Could someone install note everything and make a paint note with the smallest brush. Then try to make some straight lines (without the phone being connected to the a/c). Draw them really slowly from the left to the right. Mine usually jumps 1 pixel up and/or down and is a bit wavy (which isn't normal for touchscreen phones cause I tried the same thing on my friend's optimus 2x and the lines where as straight as could be). Maybe if you guys make a screenshot (home button+lock button) we could compare them and see if there is really a problem with specific phones or with the Galaxy line in general.
This was something I noticed when I first got the phone, if I kept my finger on while browsing, it would "shake" and be extremely annoying. Same thing happens when you hold an application in the left corner of the screen.
If my phone is charging, the problem is gone! It's smooth, and doesn't "shake".
Soon as the charger is removed problem is back
Going to return this tomorrow and see if they'll exchange it.
Just another 'my phone is red, yellow screen thread'. Does it affect your day to day usage? If it does,i too is concerned.if not, then what's the point in looking for non measure issues? This issue was up like 4 months ago and now, back. Y'all just return your phones and close annoying threads.
Sent from my GT-I9100 using xda premium
phone was working fine but from last two week the screen starts moving automatically, Wi-Fi turns on automatically at any time. the install button of Google play doesn't work (seems like touch issue) but when i touch the same spot with camera application, it works fine. i am on stock ROM (4.4.2, kernel 3.4.0, KOT49l ) and tried resetting the phone multiple times but facing the same issue.
please help me resolving this issue.
regards.
Just flash the firmware again !!
-iNCEPTiON- said:
Just flash the firmware again !!
Click to expand...
Click to collapse
These are not software problems (dead touchscreens spots), your knock on will not working. It's hardware issue, I think you need sending it back to LG
bluesky2307 said:
These are not software problems (dead touchscreens spots), your knock on will not working. It's hardware issue, I think you need sending it back to LG
Click to expand...
Click to collapse
You are just scaring ppl .. You said that my phone has probblem too .. So just dont scare ppl .. and try to help them..
i had this kind of issue with my other phone, I just downgraded to Jelly Bean and it worked fine ... and did the touch drivers update from the hidden menu 3845*#802# ...
i think you have a dead section along the top of your screen, about half an inch down. Its been fairly common. Its not real noticeable at first , bc that area of the screen isnt used often, but its EXACTLY where the play store install button is, and your knock on will no longer work. you need a new screen. or flip it to landscape whenever (seldomly) you need that area of screen. you can test it by getting LCD tester from the playstore , or by using quickmemo to draw on your screen.
findinghomer said:
i think you have a dead section along the top of your screen, about half an inch down. Its been fairly common. Its not real noticeable at first bc that area of the screen isnt used often, but its EXACTLY where the play store install button is, and your knock on will no longer work. you need a new screen. or flip it to landscape whenever (seldomly) you need that area of screen. you can test it by getting LCD tester from the playstore , or by using quickmemo to draw on your screen.
Click to expand...
Click to collapse
This happened to me exactly, about a month back. It seems to be right across where the 2nd from the top messages are. You can download YAMTT https://play.google.com/store/apps/details?id=com.rn.yamtt&hl=en
I use the PAINT option and move my fingers around the top. It was a solid strip out near the top. Knock On will no longer work, but Knockoff will.
findinghomer said:
i think you have a dead section along the top of your screen, about half an inch down. Its been fairly common. Its not real noticeable at first , bc that area of the screen isnt used often, but its EXACTLY where the play store install button is, and your knock on will no longer work. you need a new screen. or flip it to landscape whenever (seldomly) you need that area of screen. you can test it by getting LCD tester from the playstore , or by using quickmemo to draw on your screen.
Click to expand...
Click to collapse
when i touch the same spot with camera application, it works fine.
cheekugr8 said:
when i touch the same spot with camera application, it works fine.
Click to expand...
Click to collapse
that could be because the camera button has more "active area" meaning, it will still work if you tap near but not exactly in the same location. the install button on the play store is very very precise. if your knock on does work, then its probably just software. but if your knock on does not work, i recommend testing the hardware with quick memo.... draw lines all the way up and down your screen slowly, and see if there is a break in that area. if its not the screen, unroot, and go all the way back to stock
i don't know how but it has started working automatically form last 10 minutes and google play button is now accessible.
i hope it wont give that error again.
thanks for all good suggestions.
cheekugr8 said:
i don't know how but it has started working automatically form last 10 minutes and google play button is now accessible.
i hope it wont give that error again.
thanks for all good suggestions.
Click to expand...
Click to collapse
In developer options. Tick Show Touches option. you touch any area on touch screen and check dead zone or using Quick memo
Hi all,
I have a major problem with my Samsung galaxy tab 4. When I power on the tab sometimes it will hang on the splashscreen.
Then if and when I get through the frozen splashscreen the screen will flicker extremely badly, almost like interference and will freeze.
I done a factory reset, disconnected the battery, still the same issue.
Any ideas what the issues are?
Thanks in advance
skalicioustimes said:
Hi all,
I have a major problem with my Samsung galaxy tab 4. When I power on the tab sometimes it will hang on the splashscreen.
Then if and when I get through the frozen splashscreen the screen will flicker extremely badly, almost like interference and will freeze.
I done a factory reset, disconnected the battery, still the same issue.
Any ideas what the issues are?
Thanks in advance
Click to expand...
Click to collapse
I would find the correct firmware for your tab (from the Samsung site) and reflash the full Odin tar. If that doesn't help I'd contact Samsung about the issue.
Is there any point in getting in touch with Samsung after opening the tablet up?
There is horizontal and vertical lines approximately 5mm apart, coloured.
I can see the logo behind these lines but and the whole system has frozen.
This still happens after a factory reset which makes me think it may be a hardware issue.
Would it be a digitizer issue?
skalicioustimes said:
Is there any point in getting in touch with Samsung after opening the tablet up?
There is horizontal and vertical lines approximately 5mm apart, coloured.
I can see the logo behind these lines but and the whole system has frozen.
This still happens after a factory reset which makes me think it may be a hardware issue.
Would it be a digitizer issue?
Click to expand...
Click to collapse
That would be your display, not your digitizer. since you're thinking of opening the tab, check the connector
to the board from the display screen, just be patient, steady handed, and keep a light touch.
use a magnifying glass of you can't see the layout clearly, the connector may be seated wrong/crooked
there should/may be clips on either side that need to be slid out before disconnecting the ribbon.
I would get a replacement if you haven't opened the tab already.
questions belong in q&a. :good:
m
just a thought, check for moisture/corrosion anywhere, at the point you open the device, you're pretty
much S.O.L. but hey.
Yes unfortunately the Tab 4 has been opened.
By disconnecting and reseating the battery sockets i believe the warranty is void. The back has been opened.
I find if i get the device running momentarily then by gently plexing "twisiting" the unit in my hands can cause the screen to switch back to normal.
But soon after the dreaded horizontal and vertical lines appear then the device becomes frozen again, the intermitent lines jump around the screen with whatever is in the background leaving the display frozen.
Only solution is to gently open up the device and disconnect the battery and then reconnect again.
This is only a temporary solution as the problem reappears very soon after.
moonbutt74 said:
That would be your display, not your digitizer. since you're thinking of opening the tab, check the connector
to the board from the display screen, just be patient, steady handed, and keep a light touch.
use a magnifying glass of you can't see the layout clearly, the connector may be seated wrong/crooked
there should/may be clips on either side that need to be slid out before disconnecting the ribbon.
I would get a replacement if you haven't opened the tab already.
questions belong in q&a. :good:
m
just a thought, check for moisture/corrosion anywhere, at the point you open the device, you're pretty
much S.O.L. but hey.
Click to expand...
Click to collapse
So you reckon it is not the digitizer that has failed? I was thinking of replacing that.
Hmmm..
skalicioustimes said:
So you reckon it is not the digitizer that has failed? I was thinking of replacing that.
Hmmm..
Click to expand...
Click to collapse
I'm not so sure after what you said about twisting the tab, can you get into the system through adb ?
After the tab "freezes" hook up to your comp and get adb shell running, run any/all of the following
logcat -d
mount
ps
dmesg
and do some directory hopping to see what you can access, reason being we narrow it down to display/digitizer/something loose on board.
just to refresh my memory, the same behavior occurs in recovery ?
also tap your power button to screen-off/lock.
and at the end after adb test, force reboot to recovery with button combo.
m
moonbutt74 said:
I'm not so sure after what you said about twisting the tab, can you get into the system through adb ?
After the tab "freezes" hook up to your comp and get adb shell running, run any/all of the following
logcat -d
mount
ps
dmesg
and do some directory hopping to see what you can access, reason being we narrow it down to display/digitizer/something loose on board.
just to refresh my memory, the same behavior occurs in recovery ?
also tap your power button to screen-off/lock.
and at the end after adb test, force reboot to recovery with button combo.
m
Click to expand...
Click to collapse
I'm unsure about your suggestions, as i don't know were to locate those commands.
I have done a factory reset, so i am just waiting for the device to charge before attempting to load new firmware through Samsung Kies which i downloaded through this link... http://www.samsung.com/uk/support/usefulsoftware/KIES/#versionInfo
are the commands you suggested within the Samsung Kies software?
ahh, no. You need to run adb on windows [ewww]
or adb on linux [yay!]
can't help you with windows.
but what about in recovery ? did you encounter the same issue or no ?
m
moonbutt74 said:
ahh, no. You need to run adb on windows [ewww]
or adb on linux [yay!]
can't help you with windows.
but what about in recovery ? did you encounter the same issue or no ?
m
Click to expand...
Click to collapse
When i was having the problems initially, i could not for the life of me get into recovery mode using the button combo's. Eventually i did get into recovery, so as a last resort i cleared cache, and done a factory reset. Now it is booting up as normal but i was going to use Kies on windows to see if it is a software issue.
So were do i go about getting
adb
logcat -d
mount
ps
dmesg.
And what would you suggest as a step by step guide from were i am at now?
Note: i haven't physically messed with the device to see if the Horizontal and Vertical screen issue is still there.
Thanks
XDA search bar
adb install
moonbutt74 said:
XDA search bar
adb install
Click to expand...
Click to collapse
i tried running adb but i'm getting unaturiosed, clicked on the revoke debugging and then adb just ran through all the commands.
then the device screen problem has arisen again and i can't get it to boot.
skalicioustimes said:
i tried running adb but i'm getting unaturiosed, clicked on the revoke debugging and then adb just ran through all the commands.
then the device screen problem has arisen again and i can't get it to boot.
Click to expand...
Click to collapse
You're not supposed to revoke adb debugging.
Look, i'm at a loss, the thing is, do you blow more cash on a quess, or cut your losses.
As to learning how to use adb, XDA searxh box, using adb.
m
not a bother.
thanks for your help :good:
skalicioustimes said:
not a bother.
thanks for your help :good:
Click to expand...
Click to collapse
Hi,
you're not bothering me, i'm just saying you have to jump in all the way. :good:
m
moonbutt74 said:
Hi,
you're not bothering me, i'm just saying you have to jump in all the way. :good:
m
Click to expand...
Click to collapse
ah i understand, it's just it's driving me crazy. a bit like a crossword puzzle that i can't finish and i'm looking for someone to give me the answer without me having ta look up the answer in a dictionary....hahaha.
i suppose i am looking for someone who had a similar problem, a few clicks here and there
skalicioustimes said:
ah i understand, it's just it's driving me crazy. a bit like a crossword puzzle that i can't finish and i'm looking for someone to give me the answer without me having ta look up the answer in a dictionary....hahaha.
i suppose i am looking for someone who had a similar problem, a few clicks here and there
Click to expand...
Click to collapse
dude are you on hangouts ? if so pm me.
moonbutt74 said:
dude are you on hangouts ? if so pm me.
Click to expand...
Click to collapse
sent you a message on hangouts. thanks
Flashed the stock kernel using Odin, i hope that gets rid of the screen issue :fingers-crossed:
Well 3 hours later and the Tab is going good
My daughter is delighted that it's sorted and she hopes it stays that way
Many thanks to Moonbutt74 for your time and effort, it's very much appreciated.
Would you say that it's good to go? And is there anything else i need to do to the device before handing it over to her?
Cheers