INTRO
I've started this thread to port the EzInput Keyboard to QVGA resolution. The keyboard is now fully functional yet still has a couple of small glitches to be fixed in portrait mode.
I am doing all the testing on my elfin, so I cannot assure that it will work on other devices so you'll have to test it yourselves!
You can download it here:
http://www.sendspace.com/file/uxi3be
THANKS
I must thank
DupinBJK:
http://forum.xda-developers.com/showthread.php?t=486227
nikoan89:
http://forum.xda-developers.com/showthread.php?t=489032
and
Conflipper
for their hard work on the VGA port, since I have mixed parts of their ports to get this QVGA version working.
KNOWN BUGS
XT9 is not currently working: the keyboard seems to get the coordinates (size and position) of the VGA keys. E.g.: if you press "q", "a" or "w" the keyboard will write "q" on the screen, since the three letters are in the area of the "q" key in a VGA screen (double size).
Any help on this matter would be really appreciated!!!
XT9 UPDATE 05/01/2009:
I´ve managed to get XT9 working by replacing the xT9ime.dll of the EzInput 2 with the EzInput 1.5 dll supplied with the ROM I am using. The problem now is that I cannot change XT9 mode back to normal mode .
Anyway I encourage you to test this and see if we can get a solution to the XT9 issues.
To test it, just go to the windows directory, rename eT9ime.dll to something else (e.g. eT9ime.dll.OLD) and reset your device (this should restore the dll supplied with your ROM).
I´m waiting for your comments!!!!
VIBRATION/XT9 UPDATE 05/13/2009:
I managed to get vibration to work a couple of weeks ago, but I wanted to fix the T9 mode before releasing a new version.
I´ve been working on T9 and have not been able to find where the code responsible for calculating the key pressed (based on the coordinates) is.
OPTION A: If anyone is able to find such place in the code or just point me in the right direction, I´ll find the time to patch et9Ime.dll so that QVGA users can enjoy T9 in this keyboard.
OPTION B: Another possible option would be to patch the et9Ime.dll from ezinput 1.5, but the mappings of some important keys seem to be different (XT9/ABC switch for example), and also different registry keys need to be updated so that everything works as it should.
Sorry for the lack of feedback, but I need more time for fixing these issues since this is the first time I am dealing with SIP/IME/IMM and stuff and I´ve found it a little bit more complex than I thought it would be.
HOWTO
Additionally, I'm planning on writing a very simple "howto" to explain people what they can do to adjust/fix/change the layout of the keyboard.
PS: I cannot post any screenshot now, so if anyone of you can upload one I'd be grateful.
problem on XT9 mode, maybe is the key mapping, i dunno that
for example type q,w,a,s the result is --> qqqq
type e,r,d ---> www
thanks for your hard working
T9 issue
You're right (i did not test the XT9 )
I'll have a look at it.
Thanks
Nice
Just 2 questions :
- vibrate when keys are pressed : Don t work normal maybe ...
- Is there a way to change language to french? i see 40C file ...
ty
looks great, good to finally have EZInput for QVGA.
major bug I noticed it messes up the keyboard mapping..for example Caps does not function, nor does the light, just flickers on then off when caps is hit, I believe to turn caps on and off (at least for me) I would have to use function, which also works for function (if that makes sense) lol
also the function keys got incorrectly mapped, I will try the tilt keyboard fix, hopefully that will work, and you can post that Cab.
Minor Issue: no SIP image to open the keyboard on the phone. its a black square, hit the square to active SIP. Would be nice to get a cool new icon though ;P
other then that, I will continue to test this, because the spacing between the keys and the skin is very nice
Thanks for your hard work and the post
I installed this new version and the only major thing I see compared to all the rest of the one you have posted is that the SIP Icon for the Keyboard that shows between the softkeys is missing, if you press the empty space the Keyboard still pops up and is functional but the icon is gone.
thanks man. Work great
So I don't have the phone keypad...is this just a problem with me or does anyone else have this problem?
XT9 is off, but that's fine cause I don't find a need for xt9 on a full keyboard anyways. Though like I said in the other thread I wish there was compact qwerty, or at least I could have the compact qwerty from my other keyboard as well.
Thanks a lot! Im at school now, but as soon as I get home, I'll install this on my phone.
- Thanks, your job is really appreciated.
Great !!!
I've been waiting for this for sometime now and just say thanks for the Qvga version Just wondering if anyone is working on the xt9 bug, i have gotten accustom to using that but if not no worries still a great keyboard !!!
Well, this full qwerty is a huge improvement over the EZ-Input one. I installed the keyboard and used the full qwerty without any problems. HOWEVER, does the Compact QWERTY mode not work with this? Thanks.
Thank you man, you are awesome !
I don't have any problems with it, except the reported bug of the SIP Icon.
But the keyboard on my Elf is a bit slow without O/C. (WM 6.5)
I love this keyboard !
XT9 bug
I've been looking at the XML files, the kdb files and the ldb files and I still cannot figure out the place where the XT9 keys size/position (x,y,h,w) is defined.
Does anyone know whether it's hardcoded in a PE module or it can be configured anywhere?
BTW, I'm afraid Compact QWERTY is not possible for the time being...
Sorry if I'm repeating. If I switch to numeric and press a key and then go back to ABC then all the keys are screwed up and when I press them I get the wrong keys. Do others have the same problem?
littld, i'm not experiencing that behaviour, sorry
asak0 said:
I've been looking at the XML files, the kdb files and the ldb files and I still cannot figure out the place where the XT9 keys size/position (x,y,h,w) is defined.
Does anyone know whether it's hardcoded in a PE module or it can be configured anywhere?
BTW, I'm afraid Compact QWERTY is not possible for the time being...
Click to expand...
Click to collapse
I have been trying to find this out too, I have looked everywhere and can't find the positions for XT9.
Side note, on all 3 previous versions you could use XT9 in ABC and it worked perfectly, but in the new version it just types normally in ABC and XT9 is still broke.
ems275 said:
I have been trying to find this out too, I have looked everywhere and can't find the positions for XT9.
Side note, on all 3 previous versions you could use XT9 in ABC and it worked perfectly, but in the new version it just types normally in ABC and XT9 is still broke.
Click to expand...
Click to collapse
You mean in the previous versions I posted in the QVGA Rhodium Development thread?
asak0 said:
You mean in the previous versions I posted in the QVGA Rhodium Development thread?
Click to expand...
Click to collapse
Yes, all 3 you posted in that thread. If set to XT9 all key mapping was off as I had posted in that thread and others. But ABC worked as XT9 without a problem. It was weird. But I am running the last posted version which I downloaded from sendspace and it works as described above. When I installed the one when you opened this thread also from sendspace XT9 key mapping is still the same, totally off and ABC just functions as it should, regular typing with no text prediction.
Hope that makes sense?
ems275 said:
Yes, all 3 you posted in that thread. If set to XT9 all key mapping was off as I had posted in that thread and others. But ABC worked as XT9 without a problem. It was weird. But I am running the last posted version which I downloaded from sendspace and it works as described above. When I installed the one when you opened this thread also from sendspace XT9 key mapping is still the same, totally off and ABC just functions as it should, regular typing with no text prediction.
Hope that makes sense?
Click to expand...
Click to collapse
Not really...
Anyway I'll play around a bit with the different modules to see what I can get.
https://docs.google.com/leaf?id=0B1VD5urJF8c-YzMxOWNlYWYtODFhMi00NWRkLWIyMzMtMDU3YTExM2RlNjli&hl=en
It is the latest updated version of Dosbox from adosbox.googlecode.com, with keys mapped to match the G2 keyboard. It's my first actual packaged Android app, so hopefully I didn't screw anything up.
Mouse support is disabled, only the left ALT key works to access extended characters, and the ALT key seems to become stuck if you hold it down for too long, but you can un-stick it by pressing it once and releasing.
The track pad is a little too sensitive for my liking, but a few CGA games I tried seem to work well (Telengard, Ultima IV, Legacy of the Ancients.)
You'll need to put DOSBOX.CONF from adosbox.googlecode.com in the root folder of your sdcard.
I don't make any promises as to whether this works or how well it works!
*edit*
Just to clarify, this is not MY port, all I did was take someone else's hard work and fix keymappings for the G2.
Also, no matter what you set the CPU cycles to, it seems to run as fast as it possibly can. It consumes 100% CPU usage and does not hibernate in the background when you switch apps, so be careful!
*/edit*
sweet!
DOSbox!
thx
Has this worked for anyone?
This worked for me, which is great. Made it easier to play with.
It is a tad slow, and there is no sound, but hey, it's dosbox on a friggin cell phone!
The real problem with this port is the lack of a good way to do savestates in DosBox. Since the video hardware can be weird and restoring its state can be tricky there is no official support for saves states in DosBox at all, although there have been some patches.
Anyway, I'm getting off topic here. Thanks for the work fixing the keyboard.
How did you do this? I have a motorola Flipside and I would like to fix the adosbox key mappings for it. Is there anything I can do with settings like the Mapper.txt file, or does it require modifying the code? (I know its not the best phone but my family is on att and they are paying the bill)
I was able to work around not having colon by using this keymap file: http://forum.xda-developers.com/showthread.php?t=837002 and then changing SEARCH to SEMICOLON
Other then this i didn't see any other characters that weren't there (even though some were presented incorrectly)
I am new to adosbox, does this mean I could finally run windows 3.1net on my G2? Lookout ms paint, here I come!
Wait, no mouse? Bummer.
Sent from my HTC Vision with CM 6.1 and Pershoot's Kernel.
keenerb:
How did you modified the bindings? I've changed left and right arrow keys mappings to shift and dot in mapper-0.74.map but it has disabled trackpad x axis
And do you know which codes have these two shortcut keys (that ones with three dots and numbers)?
I'm trying to remap keys for adosbox 0.2.5
Greetings.
----------edit---------
I've managed to change the:
Left FN - it's recognised as Left alt key
Left Shift
Tab
...as 3 of 4 arrow keys.
This disables trackpad scrolling however.
But it let's for playing dos games like Hocus Pocus and so on where you need arrow keys.
Do you (or anyone) know what are the numbers of following keys?:
Keyboard menu key
Shortcut key 1
Shortcut key 2
Search key
Sym key
We've got much room to bind.
Or maybe anyone knows where or how to check those numbers?
I know you are not the original author of the android port of DOSBox but I just cannot get any replies from the person listed as the author and I need to find out how to change things like the display resolution, etc.and thought you might know.
I have a dos program that runs fine on my DOSBox 0.74 installed on my Windows 7 laptop. But every time I try to run it on aDOSBox installed on my rooted android 2.3.4 phone, aDOSBox crashes and throws me out into android. I need to find out how to find out what is causing the crash. I think it might be the display but am not sure. Can you help?
Thanks.
hey! i've got this issue with the mapping of the italian keyboard. The FN key doesn't work, when i press it, it gives me the @ symbol. I wanted to fix the problem my self by editing the file in the rootfs.img, but to open it you need to mount it in Ubuntu. I installed Ubuntu, but i couldn't manage to mount the file, since it's the first time i use linux. I entered in boot mode by typing: sudo bash (it makes me a root user)
then i typed: mkdir mnt/New_folder, but it kept on saying "cannot create directory" . So now i can't create the new folder to mount the rootfs.img !!!! It's driving me crazy!! please help!! I would appreciate if someone could explain me how to do it or fix this thing for me!!! Thanks!!!!!!
americano91 said:
hey! i've got this issue with the mapping of the italian keyboard. The FN key doesn't work, when i press it, it gives me the @ symbol. I wanted to fix the problem my self by editing the file in the rootfs.img, but to open it you need to mount it in Ubuntu. I installed Ubuntu, but i couldn't manage to mount the file, since it's the first time i use linux. I entered in boot mode by typing: sudo bash (it makes me a root user)
then i typed: mkdir mnt/New_folder, but it kept on saying "cannot create directory" . So now i can't create the new folder to mount the rootfs.img !!!! It's driving me crazy!! please help!! I would appreciate if someone could explain me how to do it or fix this thing for me!!! Thanks!!!!!!
Click to expand...
Click to collapse
Hi, there's a typo in the example "startup.txt", you have to put the _ like for other keyboard layouts, i.e. "rhod100_it"
Happy xdandroiding
Ciao, c'è un errore di battitura nei file di esempio, devi mettere il trattino basso _ come negli altri: "rhod100_it".
Italian Rhod 100 Key Map
americano91 said:
hey! i've got this issue with the mapping of the italian keyboard. The FN key doesn't work, when i press it, it gives me the @ symbol. I wanted to fix the problem my self by editing the file in the rootfs.img, but to open it you need to mount it in Ubuntu. I installed Ubuntu, but i couldn't manage to mount the file, since it's the first time i use linux. I entered in boot mode by typing: sudo bash (it makes me a root user)
then i typed: mkdir mnt/New_folder, but it kept on saying "cannot create directory" . So now i can't create the new folder to mount the rootfs.img !!!! It's driving me crazy!! please help!! I would appreciate if someone could explain me how to do it or fix this thing for me!!! Thanks!!!!!!
Click to expand...
Click to collapse
It just so happens that I was working on a new keymap for the Italian Rhod 100. I'll see if I can post a new version of my rootfs package with the updated Italian and French keymaps later today.
sad0felix said:
Hi, there's a typo in the example "startup.txt", you have to put the _ like for other keyboard layouts, i.e. "rhod100_it"
Happy xdandroiding
Ciao, c'è un errore di battitura nei file di esempio, devi mettere il trattino basso _ come negli altri: "rhod100_it".
Click to expand...
Click to collapse
Wow!! that's all?!?!? i can't believe i wasted an entire day after this! thanks!!
tutto qui`!?!? non credevo fosse cosi` banale la soluzione XD e io che ci ho perso un giorno intero!! grazie mille
EDIT: the keyboard is still not fully functional. The FN works to put all the secondary letters and symbols, but it doesn't work to enable caps lock, to open the window with all the symbols, to enable xt9, to open a new sms and to go on the web.
@F22 : thanks! i really hope your edit made it fully functional!!
americano91 said:
Wow!! that's all?!?!? i can't believe i wasted an entire day after this! thanks!!
tutto qui`!?!? non credevo fosse cosi` banale la soluzione XD e io che ci ho perso un giorno intero!! grazie mille
EDIT: the keyboard is still not fully functional. The FN works to put all the secondary letters and symbols, but it doesn't work to enable caps lock, to open the window with all the symbols, to enable xt9, to open a new sms and to go on the web.
@F22 : thanks! i really hope your edit made it fully functional!!
Click to expand...
Click to collapse
*cough* There's fully functional and there's fully functional. Let me explain. You have a keyboard designed for Windows Mobile 6.1/6.5. Some keys in Windows Mobile don't exist in Android. Some of the keyboard combinations that are available on Windows Mobile just aren't available on Android. To get the same functionality in android you thus need to adapt to the android way of doing things. The symbol palette for android is also pretty minimal (just 12 characters) unfortunately. I've submitted a patch to system.ext2 to expand it to 18 characters, but most people won't see the expanded symbol palette until FRX04 is released, probably in late December. So no, you won't get everything that is currently printed on your keys even with my new Italian keymap. Your FN, Ctrl and SYM keys will work. Envelope will be mapped to SEARCH. Internet & SMS won't work because there is no way to assign that sort of functionality to a key without replacing the keycode and losing the rest of the key's functionality.
My suggestion would be to use short-cuts from within android for things like the internet and sms from the keyboard. Once your envelope key is matched to SEARCH in the new keymap you'll be able to do that since short-cuts in android combine the search key with another key. For example, by default, search+b opens up your browser, search+s opens up messaging, search+g opens up Gmail, search+e opens up email, search+m opens up the music player, etc... (These are adjustable from within Settings>Applications>Quick Launch. Personally, on my phone, I've moved messaging to Search+M and the music player to Search+P for easier use since it's awkward to press S while holding down the envelope key.) I'll look into XT9. I'm not sure about that one at the moment as it doesn't exist on my 210.
F22 said:
*cough* There's fully functional and there's fully functional. Let me explain. You have a keyboard designed for Windows Mobile 6.1/6.5. Some keys in Windows Mobile don't exist in Android. Some of the keyboard combinations that are available on Windows Mobile just aren't available on Android. To get the same functionality in android you thus need to adapt to the android way of doing things. The symbol palette for android is also pretty minimal (just 12 characters) unfortunately. I've submitted a patch to system.ext2 to expand it to 18 characters, but most people won't see the expanded symbol palette until FRX04 is released, probably in late December. So no, you won't get everything that is currently printed on your keys even with my new Italian keymap. Your FN, Ctrl and SYM keys will work. Envelope will be mapped to SEARCH. Internet & SMS won't work because there is no way to assign that sort of functionality to a key without replacing the keycode and losing the rest of the key's functionality.
My suggestion would be to use short-cuts from within android for things like the internet and sms from the keyboard. Once you have the search key mapped to envelope you'll be able to do that since short-cuts in android combine the search key with another key. For example, by default, search+b opens up your browser, search+s opens up messaging, search+g opens up Gmail, search+e opens up email, search+m opens up the music player, etc... (These are adjustable from within Settings>Applications>Quick Launch. Personally, on my phone, I've moved messaging to Search+M and the music player to Search+P for easier use since it's awkward to press S while holding down the envelope key.) I'll look into XT9. I'm not sure about that one at the moment as it doesn't exist on my 210.
Click to expand...
Click to collapse
OK, i understand now. I really cared about the SYM function, the rest doesn't matter so much. Thank you for explaining me!!....i wanted to ask 2 more things.
1) after i changed from :"rhod100it" to "rhod100_it" and rebooted android through the XDANDROID icon, it changed back to "rhod100it", so i have to boot android with haret.exe
after i change it. Will this problem be solved with your rootfs.img? if not, can i solve it on my own?
2)the change i made in startup.txt, made the power button not functional in android. With the power button and the home button(hang call) i used to turn off/on the screen (i changed the function of the home button in the OPTIONS and gave it the function to go back on the home page). Now i can't turn off the screen(i can only turn it on when the screen turns off by it self) unless i put the home button's function back to default. Again, will this problem be solved with your rootfs.img? if not, can i solve it on my own?
americano91 said:
OK, i understand now. I really cared about the SYM function, the rest doesn't matter so much. Thank you for explaining me!!....i wanted to ask 2 more things.
1) after i changed from :rhod100it" to "rhod100_it" and rebooted android through the the XDANDROID icon, it changed back to "rhod100it", so i have to boot android with haret.exe
after i change it. Will this problem be solved with your rootfs.img? if not, can i solve it on my own?
Click to expand...
Click to collapse
The init script in rootfs specifically looks for physkeyboard=rhod100_it in your startup.txt. If it sees that then the Italian keyboard map & layout files will be used. If your startup.txt is being overwritten then I assume you're using some sort of startup utility. That isn't part of the rootfs. Sovereign wrote the startup utility which Reefer packages into his builds. If you're using one of Reefer's builds then you you should talk to Reefer or Sovereign about fixing that so that it works properly in the future for Italian 100's.
2)the change i made in startup.txt, made the power button not functional in andoid. With the power button and the home button(hang call) i used to turn off/on the screen (i changed the function of the home button in the OPTIONS and gave it the function to go back on the home page). Now i can't turn off the screen(i can only turn it on when the screen turns off by it self) unless i put the home button's function back to default. Again, will this problem be solved with your rootfs.img? if not, can i solve it on my own?(for example by changing kernel, i recently updated it to the last one....maybe an older version might help...)
Click to expand...
Click to collapse
I wasn't aware that there's an option in startup.txt that makes the power button non-functional. How did you do that? My rootfs.img doesn't touch the power button. It operates as it normally does. It simply adds an option to startup.txt to remap the endcall button to the keycode HOME so that it not only works as home on a short press, but the ability to long press it and get the recent apps list is also preserved. (The software option in spare parts that currently exists doesn't remap the scan code, and thus the ability to pull up the recent apps list is lost.)
F22 said:
The init script in rootfs specifically looks for physkeyboard=rhod100_it in your startup.txt. If it sees that then the Italian keyboard map & layout files will be used. If your startup.txt is being overwritten then I assume you're using some sort of startup utility. That isn't part of the rootfs. Sovereign wrote the startup utility which Reefer packages into his builds. If you're using one of Reefer's builds then you you should talk to Reefer or Sovereign about fixing that so that it works properly in the future for Italian 100's.
Click to expand...
Click to collapse
OK thank you! i'll talk to him if i can't fix it!
F22 said:
I wasn't aware that there's an option in startup.txt that makes the power button non-functional. How did you do that? My rootfs.img doesn't touch the power button. It operates as it normally does. It simply adds an option to startup.txt to remap the endcall button to the keycode HOME so that it not only works as home on a short press, but the ability to long press it and get the recent apps list is also preserved. (The software option in spare parts that currently exists doesn't remap the scan code, and thus the ability to pull up the recent apps list is lost.)
Click to expand...
Click to collapse
You misunderstood...when i said "change in the startup.txt" i meant the change from "rhod100it" to "rhod100_it". After this change, the power button became nonfunctional...this is why i asked you...
americano91 said:
OK thank you! i'll talk to him if i can't fix it!
You misunderstood...when i said "change in the startup.txt" i meant the change from "rhod100it" to "rhod100_it". After this change, the power button became nonfunctional...this is why i asked you...
Click to expand...
Click to collapse
That's strange. Your keyboard should have no effect on the power button. In fact, you can't change the power button's functionality from the rootfs where the keyboard is handled, only the kernel. What version of the kernel are you currently running? And please post your startup.txt.
F22 said:
I wasn't aware that there's an option in startup.txt that makes the power button non-functional. How did you do that? My rootfs.img doesn't touch the power button. It operates as it normally does. It simply adds an option to startup.txt to remap the endcall button to the keycode HOME so that it not only works as home on a short press, but the ability to long press it and get the recent apps list is also preserved. (The software option in spare parts that currently exists doesn't remap the scan code, and thus the ability to pull up the recent apps list is lost.)
Click to expand...
Click to collapse
Hi both.
I guess, because all of this happened to me too the very first time I approched to Xdandroid, that if no correct value is found in startup, the default keymap is loaded.
Can't be sure but I think default is Tilt2.
Maybe Tilt2 has power/endcall ... tilted ...
Therefore some language could be more advanced than others in regard of testing branches/key assignments' scripts.
In this regard I am using your personalized rootfs, with endcall/power on power button and home/recent tasks on red button.
For sym I use touch keyboard, which contains all accents. Quite tricky closing and opening, but not as slow as only touch
Cheers
ps
I read in another thread that you might need some italian to complete/check the IT keymap.
Can I help?
F22 said:
That's strange. Your keyboard should have no effect on the power button. In fact, you can't change the power button's functionality from the rootfs where the keyboard is handled, only the kernel. What version of the kernel are you currently running? And please post your startup.txt.
Click to expand...
Click to collapse
I'm using this kernel: htc-msm-linux @ 20101124_215731(the newest one) and this is my startup.txt:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=2,1,3 force_cdma=0 pm.sleep_mode=2 acpuclock.oc_freq_khz=786432 hw3d.force=1 physkeyboard=rhod100_it"
boot
americano91 said:
I'm using this kernel: htc-msm-linux @ 20101124_215731(the newest one) and this is my startup.txt:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=2,1,3 force_cdma=0 pm.sleep_mode=2 acpuclock.oc_freq_khz=786432 hw3d.force=1 physkeyboard=rhod100_it"
boot
Click to expand...
Click to collapse
I copied your startup above onto my phone and I'm having no trouble using the power button to sleep/wake my phone. Now granted, the first time I tried it my phone was incredibly sluggish, and several of my keys seemed to produce 2 or 3 copies of the same letter every time they were pressed. Nevertheless initial sluggishness when you replace an XDAndroid component is a common issue unfortunately. A reboot fixed that and now all seems well with your startup.txt. So it doesn't look like your startup.txt is the source of your problem with the power button. Are you absolutely certain you updated to the 11/24 kernel and not an older one? Your problem sounds very much like a kernel issue.
F22 said:
I copied your startup above onto my phone and I'm having no trouble using the power button to sleep/wake my phone. Now granted, the first time I tried it my phone was incredibly sluggish, and several of my keys seemed to produce 2 or 3 copies of the same letter every time they were pressed. Nevertheless initial sluggishness when you replace an XDAndroid component is a common issue unfortunately. A reboot fixed that and now all seems well with your startup.txt. So it doesn't look like your startup.txt is the source of your problem with the power button. Are you absolutely certain you updated to the 11/24 kernel and not an older one? Your problem sounds very much like a kernel issue.
Click to expand...
Click to collapse
What about the setting Power Button Ends Call, in Settings, Accessibility?
Could that be guilty?
Maybe Americano enabled it while in berserk mode to get a solution
sad0felix said:
What about the setting Power Button Ends Call, in Settings, Accessibility?
Could that be guilty?
Maybe Americano enabled it while in berserk mode to get a solution
Click to expand...
Click to collapse
It would still work as power outside of a phone call. Inside of a phone call you'd just have to press it twice, once to end the call, and then a second time to put the phone asleep.
americano91 said:
I'm using this kernel: htc-msm-linux @ 20101124_215731(the newest one) and this is my startup.txt:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=2,1,3 force_cdma=0 pm.sleep_mode=2 acpuclock.oc_freq_khz=786432 hw3d.force=1 physkeyboard=rhod100_it"
boot
Click to expand...
Click to collapse
Wow, I never tried, I guess sleepmode 2 is to have it stable while so overclocked ... your battery must by crying, mate!
Updating the Italian Key Map
sad0felix said:
Hi both.
I guess, because all of this happened to me too the very first time I approched to Xdandroid, that if no correct value is found in startup, the default keymap is loaded.
Can't be sure but I think default is Tilt2.
Click to expand...
Click to collapse
Well there are two defaults. First there's the keyboard entry in the default startup.txt and second there is the default keyboard if there is no keyboard entry in startup.txt. The first is either a tilt2 or a rhod210 depending on where you pull your startup.txt from. The second is the raphael (touch pro 1), that's what the init script assigns if you don't tell it anything at all about your keyboard.
Therefore some language could be more advanced than others in regard of testing branches/key assignments' scripts.
Click to expand...
Click to collapse
Currently the key maps/layouts are a hodgepodge. People created them for their own devices, sometimes hex-editing a different model's key map binary instead of creating a source file and then compiling it. So over half the existing keymaps in the rootfs repository lack source files. And it's pretty clear that a lot of the entries were just stabs in the dark by people who didn't understand what they were doing. I'm trying to bring some order to the mess. This project would be taking me far less time if I only did my 210 and stopped there, but I've expanded the project to include all rhod & raph models that we currently have keymaps/layouts for. Currently that's 9 for the rhod & 5 for the raph. I've even created a keymap/layout set for rhodiums with broken keyboards. So make that 10 for the rhod.
In this regard I am using your personalized rootfs, with endcall/power on power button and home/recent tasks on red button.
For sym I use touch keyboard, which contains all accents. Quite tricky closing and opening, but not as slow as only touch
Click to expand...
Click to collapse
You'll have a working SYM key as soon as I get around to updating my rootfs. The Italian and French keymaps are the only two that weren't updated in the Nov. 22nd rootfs I posted. Well they were the only rhodium keymaps that weren't. Still need to do nearly all the raph keymaps, and I haven't even looked at the kovsky keymaps yet...
Cheers
ps
I read in another thread that you might need some italian to complete/check the IT keymap.
Can I help?
Click to expand...
Click to collapse
Certainly. Can you post a pic of your Italian keyboard? I've already adjusted the key layout and decompiled the key map binary. I'm trying to place the same keys in the Italian map that I've added to the other keyboards. I'd like to see what's taken and what's available. We can then discuss alternate places to put those keys if the place I've used on the other keyboards is taken. I already know that fn-a which I've used for { on other keyboards is taken. On the German key map I've moved it to fn-d, but I'm not sure if that's available on your keyboard or not. According to the drawing in the manual it's available, but I suspect the drawing may be wrong since there was a ? there in the binary and I don't see the ? character printed on any of the keys in the drawing.
Preferably I'd like to pick keys that are both intuitive and available on all nine rhodium keyboards that we currently have defined within XDAndroid, and if not all, then at least the five 100's that are currently available in XDAndroid.
F22 said:
Well there are two defaults. First there's the keyboard entry in the default startup.txt and second there is the default keyboard if there is no keyboard entry in startup.txt. The first is either a tilt2 or a rhod210 depending on where you pull your startup.txt from. The second is the raphael (touch pro 1), that's what the init script assigns if you don't tell it anything at all about your keyboard.
Click to expand...
Click to collapse
Yep, I wasn't clear, that's how I guessed it had to be working: no physkeyboard? Fallback set. I obviously didn't know what it was, though
Currently the key maps/layouts are a hodgepodge. People created them for their own devices,
CUT
I've even created a keymap/layout set for rhodiums with broken keyboards. So make that 10 for the rhod.
Click to expand...
Click to collapse
I can imagine the mess.
And yup, I read the thread of the unlucky guy with the swimming rhodium ... and crazy keyb.
Rice is very useful in such cases. My good old E71 knows something about it.
Certainly. Can you post a pic of your Italian keyboard?
Click to expand...
Click to collapse
Sure ... just wait till I get home, TP2 is great phone but can't shoot itself
Preferably I'd like to pick keys that are both intuitive and available on all nine rhodium keyboards that we currently have defined within XDAndroid, and if not all, then at least the five 100's that are currently available in XDAndroid.
Click to expand...
Click to collapse
Let's keep adherent to the standard.
Just to talk: I don't even know if it's possible to make them work in Android, but the keyb combos I miss most are CTRL+arrows, CTRL+SHIFT+arrows, CTRL+X, CTRL+C, CTRL+V.
All the rest is not very much used, really.
I'll post the picture ASAP.
Then will wait for files to update/check
sad0felix said:
I can imagine the mess.
And yup, I read the thread of the unlucky guy with the swimming rhodium ... and crazy keyb.
Rice is very useful in such cases. My good old E71 knows something about it.
Click to expand...
Click to collapse
Rice? How did you apply your um...treatment?
Just to talk: I don't even know if it's possible to make them work in Android, but the keyb combos I miss most are CTRL+arrows, CTRL+SHIFT+arrows, CTRL+X, CTRL+C, CTRL+V.
All the rest is not very much used, really.
Click to expand...
Click to collapse
Whether or not these combinations will work is dependent on the application. Android doesn't have a ctrl keycode, but many applications treat the keycode DPAD_CENTER as if it were the ctrl key. So mapping DPAD_CENTER to the scan code for the physical ctrl key gives us a functional ctrl key in many applications including terminal emulator. Four of the five Euro 100's had their ctrl keys mapped to MENU instead in their layout files however. I had to replace MENU with DPAD_CENTER to make the ctrl key work. Everyone I've talked prefers a working ctrl key, but there's probably someone out there who will scream when this change gets committed and subsequently makes it into the auto-build.
I'll post the picture ASAP.
Then will wait for files to update/check
Click to expand...
Click to collapse
Sounds good.
F22 said:
Rice? How did you apply your um...treatment?
Click to expand...
Click to collapse
LOL, don't tell me you grandma never told you this secret!!!!
Rice is very, very hygroscopic. Even more than common salt (sodium chloride).
In fact here is common to see rice mixed with salt, as a speedy remedy to keep salt dry.
Only silica sachets are better than rice, but they are very expensive or too small to fit the role here.
I bet everyone will agree that diving an electronic device into salt would not end well.
On the other side, diving an electronic device into rice grains is safe (even if some grain get into it, it's easy to shake them away when all is dried up), and clean (rice doesn't produce as much powder/dust as, i.e., wheat, that could cloak up wet stuff).
----------
My E71 falled into a river, while staying, supposedly safe, into my pocket ... ^_^
A friend pushed me in. On his defence, he didn't know I had it. Happens.
The phone is still fine, after more than 1 year after that unexpected bath.
Everyone I've talked prefers a working ctrl key, but there's probably someone out there who will scream when this change gets committed and subsequently makes it into the auto-build.
Click to expand...
Click to collapse
Yup, that's sure. Never change anything unexpectedly ... or the barbarians will roll over you in seconds.
But no one forbids people to shape their keyboard layout as they like best, right?
So maybe I can help the project a little bit, while learning how to fish so to avoid just asking for fishes, if you know what I mean
Being able to build things on my own gives me a lot more satisfaction than taking/buying them done.
F22 said:
Are you absolutely certain you updated to the 11/24 kernel and not an older one? Your problem sounds very much like a kernel issue.
Click to expand...
Click to collapse
i'm absolutely sure it's the 11/24 kernel. And besides.....before i changed the rhod100it in the startup.txt everything worked fine! also i have a friend of mine that has the exact same problem, and we both upgraded to the 11/24 kernel...do you know if there will be a new release soon??? it could be my only hope! it's a really weird situation...i don't know why but i have the feeling that when i'll substitute my rootfs with yours, everything is going to work out!! i guess i'll just have to wait until then........
sad0felix said:
Wow, I never tried, I guess sleepmode 2 is to have it stable while so overclocked ... your battery must by crying, mate!
Click to expand...
Click to collapse
yeah!! can't get to the end of the day!! is there something i can do to improve it??
EDIT
I just ran android through the startup program (since it overwrites the stratup.txt changing rhod100_it to rhod100it) instead of running it with haret.exe, and the power button works again but obviously i have a crappy keyboard