Database Users

T-Mobile GPRS / EDGE GOOGLE FIX - regedit MTU setting

For those of you who cannot browse GOOGLE sites using the unlimited T-Mobile GPRS/EDGE plan do the following:
On your WM5 device, use a registry editor and do the following:
Go to HKLM\Comm\Cellular Line\Parms\tcpip
and add a DWORD registry key called MTU with value 1460 (UPDATED)
Open PocketIE/Opera/Netfront and go to any Google page you want!
Oh, and make sure your internet gateway is using:
internet2.voicestream.com

It seems as though the fix is not working for all cities.
I'm actually in New York City, so I guess the MTU values could be different in different areas. Works great on an MTU of 1460 in NYC.
You can try values from 1500 (default) all the way down to 1400.
Trial and error, if it does work for you though, please post the city and MTU value you got it working with.
Goodluck everyone. I have been struggling with this since February and am really pleased I have finally managed to resolve it.
If there are any other New York City T-Mobile users, please confirm the fix.
Thanks.

The following solution worked for me on my T-Mobile MDA. Note: the NdisWan key did not exist, I had to create it from scratch. Before adding the information below into my registry, I was unable to get past the initial google page. Now I can google anything, and use google maps too! And BTW I am in Long Island.
Change the MTU Settings for PPP Connections
Click Start, click Run, type regedit in the Open box, and then click OK.
Locate and then click the following subkey in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\NdisWan\Parameters
Add a Protocols subkey (if it does not already exist). To do so:
a. On the Edit menu, point to New, and then click Key.
b. Type Protocols, and then press ENTER.
4. Add a 0 (zero) subkey to the Protocols subkey. To do so:
a. Click the Protocols subkey that you created step 3.
b. On the Edit menu, point to New, and then click Key.
c. Type 0 (zero), and then press ENTER.
5. Click the 0 subkey that you created in step 4.
6. On the Edit menu, point to New, and then click DWORD Value.
7. In the Value data box, type ProtocolType, and then click OK.
8. On the Edit menu, click Modify.
9. In the Value data box, type 800, make sure Hexadecimal is selected under Base, and then click OK.
10. On the Edit menu, point to New, and then click DWORD Value.
11. Type PPPProtocolType, and then press ENTER.
12. On the Edit menu, click Modify.
13. In the Value data box, type 21, make sure Hexadecimal is selected under Base, and then click OK.
14. On the Edit menu, point to New, and then click DWORD Value.
15. Type ProtocolMTU, and then press ENTER.
16. On the Edit menu, click Modify.
17. Under Base, click Decimal, type the MTU size that you want in the Value data box, and then click OK.
18. Quit Registry Editor.
19. Restart your computer.
The MTU size that worked with the customer I was talking to was 1350.

Squuiid said:
For those of you who cannot browse GOOGLE sites using the unlimited T-Mobile GPRS/EDGE plan do the following:
On your WM5 device, use a registry editor and do the following:
Go to HKLM\Comm\Cellular Line\Parms\tcpip
and add a DWORD registry key called MTU with value 1450
Open PocketIE/Opera/Netfront and go to any Google page you want!
Oh, and make sure your internet gateway is using:
internet2.voicestream.com
Click to expand...
Click to collapse
This worked PERFECTLY! I'm in NYC as well and 1450 worked. (for what's it worth, that long process also described in this thread DID NOT work for me)

Squiid you are the man I work in NYC and live in NJ works like a charm... it's especially great cause i'vee ben trying to access all my gmail and GFYD accounts and it's been so inconsistent. It works well thus far thanks!

Squiid you are the man I work in NYC and live in NJ works like a charm... it's especially great cause i'vee ben trying to access all my gmail and GFYD accounts and it's been so inconsistent. It works well thus far thanks!

The registry fix for MTU of 1450 seems to be working in Dallas, thanks for the tip.

ok... so right after I added the editi in the registry it worked right away I was sitting at the starbucks on W35th and 7th. Then I went to a building right down the street and had to google something I couldn't access any google page.
I had great service in the building just no google pages which thought I had fixed. Now I can't access them from anywhere in the city again? the MTU edit is still in my registry.
Any ideas on this? thanks?

This worked for me, PHL market.
It allowed me to get to google.com.
However I still can't access any of the other google sites. (local/maps)

