G2 roms question - G2 and Desire Z Q&A, Help & Troubleshooting

Hi guys, i have rooted my desire Z using visionary, i want to know if it is possible to just flash the roms available for the g2 on my desire Z or i need to take extra steps...

Yes many G2 roms will work on your DZ. The most notable of which is CM6.1 here.
If you'll note also Cyan has posted both these phones together in the same category.
That should tell you how similar they are and that, unless the dev specifies it, their roms can be interchangeable.

Right now there are a whole different set of forums for the Desire Z. But they're basically the same phone, so I understand the forums will be merged very soon.
Probably the only issue you may hit is the fact that the hardware keyboard layouts are different, and this also affects the capacitive keys since they use the same keymap - e.g. if you flash Cyanogen then I think you'll find the capacitive keys stop working, but there's a fix for that in the DZ forums.

steviewevie said:
Right now there are a whole different set of forums for the Desire Z. But they're basically the same phone, so I understand the forums will be merged very soon.
Probably the only issue you may hit is the fact that the hardware keyboard layouts are different, and this also affects the capacitive keys since they use the same keymap - e.g. if you flash Cyanogen then I think you'll find the capacitive keys stop working, but there's a fix for that in the DZ forums.
Click to expand...
Click to collapse
I have a Desire-Z running CM 6.1. My capacitive buttons worked just fine after flashing the ROM. Only thing that didn't work keyboard wise were the two shortcut keys on the keyboard to the right of the spacebar.

Related

[Q] Multitouch bag Desire Froyo

I think you have all seen the problem with multitouch (or dualtouch, as u wish). I have been reading a lot of info on other sites, including this, but no one can exactly tell, if this problem can be fixed (for example with new ROM or with something else). I have read in the summer that when the froyo comes, then this bug will be fixed, but as I see now, nothing's changed. So what do you think, can this bug be fixed on this device?
Its a matter of the touch-pad used on the device which doesnt support true multitouch..
So in short..
NO..
the multitouch problem on the Desire cannot be fixed software-wise..
Okay. But I don't understand. This is because of touchpad. Ok. I don't need multitouch, dualtouch is enough for me. But why there is a problem with x and y axis, when I cross two axes. Why can't I somehow change values, when x0 would not stick together with x1. So that the values of x0 and x1 will only be equal, when two axes are on the one straight line.
stavec said:
Okay. But I don't understand. This is because of touchpad. Ok. I don't need multitouch, dualtouch is enough for me. But why there is a problem with x and y axis, when I cross two axes. Why can't I somehow change values, when x0 would not stick together with x1. So that the values of x0 and x1 will only be equal, when two axes are on the one straight line.
Click to expand...
Click to collapse
I think because the touchpad is a single-touch pad, but the driver (software) throught some workarounds make possible to detect 2 "singles" touch through the different positions on the 2 axis..But when you cross the 2 axis the workaround doesnt work well (and no solution to make it works)..A touchpad like that will never detect 2 multitouch correctly..Fortunally htc used an other new touchpad for the new smarthphones (wildfire, evo, desire hd..)..
No solution
is it possible to change touchpad from desire to new one like on hd or evo?
andQlimax said:
I think because the touchpad is a single-touch pad, but the driver (software) throught some workarounds make possible to detect 2 "singles" touch through the different positions on the 2 axis..But when you cross the 2 axis the workaround doesnt work well (and no solution to make it works)..A touchpad like that will never detect 2 multitouch correctly..Fortunally htc used an other new touchpad for the new smarthphones (wildfire, evo, desire hd..)..
No solution
Click to expand...
Click to collapse
Its simply because of the algorhythm the touch panel uses to determine the 2nd finger location
Sent from my HTC Desire using Tapatalk
stavec said:
is it possible to change touchpad from desire to new one like on hd or evo?
Click to expand...
Click to collapse
NO! For starters there diffrent sizes not to mention all the driver issues and the fact that every desire rom in existance would give you a black screen, because they use desire touch screen drivers lol
Sent from my HTC Desire using Tapatalk
Why would an input driver mismatch give you a black screen? The touch panel != screen. You would just not have touch input unless you could port the drivers.
Man dont u get it? They have completely different sizes! And all this work and risk just to be able to play 3 or 4 more games...?!
Hardware mods on a cell phone, really?!?
stavec said:
So what do you think, can this bug be fixed on this device?
Click to expand...
Click to collapse
Sorry, man. AFAIK, this is entirely a hardware issue. And while Android is OSS, mobile phone hardware isn't really your desktop tower ATX plug-and-play kinda hardware.
Look, if you're asking questions like "can I replace the screen on my cell phone?", you need to take a step back and think about what you're saying.
If you're interested, I know that CyanogenMod comes with a DevTools suite that includes "Pointer Location", which is actually a really good way to visualize the multi-touch / dual-touch nature of the HTC Desire. You can actually see when the two touch points cross axes that there is some hang-up, but as you drag your fingers on, the two locations become uncoupled again.

Isn't there a fix for multi-touch axis flipping

