yashsingh1/xdaforums huggingface dataset:
[G Tablet General] hazkal:
This really should be sticked..

I was having a horrible time with areas on my screen, mostly along the outer edges (home button on top left, enter or backbutton on keyboard, etc).

This finally fixed it. I had installed TnT 4.4.0 and had to put the calibration.ini file on /sdcard not /sdcard2.

Glad I found this and tried both locations.

edit: wrong TnT version listed
[G Tablet General] themsn:
with root explorer I placed the file one level up above /sdcard (so essentially in root)

and that's the file that calibrated and then seemed to have disappeared after I rebooted.

But anyway, it worked beautifully!

And I definitely vote that this should be stickied as well!
[G Tablet General] dfin13:
+1 for this fixing the touch screen issues. I found myself jabbing at the home soft key so many times I wanted to toss this thing out the window. I had to hit it at just the right angle -- same went for anything along the edges. Now it's perfect.
[G Tablet General] drum747:
You guys are awesome!! My tablet never had this problem but my wife's g tablet from Woot had the dead zones and I found this thread and bingo! Like a brand new screen! Thanks a million! She is very happy now and I don't have to hear how I suck for making her get one!
[G Tablet General] StingRay_:
Major thanks to epods_one, roebeet, rcgabriel, and others for posting calibration info, instructions, and files!

Was rather discouraged yesterday evening with the touchscreen and how difficult it was to select, scroll, etc....this fix turned my Gtab into a completely different machine!
[G Tablet General] Kershek:
I tried doing this (without the period after TSCalibration) and I get an error:

can not open the file calibration.ini in emmc !

I've placed an empty calibration.ini in both sdcard and sdcard2. I also tried using "exec /system/bin/TSCalibration"

I tried booting with the calibration.ini in both sdcard and sdcard2, leaving it for a few minutes before using, and I still have dead spots along the edges.

I'm using the brand-new VEGAn-TAB GingerEdition STABLE RC1 build on a Viewsonic G-Tablet.

Any ideas?
[G Tablet General] toonvox:
I started getting dead zones on both the left and right sides of my G Tab after I applied a Skinomi screen protector. I was going nuts. I ran the Terminal Emulator, ran these commands, bingo.

THANK you! THANK you. You're all going to heaven.
[G Tablet General] Kershek:
To reply to my own post, I flashed my ROM to VEGAn beta 5.11, noticed the continuing dead spots, touched calibration.ini in both sdcard and sdcard2, and whammo! Very responsive screen! I guess it was the VEGAn GB version that was doing it... That's ok, because the lack of video acceleration was killing me.

Thanks for this thread!
[G Tablet General] TommyGloves:
I thought I'd post to say "Thank You!". I just recieved my GTab yesterday from the second round WOOT sale. I decided to try the CyanogenMod-7.0.0-Harmony ROM. Spent sometime today getting it all setup and was also experiencing the deadspot issues. I used the suggested Terminal method and it worked perfect! :D

For TSCalibration to work in CM7, it requires the calibration.ini file to be in /emmc

(I'm new...so I'm not sure if this is obvious to everyone. ;) )
[G Tablet General] requiem3:
I'm having this exact same issue, was TScalibration not found for you either when you tried to run it in terminal emulator?

I'll try switching ROMs as you did
[G Tablet General] Kershek:
Well, I was able to run TScalibration, but I got the error "can not open the file calibration.ini in emmc !" After switching ROMs I noticed TommyGloves in this thread said there was an emmc directory, so if you haven't switched yet, try creating a calibration.ini in that directory and trying it again.

Truthfully, though, I've been very happy with 5.1.1, mostly because of the video acceleration. I also found VTL Launcher to give me the same launcher options on the sides as the VEGAn Gingerbread ROM had.
[G Tablet General] rajeevvp:
It seems to me, after looking at a strace output, that we should be able to get rid of the whole calibration.ini file creation mess with this simple command:

$ su
# echo 1 > /sys/devices/platform/tegra_touch/calibration

Both the echo and the TSCalibration commands produce the same kernel message:

[74641.298524] AT168_SetCalibration OK .

This is, basically, what the TSCalibration command does (edited strace output):