MTU of 1460 best
Have done some adittional testing, an MTU value of 1460 works best!
1450 sometimes works on all google sites other times not.
1460 seem to work all the time.
Please leave your feedback, and for those that have, thanks.

Not working here
Squuiid said:
For those of you who cannot browse GOOGLE sites using the unlimited T-Mobile GPRS/EDGE plan do the following:
On your WM5 device, use a registry editor and do the following:
Go to HKLM\Comm\Cellular Line\Parms\tcpip
and add a DWORD registry key called MTU with value 1460 (UPDATED)
Open PocketIE/Opera/Netfront and go to any Google page you want!
Oh, and make sure your internet gateway is using:
internet2.voicestream.com
Click to expand...
Click to collapse
I´m not with T-Mob but I do have these problem, I tried the values you suggested but doesn´t seem to work. Is there a range of values that I should try?

I figure out myself
luiggi said:
I´m not with T-Mob but I do have these problem, I tried the values you suggested but doesn´t seem to work. Is there a range of values that I should try?
Click to expand...
Click to collapse
Here one may find a useful list of values depending of the connection type
http://www.stearns.org/p0f/mtu.h
by the way, none of these worked for me.

adamb2k6 said:
The following solution worked for me on my T-Mobile MDA. Note: the NdisWan key did not exist, I had to create it from scratch. Before adding the information below into my registry, I was unable to get past the initial google page. Now I can google anything, and use google maps too! And BTW I am in Long Island.
Change the MTU Settings for PPP Connections
Click Start, click Run, type regedit in the Open box, and then click OK.
Locate and then click the following subkey in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\NdisWan\Parameters
Add a Protocols subkey (if it does not already exist). To do so:
a. On the Edit menu, point to New, and then click Key.
b. Type Protocols, and then press ENTER.
4. Add a 0 (zero) subkey to the Protocols subkey. To do so:
a. Click the Protocols subkey that you created step 3.
b. On the Edit menu, point to New, and then click Key.
c. Type 0 (zero), and then press ENTER.
5. Click the 0 subkey that you created in step 4.
6. On the Edit menu, point to New, and then click DWORD Value.
7. In the Value data box, type ProtocolType, and then click OK.
8. On the Edit menu, click Modify.
9. In the Value data box, type 800, make sure Hexadecimal is selected under Base, and then click OK.
10. On the Edit menu, point to New, and then click DWORD Value.
11. Type PPPProtocolType, and then press ENTER.
12. On the Edit menu, click Modify.
13. In the Value data box, type 21, make sure Hexadecimal is selected under Base, and then click OK.
14. On the Edit menu, point to New, and then click DWORD Value.
15. Type ProtocolMTU, and then press ENTER.
16. On the Edit menu, click Modify.
17. Under Base, click Decimal, type the MTU size that you want in the Value data box, and then click OK.
18. Quit Registry Editor.
19. Restart your computer.
The MTU size that worked with the customer I was talking to was 1350.
Click to expand...
Click to collapse
I'm using an 8525 with
CE5.2.1622 ( Build 18128.0.4.4 )
ROM 3.62.502.3 ( 10/11/07 )
Radio 1.16.00.00
Protocol Ver: 32.53.7018.01H
( Yes I used pof's SIM/CID Unlocker....way to go pof ! )
Anyway, I've tried adding these keys ( which, by the way, once I reboot the 8525, I lose all BUT the "ProtocolType" entries under the "0" key ), and setting my MTU from 1430 to 1460 as the original author suggested, and I can get past google.com, and it simply dies "Opening" gmail/calendar/maps.
THe funny thing is I'm running Xplode's WM6 ROM for BlueAngel on an older Siemens SX-66, and even though it DOESN'T have any of these entries mentioned, it works....I can go to gmail just fine, even without the registry settings.
Has ANYONE gotten a consistent solution to this ? Is there any particular ROM image someone can recommend to move to that includes fixes for this ?
Thanks.

Updated Radio ....still doesn't work.
I updated the Radio ROM To 1.54.30.10, and it still doesn't work. Even though now, I have 2 "cellular line" entries in the HKLM\COMM section of the registry.

HTC P6500 & HP IPaq 614c PPP Protocol MTU
Hi everyone,
I am wondering if any can look over my problem and possibly offer some advice?
I have a problem probably generic to most PDA devices where i can not change the MTU size for the PPP Protocol.
I have made the changes as advised in this thread and neither have worked for me, the MTU is still default 1500.
Changes made are as follows:
"HKLM\Comm\Cellular Line\Parms\tcpip" Set to 1450, MSS is still 1460
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NdisWan\Parameters\Protocols\0" and also changed \Parameters to \Parms as they all within Registry on WM6 and set ProtocolMTU, PPPProtocolType and ProtocolType as in XP, MTU set to 1450 but the MSS is still 1460.
I am using Windows Mobile 6.
The tool i use on the PDA is the Microsoft Power Toys Analyzer, copy the file to my XP machine and open the netlog0 file with Wireshark and investigate the capture.
The latter of the two keys is how the MTU is changed on a Windows XP machine.
I do know that data cards connected to a PC that use the WWAN protocol for GPRS connection will list a Wireless Network Interface card and for that the MTU would be changed under the network adapter itself, if they are using the PPP Protocol and listed as a Dial Up adapter the the latter key above must be used, all tested and works a treat.
I am imaging that PDA devices must work in the same way.
The devices i am currently using definatly use the PPP Protocol to connect, can anyone advice how this MTU is changed or even advice how to tweak registry to get GPRS to use WWAN, the latter may be impossible for me as i am not a software developer, tweaks i can handle.
Well thanks for looking at my post and i hope someone can point me into the correct direction.
Many Thanks
Martin.

!!ONLINE!![ROM_Android_hero]no, it's not flashable!!!Umbrella Corpv2 working media

Hi there,
as anounced her is my first Umbrella Themed Android Rom. It is a mixture of several vogue, dream and saphire roms.
Here the things i added:
Some apps:
-proPaint Camera (fully working)
-RockOn
-LastFM app
-Custom boot animation and sound (just on first boot so loud)
-Umbrella Themed (more to come, if some graphical advanced people could help me i would be pleased)
-Latest Libs
-Shazaam
-New default ringtone and notification tone
-Kaiser wifi fix
Working:
Kaiser (tested by me:
-Data
-WiFi
-Camera (proPaint)
-Audio
-Phone (very responsive)
Vogue: Please tell me and i will add infos!!!
-Data ??
-WiFi ??
-Camera (proPaint) ??
-Audio ??
-Phone (very responsive) ??
I'm no developer i only wanted to give something back to this great community. Thanks goes to: dzo, Zenulator, mssmission, enatefox, pmos, vilord, craig0r, and all the others i forget taht make android on our devices possible
Download Link: Umbrella Corporation v2, with working media ROM
OPTIONAL:
Here my startup.txt (Change for your carrier to get data!!!)
#alloctest 0x2000
set RAMSIZE 0x07000000
set RAMADDR 0x10000000
#set FBDURINGBOOT 0
set MTYPE 1553
set KERNEL zImage
#set initrd "initrd.gz"
set initrd "\Storage Card\initrd.gz"
#set initrd "\Storage Card\initrd-console.gz"
#set initrd "\Storage Card\android.bin"
#
# The following kernel parameters are useful
# ppp.username - The username used to connect to the network when dialing #777
# ppp.password - The password used to connect to the network when dialing #777
# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller
# pm.sleep_mode - The mode used when the phone is off
# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,
# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt
# Default is 1, use 1 for best power savings
# board-htckaiser.panel_type - Panel type used to power the panel off and on
# 0=Don't power off the panel (Default)
# 1=Sony 2=Topoly 3=Topoly (probably just the same as 2)
#
set cmdline "clock-7x00.ahb_div=3 clock_7x00.slow=1 elevator=noop ppp.nostart=0 board-htckaiser.panel_type=1 ppp.apn=internet.t-mobile ppp.username=tm ppp.password=tm pm.sleep_mode=1 mddi.width=320 mddi.height=480 msm_sdcc.msmsdcc_fmax=32000000 no_console_suspend board-kaiser-keypad.atttilt=0"
boot
Click to expand...
Click to collapse
and my custom.hero.conf: !!just works if your card is partitioned!!
Klick
Have fun!!!!

Aside from looking rad, does this ROM do anything for us? is it faster due to the removed apk's? I love the Rogers builds, but they freeze/crash on me too often for my liking.

I removed some of the apps, like all thoose who use the g-sensor, also some unneded media files for now, as i've said this is just the first test. If all works well for you ( i got gps, data, wifi, and media files working on my kaiser) i start to tweak it, but the hero from kingklick is very fast and the rom is more responsive than many heros around here. And for me no force colse until now. ( i'll update the thread later, when back home i will tweak some other features)

Is this a real Android rom? or just a bare bones Windows ROM to run Android on top?
I need a lot more details before I can even consider using this.

slow88lx said:
Is this a real Android rom? or just a bare bones Windows ROM to run Android on top?
I need a lot more details before I can even consider using this.
Click to expand...
Click to collapse
This is as much and Android ROM as every other android ROM on the Vogue forum. It is a system image to run Android with via Haret, instructions as to such you can find in other threads/links around here.

craig0r said:
This is as much and Android ROM as every other android ROM on the Vogue forum. It is a system image to run Android with via Haret, instructions as to such you can find in other threads/links around here.
Click to expand...
Click to collapse
Ahh I see. I haven't used Android since Dzo first started with it. I was half hoping someone had finally build some semblance of a ROM with Android.
It sure looks awesome and it would be cool to have the actual Sense UI as opposed to the half ass versions I'm using on SPB MS3 and PointUI

New Version added on first post

doesnt work for me i used all ur basefiles and ur system file, deleted the existing data file.
also replaced my startup.txt with yours and it gets stuck in Loading System
using a kaiser w windows mobile 6.1

Reboot and give it some time

its good to see new stuff. keep it up.

its good to see new stuff. keep it up.
Click to expand...
Click to collapse
Thanks, will see what i can. I have mouch to learn... When i fixed one thing another thing occurs, but hey... that's the fun..

any screenshots of this build?

dude bomb azz boot screen. haha it was so loud it gave me a heart attack then i turned into a zombie.

You got no Anti-Gen at home?

How do you adjust the startup.txt for the vogue? When I run haret it tries to locate the SD card constantly.

On the androidonhtc site you found several infos on how to edit startup /default.txt

Startup.txt

I was looking at "Bangsters" Android build and I saw that he changed his startup text to have a bunch of varriables that we as users could tweak to get the setup perfect for our own needs. I was wondering if it is asking too much to incorperate this into all of the builds since there isn't a specific region that any of these builds are for like the old WM ROMS. I really do not know how much work it would take to implement this so if it is too much I totally understand, just my two cents.
AVAILABLE OPTIONS FOR STARTUP.TXT:
# conn_type: ppp,rmnet
# kernel_type: axi, noaxi, evo, custom
# gps_zone: us, europe, etc (pls check your zone based on pool.ntp.org
# lcd_res: any variable from 140 to 240, my default is 180, Froyo default is 240
# data_size: 2048 for 2GB, 1024 for 1GB, 512 for 512MB
# rel_path: Android. Be careful when changing this. this is the android folder in the sdcard

[HOWTO] 1080p resolution in Webtop!

Sorry if I posted this in the wrong place, but here it is. I'm posting this since I didn't see any info about getting this to work.
What you want to do is edit your Xorg.conf to add the new mode, then use lxrandr to set the new mode. You'll probably want to use a custom panel such as fbpanel, not sure how the default dock thing scales.
Here are the changes you want to make in your xorg.conf:
1. Replace:
Code:
# Option "DisplayMask" "TFTLCD,HDMI"
with:
Code:
Option "DisplayMask" "TFTLCD,HDMI"
(it might just say "TFTLCD", if so replace it with "TFTLCD,HDMI")
2. Replace:
Code:
Option "UseEDIDModes" "TFTLCD"
with:
Code:
Option "UseEDIDModes" "TFTLCD, HDMI"
3. In this section:
Code:
...
Section "Device"
Identifier "Tegra Mirror"
Driver "tegra"
...
Replace:
Code:
Option "DisplayMask" "TFTLCD"
with:
Code:
Option "DisplayMask" "TFTLCD,HDMI"
(this step might not be needed)
4. In this section:
Code:
...
Section "Screen"
Identifier "Screen HDMI"
Device "Tegra HDMI"
...
Replace:
Code:
Modes "1280x720"
with:
Code:
Modes "1920x1080"
and in the same section, replace:
Code:
Virtual 1336 1024
with:
Code:
Virtual 1920 1080
After that, you can then do a "killall Xorg" and then run lxrandr and set your resolution to 1920x1080.
(I'm not exactly sure on the steps as I wrote this after doing the mod, so please correct me if I'm wrong on any of them. I have attached the full xorg.conf)
View attachment xorg.conf.zip

eliplan312 said:
I have attached the full xorg.conf)
View attachment 733316
Click to expand...
Click to collapse
I suppose I can just replae the whole file instead of editing it ??

