Database Users

[ ROM Release ] the latest 2.3.9MIUI perfect port

ROM contents
1, using the latest development version of the the MIUI transplant system perfectly stable, change the model for the HTC, modify the boot animation
2, the kernel G major MIUI repair kernel, do not break the sound
3, individuals joined enhance the script and add a few features: turned on by default 80M of Zram default unlock the FPS, you can turn off to enhanced.conf
4, all normal functions, to in addition to FM, the TV-OUT .
5, by adding the RE Manager, Google PLAY, goggles, the Huawei document management, animation acceleration, replace the input method Sogou
Integrated titanium backup and MIUI control center, you can customize the status bar
8, modify the boot theme is self produced IPHONEV1 optimize the camera and power-saving mechanism. Interface fluency can be used to adjust other settings
9 , add ice4.0, window effects, if you feel slow with other settings to modify the animation speed
10, to modify the system wallpaper, system sounds, calls music and other more personalized
11, the boot since the launch of the EQ manager, automatically adjust the sound of music. Listen to music the effect of greatly optimized.
PS: MIUI2.3 now break the sound problem solved, reaches the perfect state, there are some minor issues such as: volume shock and screenshots screenshots screenshots repair will lead to gravity sensing, I have limited skills do not specify a screenshot button . After miui no major updates, and I are working on to release a small update patch package. Can be updated to the OTA, as removed from Brush Shuangqing troubled.
Think the effect is not convenient students can turn off the animation displayed inside.
Install the ROM:
1 will download the zip Brush package do not extract directly into the SDcard
Hold the volume up + power button is turned on, do not release until well into the recovery mode
Recovery, the volume up and down keys / menu Home key to move up and down the power button / Search button to confirm the back key to return to the previous menu level.
Select "Clear all data recovery factory
Select from the SD card, select the Brush package "
6 re-election to select the ZIP file from the SD card "
7 to find just download the zip Brush package confirmed
8 confirmed, Brush, wait about 1 minute to complete.
After brushing, back to the first menu, select "immediately reboot the system restart the phone
10 and then patiently wait for a while, you first start will be relatively slow.
http://www.mediafire.com/?108h4zeap2dcx31

pikachukaki said:
ROM contents
1, using the latest development version of the the MIUI transplant system perfectly stable, change the model for the HTC, modify the boot animation
2, the kernel G major MIUI repair kernel, do not break the sound
3, individuals joined enhance the script and add a few features: turned on by default 80M of Zram default unlock the FPS, you can turn off to enhanced.conf
4, all normal functions, to in addition to FM, the TV-OUT .
5, by adding the RE Manager, Google PLAY, goggles, the Huawei document management, animation acceleration, replace the input method Sogou
Integrated titanium backup and MIUI control center, you can customize the status bar
8, modify the boot theme is self produced IPHONEV1 optimize the camera and power-saving mechanism. Interface fluency can be used to adjust other settings
9 , add ice4.0, window effects, if you feel slow with other settings to modify the animation speed
10, to modify the system wallpaper, system sounds, calls music and other more personalized
11, the boot since the launch of the EQ manager, automatically adjust the sound of music. Listen to music the effect of greatly optimized.
PS: MIUI2.3 now break the sound problem solved, reaches the perfect state, there are some minor issues such as: volume shock and screenshots screenshots screenshots repair will lead to gravity sensing, I have limited skills do not specify a screenshot button . After miui no major updates, and I are working on to release a small update patch package. Can be updated to the OTA, as removed from Brush Shuangqing troubled.
Think the effect is not convenient students can turn off the animation displayed inside.
Install the ROM:
1 will download the zip Brush package do not extract directly into the SDcard
Hold the volume up + power button is turned on, do not release until well into the recovery mode
Recovery, the volume up and down keys / menu Home key to move up and down the power button / Search button to confirm the back key to return to the previous menu level.
Select "Clear all data recovery factory
Select from the SD card, select the Brush package "
6 re-election to select the ZIP file from the SD card "
7 to find just download the zip Brush package confirmed
8 confirmed, Brush, wait about 1 minute to complete.
After brushing, back to the first menu, select "immediately reboot the system restart the phone
10 and then patiently wait for a while, you first start will be relatively slow.
http://www.mediafire.com/?108h4zeap2dcx31
Click to expand...
Click to collapse
Thank you for sharing this rom, but i have some questions: have you tried it? If yes, which are the bugs? Does it work perfect and fast?