execve("/system/bin/TSCalibration", ["/system/bin/TSCalibration"], [/* 16 vars */]) = 0
...
open("/proc/cmdline", O_RDONLY|O_LARGEFILE) = 3
read(3, "mem=448M@0M nvmem=64M@448M vmall"..., 1024) = 371
write(1, "get devicetype!\n", 16) = 16
write(1, "get btmac!\n", 11) = 11
open("/data/BCM4329B1.hcd", O_WRONLY|O_LARGEFILE) = 4
lseek(4, 28, SEEK_SET) = 28
write(4, "\234^\326\23\32\0", 6) = 6
close(3) = 0
close(4) = 0
open("/mnt/emmc/calibration.ini", O_RDONLY|O_LARGEFILE) = 3
write(1, " open the file calibration.ini i"..., 48) = 48
open("/sys/devices/platform/tegra_touch/calibration", O_RDWR|O_LARGEFILE) = 4
write(1, " open the file calibration in /s"..., 86) = 86
write(4, "1", 1) = 1
close(4) = 0
close(3) = 0
exit_group(0)

Also see this post.
[G Tablet General] Akeey009:
Js go n root yo decice and increase yo phns touch by editing d scripts...

:)
[G Tablet General] collindv:
was that English?
[G Tablet General] MrFVD:
Hi,

can you please tell me which script is

Thanks in advance ;)
[G Tablet General] harryaliasharish:
I want to caliberate my mobile touch

Hi, I am getting the below error in my mobile. Please help me out.

can not get devicetype!

can not get btmac!

can not open the file /data/bluecore6.psr!

open the file calibration.ini in sdcard success!

open the file calibration in /sys/devices/platform/tegra_touch/calibration success !

can not write the file calibration !
[Desire HD General] PenFold109:
Hi all,

I've finally got my hands on the DHD, and after using winmo for the last ~5 years I'm loving it, but I seem to have a problem with receiving calls.

Earlier tonight at work I was using the market place, playing a bit of Angry birds, and I got a couple of texts from T-mobile saying I had missed calls, I also had a few missed the night before aswell while i was playing around with it.

I've asked the people who called and they said the calls go straight to answer phone as if the phone is off/has no signal, but the signal is great both at home and work.

So far I have rooted and S-OFF'd the phone, but have not installed a custom ROM yet. I thought this may be kinda like the Iphone 4 touch of death issues, but cant get it loose signal by covering it with my hands.

Has anyone else had this issue, or does it look like I may have a dodgy handset?
[Desire HD General] olivierlee:
Does your phone have 3G coverage at your workplace or is 3G enabled on your phone? 2G allows only voice OR data at the same time, while 3G allows both. So if you were using data e.g. marketplace, syncing etc., your call might not get through. Might be worth checking your phone settings.
[Desire HD General] Burning_aces:
:o didnt know that, will have to re-enable 3g D:
[Desire HD General] PenFold109:
Sorry it took me so long to get back to this thread. Thanks for the replies, After being on shift for the last week it seems that my workplace is in a bit of a coverage grey area, so depending where I am stood, strength of the wind or the current celestial alignment, the phone will swap between 3G and HSDPA, so from what I can find it looks like I may of missed these calls due to this issue.
[Desire HD General] olivierlee:
It should not matter if you're swapping from 3G and HSPDA, you should still be receiving calls if you're on 3G. HSPDA is 3G, but faster. It you still miss calls, I'd suggest talking to your provider.
[Captivate Q&A, Help & Troubleshooting] Aus_Azn:
I've had this phone since its launch, but I'm now encountering this strange problem.

While I can get into Download Mode without difficulty, I have an issue with connecting it to my PC. While it'll pick it up fine while the phone is in recovery or normal modes, DL mode causes it to give me this error, thus blocking Odin and my chances of returning it to stock.

I desperately need to flash my way out of this battery-draining and unstable OC/UV kernel, but Odin won't recognize it because Windows won't recognize it.

I am using Win7 x64 and WinXP x86, both with appropriate drivers and both not working and having the same issue.

CWM is similarly failing to work, producing a "failed to chown" something or other. Is my phone basically gone at this point?
[Captivate Q&A, Help & Troubleshooting] shadowscreation:
My suggestion is to reinstall the drivers for the device and if cwm is not working right then use rom manager to install another version of it and if that doesn't work im pretty sure in the development section u can dl the update file with cwm on it
[Captivate Q&A, Help & Troubleshooting] Aus_Azn:
I've done the former, I'll try the latter after work today.
[Captivate Q&A, Help & Troubleshooting] Aus_Azn:
command symlink

calling command set_perm_recursive

E:Can't chown/mod /data/

(I/O error)

E:Failure at line 69:

set_perm_recursive 0 0 0777 0777 DATA:

Installation aborted.

