Hi,
I've installed CM7.2 on my RHOD but the layout of HW keyboard is wrong. How can I change it to us layout?
Cheers,
Tom
It should 'detect' your keyboard layout.
Do other NAND ROM's have this issue?
I'm not sure, only NAND I tried was the CM7.2
_eph said:
I'm not sure, only NAND I tried was the CM7.2
Click to expand...
Click to collapse
At least give OMGB a shot...
Although, IIRC CM7.2 from Mr. Walter detected my keyboard no problemo. I'm sure we can get the right one shoehorned in, I'm just curious if it happens to you on other ROM's.
Ok, I've tried OMGB. The layout of normal letters/numbers seems to be correct but the function keys seem to be broken. Fn types @, Ctrl lights up the FN led but doesn't act like Fn, arrows are wrong (up is left, right is up, left is down, down is left).
Any more ideas?
Thanks
You could try copying the keyboard map file from the rom that worked to the one that didn't.
_eph said:
Ok, I've tried OMGB. The layout of normal letters/numbers seems to be correct but the function keys seem to be broken. Fn types @, Ctrl lights up the FN led but doesn't act like Fn, arrows are wrong (up is left, right is up, left is down, down is left).
Any more ideas?
Thanks
Click to expand...
Click to collapse
You never even stated which RHOD you have... I kind of assumed "US" layout meant one of the US RHOD's, but it sounds like you have something different.
So which one is it?
wizardknight said:
You could try copying the keyboard map file from the rom that worked to the one that didn't.
Click to expand...
Click to collapse
CM & OMGB were the only android roms I tried. Keyboard didn't work properly with neither of them. I used haret with win6.5 rom before. Can I use keyboard map from win rom?
_eph said:
CM & OMGB were the only android roms I tried. Keyboard didn't work properly with neither of them. I used haret with win6.5 rom before. Can I use keyboard map from win rom?
Click to expand...
Click to collapse
WM and Android are totally different. Haret and nand android will probably work ok though.
arrrghhh said:
You never even stated which RHOD you have... I kind of assumed "US" layout meant one of the US RHOD's, but it sounds like you have something different.
So which one is it?
Click to expand...
Click to collapse
I've got RHOD110 (got it in New Zealand).
The 100's have a awful time with issues, and you have an odd subset of that. No wonder you are having trouble.
You will probably have to make your own keyboard map.
_eph said:
I've got RHOD110 (got it in New Zealand).
Click to expand...
Click to collapse
wizardknight said:
The 100's have a awful time with issues, and you have an odd subset of that. No wonder you are having trouble.
You will probably have to make your own keyboard map.
Click to expand...
Click to collapse
This ^^.
I think someone might've made a layout for F22's rootfs - you can poke around there and re-use it perhaps. Otherwise, you will have to make your own layout. There's really not many with the 110, at least not interested in this project... so the layout isn't solid. I think the 100 still has layout issues with the FN and CAPS key as well.
arrrghhh said:
This ^^.
I think someone might've made a layout for F22's rootfs - you can poke around there and re-use it perhaps. Otherwise, you will have to make your own layout. There's really not many with the 110, at least not interested in this project... so the layout isn't solid. I think the 100 still has layout issues with the FN and CAPS key as well.
Click to expand...
Click to collapse
Can you please point me to correct direction regarding this? Where is that keyboard map located? How can I reuse it?
Thanks
_eph said:
Can you please point me to correct direction regarding this? Where is that keyboard map located? How can I reuse it?
Thanks
Click to expand...
Click to collapse
One nice thing about NAND, the files are easily edited before flashing.
For example, CM7.2.0-RC1-rhodium-GSM-kernel-3.3.6-201200523.zip\system\etc\keymaps\ is where the keymaps are.
I'm not sure which one your device is getting mapped to... and I'm also unsure of what you need to do to get yours detected properly. Sorry I can't really help more...
_eph said:
Can you please point me to correct direction regarding this? Where is that keyboard map located? How can I reuse it?
Thanks
Click to expand...
Click to collapse
http://www.kandroid.org/online-pdk/guide/keymaps_keyboard_input.html
arrrghhh said:
One nice thing about NAND, the files are easily edited before flashing.
For example, CM7.2.0-RC1-rhodium-GSM-kernel-3.3.6-201200523.zip\system\etc\keymaps\ is where the keymaps are.
I'm not sure which one your device is getting mapped to... and I'm also unsure of what you need to do to get yours detected properly. Sorry I can't really help more...
Click to expand...
Click to collapse
I am having the same problem of an incorrect HW Keyboard layout on GBX0* + 3.4.17 kernel - update 11/7/12 using a UK Rhod 100. In system/usr/keylayout/ the qwerty.kl file is correct and can be editted and the changes persist after a reboot. I was able to map the end call key to home.
However the microp-keypad.kl file which contains the keymap for the HW keyboard is incorrect and matches the default layout in system/etc/keymaps/default. Any changes made to this file have no effect and after a reboot the files changes back to the default one. The files I need are in system/etc/keymaps/rhod100_uk. i have also tried editing the default layout files with no success. Again after a reboot they revert to the original files.
I had a similar problem with the CM7.2 NAND ROM. While using the 2.6.27 I was able the use the correct keyboard layout however after flashing a kernel update to 3.3.6 the keyboard layout was incorrect (and was the default layout).
I am unable to find any .kl files in the GBX0 zip and therefore I am unable to make any changes prior to flashing.
Thanks all those still developing for the Rhod.
akk29 said:
I am having the same problem of an incorrect HW Keyboard layout on GBX0* + 3.4.17 kernel - update 11/7/12 using a UK Rhod 100. In system/usr/keylayout/ the qwerty.kl file is correct and can be editted and the changes persist after a reboot. I was able to map the end call key to home.
However the microp-keypad.kl file which contains the keymap for the HW keyboard is incorrect and matches the default layout in system/etc/keymaps/default. Any changes made to this file have no effect and after a reboot the files changes back to the default one. The files I need are in system/etc/keymaps/rhod100_uk. i have also tried editing the default layout files with no success. Again after a reboot they revert to the original files.
I had a similar problem with the CM7.2 NAND ROM. While using the 2.6.27 I was able the use the correct keyboard layout however after flashing a kernel update to 3.3.6 the keyboard layout was incorrect (and was the default layout).
I am unable to find any .kl files in the GBX0 zip and therefore I am unable to make any changes prior to flashing.
Thanks all those still developing for the Rhod.
Click to expand...
Click to collapse
GBX0* is a different rom than CM7.2, and will have many files in a different place. You would be better off making a new thread, or posting the the thread for that rom.
I see that this issue has now been tackled in the ROM development thread. I will download the new package. (Sorry I was unable to post in that thread)
Related
Hey when reciving a email and trying to click a link instead of the link being opened in a web browser whether it be opera or IE i get a error saying The file operalaunch cannot be opened . And isnt signed or truste certificate. Any clue on how to fix this so that i can open links directly from my email.
about a year and a half ago, i ran into this problem. I googled and found a reg hack for it. After growing out of opera and into netfront, i lost the reg hack. Well just recently i decided to reinstall my old opera 8.6, and thru the time of having netfront installed i lost the reg hack info. I tried to google again, but this time i had no luck in finding it. If you happen to stumble upon it please tell! Good luck!
As posted in Thread # 297115...
You only need to make one change:
In HKLM\SOFTWARE\Microsoft\Shell\Rai\: DEFBROWSER is a key called "1". Change the string value from "OperaLaunch.exe" to "\Program Files\Opera\OperaLaunch.exe" (or whereever Opera is actually installed). You need to include the quotes around the string. Save and restart your device.
John
thanks im trying that right now
johnburn said:
You only need to make one change:
In HKLM\SOFTWARE\Microsoft\Shell\Rai\: DEFBROWSER is a key called "1". Change the string value from "OperaLaunch.exe" to "\Program Files\Opera\OperaLaunch.exe" (or whereever Opera is actually installed). You need to include the quotes around the string. Save and restart your device.
John
Click to expand...
Click to collapse
tried and doesnt work...quotes n all could u point me to the thread i tried looking and searching cant find that thread u menitoned.
rblover69 said:
tried and doesnt work...quotes n all could u point me to the thread i tried looking and searching cant find that thread u menitoned.
Click to expand...
Click to collapse
work for me with little mod to the reg string
Change the string value from "OperaLaunch.exe" to "\Program Files\Opera\Opera.exe"
yea i think i misspelled aword thats why..checking now lol thanks
i see what the problem was the first link to change the value data ending with the operalaunchexe isnt correct when applied the same error continues
but adding just opera/opera.exe corrects it and it works fine thanks all.
Binyo said:
work for me with little mod to the reg string
Change the string value from "OperaLaunch.exe" to "\Program Files\Opera\Opera.exe"
Click to expand...
Click to collapse
I am not sure how that could work, because there is no executable file called Opera.exe. There are two, one called OperaLaunch.exe and the other is OperaWM.exe. You can just run OperaWM.exe, I am not sure what OperaLauch.exe does (probably just memory checking and other housekeeping).
John
rblover69 said:
i see what the problem was the first link to change the value data ending with the operalaunchexe isnt correct when applied the same error continues
but adding just opera/opera.exe corrects it and it works fine thanks all.
Click to expand...
Click to collapse
The reason the error message appears with the default setting (which is just OperaLauch.exe) is that the operating system can't find it. Think of your PC which has the PATH variable which tells the OS where to look for executables in common folders such as \WINDOWS. Well the PPC doesn't have that concept (as far as I can tell). You have to tell the OS exactly where the file is located, either in a "path" string such as in this case, or referenced in another section of the registry.
Of course, if you installed Opera somewhere else (e.g. on the Storage Card), then the path would have to be adjusted accordingly.
John
thanks.....with the path u provided with opera/opera.exe it opened my hyper links no prob thanks guys. Im not sure how that worked as far as not being opera/operalaunch....but it worked. Thanks it was a little annoying issue. lol
rblover69 said:
thanks.....with the path u provided with opera/opera.exe it opened my hyper links no prob thanks guys. Im not sure how that worked as far as not being opera/operalaunch....but it worked. Thanks it was a little annoying issue. lol
Click to expand...
Click to collapse
You're welcome. Glad it's working. I agree that it was annoying and I was happy too when I found the fix...
John
Update: New release (RLS 5)
-Comes with 'rogue tools' for overclocking and setting display density will need an update over market to support nike, myn told me he will push it to the market during the next day or so)
-feels smoother, connectivity seems to be a lot better (I never had a faster browsing experiance on my nike than with this build and opera mini), rejoining network after lost signal also seems to be faster
-nice new weather/clock widget
-if you use installd version, the androidupdate.tar from rls4 is still necessary for powermanagement
Myn's new (16.03.2010) Donut android build runs quite smooth on nike! Finally a decent alternative to Ion on nike.
Get it from the vogue forums (SQSH version):
http://forum.xda-developers.com/showthread.php?t=619980
Here is a link to the basefiles I am using:
http://84.23.71.227/kerneloftheday/RootfsBasefiles20100318.zip
The kernels are from dzo's branch with a few minor fixes (vibration, irq-wakeup, red led blinking when in sleep mode). Additionally the kernels should work with enabled HW3D in eclair with boot parameter hw3d.version=1 (not tested yet...).
HowToInstallInANutshell:
-delete old android files from sd
-extract basefiles to sdcard
-extract system.sqsh from myns package and copy to sd
-if you are on a nike100 make sure deafault.txt points at the kernel without vibration (included)
-otherwise default.txt should be fine, most parameters are ignored anyway.
-run haret
-be happy
Impressions:
-sleepmode 1 ok, wakes up, red led blinking. Battery life seems ok, but i only tested a few hours...
-very fast
-many locales, not just english like in good ol' ion
-quite stable net, nice apn autodetect (just had to select from two alternatives), working google stuff
-still not working: bt, incall volume, cam
So, give it a shot and leave your impreesions here!
mblaster
********** UPDATE ************
Installation with the NoRootfs Method is now possible with working net and powermanagement. This gives us the possibility to use the Themes and the default font and everything else that can be provided via androidupdate.tar
See the Wiki for installation instructions. Make sure that you have the provided 'androidupdate.tar' (see attachment, file is in the zip archieve) in your andboot folder along with the androidinstall.tar when installing.
To install themes just copy them in you andboot folder (must be named androidupdate.tar), reboot into menu -> update (-> fix permissions).
PS: Doesn't seem to work with eclair builds, but could work with other donuts
PPS: This should also work with ext2, if someone tried successfully please let me know. €: Works with ext2
Additionally the kernels should work with enabled HW3D in eclair with boot parameter hw3d.version=1 (not tested yet...).
Click to expand...
Click to collapse
you've added hw3d support? I tried to do that - all that I got is 3D without textures or simply nothing - black screen. I did same as in this commit in repo.
I did the same. The only build i saw it working was aosp eclair for kaiser (gallery3d worked). Otherwise i got the same errors. I read that the other devices suffer from similar problems.
Ps: Writing this on myns donut. Everything stable so far.
mblaster said:
Myn's new (16.03.2010) Donut android build runs quite smooth on nike! Finally a decent alternative to Ion on nike.
...
So, give it a shot and leave your impreesions here!
mblaster
Click to expand...
Click to collapse
Hi mblaster,
works like a charm here. Very fast and stable. This is the first ever Donut Build with stable working Data i've seen....
Only Point is, that icons are really very small. Seem to me even smaller than in the old Cupcake Releases with 320x480...
Tried higher settings for lcd.density, but screens don't fit than anymore.
Have you tried it with a non modded system Image ?
Greetz, lagloose
ECLAIR
because you are starting another section of the eclair?
already has almost no one accessing the other thread ...... I have a question there for two days and no one responds more ..
I am very impressed with the progress of the android in my eclair NIKI100 (20 keys)
is making calls, receiving messages, all volumes of the system are working (calls, music (I had to install another player why that came standard did not work), alarm etc. ..) I'm using it for three days, battery lasts long , it does not heat the unit, since I use it in everyday life.
now I have some questions for you:
is so difficult to operate the headphones?
I love listening to music, especially in the way of work, if possible, please someone do work ....
particularly hate wm, I think one day we niki users, we can get the WM and definitely use the android, (because you can try to do everything, are the gods of HTC ....).
another question, I can change the theme of the eclair? wanted it like this: http://forum.xda-developers.com/showthread.php?t=600154, it is possible??
I'm not charging, just begging! rsrsrsrs
Congratulations XDA....( GODS OF HTC)
Hi there,
together with mblaster's combination of basefiles in the first post of this Thread, the sqsh Version of the image in this thread http://forum.xda-developers.com/showthread.php?t=591104 works also...
mblaster; seem's you've found/made the ultimate combination for Donut Images. PERFECT !
Greetz, lagloose
Theming with Metamorph
I been reading around on Vogue's thread and Metamorph catched my attention. It can style up android theme. Is this apps runs well on this build. I am confused because based on this site http://www.androlib.com/android.application.stericson-xda-metamorph-xnFD.aspx it can only run n Rooted phones. What is rooted phones anyway and can this run well in nike100 with the android build posted in this thread?
When is the nand version available? I think the only thing missing now in nike100 are camera and vibration features. Great job!
More Power!!!
Anyone encountered the "Half Size" icon problem ?
This is, when there's a reload of the Home Screen, all icons are suddenly half the size than normal. I had this after leaving the Browser.
Couldn't find a solution for that behaviour. Any ideas ?
Greetz, lagloose
ohh, nice ROM, everything is fine except one - it says that my pin code is incorrect ;//
and what else.. is it possible to get to wifi on Nike using wifi-enabled android?
jefins said:
ohh, nice ROM, everything is fine except one - it says that my pin code is incorrect ;//
and what else.. is it possible to get to wifi on Nike using wifi-enabled android?
Click to expand...
Click to collapse
You have to disable PIN in WinMobile afaik for all builds so far.
About wifi: The stickies say no wifi on nike. Never.
"never ever say never" ;DD
thanks anyway for Pin code tip.
Network problem
got two bugs here.
1. browsed from wm then switchd to android. i cannot connect anymore when in android. even if i reconfigure my apn.
2. switching from phon mode to airplane mode and airplane mode to phone mode will stuck in airplane mode.
@mblaster
how to enable apn autodetect?
@mblaster
First of all, good idea with the new wiki. Hope to add some things in the near future...
had the idea of creating system.sqsh files of all variants (Themes) of the original Vogue Thread. So i downloaded one of the androidupdate.tar files, und untared it "over" the files of the original ones in the androidinstall.tar file. Made an ext2 System and then a Squashfs System with genext2fs.
But no success....
Booting stucks obviously just before the Android Setup Wizzard should appear. Any Ideas ? Perhaps a permission problem ?
Greetz, lagloose
lagloose said:
@mblaster
First of all, good idea with the new wiki. Hope to add some things in the near future...
had the idea of creating system.sqsh files of all variants (Themes) of the original Vogue Thread. So i downloaded one of the androidupdate.tar files, und untared it "over" the files of the original ones in the androidinstall.tar file. Made an ext2 System and then a Squashfs System with genext2fs.
But no success....
Booting stucks obviously just before the Android Setup Wizzard should appear. Any Ideas ? Perhaps a permission problem ?
Greetz, lagloose
Click to expand...
Click to collapse
me again...
just got a flash in my brain...
probably a story about the rootfs because of different load types (NoRootFs vs. Classical sqsh File) ?
so what about mounting the original sqsh Image and untaring the update "over" the rootfs ? ...
@lagloose: Might be an issue because the androidupdate.tar files are made for norootfs. Perhaps its time to move on to an installed version without rootfs...
@ebautista: Sorry, but I do not maintain myn's build. Perhaps it would be a good idea to report bugs in myn's thread in the vogue forums. APN detection worked for me right out of the box. Do you use the basefils from this thread?
€: your brainflash was faster than my typing... but perhaps you should at laest try to set the right permissions, it might work
Hi all,
Just tested sqsh Image from http://forum.xda-developers.com/showthread.php?t=628459. Not completely tested but seem to work also with our basefiles.
I'm working on a way to get themed Images for us Nike Users. Still some problems to solve, but shouldn't be that difficult...
As soon as i've found a way, i'll state it here.
Greetz, lagloose
I really would suggest to move on to NoRootFs for various reasons:
The theme packages are already available there
The basefiles are still supported and regularly updated, while SQSH is dying out, and as there are very few devs for nike we should try to profit from the progress made on other devices
There should be no drawbacks, just a few more MB on sd-card for the system
The installer for systems / updates is extremely useful (theming, installing your favourite apps in one shot ...)
Give it a try, you will find a little howto and links to ressources in the wiki
mblaster,
€: OK, I have good and bad news. The good news is that it seems like you can keep your datafile after switching to norootfs. The bad news is that sleep doesn't work anymore (same settings/build/kernel) -> The problem that prevents us from using more recent builds seems to exist inthe basefiles!!!
Basically thids leaves two possibilities: Either its in the part of the nonexistant rootfs that now is part of the system, or (my guess) it is in the initrd. At least it does not seem to be a problem with the kernel.
mblaster said:
...
€: OK, I have good and bad news. The good news is that it seems like you can keep your datafile after switching to norootfs. The bad news is that sleep doesn't work anymore (same settings/build/kernel) -> The problem that prevents us from using more recent builds seems to exist inthe basefiles!!!
Basically thids leaves two possibilities: Either its in the part of the nonexistant rootfs that now is part of the system, or (my guess) it is in the initrd. At least it does not seem to be a problem with the kernel.
Click to expand...
Click to collapse
..same here after trying. I also couldn't get a Data Connection. Obviously Network Device ppp0 is missing. So i'd guess, that your guess concerning the initrd is correct. Unfortunately, i won't have the time to look after the problem in the next days. So for now we still have to use the SQSH files, until the problems are fixed...
hi, mblaster,
i want to download the file as "Get it from the vogue forums (SQSH version):
but i cant aceessed "mediafire"
Could you email to me a file that it can running on nike100, thnks
my mail is [email protected]
See Post 1 for UPDATE!
lagloose said:
..same here after trying. I also couldn't get a Data Connection. Obviously Network Device ppp0 is missing. So i'd guess, that your guess concerning the initrd is correct. Unfortunately, i won't have the time to look after the problem in the next days. So for now we still have to use the SQSH files, until the problems are fixed...
Click to expand...
Click to collapse
I am quite sure now that the initrd is fine and the problem is in the Rootfs, or better what is left of it. The latest working basefiles include a Rootfs dated to 2009-11-16. There is a newer Rootfs on sourceforge (sometime in december 09) that shows the same problems (net/powermanagement/shutdown). As parts of the rootfs are included in the androidinstall.tar images, thos errors are still there. My update file (now included in post 1) overwrites those files with versions from the 11/16 rootfs. That leeds to a working system (with the new initrd).
Unfortunately the update is incompatible with the newer eclair builds that are around. Seems like they use another rootfs that rejects the old files...
Does anyone maintain a git repo of the rootfs? It would be interesting to patch the problem for good
Hello all,
I do not have a lot of posts, so cannot post in the DEV thread.
Also I think it is good to discuss it separately not to spam the DEV thread.
For the ones having uppercase problems:
Press the text input box for some time and a popup will appear for input method. Use Android Keyboard. Done.
Several people asked is it ok for everyday use - yes it is. Using it for a week without problems. Got only a reboot twice by disconnecting the phone from the USB cable with 3.1. Do not get it now with 3.2.1. I got no random reboot so far, expect after FC with 3.2 and root explorer.
About the updates:
You can update all the time to copy the last package as update.zip to your sdcard and then running xrecovery 'install update.zip' method. When I first went from SE to Cyan 3.1 the phone stuck on reboot. Went to xrecovery and did a factory reset and the phone booted normally (with Cyan and not the SE stock).
If you check the contents of the .zip it's easy to understand what will get updated.
About current problems:
Besides the one described by owain, I get forced closed when the market starting to install any application and when running root explorer with 3.2 and 3.2.1 (which has no update regarding these). Also for root explorer I get a reboot after FC. With 3.1 both was working fine. I've seen some changes in the zips that I do not understand the reasons for (why ADWLauncher.apk and MarketUpdater.apk was totally removed from /system/app, things like that).
I will continue to report here if the thread will not get removed. Please try to be specific about your experiences to help the other users.
Thanks a lot,
arch
I try to create an inventory of exact issues and solutions below:
Issue #1: No uppercase
Solution: Press any text input box for some time and a popup will appear to choose an input method. Use Android Keyboard. Done.
Issue #2: There are no zoom buttons in the browser.
Solution: Go to settings within the browser, disable/enable zoom controls. They will be visible thereafter.
Issue #3: Market stoppes working in the moment after the installation of an application finishes (forced close).
Solution: None so far. Tried this (http://forum.xda-developers.com/showpost.php?p=11708912&postcount=479), but it was not working for me (caould not install Vending.apk). If someone could post exact steps to reproduce, it would be fine.
Issue #4: Root explorer gets a forced closed on restart. Get an 'SD card safe to remove message' and a reboot soon thereafter.
Solution: None so far.
Issue #5: Disconnect from a running PPTP VPN connection. Get an 'SD card safe to remove message' and a reboot soon thereafter.
Solution: None so far.
Issue #6: Keyboard backlight is still on after sliding back the keyboard.
Solution: It has some timeout. After a while, the backlight is switched off.
Issue #7: Sym(bol) button not working
Solution: After pressing it (blue+sym) press space and a pop-up will appear for selection. If you don't see the char you wish for, blue + long press the key which likely has it as an alternative (instead of pressing sym). E.g. long pressing blue + Z (which is 3) will give you 3, 3/4, 3/8.
hi everybody
it seems like we've got an incredibly smooth and fast rom so far. everything works flawlessly
I still have only 2 small (really small) issues:
1) changing language on a hardware keyboard. on a stock SE rom there was a tiny selection box on a screen. now there's nothing. I just can't change language on a hardware kb...
2) there's no zoom buttons in a browser.
is it bugs or just my stupidity? if someone will help me, I'll appreciate it a lot
bw, have anyone noticed the same things or maybe it's just my install ?
Market Mobile Networks ?
Hi,
market does not work when mobile networks is on.
What settings do I have to invite the Market.
E-Plus
LG Josef
Good idea to make the discusion for the low level ones
I have problemes with blue tooth. If i boot with bt aktivated ihave it but if i deaktivaate it and aaktivate it again in don t work
Anyone else have this prob ?
Sent from my U20i using XDA App
This my first post i think, but I've been watching this forum for a while for updates.. Thanks for making this post.. I was just going to spam the forum with posts so i could post in the development thread. But then i happen to find this thread.
Does anyone have the original camera apk? or would it NOT work?
The basic one on 2.2 is UGLY and not very good for the small screen. Also the file names are annoying.
I find the original one on 2.1 was alot better, it fit the screen better. Also i like how it saves the files as DSCxxxxx made it really easy to use.
Vignette takes way too long and does NOT flow well. (takes long to save photos + You can't press the camera button to get back to taking photos.
The original one on the 2.1 firmware flowed well and you could take pictures easily.
If not can anyone recommend an app that works just like it, or really similar?
sym key
Damn me... i see your thread just when i post a thread for the sym key... :-|
By the way, the sym key doesn't work as expected, it doesn't pop up special characters, special punctuation marks and emoticons selection (as it does in SE stock rom).
Anyone with the same issue?
ff0000.it said:
Damn me... i see your thread just when i post a thread for the sym key... :-|
By the way, the sym key doesn't work as expected, it doesn't pop up special characters, special punctuation marks and emoticons selection (as it does in SE stock rom).
Anyone with the same issue?
Click to expand...
Click to collapse
It's a known issue of this ROM. You can type special carakters like "ä" by (in this case) long pressing the "a", "ö" long pressing the "o" and so on.
for capital letters you have to do this:
kinglargo said:
Shift didn't work at start either but got fixed when I started to disable/enable stuffs in "Settings > Language & Keyboard" like "Android Keyboard" "HTC_IME mod" and "Default Input"..
Click to expand...
Click to collapse
Deehee3 said:
It's a known issue of this ROM. You can type special carakters like "ä" by (in this case) long pressing the "a", "ö" long pressing the "o" and so on.
Click to expand...
Click to collapse
I don't use those special characters, but symbols like '_', '"', '{', '}', '$', '%', '<', '>' and so on, should be very useful
Mark this as solved and mark me as idiot!
i've update my x10mini pro to Cyanogen 2.2.. im a brazilian and the keyboard layout is wrong.
here the /system/usr (http':'/'/'www'.'mediafire'.'com'/'?'5qr3vk5r50fnx1v') of brazilian 2.1.1.A.0.6..
and here, the keyboard http':'//'1'.'bp'.'blogspot'.'com'/_bl-dkgjBPqA/TQd_gMW-3fI/AAAAAAAAD5k/YSyLym8c_5A/s1600/'DSC_0297'.'JPG
can anyone help me?
PS.: I CANT POST EXTERNAL LINKS, SO PLEASE.. REMOVE THE '
I have notices that the Market is the old and not the Market that enabled all Resulutions
ff0000.it said:
I don't use those special characters, but symbols like '_', '"', '{', '}', '$', '%', '<', '>' and so on, should be very useful
Click to expand...
Click to collapse
first press "sym" and then the "space"...
i can`t install some apps which earlier worked good..such as angry birds,androzip,galcon,svox voices...
who has the same problems with this rom?
I still have some problems on market too
7.0
Guys,
let's wait for 7.0 and forget this version or accept for the next couple of days that market has an FC. Owain is going ahead like a machine...
Thread closed, cheers,
arch
Hi to all, this is one of my first posts here (maybe the first).
I've just installed this custom rom, i had some trouble with the market solved installing market.zip as suggested in the official thread of this CyanogenMod 3.2.1 and now it seems working fine.
I've just a question about the next apk installation... where install them? Or better, wich settings use?
I mean...
go in Settings > CyanogenMod settings > Application settings
have I to select "Allow application moving"?
And then change something in "Install location"?
By the way I prefer to install the applications in the sd card because of previous problems of full memory with Android 2.1.
Please tell me something about this question and sorry fo my poor english
so for me all is well done but bluetooth is still not working, only after the 1st boot
but after deaktivating und aktivating threre is no blutooth again.
Is there a fix posible ?
3.2.1b ROM
Dear all,
I put a 3.2.1b ROM here: http://forum.xda-developers.com/showthread.php?t=982489
Couldn't help much with application install, bluetooth, just checked and merged the sources from owain and nobodyAtall.
Have a nice day,
arch
As yet I can not post on dev, I'll put here, I hope you see,
I just want the original x10 mini pro portuguese From Brazil(PT-BR)
link below the keyboard, remove the spaces ok.
http ://stanasoft.com/site/images/x10_mini_pro_keyboard_pt-br.jpg
Andreson01 said:
As yet I can not post on dev, I'll put here, I hope you see,
I just want the original x10 mini pro portuguese From Brazil(PT-BR)
link below the keyboard, remove the spaces ok.
http ://stanasoft.com/site/images/x10_mini_pro_keyboard_pt-br.jpg
Click to expand...
Click to collapse
Please check out this Thread and install the sony erricsson Zip (Huge Download link) follow the instructions exactly!
HardWare Keyboard Thread
Yeah, support slade with his efforts on the keys!
Thanks a lot mate!
Hi All,
I am having some problems with the stock keyboard, i have got a log cat of the error, basically the Keyboard Crashes and i cannot get it not to crash, i am wanitng to replace sense keyboard with Stock HC Keybnoard which i know is possible because GUMBY has done it but i wont work for me, any suggestions.
What files are required in order for the Keyboard to Run ?
I can't look at the log at the moment but I'm pretty sure you need the "libjni_latinime.so" from the source you got the keyboard from.
Gumby63 said:
I can't look at the log at the moment but I'm pretty sure you need the "libjni_latinime.so" from the source you got the keyboard from.
Click to expand...
Click to collapse
That sorted it, i have been stuck with that for a while, the errors and log cats do not mention the fact that it is missing a dependent file or anything :/
Thank you very much for your help, and good to see you back in the forum.
So, I have a MTK device, a chinese one.
I just finished my first ROM port. I expected to be problems.
The things I can´t solve:
-The sound (everything related to) -> yes, I tried to replace libaudio.primary.default.so
-The buttons (Power, Volume ones, and Camera).
If someone can, plesase help me.
popoNXN said:
So, I have a MTK device, a chinese one.
I just finished my first ROM port. I expected to be problems.
The things I can´t solve:
-The sound (everything related to) -> yes, I tried to replace libaudio.primary.default.so
-The buttons (Power, Volume ones, and Camera).
If someone can, plesase help me.
Click to expand...
Click to collapse
For the button mapping issue I would recommend pulling /system/usr/keylayout/yourdeviceslayout.kl from the stock ROM looking at the power, volume, and camera keys on that then changing the key layout file on the port ROM. For audio make sure you've included all the audio libraries needed others are likely needed besides libaudio double check the libs folder.
No way
shimp208 said:
For the button mapping issue I would recommend pulling /system/usr/keylayout/yourdeviceslayout.kl from the stock ROM looking at the power, volume, and camera keys on that then changing the key layout file on the port ROM. For audio make sure you've included all the audio libraries needed others are likely needed besides libaudio double check the libs folder.
Click to expand...
Click to collapse
So, I made another ROM including all the stock audio libraries, and what I got is a bootloop.
popoNXN said:
So, I made another ROM including all the stock audio libraries, and what I got is a bootloop.
Click to expand...
Click to collapse
Did the keyboard trick I suggested work for you? Check what audio libraries rely on the main audio library you were using before.
One step
shimp208 said:
Did the keyboard trick I suggested work for you? Check what audio libraries rely on the main audio library you were using before.
Click to expand...
Click to collapse
Yes, the keys are fixed now.
I tried replacing the libraries one per one, in some different sequences. Nothing worked.