yashsingh1/xdaforums huggingface dataset:
[HD2 Android Q&A, Help & Troubleshooting and Genera] Archer:
Most Android ROMs (if not all) use a hard-coded value for the MAC address for your wifi card, which is how your router identifies each device. Because you're using the same ROM, you're probably using the same MAC address. The problem won't occur if one or both of you are running Windows, since the card's real MAC address will be used.

You can check this by going to Settings -> Wireless & Networks -> Wi-Fi settings -> Menu -> Advanced and comparing the MAC address of each device.

If you are using the same MAC address then this problem will always occur. Either use different Android builds, or find out how you can change the MAC address. I have seen one build, a while ago, that actually came with instructions on how to set the MAC address, but I think it was specific to that particular build. I don't know if you can do it on any other.

Hope this helps mate.
[HD2 Android Q&A, Help & Troubleshooting and Genera] dpgc213:
Thanks mate, Ill have a look.

What a coincidence, I live in Northampton also
[HD2 Android Q&A, Help & Troubleshooting and Genera] Archer:
As long as you're not trying to use my wifi lol
[HD2 Android Q&A, Help & Troubleshooting and Genera] dpgc213:
haha, I wont.

I just checked the MAC addresses were the same.

Ill load a different android build on mine and see if it works.

Thanks again
[HD2 Android Q&A, Help & Troubleshooting and Genera] Reno_79:
There's a couple of builds that let you change MAC address in the startup.txt as well.

And I'm just down the road from Northampton lol, small world!
[HD2 Android Q&A, Help & Troubleshooting and Genera] dpgc213:
Thanks,

Do you know which builds allow me to do that?

Ive just loaded a different version of android and I get the same MAC address.

Edit: Isit that part that says edit CMDline?

Edit 2: It was that CMDline part.

Thanks for all the help :D Northamptonshire ftw lol
[HD2 Android Q&A, Help & Troubleshooting and Genera] Reno_79:
Just done a (very) quick search and the only build I could find that appear to support it was NexusHD2-FRG83 http://xdaforums.com/showthread.php?t=793924

But I'm sure I read a couple of others that do from a while ago.
[HD2 Android Q&A, Help & Troubleshooting and Genera] dpgc213:
Thanks, i found that it was possible in the build I was already using. Ive changed it and all is good now :D

Cheers for help
[G2 and Desire Z Android Development] Novek:
Hi all!

After searching the wide web of the world I didn't find anyone who cared to program the special characters for nordic keyboards (æ,ø and å). The norwegian stock ROM has got these mapped to own keys, but I've never liked to use stock ROMs, so I was stuck with the "long press method".

New! Now Spanish is also supported!

If you screw up your phone trying to adb push, cp -f these files I'm not responsible yada yada yada (nothing wrong should happend, really)

What I've done is taking the modified files from teferi, and added my own editing for the quick keys (as I had to make place for the chars I removed from jkl) and the special chars of course.

Confirmed on my G2 (running the Sense ROM from MoDaCo), but should work for the Desire Z too! Any guinea pigs out there?

*Norwegian*
version 0.3:
-Fixed issue with , and ; didn't work on hardware keyboard.

version 0.2:
Quick change to the "Z" button, since "`" is used in command substitutions.
-alt-z is still "^", alt-shift-z = "`"

version 0.1:

-alt+j,k,l = æ,ø,å (alt+shift gives capitol letter).
- make ".com" a TAB key, as it ought to be
- left softkey is now "\" "|" "/"
- right softkeys are now "[" "(" "<" and "]" ")" ">"
- alt-z is now "^"

*Spanish version*
Version 0.2
-Corrected filenames for the new files, and included the right "originals".

Version 0.1
[Key] - [Shift + key] - [FN + key] - [Shift + FN + key]

a - A - ! - á
e - E - 3 - é
i - I - 8 - í
o - O - 9 - ó
u - U - 7 - ú
n - N - = - ñ
? - ¿ - " - ¡
. - < - : - >

INSRUCTIONS:

*Add -wwe after "keypad" in the filename for both files if your running a Desire Z based ROM. CM and G2-based will work without -wwe*

- download file

- unzip *.zip

- adb push vision-keypad.kl /sdcard/

- adb push vision-keypad.kcm.bin /sdcard/

- adb shell

- su (if you don't have ro.secure turned off)

- mount -o remount,rw /dev/block/mmcblk0p25 /system

- cp -f /sdcard/vision-keypad.kl /system/usr/keylayout/

- cp -f /sdcard/vision-keypad.kcm.bin /system/usr/keychars/

- reboot

Btw... backup of original keymapping is included... just rename them without .orig, and follow the procedure above :)

