|
||||
The only way I know of requires a registry hack oem built into a kitchen. Since this is a turn-key rom at present, the hack won't be possible. Can you get past it by tapping anywhere on the screen? If so, you could apply the reg hack after you get past.
__________________
One ROM to rule them all,
One ROM to find them. One ROM to bring them all, And in the kitchen, bind them. |
|
||||
I have the same problem with the broking digitizer in the middle of the screen, i figured this might happen and has stopped me from trying out Helmi's new rls. You are now my guineapig lol. Try these steps and let me know how it goes.
1. make a blank file on your pc and name it "welcome.no" 2. dock 6700, copy welcome.no file to your device root. 3. unplug, softreset if all goes well it should bypass the align screen 4. isntall a Registry program that you can navigate without using the touch screen 5. under HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH\ insert/modify Value name: "CalibrationData" Value data: "2000,2042 3381,3128 3518,900 569 528,3118" that value data is from my 6700, yours almost surely be missaligned with them but atleast its a starting point for you to tweak with it, well that is of course if any of these steps work on WM6. Its what I do with WM5 roms. Good luck, Creeper |
|
||||
I have had problems with the scroll bars. The icons are dead on but the vertical scroll bar is off. Actually, my alignment problems seem to be no existent with some flashes and very bad with others.
A friend of mine has had the same scroll bar issues with this ROM. He just faked out the alignment by taping left of the crosses a bit. |
|
||||
I ended up removing the display from another XV6700 and attaching it to my activated phone then turned it on and did the alignment. (I bot a second XV6700 for my girlfriend but she did not want it so I have a second phone that is not activited). I used the reg edits from "creeper" to tweek alignment on bad screen the XV6700. Thanks creeper
But now I have another problem the contacts screen just flashes for a second then goes away. Also when I softboot the phone it displays a message that "The file 'sddaemon' cannot be found..." I guess the 2 are related. Does anyone know a fix for this problem? |
|
||||
![]()
I have the same problem after changing to wm6. I used the Verizon file for 1.02 bootloader (there are two versions for Verizon phones). During programming my phone display said it had a earlier version bootloader, (ver. 1.00), but I doubt that had anything to do with it. I need this phone for medial reasons so this is a serious problem for me. Did you ever find a fix? If not I may start a new thread on this subject.
|
![]() |
|
|
|