Not to be a party pooper, but im sure many of us would rather see hdmi mirroring than a higher resolution in webtop which uses a lot of resources.
I voided my warranty and your mum.

pukemon said:
Not to be a party pooper, but im sure many of us would rather see hdmi mirroring than a higher resolution in webtop which uses a lot of resources.
I voided my warranty and your mum.
Click to expand...
Click to collapse
that has zero relevance to this topic.

pukemon said:
Not to be a party pooper, but im sure many of us would rather see hdmi mirroring than a higher resolution in webtop which uses a lot of resources.
Click to expand...
Click to collapse
Based on what I've seen it doesn't really use much more resources than usual. The Tegra 2 is pretty capable.
noxlord said:
I suppose I can just replae the whole file instead of editing it ??
Click to expand...
Click to collapse
Yes, you can just replace the entire file.

Gonna try it now... then feedback

In fact, you only need to edit Section "Screen", reboot and xrandr -s 1920x1080
#add to mode you want
Modes "1280x720 1440x900 1920x1080"
# add # in front of virtual
#Virtual 1920 1080

Where is this xorg.conf located? i cant find it in my rom

Hi, I actually posted another thread about how to get the Photon to have 1080p and either/or mirroring and webtop. I was referred to this thread.
So, I did the whole thing of using the edited Atrix xorg.conf file and did a reboot. But I don't understand how/where to do this command: xrandr -s 1920x1080. I have typed (while SU) that in the /etc/X11 directory -- the response is "xrandr: not found". I have done this both while attached to monitor and not.
what is xrandr? is it possible that xrandr works in the Yes, am a newbie.
Also, I am unclear on this below:
#add to mode you want
Modes "1280x720 1440x900 1920x1080"
# add # in front of virtual
#Virtual 1920 1080
Granted this is a photon so it may not work, but worth a try. However, it looks like the xorg.conf file is the same for the Atrix and the Photon.
Anyhow, thanks.