Guide to make your own keys:
Download a hex editor (i prefer xvi32), open the "kcm.bin", and alter the symbols shown in the attached .jpg. If you wish to alter the "main" char of the key, you can change that in the .kl file with notepad (check the difference between esp and nor to see an example).

Thanks to teferi for the base files :D
[G2 and Desire Z Android Development] reycat:
Great work! But, since I'm not Norwegian, I'm not going to try it :)

However, I'd love to see a modification of the original English Desire Z Sense keymap with just a few modifications.

Here's a picture of the Desire Z keyboard :)

http://www.theunwired.net/media/news/htc_desire_z_front_open.jpg

1) Getting á, é, í, ó and ú by Shift + FN + a, e, i, o, u (I think it's Shift + Alt in the G2 keyboard). Currently I have to long press the vowel key and then touching the screen. Not efficient.

2) Getting ¿ by using Shift + ? , and maybe ¡ by pressing Shift + FN + ?.

Would it be possible?

If you need the original files or whatever, just tell me :)

Thank you in advance.
[G2 and Desire Z Android Development] Novek:
I would need to get the original desire z keymapping files as I've just the g2... they are a little different with the non-letter keys.
[G2 and Desire Z Android Development] reycat:
Here it is :)

I've just uploaded a file with the two directories, keychars and keylayout.

I think it's interesting that there are several kcm.bin files and several kl files, for different languages, but I don't know how to select them.

Thank you again.
[G2 and Desire Z Android Development] Novek:
Actually... You can't keep both ! and "á" at the "A" key.... or at least you can't get the "á" capitol that way...

It would then be a, A, !, á available on that key.

Do you want me to remove the !, or...
[G2 and Desire Z Android Development] reycat:
I don't mind having to long press A to get the Á, I don't use it that often :-)
[G2 and Desire Z Android Development] stian230:
cool. this is useful for me. I don't got the Nordic version so thanks
[G2 and Desire Z Android Development] reycat:
Novek, have you had time to look over the Spanish version?

No rush, just curious. :)
[G2 and Desire Z Android Development] Novek:
I've actually haven't had time today but I'll try to find some time tomorrow or wednesday...

