Hardware keys are not working on custom roms - Xiaomi Mi 5 Questions & Answers

My mi5 hardware keys ( back, home touch and recent) are not working on custom roms (no MIUI roms).
but, It works correctly on MIUI.
How should i fix this?

torippyd said:
My mi5 hardware keys ( back, home touch and recent) are not working on custom roms (no MIUI roms).
but, It works correctly on MIUI.
How should i fix this?
Click to expand...
Click to collapse
How did you fix this?
I tried CM14.1 From download.cyanogenmod.org
I downloaded cm-14.1-20161217-NIGHTLY-gemini.zip (609.14 MB).
Problem is the while the home button works the hardware / capacitive buttons either side don't work.

It has been said a lot of times in CM threads. Anyway, Xiaomi released old drivers for your touchscreen panel, so they won't work correctly until they release updated drivers.

azazello22 said:
It has been said a lot of times in CM threads. Anyway, Xiaomi released old drivers for your touchscreen panel, so they won't work correctly until they release updated drivers.
Click to expand...
Click to collapse
So you'r saying that there is no workaround? except screen buttons of course ...
I've got same problem.
On latest stable and dev MIUI 8 from xiaomi.eu hardware buttons work like a charm, but no mater which CM i'll install they don't...

you should feedback to ROM developers .

Related

[Q] Menu button not functional [ICS]

Hey dudes, just installed the teamhacksamsungs ICS rom which is AWESOME btw!
Now to the issue, since my menu hardware button is broken i've been using a app called ButtonRemapper which remapps the hardware buttons. It worked flawlessly on gingerbread roms, since it needs root access i need permissions from superuser, anyone knows how i could get it to work?
Sincerely..
EDIT: Superuser doesen't ask for permission in ICS but it does in Gingerbread.
This sounds like you have flashed the wrong kernel for your phone.
What model is your hardware? It may not yet be supported.
FAQ section of hacksung: http://forum.xda-developers.com/showthread.php?t=1363593
Is there a Captivate/Vibrant version?
A captivate build from the same source (but with captivate config) is available here. We currently lack a developer/maintainer for Vibrant.
Does this work for I9000B?
No, the I9000B requires a different kernel configuration. A build for I9000B may be added later in the process.
If you are infact on the right kernel, then suggest Odin flash to Ficeto's XXJVT base rom from the DarkyRom website (beta section), flash to CM7, then flash to ICS again.
Good luck.
I've got an i9000 international since i'm from sweden, any more suggestions?
build 10 has a bad version of su. There's a fix in the hacksung ics thread.
i had the similar problem when i flashed MyICS the menu button didnt work i just re-flashed and it started to work again
Okay, the menu button is broken, physically.
That's why i need it to work
Anyway, do you guys think i'm capeable using ICS without any home button?
meh.hajj said:
Okay, the menu button is broken, physically.
That's why i need it to work
Anyway, do you guys think i'm capeable using ICS without any home button?
Click to expand...
Click to collapse
There's a market app that emulates a home button with an overlay on screen button...can't recall the name of it though.
Only downside with a broken button is no three button recovery/download.

Whats about CyanogenMod 10.1

I want not talk to much
Just want to create a topic where people can write their news about CM 10.1
I think such a thread could be interesting for people that heard from Android 4.2 - Jelly Bean
So let's start the topic
You can download the last UNOFFICIAL build of CM10.1 for SGS i9000 from:
http://forum.xda-developers.com/showthread.php?t=2013707
THIS BUILD NOT WORK PERFECT! - (26.11.12)
For most of us, simply flashing the 4.2 Gapps package is good enough already.
snapper.fishes said:
For most of us, simply flashing the 4.2 Gapps package is good enough already.
Click to expand...
Click to collapse
Maybe for you
Lots of people have been waiting for CM10.1
I installed that rom yesterday (and today i installed the new build) and it seems to work fine.
Except for me the swype-like keyboard isn't working, does anyone know where i can find known issues or bug reports for this rom?
sterfpaul said:
I installed that rom yesterday (and today i installed the new build) and it seems to work fine.
Except for me the swype-like keyboard isn't working, does anyone know where i can find known issues or bug reports for this rom?
Click to expand...
Click to collapse
you can ask in the post of the developer here:
http://forum.xda-developers.com/showthread.php?t=2013707
Same here
Everything I tried, except swype, working!
Keyboard working - but not the swype part
work fine fast nice interface
but i think it haven't a long battery life if i compare it with gingerbread
every thing is working fine for me with cgm 10

[DISCUSSION] Fixing the OB's softkeys

Hi,
I just wanted to create a centralized thread for all the discussion surrounding the work of fixing the softkeys.
Many users are reporting, including myself, about the softkeys not working properly after some time on the ICS roms.
My 25 cents:
Is it a kernel issue? ROM issue? I have tried multiple ROMs but none have fixed the issue.
Multiple kernels tried too, to no avail. I suspect it is a software issue though. It's as if the buttons go into some state of sleep mode in the software, and after a few minutes come back for a few milliseconds. Just my thoughts into it.
-
Sergio
After facing the issue, i smartflashed gingerbread, there also softkeys not worked.
It is a kernel issue for sure. Worked great on GB, but I think they messed up the driver in ICS. Have you tried my blue kernel already? Dont know if I fixed it there, but it is worth a try. Or compile your own kernel, but use the GB Softkey files. Should work just fine with some mods here and there
Sent from my XT1052 using XDA Free mobile app
Has anyone successfully fixed this issue?
I am facing the same problem after flashing ICS on my OB.
i fixed it by replacing the digitizer, i had to order 2 cause the first arrived with the same problem.
Maybe
hackerse7en said:
i fixed it by replacing the digitizer, i had to order 2 cause the first arrived with the same problem.
Click to expand...
Click to collapse
I don't know about that though, mine works excellent through the CM key test. Just fails in the OS. And I can't use the kernel by Nooby, I'm on Nameless KK. But before that I tried IZS, GB, 2.1, etc to no avail.
I'm gonna research this and try and fix it in the Aeroi Kernel