How to fix an inverted touch axis (and a small request)

So I have something to offer to you and something to ask in return
I've built Atmel's mxt-app (https://github.com/atmel-maxtouch/obp-utils), and have attached it to this thread. On the Desire Z, it can be used as such, from a root prompt:
Code:
#chmod 755 mxt-app
#./mxt-app -d 0 -a 4a
You won't be able to grant execute permissions on a fat32 partition (for example, your SD card), so copy it to somewhere on an ext partition first (/data/local/tmp works well).
It's probably of questionable utility to most, but certainly interesting to play around with.
Anyway, now my own request: I've installed a replacement digitizer, and the x axis is inverted. My gut says this is a config issue with the screen's firmware, but Atmel have a really weird strategy whereby their driver is completely open source but you need to sign an NDA to get the config specification. So, I would like to grab a working configuration from somewhere and just load the whole thing into mine. This is where you come in! If you are feeling helpful:
Code:
#./mxt-app -d 0 -a 4a
S
output.cfg [i]or whatever you want here[/i]
Q
#cp output.cfg /sdcard
Then upload output.cfg from your SD card to here (or just copy/paste its contents, looks like ASCII encoded octal :/) For bonus points, tell me what ROM you are using, as copying configs between different driver versions may not work so nicely.
Cheers!
Jarrad

OK! So I've had a little success and managed to fix the x-axis on my touchscreen being inverted. This goes for anyone using a phone with the mxt224 touchscreen, though the fix isn't perfect - it needs to be reapplied every boot.
TL;DR:
Code:
#./mxt-app -d 0 -a 4a -T9 -W -r9 -n1 [b]01[/b]
should do it for the DZ/G2.
To be more exact, you need to flip the third bit (bit 2, with the least significant bit on the right being bit 0) of Register 9 of the T9 config block - you can read this register like
Code:
#./mxt-app -d 0 -a 4a -T9 -R -r9 -n1 -f
On my touch screen, this outputs (among other things) a value of
Code:
0000 0[b]1[/b]01
. This equals 05 - flipping the bit makes this value equal to
Code:
0000 0[b]0[/b]01 = 01
. The number at you are using to set needs to be specified with a two-hex-digit byte, so say if you are changing 1100 0111 to 1100 0011, you would need to write C3 as your number. Windows calculator in Programmer mode can help with this. It's also important to write zero as the first digit - the program will interpret 1 as 10! You need to write 01.
It would still be really useful to have an output config of a stock touchscreen posted here, as detailed in the previous post, as there are a few other things that the aftermarket controller does differently to the factory DZ part (reporting rate and edge detection are the things I've noticed).

Akdor 1154 said:
OK! So I've had a little success and managed to fix the x-axis on my touchscreen being inverted. This goes for anyone using a phone with the mxt224 touchscreen, though the fix isn't perfect - it needs to be reapplied every boot.
TL;DR:
Code:
#./mxt-app -d 0 -a 4a -T9 -W -r9 -n1 [b]01[/b]
should do it for the DZ/G2.
To be more exact, you need to flip the third bit (bit 2, with the least significant bit on the right being bit 0) of Register 9 of the T9 config block - you can read this register like
Code:
#./mxt-app -d 0 -a 4a -T9 -R -r9 -n1 -f
On my touch screen, this outputs (among other things) a value of
Code:
0000 0[b]1[/b]01
. This equals 05 - flipping the bit makes this value equal to
Code:
0000 0[b]0[/b]01 = 01
. The number at you are using to set needs to be specified with a two-hex-digit byte, so say if you are changing 1100 0111 to 1100 0011, you would need to write C3 as your number. Windows calculator in Programmer mode can help with this. It's also important to write zero as the first digit - the program will interpret 1 as 10! You need to write 01.
It would still be really useful to have an output config of a stock touchscreen posted here, as detailed in the previous post, as there are a few other things that the aftermarket controller does differently to the factory DZ part (reporting rate and edge detection are the things I've noticed).
Click to expand...
Click to collapse
Hi,
How you figured which bits to flip?

I think I found a list of the different registers somewhere and set about flipping bits in the ones that seemed appropriate, haha. It took a bit of mucking around.
Sent from my XT1053 using XDA Premium 4 mobile app

Akdor 1154 said:
I think I found a list of the different registers somewhere and set about flipping bits in the ones that seemed appropriate, haha. It took a bit of mucking around.
Sent from my XT1053 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can you recover that list somehow? It's very needed for some other crappy atmel controller.
Thanks,
Vadim

vadimbrk said:
Can you recover that list somehow? It's very needed for some other crappy atmel controller.
Thanks,
Vadim
Click to expand...
Click to collapse
It's in atmel_mxt_ts.c in the linux kernel from memory.

Akdor 1154 said:
It's in atmel_mxt_ts.c in the linux kernel from memory.
Click to expand...
Click to collapse
Thanks. Have you found a way to make it pernenent?
My device runs windows, in linux I can make it work, as soon as I reboot, ghost touches again...

Nope, I ended up just dropping a script in init.d. On Windows you could just stick a batch file in start-up.
Sent from my XT1053 using XDA Premium 4 mobile app

Akdor 1154 said:
Nope, I ended up just dropping a script in init.d. On Windows you could just stick a batch file in start-up.
Sent from my XT1053 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
To run it on windows it needs to be ported first.
I found a solution to my specific problem, putting the controller in bootloader mode, reboot to windows(touch doesn't work) and disconnecting the controller. Upon connecting it back the device ghost touches disappeared.
Same method of sticking a controller in bootloader mode works on another(android) device with a similar problem to yours. Try it.

vadimbrk said:
To run it on windows it needs to be ported first.
I found a solution to my specific problem, putting the controller in bootloader mode, reboot to windows(touch doesn't work) and disconnecting the controller. Upon connecting it back the device ghost touches disappeared.
Same method of sticking a controller in bootloader mode works on another(android) device with a similar problem to yours. Try it.
Click to expand...
Click to collapse
From the command line that you using its looks like you used an old version of the utility.
Have you tried the --backup parameter? Its save the config to nvram and making the change permanent.

Ah yeah that was a brain fail on the porting, in my defence it was 7am when I replied I haven't needed to play with it much since this thread was posted, I upgraded to a Moto X at the start of the year. I guess if I could make the config permanent I could happily sell my dz though, so thanks for that
Sent from my XT1053 using XDA Premium 4 mobile app

Hi, i also replaced my digitizer with a replacement and the x-axis is flipped.
How can i modify the driver?
mxt-app does not start: error: only position independent executables (PIE) are supported