MyNameIsKappa said:
Thank you for sharing this rom, but i have some questions: have you tried it? If yes, which are the bugs? Does it work perfect and fast?
Click to expand...
Click to collapse
Im using it right now its very fast and stable with tweaksv5 and kickasskernelizer i get 2500+ on quadrant but i only want to change the long press search key to open the mini menu with send sms and take screenshot option than open camera..anyone knows how i can change it?
Ok i fix it! ^_^ now the only one not working is the screenshot but there an app for that!

so no bugs on this rom?

matteof93 said:
so no bugs on this rom?
Click to expand...
Click to collapse
ss don't work i don't found other bug everything works fine

is this me or its to iOs looking?, and whats about with more statistic? does someones some numbers , on why this is perfect?

blksina said:
is this me or its to iOs looking?, and whats about with more statistic? does someones some numbers , on why this is perfect?
Click to expand...
Click to collapse
You can also change the theme if you like, some people prefer the look of iOS but not the way it performs.

It has only English and Chinese?

sewa2k said:
It has only English and Chinese?
Click to expand...
Click to collapse
Yes, I'm using it right now as we speak. It has both English (which I use) and Chinese.
The only issue is that I can't seem to sync my account.

KayxGee1 said:
Yes, I'm using it right now as we speak. It has both English (which I use) and Chinese.
The only issue is that I can't seem to sync my account.
Click to expand...
Click to collapse
It needs gapps!

pikachukaki said:
It needs gapps!
Click to expand...
Click to collapse
My gapps were bad, thanks!

is there a Russian language in this firmware?

Can I update to this ROM with only wiping cache and dalvik from MIUI 2.3.2?
EDIT: Nevermind, I've tried it and I can confirm that you can't update from MIUI 2.3.2 with only wiping cache and dalvik

borisstone said:
is there a Russian language in this firmware?
Click to expand...
Click to collapse
No, sorry. There are only a few versions of English based on the region, and Chinese.

pikachukaki said:
Im using it right now its very fast and stable with tweaksv5 and kickasskernelizer i get 2500+ on quadrant but i only want to change the long press search key to open the mini menu with send sms and take screenshot option than open camera..anyone knows how i can change it?
Ok i fix it! ^_^ now the only one not working is the screenshot but there an app for that!
Click to expand...
Click to collapse
Thank you! I upgraded to this ROM and i can confirm that is perfect!
Could you tell me please how did you change the long press search key to open another application?

MyNameIsKappa said:
Thank you! I upgraded to this ROM and i can confirm that is perfect!
Could you tell me please how did you change the long press search key to open another application?
Click to expand...
Click to collapse
/system/usr/keylayout/qwerty.kl
change
#key 127 SEARCH WAKE_DROPPED
#key 217 CAMERA WAKE_DROPPED
to
#key 127 SEARCH WAKE_DROPPED
#key 217 SEARCH WAKE_DROPPED

pikachukaki said:
/system/usr/keylayout/qwerty.kl
change
#key 127 SEARCH WAKE_DROPPED
#key 217 CAMERA WAKE_DROPPED
to
#key 127 SEARCH WAKE_DROPPED
#key 217 SEARCH WAKE_DROPPED
Click to expand...
Click to collapse
Thank you, it works !

MyNameIsKappa said:
Thank you, it works !
Click to expand...
Click to collapse
np!!i want it to have the mini menu so i can took screenshots...how is your battery drain??this is my only concern with this rom!

I do not understand a thing, is based on ics?

Kautuak said:
I do not understand a thing, is based on ics?
Click to expand...
Click to collapse
No its based on 2.3.9 miui but has ics animations...its translated from chinese but you can get the picture of what about this rom is!

[GUIDE] Simple way to change physical keyboard keymappings!