Just found a bug in the norwegian mod (the comma button doesn't work) so I'll fix that tomorrow too...

/edit

New version up with the , and ; working... :D
[G2 and Desire Z Android Development] GlobaL_TroTTer:
bra jobba!! my friend just go a desire z and he was looking for this:)
[G2 and Desire Z Android Development] reycat:
As I said, no rush... And thank you for your work :)
[G2 and Desire Z Android Development] AnyDone:
I would like to state that these files /system/keymap/* and /system/kaychar/* might be affecting the capacitive buttons belove the screen also. This will not brick anyone's phone (probably :P) but will make it hard to do anything unless fixed.

What I understand:

everyone should use only the files that are meant for their specific DZ version and modify that.

I.E. G2 files on Scandinavian DZ renders capacitive buttons useless. And if u dont have adb access nearby it can be hard to do anything :P
[G2 and Desire Z Android Development] reycat:
Novek, I hadn't seen your private message. I already answered and I'm willing to try your alternative files :)

By the way, does anybody know why there is a lot of different files in /system/usr/keychars and keylayout? I mean, there's a vision-keypad.kcm.bin and a vision-keypad-esn.kcm.bin.

It would seem that the esn file could be useful for us Spanish speakers, but I don't know how to use it.
[G2 and Desire Z Android Development] reycat:
Hi Novek.

Thanks a lot for the Spanish version, but I'm afraid I'm doing something wrong.

I substituted the original files for the ones you have uploaded (I tried both doing it via Root Explorer and following your guide using adb) and when I press Shift + FN + N I still get = instead of ñ. The same with the rest of the keys.

I think I've read somewhere that the Desire Z uses the vision-keypad-wwe.kcm.bin and vision-keypad-wwe.kl file instead of the ones without wwe, could that be it?
[G2 and Desire Z Android Development] Novek:
I would assume that you can just rename the files I posted...

/edit

If it works after renaming to wwe, I'll change the uploaded files..

I'll also re-do the norwegian keymapping with the DZ-files tomorrow - removing the files for G2 now.
[G2 and Desire Z Android Development] reycat:
Takk veldig mye!

:) I just renamed the files and it worked. Thank you very much :)

Edit 1. Mmm.. it worked at first, but now when I use Shift+FN+key I get Á, É, Í... instead of á, é, í.

Edit 2. Nevermind... :D :D I get the capitalized version when the autocorrection kicks in, at the begining of a sentence :)
[G2 and Desire Z Android Development] daveeer:
?

Hi!

Im Hungarian so i am very interested on this application. lots of time I need áéóöőüű!!! :o Im a begginer in the android world. :rolleyes:

Could everyone help for me pls!

I wanna know is this appl. works in the original ROM or not?

And could you write a step by step guide for the installation?

Bests, David!
[G2 and Desire Z Android Development] reycat:
Hi again, Novek! Just noticed that my SYM key is now working like a shortcut key When I press it, I get the "Keyboard shortcuts: Would you like to assign a shortcut to the hardware keys?" screen.

Could you make another version with this fixed? Thank you in advance :)
[G2 and Desire Z Android Development] steviewevie:
In the first posting, it pretty much is a step-by-step guide. Is there any particular part that's confusing you ? Don't be afraid to ask specific questions about things. It's not dumb to ask questions, it's dumb to just try something when you don't understand what you're doing and it could mess up your phone ! :)

Yes, as far as I know this should work with the original ROM.
[G2 and Desire Z Android Development] jubilleum:
It's not really clear for me, how can I make my own layout?

So which file included "which key is which letter" table, and how can i edit it?
[G2 and Desire Z Android Development] Novek:
I'm going to make a guide regarding how to change these files to your own likings :D I'll check the SYM-key also reycat :D

/edit

I've now uploaded the norwegian package, and a .jpg to explain the hex-editor possibilities + a little guide on how to make your own files.

@reycat - could you try to replace your .kl file with the one attached in the new esp.zip?
[G2 and Desire Z Android Development] dzefas:
What about Lithuania? ą č ę ė į š ų ū ž
[G2 and Desire Z Android Development] reycat:
Wow, that was quick :)

Just tried it and the SYM key brings up a menu that is only useful for typing web pages (www., mobile., wap., http://, .org...). It's not the symbol menu I had with the original files.

By the way, I'm going to try to edit the files following your instructions, I just realized I also need the ç key and I'm willing to give it a go :)
[G2 and Desire Z Android Development] reycat:
It's driving me crazy, I don't know why is this happening (the SYM key thing).

I've checked and the last .kl file you provided is exactly the same I was using before all this. And I got the symbol menu. Why isn't it working now? No idea.

But thank you for giving the keys to hex editing the .kcm file, I just added the ç symbol. :)

Edit: I just tweaked my .kcm file instead of using yours (I guess it's based on a G2 file instead of a Desire Z one) and now the symbol menu works :) I swapped the FN+Shift and FN options so that á, é, í, ó and ú are just FN+A, etc, instead of FN+Shift+A. If some Spanish guy wants to give it a try, be welcome :)

Again, thank you very much, Novek.
[G2 and Desire Z Android Development] reycat:
dzefas, it seems that, thanks to Novek instructions, I'm geting the hang of it. If you attach your vision-keypad-wwe.kcm.bin file and describe how do you want to get those symbols, I may be able to help you.

I mean something like:

ą -> FN + Shift + A

č -> FN + Shift + C

.

.
[G2 and Desire Z Android Development] Novek:
Nice to hear :D

I've got much to do with school etc. so have too little time to make those files now, so thanks for the mods reycat :D
[G2 and Desire Z Android Development] Xikeon:
Hi,

This seemed to work a while for me but now I'm having some problems. I'm running an HTC Desire Z with overclock to 1.4 GHz (EZ-DZ Godspeed with stock HTC Desire & Sense kernel), rest is stock and installed the spanish version in the first post.

Now shift+fn+. gives >, which is fine, yet shift+. still gives . instead of <.

Any way to fix this? Could it be that my language is set to English (Netherlands) it doesn't use the wwe? Awkward thing is that it worked for a while..

Thanks in advance.
[G2 and Desire Z Android Development] reycat:
I don't know why it doesn't work. However, here is another version, you can get < and > using Shift+FN + . or ,
[G2 and Desire Z Android Development] Xikeon:
Thanks reycat, seems to work. Now let's hope this one keeps on working.

Compared them both in a hex editor and they don't seem to be very different, don't see anything which would break the old one. Ah well, thanks.
[G2 and Desire Z Android Development] TimD123:
Just in case other people would like to know. I have a Bell Desire Z running Cyanogenmod 6.1 and all I did was grab all files from /system/usr/keychars and /system/usr/keylayout from the original ROM and replaced them in CM.

This worked as I'm now able to use the British pound symbol on the hardware keyboard.
[G2 and Desire Z Android Development] nagusia:
This is just something for people with a Spanish hardware keyboard layout. I have virtuous_sense-vision-v2.0.0 installed and on my model the apostrophe key (to the left of the FN key on the right) would a) bring up the google search box when browsing or b) when writing an email with +FN just bring up the symbols window or otherwise nothing. When I looked at the vision-keypad-wwe.kl file it has this entry:

key 217 SEARCH WAKE_DROPPED

In other words it corresponds to the search key on English models. (I've seen this in photos.) Then when I looked at vision-keypad-esn.kl I found in the same place:

key 40 APOSTROPHE WAKE_DROPPED

However, further down key 40 is listed as "# not use in vison". Thus renaming this file

and replacing the orginal vision-keypad-wwe.kl doesn't work. I replaced the entries (third entry down under column #0) in both the kl files with:

key 217 APOSTROPHE WAKE_DROPPED

Now it works as it should. I'm posting this here because I see that the attached vision-keypad-wwe.kl file has the same problem as far as Spanish layout keyboards are concerned. If you have a Spanish hardware keyboard layout you will have to edit the file.
[G2 and Desire Z Android Development] Quu:
*cough* http://xdaforums.com/showthread.php?t=853509
[G2 and Desire Z Android Development] Creonek:
please Polish keyboard.
[Desire HD General] santet:
I am experiencing this funny issue. I have been unable to update any of my old apps that show updates available. I am able to download new apps though. On trying to update, the download completes successfully but I get an "update unsuccessful" notification.

Anyone else experiencing the same problem. Started on the 18th of november for me.

My phone it's non rooted stock desire hd with latest firmware.
[Desire HD General] ch1lko:
i have the same issue since today - can download new apps, but cannot update existing
[Desire HD General] NoEnd:
i'm sure it is a HTC problem, not an android problem
[Desire HD General] bobbyphoenix:
It's a Market issue. The 18th is when the Market went down for six hours for a huge maintenance upgrade. They are still working out bugs. Hopefully they will all be fixed soon.
[Desire HD General] santet:
OK. Then I'm going to sit tight then. Anyone rooted their htc desire hd.

I know that with the g1 and previous devices rooting meant that you had to install a custom rom and ota updates will no longer be received. Is it the same with the desire hd.?. Are there any good roMs out there, what extras features do they provide.

Just point me to them and I'd look at them myself.
[Desire HD General] santet:
I am still experiencing this. Anyone still getting it out managed to solve theirs.
[XPERIA X10 Q&A, Help & Troubleshooting] dacihappymaker:
is one click lag fix work on x10 ?
[XPERIA X10 Q&A, Help & Troubleshooting] kill3rmus:
I also would like to know, but it seem to only work with samsung i900?
[XPERIA X10 Q&A, Help & Troubleshooting] Wolfbreak:
Doesnt work^^ I tried it. X10 stuck at Sony Ericsson Bootscreen^^
[XPERIA X10 Q&A, Help & Troubleshooting] HunteronX:
I'm sorry, but WHAT!

That changes specific partition filesystems for the Samsung Galaxy S, because of a NAND firmware problem that it has. Don't even bother running it on the X10, it probably won't do anything good.
[XPERIA X10 Q&A, Help & Troubleshooting] gavriel18:
No and it wont work afaik. I think the lag fix converts the phones filesystem from rfs (samsung proprietary system) to ext4. Someone please correct me if i am wrong. :-)

Edit: beat me by a second hunter. But i guess i was right?
[XPERIA X10 Themes and Apps] notowork:
After the gmail app kept giving some unexpected error i tried searching for an alternative for it.

I came across Seven, it has some solid features. you guys might wanna give it a try (if you haven't :P).

Seven has IM and Email with exchange support.

http://community.seven.com/main.php

P.S.

Moderator you can delete this thread if it is duplicate :)
[Touch Pro2, Tilt 2 Windows Mobile General] gunner13:
Hi,

I'm new to all this and after a lot of flashes i finally found my rom to be Energy Stock sense 2.5. Ended up with one question

Is it possible to have the people tab exactly like it is in sense 2.1 in sense 2.5?

I really like that one better, i don't want to see 6 faces at a time i want three people there. Why make me have a half-blank screen?

EDIT: Damn, sorry about the title forgot to fill it and because it's a question it didn't ask me for a title....someone fix this, i can't
[Vibrant General] heygrl:
It's no joke. Ignore the accuracy rating because it's just an estimate. Look at the SNR's between the two. It works much better in buildings, with Google Navigation, has no problem getting a lock, reported accuracy when driving is often 5-7 meters vs 10 then 40 then searching for GPS with the old phone. Never loses it's GPS lock, EVER and I've been testing it for a few days now. No big circles (stable lock)..

just fyi, when someone says their GPS works fine - they might be telling the truth
[Vibrant General] kdf2883:
Just curious, why did you get your phone replaced?
[Vibrant General] heygrl:
The headset jack
[Vibrant General] lqaddict:
The replacement you got is JI6, correct?

Also if you leave it stationary, does the SNR jumps up and down or stays relatively stable?
[Vibrant General] samnada:
I see you're using 3G on the new one, and wifi on the old one. I get faster locks with wifi off. Can you try them both setup exactly the same? Not saying this accounts for the difference, but I like to see exact comparisons on things like this.

Thanks.
[Vibrant General] heygrl:
It's the same with or without WiFi on. It was tethered to the other phone. aGPS data was already downloaded. I've tested it both ways and there is no difference, the new phone reports higher SNR's
[Vibrant General] samnada:
Cool. Thanks.
[Vibrant General] heygrl:
It's much more stable (obviously because of the increased SNR) but I don't know what the reasonable range is. Like I said below, it's cloudy so they should be unstable

Furthermore: off of WiFi for both like requested

It's cloudy today. The new Vibrant's GPS performed admirably when going under clouds while driving but accuracy did decrease. The old Vibrant is probably so bipolar because they are passing clouds. Maybe 2 minutes before I took that pic it had a better lock and as you can see, 4 minutes inbetween shots and the SNR has lowered and shifted on the new Vibrant but the older one completely lost it's (inaccurate) GPS lock.
[Vibrant General] lqaddict:
You should be pretty much on the dot if your SNR is between 30 and 45, the higher the better obviously.
[Vibrant General] ZX3ZX4:
heygrl-

Just so I'm clear...are both of those phones set up identically, i.e., stock 2.1 JI6, etc.? No other differences in settings?
[Vibrant General] rbcamping:
This is true, I traded my phone in because of gps, lag, freezing and crashing, etc...... Got a new phone and transferred all of my stuff to the new phone and the gps was dead on, no more lag and no more freezing, When I tried to use the bluetooth, no worky. tried everything, and so did tmobile, called in and ordered another one, it showed up and everything was great including the bluetooth, loaded in my apps and files and bluetooth quit working,:eek: went to tmobile store and they messed with it including a reset to stock and still no worky, pulled battery and it started working, reloaded my apps and files, no bluetooth again, pulled battery and it now works:confused:

I pulled the battery on the 1st phone twice and it made no difference????????

What can I say, I think the refurbished phones have been changed some how.....

The gps finds my location on a cold start in about 10 to 15 seconds and if I try it in navigator on a cold start it may take several minutes. on a hot start it takes about 5 seconds:)

The compass seems to work and when the car is stopped the arrow stays in one place on the map, but it may point in different directions.

If anyone has a phone that has lag issues and or the gps sucks, I would recomend that you do a warrenty trade in immediately, this sticks it to tmobile and samsung and should give you a phone that works:D
[Vibrant General] SamsungVibrant:
Maybe the reason your new one works better is because you haven't messed it up by tinkering with the GPS settings.

I've followed the GPS drama since the Vibrant came out, and remember reading your posts, you've messed around with the GPS settings a lot on your old phone.

Personally, I don't know who came up with all those fake GPS "fixes" for the Vibrant on this forum, they never worked, and just made GPS performance for me worse. I've had better luck on all stock settings. Seriously, why did the mods allow that thread to continue titled "GPS FIX" bogus, no fix at all.

Maybe going into your GPS settings and deleting data and tinkering with **** is not a good idea.

Enjoy your new phone.
[Vibrant General] heygrl:
I didn't touch the LBSTestMode settings on either phone. It's pointless stuff, it doesn't last/can make stuff worse for how ever long it lasts. Either way it doesn't really make a difference here. I recently lost everything on my old phone thanks to Eugene's FroYo and had to start fresh again. Even beforehand I haven't done anything in LBSTestMode. Changes in GPS software have to come from Samsung.
[Vibrant General] SamsungVibrant:
how many exchanges have you done?
[Vibrant General] heygrl:
One at the crapshack and one from T-Mobile
[Vibrant General] SamsungVibrant:
Hopefully you won't need anymore. Enjoy your new phone.
[Vibrant General] Gigamaster89:
Even when locked, my vibrant only accurate to 30 feet meh.
[Vibrant General] heygrl:
That's a problem, because even under these poor weather conditions (for GPS) getting down to 24FT/over my house on the map in my house is not a problem. Not any worse than the DROID X