Failure at line 6:

install_zip SDCARD:/Perception-Build-8-non-oc-uv.zip

Here's my error message from CWM. This is after reinstalling both ROM Manager and CWM. This is preceded by a million "command symlink" commands, leading me to believe that something is failing to work here.
[Captivate Q&A, Help & Troubleshooting] shadowscreation:
If ur trying to flash a new rom I've had this problem before the reason it isn't working is u need to flash back to stock first before u can install a new rom but it will work if u want to flash the same rom over the one u have something to do with the kernel I believe not quite sure but the way I've fixed that is to flash back to stock before flashing a new rom

Edit:::: or u need to disable lagfix by putting a file in ur root folder named disable-lagfix
[Captivate Q&A, Help & Troubleshooting] delugeofspam:
okay thanks unhelpful guy

if you read his original post, he can't get his pc to recognize the phone in download mode. big problem.

same problem i've got.
[Captivate Q&A, Help & Troubleshooting] mcord11758:
Have your tried different usb ports. If you are using a pc try the port in the rear of your tower.

Are you using oem usb cord?

Have you tried running odin as administrator

Where did you get the drivers from
[Captivate Q&A, Help & Troubleshooting] goob1284:
I've had this happen and I was pissed. No matter what I did, my computer would not see this phone and the phone was bricked with cognition. So I don't know exactly what I did BUT this comes close. Uninstall keys and go to control panel and unistall any samsung drivers. Restart computer. Install only the samsung drivers found on the samsung support page at the official samsung website. And then try putting it in download mode again. I seriously spent 7 hours on getting this to work. If this doesn't work.then you need to find the right drivers. I know there's like 3 different driver packages and kies that have the ring one, but some just completely mess you up. So.find the right one with the right drivers. Good luck! Oh and have patience, that's key.
[Captivate Q&A, Help & Troubleshooting] delugeofspam:
Okay, I'll take your advice. I thought I tried every combination of installing and uninstalling until I nearly ripped my hair out. I tried patching the GPS and it totally boned all GPS functionality, so reverting to stock is apparently my only option... and my phone isn't recognized in download mode. So I guess a few more uninstalls and restarts and we'll see if I blow my brains out today...
[Captivate Q&A, Help & Troubleshooting] delugeofspam:
Yeah. I just uninstalled Kies, Samsung Drivers, and Samsung New PC Studio. I rebooted twice, and then reinstalled the drivers (from the OP, which are identical to the ones on the Samsung site) and rebooted.

Guess what? No effing luck. Nothing shows up in Odin (remove battery, run odin, plug cable in, plug phone in, return battery and enter download mode) and my taskbar tells me that "A USB Device has malfunctioned and is not recognized."

What the HELL is going on? There are several people with this problem and nobody seems to have an answer that isn't "buhhh you have the wrong drivers."
[Captivate Q&A, Help & Troubleshooting] mcord11758:
I had this issue, used a different computer and it worked. I did have to try multiple drivers to get it to work though.

What usb jack are you using

Have you tried running ofin as administrator
[Captivate Q&A, Help & Troubleshooting] delugeofspam:
CHECK OUT THIS POST FROM SteveVHT ON THE ANDROID FORMS:

I'm trying it right now.

edited:It was for a Samsung MOMENT, but imagine a company flubbing two series of drivers the same way.
[Captivate Q&A, Help & Troubleshooting] delugeofspam:
FFS

it's still not working :(
[Captivate Q&A, Help & Troubleshooting] jtdroid:
Same problem here. Windows 7 will not detect my phone in download mode. I have tried every set of drivers out there. Detects it in regular (mass storage), and USB debugging mode though.
[Captivate Q&A, Help & Troubleshooting] mcord11758:
If you are using a pc, are you using the rar usb port
[Captivate Q&A, Help & Troubleshooting] jtdroid:
Tried all 4 ports on the back of my computer
[Captivate Q&A, Help & Troubleshooting] mcord11758:
I believe if you right click odin you can run as administrator. Some say this has helped
[Captivate Q&A, Help & Troubleshooting] jtdroid:
I don't believe this to be a problem with Odin (even though I tried that method). Odin picks it up perfectly fine while in USB debugging mode. Windows simply will not pick it up when it enters download mode.

Any other mode Windows will "chime" when the phone is connected. Download mode doesn't do anything. No sound, chime, icon, nothing....
[Captivate Q&A, Help & Troubleshooting] goob1284:
Did you try deleting all drivers then going into download mode and letting windows install the drivers by itself?
[Captivate Q&A, Help & Troubleshooting] delugeofspam:
You know, this might be the only thing I haven't tried.