Now Google maps 5 is out and rotation dosent work, I was wondering about it and remembered that a website had said a member of cyanogen had fixed the axis flipping on the nexus I don't know if this was true, any idea ???
Sent from my HTC Desire using XDA App
I seem to also remember something about this...?
Jesus, Google says that his beloved N1 doesn't support it and you want a fix. Here+s a fix : sell the Desire and get a phone with the full multitouch capable panel.
A colleague of mine has a Desire with a rooted ROM (a Sense 2 one) and the rotation works.
So yes, there is a fix.
I hope that HTC will officially release a (Sense 2) upgrade for the Desire, and that will contain the fix, I don't feel like rooting.
O rly.
FYI Sense 2 is the version that shipped with Desire. If you mean the newer Sense, that's on the Desire HD, that's Sense 3.
Which ROM is that again ? And please let him install http://www.appbrain.com/app/multitouch-visualizer-2/org.metalev.multitouch.visualizer2 and make a vid of the "fix".
Filini1974 said:
A colleague of mine has a Desire with a rooted ROM (a Sense 2 one) and the rotation works.
So yes, there is a fix.
I hope that HTC will officially release a (Sense 2) upgrade for the Desire, and that will contain the fix, I don't feel like rooting.
Click to expand...
Click to collapse
Maybe Google maps thinks the phone supports multitouch as its a dhd rom and activates the option to use rotate. Rotate should still work...but because of the dual touch 'bug' it will get it wrong some of the time.
Yeah, I remember reading about a fix included in the core, but it was disabled. How would I enable it?
Can't we get the apk which is getting installed on the DHD?
I've read about this after some issues with Nova, which I guess is why it isn't supported anyway. The screen itself is not multi-touch and is apparently dubbed "double-touch" and the axis switching is hardware related, however there is a setting buried somewhere in the Android SDK that was designed to only be enabled for a certain device. Enabling it on the Desire, however, was supposed to alleviate some of the issues with axis-switching, although not a total fix. It was mentioned that CM had this setting enabled on their ROMs for Desire, but whether that is still the case I cannot say. This is just from memory, I'll have to do a bit more digging to refresh my memory.
EDIT: Asked around on the CM IRC and that particular 'feature' was indeed pulled, however was reinstated a few days ago, so probably only on the nightlies for the moment.
EDIT 2: Flashed a CM nightly and it doesn't appear to have made matters any better
Yes the multitouch is indeed enabled in maps on dhd roms, but the problem is not fixed. You can easily see, when your cross the axis with your fingers, and it definately still doesn't work well.
Yes, this issue is very irritating when playing games like SliceIt as well.
The touchscreen hardware is only capable of determining the rectanlge containing the 2 touched points.
If the desire screen is capable of detecting two fingers as long as they don't cross on the y and x axis, two finger rotation should be more than possible on google maps just as long as you keep the rotation no larger that 90 degrees between the y and x axis and even then it should only cause a "hickup" in the rotation so although it won't be great, if active, it should be ok for use!
The two touches is not what bothers me it is the axis flipping that's annoying I will try to flash a nightly and will see what happens.
Sent from my HTC Desire using XDA App
thed0g said:
Jesus, Google says that his beloved N1 doesn't support it and you want a fix. Here+s a fix : sell the Desire and get a phone with the full multitouch capable panel.
Click to expand...
Click to collapse
There's a nexus one two finger fix. Don't know of adesire port of it.
In nexus one development section.
Desire is the source of all suffering.
Has anyone found a fix for multitouch on the desire yet?
i found a link(http://forum.xda-developers.com/showthread.php?t=767654&page=4) to another post on fixing multitouch on an acer liquid sharing drivers for developers, so can people please take a look and see if something can be done for the desire?
thanks in advance
Have you read the lasts posts in the thread you quote ?

[Q] HW keyboard: long press for numbers?

Is there a way on the hardware keyboard to get the numbers (and the other Fn characters) by long pressing the keys?
Used the search, used Google, but either I'm using the wrong keywords or it doesn't exist.
I would like to know if this is possible too because I know you.can do this with the virtual keyboard
Sent from my HTC Vision using XDA App
Are Evilcuber and I the only ones interested in this, or are we the only ones stupid enough not to find out how to do it?
I would like to know it too
Sent from my HTC Vision using Tapatalk
Me too!!!!!!!
Yes!! Interest here too.
Sent from my T-Mobile G2 using Tapatalk
and me!!!
could be usefull... anyone up for an app that could enable this????????
Bump and hoping somebody has the answer...
You could try a Sense ROM. I know Virtuous Sense 2.0 does this, though there are some other long-pressing problems.
Yep, I use Virtual Sense 2.0.0 and there you can get to the numbers and other FN-characters by holding the respective key. But you have to have a Desire Z or G2 to use that ROM. I like it a lot, because it's based on the latest Stock-ROM providing you Android 2.3.3 with automatic smart overclocking and other Features.
And I personally haven't experienced and other long pressing problems so far...
Tronar
Hmm, I have a Desire Z, but to flash a different ROM just to get the long-press function...
I'm running CM 7, and I really like that. Maybe I should Virtual Sense.
But if it would be possible under Cyanogen, I would be happy
-edit- Oh, you meant Virtuous Sense. That's why I couldn't find it
Weekday-bump!
Weekend-bump!
I want this feature too.
It is not available in virtuous unity 1.31.0
i have no idea how to do so even though i am interested to do so..
troublesome to keep on pressing the FN button with another finger
Holiday-bump!

[Q] Ice Cream SENSEwich Beta 6

Hi, I'm trying to send message to thread about http://forum.xda-developers.com/showthread.php?t=1546915, but as I am a new member of the forum, I need to rack up 10 posts before making a post directly to correct thread.
So here I go with the questions here, with 10 posts or so if I get reply's here.
First post and first question 1:
Hi, thanks for good custom rom.
The question:
I did superwipe for my Desire Z and installed the latest beta 6 to my phone. Noticed that it is currently missing all international keyboard configurations for the physical keyboard that the CM9 and other ICS firmwares have. Otherwise than that it is working quite well.
So can you please add to Beta 7 or RC (when ever that is coming) the missing keyboard configurations? I also tested the bluetooth (which was not working with other ROMS that well) and it works quite well with my car audio and Nokia's BH-905i headset...
Please do notice that Sense ROMs do not have international settings for the hardware keyboard. Apart from the stock ROM, no other Sense 3/3.5/3.6 and even 4 have this setting.
Use the search tool in the right of the thread title. This has been discussed before in the Ice Cream Sensewich thread.
Ah my bad, just interested why it cannot be put in there when other roms have it?
dun1982 said:
Ah my bad, just interested why it cannot be put in there when other roms have it?
Click to expand...
Click to collapse
Well, as opposed to AOSP (Cyanogen, ILWT, etc) where code is freely available to edit and change stuff, Sense is HTC's proprietary code. They are not required to show us the code, so inner workings of Sense are hidden to us.
Some of the stuff can be edited because it's available by changing some parameters, but for the most part, Sense is pretty much an inaccessible gate.
bogdan5844 said:
Well, as opposed to AOSP (Cyanogen, ILWT, etc) where code is freely available to edit and change stuff, Sense is HTC's proprietary code. They are not required to show us the code, so inner workings of Sense are hidden to us.
Some of the stuff can be edited because it's available by changing some parameters, but for the most part, Sense is pretty much an inaccessible gate.
Click to expand...
Click to collapse
So this wont help (http://forum.xda-developers.com/showthread.php?p=25013313) to get at least Nordic hardware keyboard to work? I can try and flash it to my device and see if it works. I'll report back if I encounter some issues while doing it.
dun1982 said:
So this wont help (http://forum.xda-developers.com/showthread.php?p=25013313) to get at least Nordic hardware keyboard to work? I can try and flash it to my device and see if it works. I'll report back if I encounter some issues while doing it.
Click to expand...
Click to collapse
I am no developer, but if the part about the hardware keyboard is managed by the operating system, and not by Sense's framework, then yes, it should be just a manner of adding the correct keymaps. Probably no one has bothered to do that, yet ?
I guess you can copy any working keymaps and keylayouts to IceCreamSensewich. You can find the keymaps and keylayout in the /system/usr folder.

Anyone experiencing these keyboard issues with CM7?

I always start with a preemptive apology if this has been posted elsewhere (I searched hard, but sometimes I end up getting chastised)
First, specs of the culprit phone:
HTC Desire Z (T-Mobile G2) Running CM7 Stable.
Anyway! I have been enjoying my G2 since the day I upgraded from my day one G1. I am familiar with rooting, but not an expert with the android system. Something has always bothered me on the G2 with CM7. After rooting and flashing my top row of buttons do not input the correct numbers when forced into a numerical entry only (e.g. I want to dial with the flip out keyboard.) With the stock rom if I push the button that is "Q" and "1" in the dialer it would input a 1, but after rooting and flashing all the numbers flip around.
Specifically:
pushing Q-W-E-R-T-Y-U-I-O-P should output 1-2-3-4-5-6-7-8-9-0, instead it is 7-9-3-7-8-9-8-4-7-6. If I push alt, and then the number it works correctly.
I realize there are other ways to input the numbers (onscreen keyboard), but this is bothering me.
Any input, help, theories, etc... would be appreciated.
just tested on cm7 elitemod, same here although if you hadn't mentioned it I never would have known!
if it really bothers you I'm sure it is a cm7 issue, you could try and find another rom with a different base and see if that works or you would have to remap the buttons to the stock phone app (?) to get it to work, I'm sure there is a fix but couldn't tell you the exact steps
also you could report it to cyanogen if the team really cares about gingerbread still maybe rc3 will have a fix thanks to your bug report
Sent from my HTC Vision using xda premium
It's mimicing a touch tone phone so that when the listed number is 800-555-HELL you can type that and you'll get the proper numbers (eg. 800-555-4355)
Sent from my HTC Vision using xda app-developers app
now that makes perfect sense, not a bug at all I guess but rather a neat feature! sorry but if you report this to cm they will not care as I assume it is all as intended!
if you really want to not hit alt you'll have to have to remap yourself
Sent from my HTC Vision using xda premium

Categories

Resources