Touch Delay on Moto G 2014 Devices - In all Android 6.0.x (and up) Custom ROMs

The touch delay is present since the release of Marshmallow, Nougat and Oreo ROMs in Titan (not sure about Falcon). There is no escape. It's good to see our 2014 devices with the latest version of the Android, but this error is very annoying and is being ignored. Doesn't matter how good the ROM is. If you using any custom ROM with Android 6.0 and up on titan, i'm sure you have this issue.
So i want to open a discussion about this issue here
If you don't know what i talking about, let's simulate the issue:
Try to write something in stock keyboard of your MM,Nougat or Oreo ROM. Now try pressing a second finger in the screen out of the keyboard and write anything else... You noticed? No?
Try to play a very intensive tap game, like Geometry Dash. Play a bit. Now play with a second finger on screen... You noticed?
Only KitKat and Lollipop Roms are free from this bug.
So, the only workaround for this touch delay is pressing a second finger on screen. Shame.
The questions left: Anyone knows a solution? The cause of this issue? There is no way to fix this?
I tried some custom kernels, no success.
I don't think anyone will ever fix this issue unfortunately,it was supposed to be fixed with the last official update(MM 6.0,bootloader 0x4887),but the problem is still there.
Metalhead666 said:
I don't think anyone will ever fix this issue unfortunately,it was supposed to be fixed with the last official update(MM 6.0,bootloader 0x4887),but the problem is still there.
Click to expand...
Click to collapse
Some people say the same on Lenovo Foruns...
Pixx 1001 said:
Some people say the same on Lenovo Foruns...
Click to expand...
Click to collapse
I think it is a kernel related issue rather than the bootloader,like some people said on lenovo foruns.I don't have proper knowledge to fix it,you could try to contact some of our developers,maybe there's still someone interested.
I don't notice this on the dirty unicorn 11.7 i am using this rom for daily driver , but can you tell if this problem happen in one rom or on all the roms ? and can you tell wat rom are you using? and dit you try a custom kernel with the rom wen the delay hapen ?
HiR3x said:
I don't notice this on the dirty unicorn 11.7 i am using this rom for daily driver , but can you tell if this problem happen in one rom or on all the roms ? and can you tell wat rom are you using? and dit you try a custom kernel with the rom wen the delay hapen ?
Click to expand...
Click to collapse
Every single ROM above 6.0 that I tested have this problem (Cm,AOKP,AOSP,Lineage,Slim,DU,CypherOS,AEX,CrDroid,RR and many more),with and without custom kernels.
I don't use my Moto G to play games , but some random games from PlayStore (Minigore 2, Bejeweled 2, Samurai II) the touch doesn't work well (or simply doesn't work! You can test all of them if you want). Using a 5.1 ROM, they work normally. It would be nice if the people post more problems about this touch issue happening on apps/games on Moto G Titan. I want to know if the same happens on Moto G Falcon, 4G variants.
Just stick to stock Lollipop rom guys. Newer versions of Android are just not meant to be on this phone, either on a custom or a stock ROM.
Jimisballjohn said:
Just stick to stock Lollipop rom guys. Newer versions of Android are just not meant to be on this phone, either on a custom or a stock ROM.
Click to expand...
Click to collapse
Well, I used ViperOs (7.1) as my daily driver at work, school for a good time (6 months I guess)... I liked Nougat Features and I guess I will keep using it, or another Nougat ROM, as they work perfectly for it on Titan.
Looks like titan Pie ROMs have the issue too (Used LineageOS 16 for testing).
It sucks that this still has not been resolved. Happened to me as well on LineageOS 16.
I do not feel this in the ROM of the Pixel Experience in the version of android 9, here the touch is normal.
LightWard said:
I do not feel this in the ROM of the Pixel Experience in the version of android 9, here the touch is normal.
Click to expand...
Click to collapse
I would like to test it myself and give a feedback, but sadly, my old Moto G2 had the input of the charger/usb connector broken. If anyone have tested the ROM too, would be good if they give a feedback here.

3 different ROMs, same error message

I've tried 3 different ROMs in my new X526.
Lineage 15.1, Pixel ROM and now I'm running Arrow ROM.
The error shows up some seconds after running google photos which is trying to synchronise my collection
"Unfortunately Camera Has Stopped Working".
Is there a workaround in order to fix it?
I'm a little bit frustrated.
Thanks in advance.
Camera is an issue with new ROMs since the kernel sources are of marshmallow, but you can look around the particular section to minimize this issue
shivam321998 said:
Camera is an issue with new ROMs since the kernel sources are of marshmallow, but you can look around the particular section to minimize this issue
Click to expand...
Click to collapse
I am not really a huge fan of getting the bleeding edge ROM for my device.
I just want to work everything as it should be without annoying problems.
Maybe I should go back to an older android build.
Suggestions? Maybe Havoc?
Miui 10 and lineage nougat are pretty much okay for daily use. You could go for RR too

Categories

Resources