Here goes.

Edit:

Exactly the same megafail. :(
[Captivate Q&A, Help & Troubleshooting] doctahjeph:
Reload windows.
[Captivate Q&A, Help & Troubleshooting] delugeofspam:
I'd sooner reload the contents of my brain all over the wall behind me.

I may just start gambling, flashing ROMs left and right until I break the phone and shooting myself seems like a fun idea.
[Captivate Q&A, Help & Troubleshooting] double RL:
I know you're having **** luck right now and probably tired of the same suggestions but have you tried a Windows XP machine? I know you might not have easy access to one but I have an Asus netbook running XP and a Macbook Pro running XP on a virtual machine and both flash Odin and pick up my phone every time in download mode. A few weeks back I was out of town and only had a friends Windows 7 notebook to reflash a screwed up rom and I never could get it to work. I know plenty of people use Windows 7 w/out problems but it could be some configurations just don't mesh. Hope you get it worked out man.
[Captivate Q&A, Help & Troubleshooting] delugeofspam:
:(

one of the first troubleshooting steps was to run in XP compatibility mode... which I didn't have to do, because I'm running Windows XP SP3 :mad:
[Captivate Q&A, Help & Troubleshooting] Dani897:
this may be a dumb question, but did you master clear in odin one click while in debugging mode? i dont know if it would help but you never know.

if it failing to chown it sounds like something has the wrong permissions or a corrupt file or something. i doubt master clear would help that but its worth a shot.

i dont know much about update scripts but can you open the file and find the line that it wont chown and try to chown it in adb or in terminal emulator?

i was able to flash a phone that was so borked download mode showed no graphic! it looked like the phone was off but i hit start anyway because the phone was otherwise broken so as unlikely as it was to work there was no sense in not trying it. well it worked. not that it helps your situation but these phones can be a pain to flash but are not usually hopeless. if you have debugging capability there must be a way to fix it. however complicated it may be.

i might also suggest trying http://www.glassechidna.com.au/products/heimdall/

i hope you or a friend can compile from source.
[Captivate Q&A, Help & Troubleshooting] delugeofspam:
I can masterclear in debug mode just fine. If I put the phone in download mode the computer entirely fails to recognize it. "A USB device connected to this computer has malfuntioned." appears over my system tray, and Odin lists absolutely no ports.

ONLY in DOWNLOAD mode. Everything else works smooth as buttered silk.
[Captivate Q&A, Help & Troubleshooting] smokestack76:
Have you tried letting it connect to windows. And keep it pluged in and reboot into download mode? I cant think of anything that will block it in download mode. But when i get home i will look around more.
[Captivate Q&A, Help & Troubleshooting] yentlequible:
This is the exact problem I am having and I have still not found a solution. I tried everything. Reinstalled drivers multiple times, master cleared the phone twice, tried many USB ports. I tried on Windows 7, Vista, and XP, but they all had the same exact malfunctioning problem. Everything else on Odin works fine though, just not download mode.
[Captivate Q&A, Help & Troubleshooting] Dani897:
did you look at the link to heimdall i posted? i dont know if the windows version uses samsung drivers or not. but im prettty sure in linux there is no need for drivers. it may be an alternative to odin, as that is its purpose. it might even work in situations that odin does not.
[Captivate Q&A, Help & Troubleshooting] delugeofspam:
Someone in a thread I posted linking this thread, just to get some more attention over here, suggested that maybe the USB port isn't supplying enough power.

I'm plugged directly into the motherboard, but I honestly suspect something like this to be the case.

Does anyone having this problem happen to have access to an externally powered USB hub?

:confused:.....I know, why the hell would you own such a dinosaur?
[Captivate Q&A, Help & Troubleshooting] norcal einstein:
If you're located in the Bay Area, I'll flash your phone for you.
[Captivate Q&A, Help & Troubleshooting] delugeofspam:
When people say that they're never talking about Cape Cod Bay :(

On the wrong coast, but thank you very much anyway.
[Captivate Q&A, Help & Troubleshooting] areenchem:
SAME PROBLEM ! usb NOT recognized in download mode ! what is going on here!
[Captivate Q&A, Help & Troubleshooting] reinbeau:
Are you using the USB port on the back of your CPU? If not, then try it. It seems you need to use the one directly connected to the motherboard (I've heard of this before with other peripheral equipment). I was using the port on the front, and it didn't work, the one on the back did.
[Captivate Q&A, Help & Troubleshooting] avgjoegeek:
Recently had this issue due to having an i9000 ROM on my phone.

All I did was use the USB drivers from the Odin 1-Click post (link provided in the Q&A sticky btw) - I re-installed right over the top of the existing ones, plugged my phone back in and luckily it found it again.

With my Windows 7 Machine (64-bit) I had better luck with it just finding the device without having to reboot/re-install the drivers.

I would try the ones in there as I know they work.

Another thing you can try (since you've done everything else). Uninstall the drivers - put your phone in DOWNLOAD mode - and keep it plugged into your computer.. and then re-install them once more (I'd say use the Windows 7 box it is a little "smarter" when it comes to handling and figuring out USB Devices).

Good luck.. and you should be able to restore your phone back to stock.
[Captivate Q&A, Help & Troubleshooting] bames:
do you have an alternate computer you can try?

what rom are you on? there is a cwm version for JH7 you could return to JH7 stock OTA and see if it will recognize it. Make sure to disable any lagfix/voodoo first.
[Captivate Q&A, Help & Troubleshooting] avgjoegeek:
My concern with doing that vs. trying to get it to ODIN is that the update.zip only formats and doesn't do a complete wipe like ODIN will. If anything it could make the phone worse and not better.
[Captivate Q&A, Help & Troubleshooting] dizzyizzy:
I have a GT-I9000 that was purchased in UAE. I'm having the same exact issue. In every other mode the phone is recognized in Win XP. But when I put it in Download mode, the USB device is not recognized.

I can't upgrade the sucker even though there is a Froyo update available for it. If I could get this update in update.zip form then it would've made my life a lot easier. But as usual, why would the f-in manufacturer make it easy for you to upgrade. Kies downloads the update and unzips it into JPG_JPF_U_JPE.tar. But I can't do anything with it because the download mode doesn't work.

It seems this version of the I9000 was manufactured with the download mode not being able to be recognized. I've tried reinstalling drivers etc and all that waste of time, but can't find anything that will recognize this as a USB device.

And I can't upgrade the ROM from recovery mode because of no update.zip ROM available.

Have you guys found a solution to this problem yet?
[Captivate Q&A, Help & Troubleshooting] TigerEnigma:
USB Drivers Great Unsolved Crime!

Same Problem: Windows XP 32 bit, 1010 build JH7

Please note, I am an accountant by trade and not a programmer...so if I screwed the pooch on the lingo, forgive me. To all those who have posted a response, thank you for your thoughts and time.

Here is what I have tried:

Drivers: Kies, Kies mini, drivers from Captivate forums, , direct from Samsung USA, even Samsung UK, SDK Google USB Drivers (Although Captivate was not supported) uninstalled and reinstalled, rebooted, re-downloaded

Multiple PC's: tried a laptop, tower pc, connected to the USB ports on the back, connected to USB ports everywhere.

Windows install & "from disk": Allowed windows to configure, and changed path to folders containing the drivers....each and every flipping one, individually.

ADB/SDK Gave the reboot from ADB a shoot in the off chance it would pick up device, but this does not work either.

I have the At&t boot loop (or gray battery if usb is plugged in), the only way I can get into Download Mode is via USB Jig. Once in DM the computer does not recognize the device, Odin3 one-click will not recognize (related to USB drive issue). There is no way for me to get into recovery, three buttons of all combinations...standing on one leg, one eye closed, while facing north east and juggling a Fushigi ball....does not work either.

So, I believe the phone is dead. Everyone on here has fantastic ideas, and I believe I have tried them all. Although, I ultimately believe somehow the USB drive on the Captivate bootloader is screwed...thus it is a Brick.

If anyone has connections with the developers of note that might find a way to get Windows to "Recognize" that there is a faint heart beat here...I would gladly donate to them.

Regards,

TigerEnigma
[Captivate Q&A, Help & Troubleshooting] TigerEnigma:
Got it...sort of

Ok, this action enabled Windows to recognize the USB device and Odin opened the Com port.

Instead of plugging the USB to the computer first, I got the device in download mode, plugged in the USB cable to the device first, then plugged it into the USB port on the computer...picked it right up.

Note: It is an older model laptop...the USB ports on the back are USB 1.0. I have a USB 2.0 card installed on the side, worked through that.

Now I have to go find out why Odin3 One-Click is hanging up. There is a post for that:)

Regards,

TigerEnigma