Related
So, I decided to try Ultimate X2 BetaII. Here's my problem:
I decided to flash to OEM ROM first, as I've read this is better with some ROMs, but I think I did something stupid. Instead of using the .exe file to install (_ATT Tilt_RUU_Kaiser_CINGULAR_WWE_3.57.502.2_radio_sign_25.88.40.05_1.65.21.18_Ship.exe), I decided I wanted to install with my SD card, so I extracted the .nb file (KaiserIMG_CINGULAR_WWE_3.57.502.2_radio_sign_25.88.40.05_1.65.21.19_Ship.nbh) and renamed it "KAISIMG.nbh" and copied it to my SD card. I installed with the standard SD card method, and now I'm stuck at a (seemingly) endless screen alignment that loops over and over. The only posts I've found so far on this topic seem to deal with hardware issues, but my screen has worked okay until now, so I'm guessing I screwed something up software-wise by impatiently trying my own idea, instead of following instructions.
Mind you all, this is only my second attempt at flashing a ROM, and the first one I flashed was months ago, so you can consider me somewhat of a newb.
By the way, I just tried going through the screen align twenty times to see if there was any change, and I'm still stuck there. I haven't tried making a welcome.not file yet, but I'll give it a shot now. It seems like even if that works, there should be a way to fix my problem properly. Any ideas?
welcome.not
Welcome.not does get me past the align screen and into the Ultimate X2 Beta II ROM. This does, of course leave me unable to align my screen with the WM app. Still looking for a "proper" fix.
Did you try a different ROM?
RE: Did you try a different ROM?
I first had the screen alignment problem after flashing the OEM ROM. Afterward, I flashed Ultimate X2 Beta II, and the problem persisted. I flashed back to OEM, and the problem was still there, so I flashed back to Ultimate X2, and after conferming the existance of the same issue, I used the welcome.not bypass. I suppose this will be okay, if I can find another way to align the screen, besides the WM screen alignment utility. I saw a post regarding a possible Reg key that changes the max screen alignment repeats. Perhaps altering that key would make it save my initial alignment and end the infinite loop?
P.S. Does anyone know of a screen alignment utility that works from the device and saves the settings, a way of working around the WM utility?
Registry Keys?
Are there registry keys I could alter to fix my screen alignment?
You do have a correct HARDspl right? When you enter bootloader you should see hard spl. Flash another spl and see what happens. Sorry im not of more help but im on my phone.
I have HardSPL 3.29. Ultimate X2 Beta II is running quit well. Radio's working fine, too. I just can't figure out my screen alignment issue. If someone could hook me up with a screen alignment file or registry settings, and perhaps clue me in a little on how to implement, that would, perhaps, be a temporary fix.
Well then think old school. If the cross is moving when you press it i would think the digitizer is ok. So clean the edges around the screen really good. Maybe some lint or dust around the edges. Also maybe loosen the screws on the back a little in case the screen is in a bind.
Yeah, I think the digitizer is fine. I already cleaned the edges with a business card. I don't have a torx kit with me, but I'll keep the screw loosening in mind. I figured the problem must be a result of extracting the .nbh file from the OEM install file, rather than running the .exe. However, flashing again (I used the .exe files for the OEM and Ultimate X2 the second cycle of flashing, rather than using my SD card) hasn't helped. I ran across the following thread, and am downloading the app now. I don't know if it will help, but maybe if someone else runs it and extracts their alignment settings, they can post them for me to try out?
http://forum.xda-developers.com/showthread.php?t=396466
Reg Key
Here's another instance of the same type of solution:
corollatercel said:
So i've been having problems with the screen alignment on mine since i had one spot on my MDA screen that was dead and my screen was cracked so the alignment wizard basically got stuck in limbo when I tried to calibrate it. SO basically what I had to do was download PHM Registry Editor and change the registry key touch referenced in here.
kernelguy said:
My touchscreen had a crack only at the bottom. After skipping the 'align screen' during initial ROM load, I lived with a non-functional touch screen for a day or two. I then remembered the post from equinoxe that had registry settings for his phone. I took those settings and updated my registry. I now have a decent touch screen - at least the top 3/4 works fine.
The key and settings are:
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH]
"CalibrationData"="1922,1957 3330,639 3317,3276 600,3230 609,677 "
I could surmise that the screen is being treated as a square of 3900 x 3900 dots. 0,0 seems to be the top, right corner.
kernelguy
Click to expand...
Click to collapse
Afterwards I used the remote alignment tool (attached) to retrieve the correct settings from the correctly aligned mda(after changing the registry key then rebooting the device) then made sure the file was saved on my pc....normally it's saved by default in the C:\Program Files\Code Factory\Remote Screen Alignment directory. The file was called WIZA200.dat. I did a soft reset then when the alignment screen came up I did the skip function in the remote screen alignment application and it automatically read the proper calibration from the wiza200.dat file and then properly calibrated my mda now my screen is properly calibrated even though i never ran the alignment wizard.
So here are the Instructions folks:
1. Download the latest activesync and connect your mda to your computer and verify your device is connected(not as guest)
2. Perform a soft/hard reset on your MDA then tap your screen to start the screen alignment wizard
3. Download the remote screen alignment tool attached and install it on your machine.
4. Download the wiza200.txt file attached and rename it to WIZA200.dat then put it in the C:\Program Files\Code Factory\Remote Screen Alignment directory on your computer
5. Ensure your MDA is connected to your pc(A green activesync Icon usually indicates a connection )
6. Open the remote screen alignment tool on your pc meanwhile your phone be displaying the alignment screen wizard.
7. Click SKIP in the screen alignment tool.
Assuming everything went fine a message box displaying "The operation has been completed successfully. Your device will be restarted." should pop up on your computer and your device should restart. Afterwards your phone will run the files it always does when you do a soft/hard reset then you touch screen should be properly calibrated and work fine.
Click to expand...
Click to collapse
If someone could do a fresh, accurate screen alignment and report the registry key settings, I could try editing them for myself and see if that does it.
check your pm
check your pm
Thanks!
Thanks for the help, guys. I found the kaiser.dat file in the program's directory, opened with notepad, and copied the string into the appropriate reg key:
2002,1944 3292,635 3352,3272 681,3268 624,673
Thanks, lewnetoons, for providing your info, as well:
1862,1960 3131,673 3129,3260 628,3291 635,655
I suspect my digitizer may need replacement because it wasn't terribly accurate before I encountered this problem, but I'll have to find a proper solution for the "Align Screen" loop for a new digitizer to even matter. This is enough to appease me for now, as my screen is now responding semi-accurately, but if anyone can come up with a fix for my align screen loop, so I won't have to rely on the "welcome.not" fix, I would appreciate it a LOT.
A little off-topic, but it seems to me that five points isn't enough to align the whole digitizer in the first place.
Thanks a lot, guys, I'm good for now.
Bob_Beard said:
Thanks for the help, guys. I found the kaiser.dat file in the program's directory, opened with notepad, and copied the string into the appropriate reg key:
2002,1944 3292,635 3352,3272 681,3268 624,673
Thanks, lewnetoons, for providing your info, as well:
1862,1960 3131,673 3129,3260 628,3291 635,655
I suspect my digitizer may need replacement because it wasn't terribly accurate before I encountered this problem, but I'll have to find a proper solution for the "Align Screen" loop for a new digitizer to even matter. This is enough to appease me for now, as my screen is now responding semi-accurately, but if anyone can come up with a fix for my align screen loop, so I won't have to rely on the "welcome.not" fix, I would appreciate it a LOT.
A little off-topic, but it seems to me that five points isn't enough to align the whole digitizer in the first place.
Thanks a lot, guys, I'm good for now.
Click to expand...
Click to collapse
glad you got it fixed my brother
It occurs to me that I may not have been clear in my first post. I didn't use NBHExtract or anything. I opened the exe with 7-Zip, extracted the larger of two nbh files, renamed it, copied it to my SD card, and flashed it to my phone. I don't know why I did it that way, and it seems like it sort of worked, but something was lost in translation. I've done half a dozen or so flashes since then, but the problem still exists. Any insight into a possible permanent solution for this semi-permanent problem would be very much appreciated.
So, I've gone through a few flashes and my screen alignment still works for the most part, but it can be a pain in the ass using programs that have have small expandable menus or buttons at the bottom of the screen. I can fine tune this a little better using my slow, primitive hand-modify the registry method, but I would still appreciate any input on fixing the problem.
I guess I'm looking for one of two possible solutions:
1. A program that does exactly what the built-in screen alignment utility does.
2. A way to fix whatever I ****ed up, so I can use the screen alignment utility without it looping infinitely.
So, once again, does anyone have any helpful input?
Bob_Beard said:
So, I've gone through a few flashes and my screen alignment still works for the most part, but it can be a pain in the ass using programs that have have small expandable menus or buttons at the bottom of the screen. I can fine tune this a little better using my slow, primitive hand-modify the registry method, but I would still appreciate any input on fixing the problem.
I guess I'm looking for one of two possible solutions:
1. A program that does exactly what the built-in screen alignment utility does.
2. A way to fix whatever I ****ed up, so I can use the screen alignment utility without it looping infinitely.
So, once again, does anyone have any helpful input?
Click to expand...
Click to collapse
try flashing abu's new rom that doesn't require screen alignment. see what happens.
I flashed it within hours of its release, but I'm not sure how it's affected me, since I still keep "welcome.not" in the root directory of my SD card, and I input my alignment config into the registry after every flash. I may expirament with it, though, by removing "welcome.not" and/or reflashing.
Bob_Beard said:
I flashed it within hours of its release, but I'm not sure how it's affected me, since I still keep "welcome.not" in the root directory of my SD card, and I input my alignment config into the registry after every flash. I may expirament with it, though, by removing "welcome.not" and/or reflashing.
Click to expand...
Click to collapse
yeah give it a try and see what happens
A friend brought me a good one today. He has an AT&T Touch Pro with a touch screen issue.
He brought me the phone months ago and I flashed the ROM. All was good. He then deleted a bunch of files one night accidentally and hard booted the phone in an attempt to get the files back. Upon hard reboot the phone hung at the calibration screen and he could not get past that. To describe, the screen calibration works on 3 of the 4 corners, if you hold the press the stylus to the screen quite firmly, but the top right corner will not calibrate however long I told the stylus to the screen.
He brought it to me today and I figured that a fresh ROM would resolve the issue. So I loaded a new ROM and the phone hung again at screen calibration. So I did some research and found a "welcome.not" work around to get us past the screen calibration issue. This was successful and I was able to get us to the home screen.
The issue is that the screen is very unresponsive and I have flashed the device so it's not a ROM flash issue. Is there a driver he might have accidentally deleted that is not reinstalled on a ROM flash? I know I am probably grasping at straws here but I thought this community might have some insight to what the issue is.
I have also considered the idea that I may need to replace the digitizer for this phone if that is the issue and am prepared to do so but thought I would throw this question out to the community for any tips/tricks or ideas you may have before cracking the case on this thing.
Thanks for your help in advance.
--Mike
Oh and I forgot to mention that sometimes the screen works if you tap it continuously but most times, there is no response.
--Mike
Moved as not ROM Development.
Hey Mike,same issue over here.I couldn't find any solutions so far.By the way,what's that "welcome.not" thing?
Well,after some google search i ended up with this.http://bittangents.com/2008/10/28/removing-welcome-message-doctors-appointment-on-pocket-pc-2003/
I suppose that you were meaning that...right?
Check out this one too
http://forum.xda-developers.com/showthread.php?t=355010
The calibration of the screen
IWPantel - Thanks for referring to my blog
To stop the welcome message, you need to put the Welcome.NOT in the root of a sd card or of the device. I don't believe this is your issue, however.
There are typically three reasons why the screen will become unresponsive.
#1 You have a bad touchscreen. Assuming that the screen was working perfectly, I highly doubt this is your issue.
#2 You are calibrating the screen with the stylus straight up. Believe it or not, the touch point changes if you are straight up and down, or if you have the stylus as if you are writing. The angle will affect the touch point.
#3 You have a conflicting .reg file in the Application or Platform directory of the handheld. The calibration settings are stored in the device's registry and they need to be updated. If you did a persistant registry tweak (where it exports the registry into NV ram, the calibration settings will overwrite the calibration settings you create on system startup.
Feel free to contact me with any questions.
-Brent
brentblawat said:
IWPantel - Thanks for referring to my blog
To stop the welcome message, you need to put the Welcome.NOT in the root of a sd card or of the device. I don't believe this is your issue, however.
There are typically three reasons why the screen will become unresponsive.
#1 You have a bad touchscreen. Assuming that the screen was working perfectly, I highly doubt this is your issue.
#2 You are calibrating the screen with the stylus straight up. Believe it or not, the touch point changes if you are straight up and down, or if you have the stylus as if you are writing. The angle will affect the touch point.
#3 You have a conflicting .reg file in the Application or Platform directory of the handheld. The calibration settings are stored in the device's registry and they need to be updated. If you did a persistant registry tweak (where it exports the registry into NV ram, the calibration settings will overwrite the calibration settings you create on system startup.
Feel free to contact me with any questions.
-Brent
Click to expand...
Click to collapse
Brent, I had the same problem here! My Fuze simply stopped responding to my touchs....
#1 Taking this as true
#2 I tried a hard reset, but nothing happens. I can not touch the screen to calibrate
#3 I just can not understand what you proposed.
Please, help me!
I don`t know why, but my cell just back to normal!
Now it's everything working!
@brentblawat - How come you are a Junior Member when your answer is so hardcore.
Anyhows, I have the same problem with my phone, I have tried all the software tricks I could think of. I guess your point 3 asks us to manually enter the calibration data in registry. Have tried it doesnt work.
I cant replace the hardware as I have Tmobile MDA and I dont get the spare parts for this here. the digitizer is different from the one in Touch pro.
my hd2 Radio version is 2.05.51.05_2
when i try to launch android i get a black screen with a couple of lines ending with "jumping to kernel" and then it fades
what should i do ?
please help
I had that problem to start as well. I did a little more digging and I read that if you copy and paste the contents of the Android folder straight to the root of your sd, it would work. And it did. I booted up and got most functions to work. I'm having a couple other issues now though,
3g not working consistantly
after leaving it on overnight, I was able to turn it on 4x. The fifth time, when i tried to turn it on the 5th time, my power buttons on the bottom came on but no screen. I had to pull the battery to reboot to WM
GUYS, AFAIK you wont get droid running well (if at all) with a xx.51 radio. You will need to flash a .50 one, then you should be rolling.
Head over to the hd2 android forum and read the sticky guides, very useful and informative
Also ensure card is formatted fat 32 or it wont boot.
Just got my Infuse today (coming from an iPhone). Immediately rooted, unlocked and installed CW Recovery.
Couple quick questions.
#1) How do I get the damned <OPTION/HOME/PREV/SEARCH> bar to stay lit up? It is driving me nuts. It goes out in like 2 seconds after I have touched it. No idea why they did that.
#2) Internal SD vs the microSD card. When I connect via USB MASS STORAGE I don't see any of the folders that I KNOW are on it (Titanium Backup and some others). Are there limitations as to what can be saved on the external SD card?
#3) How do I get ClockworkMod to save backups to the external SD card and not the internal card?
#4) I thought this had SWYPE keyboard option. Can't seem to find it. Never mind! Found SWYPE
Thanks!
you cant control the hard key backlights. when you hit the screen or one of the buttons, theyll light up. my dell streak had a different behavior, turning on only when you hit the actual buttons (not the screen) and staying on for 10 seconds. its just what the hardware is set to do. are you plugging your phone into a mac? i noticed on my macs, itll double up one of the sd cards until you eject that one then you can read and write to the other. i dont have this problem in windows. theres not limitations to the file system except for the 4gb max file size (fat32).
The Jack of Clubs said:
you cant control the hard key backlights. when you hit the screen or one of the buttons, theyll light up. my dell streak had a different behavior, turning on only when you hit the actual buttons (not the screen) and staying on for 10 seconds. its just what the hardware is set to do. are you plugging your phone into a mac? i noticed on my macs, itll double up one of the sd cards until you eject that one then you can read and write to the other. i dont have this problem in windows. theres not limitations to the file system except for the 4gb max file size (fat32).
Click to expand...
Click to collapse
Wow, is that annoying. I either hit the wrong dark button and end up at "HOME" or touch the screen and screw up something else or touch a button and change the volume. Sometimes ya wonder who designed these things. I'm sure those buttons use very little power.
As for the SD issue the problem is folders on the EXTERNAL SD CARD created by for one example Titanium Backup are not visible unless I turn on USB DEBUGGING. If I use it as mass storage they don't show up. Other folders do the same. Hard to explain but I have figured it out and it another strange behavior.
Using a Win7 PC not a Mac.
Keep the Lights On will allow your capacitive touch keys to stay lit. It's still a bit buggy since it hasn't been updated for the Infuse; sometimes the backlights will stay on even after you turn the screen off.
^^
Thanks! There's an app for that!
Edit: Doesn't work very well ..... but it's better than nothing.
If someone ever gets BLN kernel mods working properly this might be more easily tunable from userland. However so far all BLN porting attempts have resulted in bugginess.
I might look into seeing if the timeout can be tweaked up a little as an interim solution. (Depends on if it's userland or kernel. If it's kernel I can probably tweak it, if it's userland someone else will have to do it.)
Entropy512 said:
If someone ever gets BLN kernel mods working properly this might be more easily tunable from userland. However so far all BLN porting attempts have resulted in bugginess.
I might look into seeing if the timeout can be tweaked up a little as an interim solution. (Depends on if it's userland or kernel. If it's kernel I can probably tweak it, if it's userland someone else will have to do it.)
Click to expand...
Click to collapse
That sounds promising. I find this "feature" is really a dumb-ass design and probably the most annoying thing I have found (so far) in my first 48hrs with this device.
#1 Some phones have the option, some don't. Check the system settings or third party apps. I know the Samsung Galaxy SII has the option to change the duration of the lights, so check that out.
#2 You need a true file explorer, not just going through it in windows. Root Explorer is great on the infuse (or any android for that matter) and is worth the $5. It lets you truly go through the entire phone.
#3 I'm pretty sure CWM only backs up internal, but I'm not sure. Try using titanium and moving your data to the internal, and then backing it up that way.
#4 Long press on an empty text field and a menu should pop up. Tap "Input Method" and then you can select which keyboard you want to use. Swype is great btw
Ok, so after a long time of trying to get my pen calibrated so that it wouldn't go all crazy in the corners and then not be off by a 5mm everywhere else I dug around the vast interwebs and with a little hex editing found the answer.
It has been posted in other places that you can use tabcal to calibrate you touch/pen input with more test points for better accuracy... however since our wonderful device has BOTH touch and pen inputs, the parameters everyone is using to manually calibrate using tabcal directly are wrong and as such many people have had issues with their touch input going all crazy after trying to calibrate their pen in this manner or the calibration simply wouldn't do anything. After messing around with settings all day I noticed if you use the calibration tool via the control panel it asks you what you want to calibrate, 'PEN' or 'TOUCH' before it starts tabcal, meaning there must be some parameter that is being passed to tabcal when you make this selection. So I opened up a cmd prompt and typed tabcal /? and was greated with a big fat nothing. Knowing that tabcal had switches since I had already been using some I decided to open tabcal with a hex editor to get a better look and thats when I found it: "devicekind=" so without further babbling from me......
HOW TO PROPERLY CONFIGURE YOUR PEN:
!First reset all of your current calibration data for both pen and touch! Now double check that your resolution is set to the native 1920 x 1080. Then copy and paste the following either in a run box or a cmd prompt:
Code:
tabcal devicekind=pen lincal novalidate XGridPts=10,60,110,160,260,360,460,560,660,810,960,1110,1260,1360,1460,1560,1660,1760,1810,1860,1910 YGridPts=10,60,110,160,250,400,540,680,830,920,970,1020,1070
Then go through the process selecting the crosshairs holding your pen and tablet the way you would normally/comfortably hold them, it is very important that you do it that way and also that you are physically accurate (disregard the onscreen indicator of the pen location) as this is how Windows determines what a regular press in that sector of your screen is.
Now after you have gone through all 273 input points you will need to edit your registry just a little should you ever want/need to reset the calibration data via the control panel reset thingy. To make this small fix go to the following in your registry:
Code:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\HID\VID_045E&PID_0799&MI_01&Col01\8&11540d24&0&0000\Device Parameters]
The "VID_045E&PID_0799&MI_01&Col01\8&11540d24&0&0000" part may be different on your device so to find it you can search for "LinearityData" under "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum" then once you find "LinearityData" rename it to "UserLinearityData" now later on if you want to you can reset the calibration to factory settings should you ever want to do such a thing.
As always, if this helped you please hit the 'Thanks' button
Jesus christ 273 points lol. I did this with a 100 and thought that was painstaking, but the thing is, if you open the calibration through cmd, it detects your hand as well as the pen. Or that could've just been a fluke when I did it. I'll try again since I exchanged my unit.
Kraize said:
Jesus christ 273 points lol. I did this with a 100 and thought that was painstaking, but the thing is, if you open the calibration through cmd, it detects your hand as well as the pen. Or that could've just been a fluke when I did it. I'll try again since I exchanged my unit.
Click to expand...
Click to collapse
This knows that you are calibrating the pen and if you touch the screen it will prompt you that an alternate input type has been detected, however if the pen is close enough to the screen touch input is ignored anyways.
Also, I just tweaked the input test points to focus a little more on corner accuracy, it still has 273 test points though.
Thank you, it worked out much better than the 100 point calibration because that one detected finger touches as well.
The best calibration method found. Although the top left corner is still inaccruate, at least it fixed the other 3 corners, Since programs rarely require cursor near the tiny top left corner area where it is affected, I think I can live with it.
UPDATE:
I calibrate again, but I align the pen completely perpendicular to the screen when calibrating the top left corner, now the top left is more accurate, especially if I align my pen, it will be very accurate.
Kraize said:
Jesus christ 273 points lol. I did this with a 100 and thought that was painstaking, but the thing is, if you open the calibration through cmd, it detects your hand as well as the pen. Or that could've just been a fluke when I did it. I'll try again since I exchanged my unit.
Click to expand...
Click to collapse
Wait, when did the Lord come in here?
I've been here a while..
this doesnt seem to work. it only does 4 points for me.
it is giving me an error. please see the attachment.
i did clicked on reset button, before running the cmd
i don't know if this could be the reason, I installed wacom latest drivers.
Trig0r said:
I've been here a while..
Click to expand...
Click to collapse
Howdy!
bijju said:
it is giving me an error. please see the attachment.
i did clicked on reset button, before running the cmd
i don't know if this could be the reason, I installed wacom latest drivers.
Click to expand...
Click to collapse
I have the same problem :/
I had they same error. I had updated to the new Wacom drivers for better pressure support in certain apps. I uninstalled ISD Tablet from PROGRAMS and FEATURES in the control panel and restarted Pro. The calibration now works. The only question left for me is what will happen if I try to reinstall the new Wacom driver.
UPDATE: Tried to recalibrate again with this method that just worked and now even without the Wacom drivers uninstalled I get the same error about resetting data.
UPDATE 2: Reinstalled Wacom drivers then uninstalled again after a reboot. Now the 273 point calibration works again. This time, I was a little more careful with each touch.
Some improvements and instructions
Congratulations! Very helpful. I was on the verge of sending my Samsung Ativ Smart PC pro back...
I optimized the solution for needs:
Code:
tabcal devicekind=pen lincal novalidate XGridPts=0,30,50,150,350,650,945,1240,1540,1740,1840,1890,1919 YGridPts=0,30,50,150,350,630,830,1030,1050,1079
I think that for most users this 130 points should suffice.
Additionally, I correct the problem of the "dead border" of my device: the touch region seems to be about 10 points smaller athen the screen at every edge. Thus, I add the very edge coordinates to the list; during calibration, I cannot click them, but I can click about 15 points inside. The mapping enures that any point closer than 15 to the edge is then mapped to the edge. This in in fact a strong non-non-linearity at the outmost 30 points, but this allows me to reach slide-in menus, etc., and I rarely write anything there.
To make the best calibration, you should for this command, which establishes a linearity correction for the hardware, hold the pen perfectly perpenticular to the screen. After this is done, you should make a regular 4-point calibration through the control panel, once in landscape and once in portrait, while holding the pen in your convenient writing position. This is apparently applied on top of the linearity correction, and corrects mainly for your pen tilt, apparently separately for screen orientation.
Note: you have to rename the LinearityData in regedit every time before you can start tabcal again, otherwise you get an error message.
2nd note: SAMSUNG should do a 100 point linearity correction in the factory already.
3rd note: hope the linearity does not drift too much...
Thanks, this worked great! Is there anyway to have multiple calibrations for different orientations? I calibrated in landscape but in portrait mode some of the corner are still off
This doesn't seem to work on 8.1, or am I crazy?
So if i have the wacom drivers I cant use this calibration fix?
I dont believe theres no way to bypass this.
I tried running the command but the error keeps poping up no matter how many times i reset the calibration via control panel.
Theres no linearity entry at all in my registry too.
Solutions anyone?
sneak3 said:
So if i have the wacom drivers I cant use this calibration fix?
I dont believe theres no way to bypass this.
I tried running the command but the error keeps poping up no matter how many times i reset the calibration via control panel.
Theres no linearity entry at all in my registry too.
Solutions anyone?
Click to expand...
Click to collapse
Uninstall drivers. Do calibration. Reinstall drivers.
Kraize said:
Uninstall drivers. Do calibration. Reinstall drivers.
Click to expand...
Click to collapse
But I thought wacom drivers would overwrite the default windows configs, am I wrong?
sneak3 said:
But I thought wacom drivers would overwrite the default windows configs, am I wrong?
Click to expand...
Click to collapse
I don't believe that they do. My config stays after I reinstalled the drivers.
I'm using the Surface Pro with the newest Wacom driver (ver 7.1.1-16).
What I did:
1. Uninstalled the Wacom driver. Restart.
2. Reset Calibration via Control Panel > Tablet PC Settings.
3. Run the 273 point tabcal command.
4. Do 4-pt calibration again via Tablet PC Settings. Restart.
Up till this point, the calibration at the corners did improve considerably. But subsequently, when I installed wacom's driver and restarted, the drift came back, somehow invalidating the 273 pt calibration.
My thoughts/queries at this point:
a. Maybe I didn't do things in the correct order?
b. Should I use an older driver instead?
c. Should I calibrate via wacom's settings panel? (Or should I focus exclusively on calibration via Tablet PC Settings?)
Note: I have not applied any registry edit, as mentioned in the 1st post. Do I need to do that to make the calibration 'stick'?