How to change FN(ALT) + key symbols, add them and even change everything on the qwerty -keyboard:
Works at least on Cyanogenmod 10 with android 4.2.2
Hi!
Today I ran into a problem. There were no < and > symbols in my phone (except virtual keyboard) and I needed them. I couldn't find any good guide how to change physical keyboard mappings so that I could use FN + button combo to get those symbols. I only found one guide, but it didn't work for me, old version perhaps? (http://forum.xda-developers.com/showthread.php?t=945921)
This is the way I found, and it's quite simple!
Quick guide:
1) Connect phone with usb and usb debugging on.
2) Find your keyboard layout name from settings -> language & input -> physical keyboard -> selected layout (for example: "vision-keypad-nor")
3 )Filename is layout + ".kcm" -> so in this example "vision-keypad-nor.kcm"
4) Go to command line and:
Code:
adb pull system/usr/keychars/vision-keypad-nor.kcm c:\vision-keypad-nor.kcm
5) Open file c:\vision-keypad-nor.kcm in notepad or other program
6) Find the key uou want to edit, for example A:
Code:
key A {
label:'A'
base:'a'
shift, capslock:'A'
alt: '#'
shift+alt:'#'
}
7) Lets edit that so we get "<" -symbol when pressing FN+A:
Code:
key A {
label:'A'
base:'a'
shift, capslock:'A'
alt: '\u003C'
shift+alt:\u003C'
}
Note: \u003C is unicode for "<". Find more unicodes: http://source.android.com/tech/input/key-character-map-files.html -> Input -> Key character map files
8) Save the file
9) Send the file back to the phone:
Code:
adb push c:\vision-keypad-nor.kcm /system/usr/keychars/vision-keypad-nor.kcm
10) Reboot phone and try pushing FN+A: If you get "<" everything went fine
Im new to this, so please tell me if somethings is wrong with this guide!
Update 28.10.2013 : Updated guide to be more clear.

Oh, sorry... I don't read your guid carefully first time. It's about an 4.x OS :-[

Now i do have one question... because ADB nor USB is not possible for me would this be possible using a root file explorer or no? I will try once I find the time and figure out how to get the www. and .com key back just may be a day or 2 before i can try.
By the way nice find

Been looking for a tutorial like this so that I can finally make better use of a few of the keys on my keyboard. Thanks a lot for the break down.
T.

NICE
Thanks soo much. Now lets make use of our hardware-keybs
Next step would be to assign scripts instead of single charakter
Imagine how many root-scripts we could execute with this as base for the hotkeys

Anyone have any luck getting the www. .com button to work like stock? Right now I have it as TAB.
Sent from my NookColor using Tapatalk 2

Anyone checking this thread anymore??
Sent from my HTC Vision using Tapatalk 4 Beta

Codes
Are that something similar to ASCII codes?

can I add a new language with this trick?

Can Anyone knows how to add second language to physical keyboard? We aready have a key to SW between 2 language but it's only work for English Lang.

nice guide! i need to make russian h\w keyboard, can someone help me with this?

Thank you all, hope that helped you
I think if you want to create a russian keyboard, you just edit that file and put the unicode -code of the russian character to every single button or so on? Not sure though.
SmIzUrF: I think you can edit that file with some root File Explorer on the phone. Just navigate to that folder and file.
I updated the guide so it is more clear

combination with hw quicksettings launcher
is it possible to combine it with HW quicksetting launcher by suzuna apps?
however they utilize hw key search button, do anyone know the ascii of hardware key search button? is it possible to map the search function into the other physical key?
thanks.

Is this guide still relevant with later roms? Some ICS or JB roms dont use the Nordic keymap and it would be useful to replace that.

Great guide! I will definitely use it!
Thanks.

wow!! thanks so much, I am running phoenixOS on my laptop and its keyboard is in German qwerty layout (strange right? - qwerty and not qwertz) but i needed the keys to be mapped according to the keyboard lettering. I am certainly gonna try this out!!

[5.0][CM12] How to Activate On Screen Buttons and turn of Capacitive Buttons

Hey guys,
There have been a ton of people asking how to activate onscreen buttons and disable the capacitive buttons since CM12 builds have started rolling out. Obviously, at some point, these features will be rolled into the ROM, but until then, I figured it would be a good idea to simply present a step-by-step thread on the issue. There have been answers all over the place button nothing dedicated and centralized, so I figured I would help some guys out.
Things needed:
CM12 Build on any variety (currently K900 and bpear have "nightlies" available in development. Check em out.
Root access. Just flash SuperSU 2.16 (http://download.chainfire.eu/589/SuperSU/UPDATE-SuperSU-v2.16.zip) if you don't have it. Root is necessary.
Zip to turn of the backlights: http://www.mediafire.com/download/p385se5ia28cqab/noSoftkeyBacklight.zip (thanks @Moody for this)
1.) Activate On-Screen buttons
- Use a program such as BuildProp Editor (look it up on the Play Store) to create a new build.prop entry. Call it qemu.hw.mainkeys, and set it's value to 0. If you are doing this manually, just add the line "qemu.hw.mainkeys=0"
- Reboot.
2.) Deactivate Capacitive buttons
- Download Root Explorer or some other program that allows editing of system level files.
- Mount your system as R/W. In root explorer at least, when you get into the system, there is a button up top to do so.
- Navigate to /system/usr/keylayout. Open Generic.kl in with a text editor.
- Comment out the follow lines by inserting a pound sign (#) in front of the line:
key 158 BACK
key 172 HOME
key 139 MENU
After this, they will read:
# key 158 BACK
# key 172 HOME
# key 139 MENU
Therse are numerically ordered, shouldn't be hard to find within the document.
- Remount your system as R/O.
3.) Turn off the capacitve back lights
- Reboot into custom recovery and flash noSoftKey.zip file you downloaded earlier.
- Reboot.
That should do it! You should now have software buttons and your hardware buttons should seemingly not exist!
Any questions or comments, please leave them here.

Anyone know how to enable hardware home long press to get to Google now?

TjPhysicist said:
Anyone know how to enable hardware home long press to get to Google now?
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.phoenixstudios.aiogestures&hl=en

Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon

Hi there, first of all, thanks. I am having a problem where after I disabled the capacitive buttons (Step 2) the power and volume buttons are not working. Thanks in advance.

You know how to enable menu key also?
Verstuurd vanaf mijn Nexus 7 met Tapatalk

Yes any chance of getting home button long press as search? Default is the menu button doing this.

Its not working bro
Tried and followed your steps , disabling capacitive keys works but enabling on screen keys not working even after changing build.prop , also i read in some post that enabling on screen key mod will not work in cm roms is that true can any one confirm me?
i am using following rom its CM12
http://forum.xda-developers.com/oneplus-one/development/devrom-cm12-scheduled-builds-t2938372
its very stable didnt experience any glitch till now , multi user and guest account works , all the other features are working too, try it out friends.

Pure awesomeness, many thanks for this guide. I'm back to my comfort zone, onscreen for me is just more intuitive.?

BTW, how to bring back the capacitive lights? I tried to remove the script at /etc/init.d and it only bootloops after reboot.
Edit: Nvm, found it, re-flashing the ROM brings back all to the default behavior including the capacitive backlights.

kmakiki said:
3.) Turn off the capacitve back lights
- Reboot into custom recovery and flash noSoftKey.zip file you downloaded earlier.
- Reboot.
That should do it! You should now have software buttons and your hardware buttons should seemingly not exist!
Any questions or comments, please leave them here.
Click to expand...
Click to collapse
For some reason this step isn't working for me. I tried wiping cache/dalvik and it didn't fix anything

Can anyone give a screenshot of the on-screen buttons?

Is this possible to do in hydrogen OS? I love that rom, but i switch back since there is no option to turn off hardwer keys and enable software key in system?
Sent from my A0001 using Tapatalk

How to add volume button onscreen by editing buid.prop

Enable on-screen NavBar on Stock ROOTed Nougat? A2017U

Any way to enable the onscreen navbar on Nougat?
I used Root Browser to edit the build.prop to change the 0 at the end of this to 1 and back again
qemu.hw.mainkeys=1
Click to expand...
Click to collapse
But had no luck after reboot either way.
Any way to enable them?

It didn't work in MM because ZTE took the on screen buttons out of the framework, rather than just from the build.prop line.
I'm guessing they did the same thing in N.

needs more than just build.prop to enable on-screen key......i'll be releasing Dmix7_N (Stock Base) but on-screen keys will be disabled by default via build.prop and re-enable via build.prop

That's odd cause when I went from lineage back to stock the nav bar followed. Full wipe, full stock zip.

I have on screen working but capacitive buttons still work as well. Does anyone know of a way to turn capacitive buttons completely off and only use on screen?

t2jbird said:
I have on screen working but capacitive buttons still work as well. Does anyone know of a way to turn capacitive buttons completely off and only use on screen?
Click to expand...
Click to collapse
Button mapper.

My stock Rooted B15 Nougat version just has an option to activate on-screen Navbar...
Setings->Features->Navigation Keys.
Is that what you meant?

iNaruX said:
My stock Rooted B15 Nougat version just has an option to activate on-screen Navbar...
Setings->Features->Navigation Keys.
Is that what you meant?
Click to expand...
Click to collapse
That's really weird, mine didn't have that? Only thing I had under "Navigation Keys" was the ability to swap them but not display them on screen?
I did, however, flash the vR26 Permissive kernel, and that automatically enabled the onscreen buttons......It also made Nougat much smoother

I'm running the B15 from DrakenFX.
Here's a screenshot from that setting.
http://i.imgur.com/3RvqIlY.jpg

DrakenFX said:
needs more than just build.prop to enable on-screen key......i'll be releasing Dmix7_N (Stock Base) but on-screen keys will be disabled by default via build.prop and re-enable via build.prop
Click to expand...
Click to collapse
you keep promise that... I'm still waiting on your ROM

iNaruX said:
I'm running the B15 from DrakenFX.
Here's a screenshot from that setting.
http://i.imgur.com/3RvqIlY.jpg
Click to expand...
Click to collapse
Been meaning to reply to this with a screenshot from "stock rooted".. There is no option to "Always show navigation bar" in stock. Not sure if DrakenFX added that, or what?
I do know the Beast Mode Permissive kernel will enable them, and I used it for a couple weeks, but while that kernel is really smooth and I had my on-screen navbar.... My battery took a fairly huge hit, and my stock camera didn't work. So I reverted back to pure, rooted, stock.

Bumping. I want to go back to the latest stock but I won't do it without onscreen nav buttons.

p4ch1nk0 said:
Bumping. I want to go back to the latest stock but I won't do it without onscreen nav buttons.
Click to expand...
Click to collapse
Fairly easy.
When rooted open build.prop (system/)
Change ro.config.navkeys=1 to 0 (ZTE kept it by default to 1 so you don't see the setting)
Leave qemu.hw.mainkeys=0 like it is
Save, restart and you'll have your enabled nav bar on stock devices.
Btw, you can disable it through settings so you can, if you want, swype down to not see it anymore.

raystef66 said:
Fairly easy.
When rooted open build.prop (system/)
Change ro.config.navkeys=1 to 0 (ZTE kept it by default to 1 so you don't see the setting)
Leave qemu.hw.mainkeys=0 like it is
Save, restart and you'll have your enabled nav bar on stock devices.
Btw, you can disable it through settings so you can, if you want, swype down to not see it anymore.
Click to expand...
Click to collapse
I changed the ro.config.navkeys=0 and i still haven't seen the on screen nav bar

nmk_123 said:
I changed the ro.config.navkeys=0 and i still haven't seen the on screen nav bar
Click to expand...
Click to collapse
First do check in settings/features/navigation keys/check always ON wether it works (you can disable it afterwards by putting it on "OFF" and have the possibility to swype up or down afterwards)
Second, try swype upwards from the bottom to see the navbar.
Check also if qemu.hw.mainkeys=0 is still 0.
It should work because these are simple build.prop scripts, so test out :good:

raystef66 said:
First do check in settings/features/navigation keys/check always ON wether it works (you can disable it afterwards by putting it on "OFF" and have the possibility to swype up or down afterwards)
Second, try swype upwards from the bottom to see the navbar.
Check also if qemu.hw.mainkeys=0 is still 0.
It should work because these are simple build.prop scripts, so test out :good:
Click to expand...
Click to collapse
Thanks, I double checked qemu.hw.mainkeys=0 is still 0.
Navigation menu doesn't have any new option.
Tried to swipe up and down as well, nothing

nmk_123 said:
Thanks, I double checked qemu.hw.mainkeys=0 is still 0.
Navigation menu doesn't have any new option.
Tried to swipe up and down as well, nothing
Click to expand...
Click to collapse
OK. Lets try to figure it out.
Have you rebooted phone ?
Have you a G version ?
Can you upload me your build.prop pls. I'll take a look on it.

raystef66 said:
OK. Lets try to figure it out.
Have you rebooted phone ?
Have you a G version ?
Can you upload me your build.prop pls. I'll take a look on it.
Click to expand...
Click to collapse
Thanks for trying to figure this out with me. I really appreciate it.
I have a U version but I'm actually using your [ROM][AROMA][A2017G][B08 7.1.1.][stock] SL!M³ DF!NR. I'm tempting to checkout ur [ROM][AROMA][A2017][V2.0.0B13 M!Favor 5.0 / 7.1.1.][stock] SL!M DF!NR to see if it makes any difference.
This is my build.prop
https:// drive . google . com/file/d/1pyEZtZxVONEiinIc9pNnv35VPwyno6Ij/view?usp=sharing
Sorry im not allowed to post outside links yet so have to do this

nmk_123 said:
Thanks for trying to figure this out with me. I really appreciate it.
I have a U version but I'm actually using your [ROM][AROMA][A2017G][B08 7.1.1.][stock] SL!M³ DF!NR. I'm attempting to checkout ur [ROM][AROMA][A2017][V2.0.0B13 M!Favor 5.0 / 7.1.1.][stock] SL!M DF!NR to see if it makes any difference.
This is my build.prop
https:// drive . google . com/file/d/1pyEZtZxVONEiinIc9pNnv35VPwyno6Ij/view?usp=sharing
Sorry im not allowed to post outside links yet so have to do this
Click to expand...
Click to collapse
No problem. We're here to help each other out :good:
I'll give a look at your build.prop later on.
But do try the Mifavor 5.0. As I'm not mistaken, the option is built in too. So nothing to change there. And this rom is quite smooth, fast and without force closes. Perhaps try it and let me know.
Tomorrow I'll take a look at your file.

nmk_123 said:
Thanks for trying to figure this out with me. I really appreciate it.
I have a U version but I'm actually using your [ROM][AROMA][A2017G][B08 7.1.1.][stock] SL!M³ DF!NR. I'm tempting to checkout ur [ROM][AROMA][A2017][V2.0.0B13 M!Favor 5.0 / 7.1.1.][stock] SL!M DF!NR to see if it makes any difference.
This is my build.prop
https:// drive . google . com/file/d/1pyEZtZxVONEiinIc9pNnv35VPwyno6Ij/view?usp=sharing
Sorry im not allowed to post outside links yet so have to do this
Click to expand...
Click to collapse
Looked into your build.prop and all should be ok. And since you installed the SLIM³ all files such as framework-res.apk and systemui.apk are overwritten in case the U models files could have been different. But as said, with all these files and your build.prop the nav bar should show up....
So for the moment i do not see an immediate solution for that matter.
As said and afaik , the Mifavor 5.0 from my rom has this nav bar build in

[Q] enable the softkeys

Redmi Note 2, Android 5.0.2, MIUI 9.6
Need to enable original soft keys. I`ve managed to edit build.prop (qemu.hw.mainkeys=0) from TWRP terminal and sed command. Keys showed BUT don`t response.
I`ve noticed a new menu option in Settings (can`t be not quite accurate, coz I have a translation enabled) - System and Device -> Advanced -> Buttons and gestures -> Screen buttons -> Change buttons positions. And if I change positions, it changed. But buttons are stil not responding.
Are there any MORE options in build.prop, that blocks it?
UPD:
[How To] Disable Capacitative Keys and Enable Soft Keys
Just in case anyone might find this useful, I've put together the instructions I found whilst trying to do this. Finally I can take photos without accidentally bringing up the Menu or closing the Camera App! First time I've ever posted here, so be kind! This works in CM11 M6 on Samsung Galaxy...
forums.androidcentral.com
I`ve found some article, that point to /system/usr/keylayout/ directory and need to comment key 139 and key 158. But there were no such filename from article. So I`ve just tried to edit Generic.kl and It doesn`t work.