Exactly as the thread title says, I am anxiously waiting on CM10.1 for this phone, but the capacitive button issue really bothers me. Will it be possible to include those fixes or is it something exclusive to the sense updates?
Related
My galaxy s' home button recently broke and as i cant immediately replace it, I've had to resort to using the on screen navigation buttons that CM10 and AOKP provide
my question is that recently CM10.1 was released and i want to know if i can enable on screen buttons in the ROM?
many thanks in advance
Hi guys,
I am looking at an improvement to change the sensitivity of the Capacitive buttons...
basically it is way to easy to accidentally press them...which is really annoying me.
I have just upgraded from the good old "Desire" which has got a hardware back button..so I am looking for altering the response of the capacitive button in a few ways...not sure what can be adjusted before ANDROID recognises a successful button-press?
'time pressed' / 'pressure??' / 'capacitance??'
Is there any more where this would be 'tune-able' through settings or other means?
Thank you very much in advance.
(in case it matters: I am rooted running LIQUIDSMOOTH rom)
they are not adjustable
Glebun said:
they are not adjustable
Click to expand...
Click to collapse
Thanks Glebun...would you mind tell me why? is that they are closed source from Samsung?
I would have hoped that this somehow accessible in the KERNEL...
thanks anyway
don't know why. hit "thanks" if I helped you
I have installed the stable release of Cyanogenmod 10.1 recently on my Xperia T but one thing really annoys me.
The camera button is acting as the power button. If you touch the camera button with only a half press the phone awakes.
So when you have the phone in your pocket it starts calling, is sending messages or is selecting/entering stuff on the lock-screen widgets for example.
Is there a way to disable the camera button as power button in Cyanogenmod 10.1?
windvanger said:
I have installed the stable release of Cyanogenmod 10.1 recently on my Xperia T but one thing really annoys me.
The camera button is acting as the power button. If you touch the camera button with only a half press the phone awakes.
So when you have the phone in your pocket it starts calling, is sending messages or is selecting/entering stuff on the lock-screen widgets for example.
Is there a way to disable the camera button as power button in Cyanogenmod 10.1?
Click to expand...
Click to collapse
There is a fix for this in CM10.1 thread at Original Development. Search for "camera" keyword.
thedisturbedone said:
There is a fix for this in CM10.1 thread at Original Development. Search for "camera" keyword.
Click to expand...
Click to collapse
Thanks, but can you give me a link to the thread or post?
I have searched the forum but can't find a solution on this one.
Only to disable the camera on the lock-screen with the app: Lockscreen policy.
windvanger said:
Thanks, but can you give me a link to the thread or post?
I have searched the forum but can't find a solution on this one.
Only to disable the camera on the lock-screen with the app: Lockscreen policy.
Click to expand...
Click to collapse
Here you go lazy person
http://forum.xda-developers.com/showthread.php?p=43159436&highlight=camera#post43159436
Read that page
thedisturbedone said:
Here you go lazy person
http://forum.xda-developers.com/showthread.php?p=43159436&highlight=camera#post43159436
Read that page
Click to expand...
Click to collapse
Thank you!
This lazy person is satisfied!
Hi all.
Currently running CM13 Unofficial on my Mi5.
It appears as though my hardware home button on my Mi5 has failed... Hard press does nothing....
This started on my previous ROM 16/09/2016, and continues on my new ROM 22/09/2016.
I strongly suspect this is a hardware issue rather than a software issue...
My question for you guys is how do I reassign buttons? Is it possible to make the right capacitive (currently app switcher) the home button?
Also, my preferred button to use as a home button would be the soft capacitive touch on the fingerprint scanner on the home button so i can retain my app switcher button....
Any help guys is greatly appreciated.
Many thanks in advance.
When Xiaomi releases Kernel Source there will be an option for non physical home button. On rr you can reassign more options to your buttons. Cm does not work on my device.
Greet
brownhound said:
Hi all.
Currently running CM13 Unofficial on my Mi5.
It appears as though my hardware home button on my Mi5 has failed... Hard press does nothing....
This started on my previous ROM 16/09/2016, and continues on my new ROM 22/09/2016.
I strongly suspect this is a hardware issue rather than a software issue...
My question for you guys is how do I reassign buttons? Is it possible to make the right capacitive (currently app switcher) the home button?
Also, my preferred button to use as a home button would be the soft capacitive touch on the fingerprint scanner on the home button so i can retain my app switcher button....
Any help guys is greatly appreciated.
Many thanks in advance.
Click to expand...
Click to collapse
If your home button is broken, then maybe you should enable 'on screen' (software) buttons from Buttons submenu in Settings?
Capacitive touch is not going to work on prebuilt kernel (every ROM so far, wait for CM's big update).
marcoly said:
If your home button is broken, then maybe you should enable 'on screen' (software) buttons from Buttons submenu in Settings?
Capacitive touch is not going to work on prebuilt kernel (every ROM so far, wait for CM's big update).
Click to expand...
Click to collapse
Have done so. Cheers for the suggestion.. I didn't know this option existed!
As for the capacitive buttons not working, I've seen this mentioned a number of times... My capacitive buttons have always worked since flashing CM?
brownhound said:
Have done so. Cheers for the suggestion.. I didn't know this option existed!
As for the capacitive buttons not working, I've seen this mentioned a number of times... My capacitive buttons have always worked since flashing CM?
Click to expand...
Click to collapse
I meant home button back/recent is always working :fingers-crossed:
marcoly said:
I meant home button back/recent is always working :fingers-crossed:
Click to expand...
Click to collapse
Fingerprint scanner has worked without a hitch too!
brownhound said:
Fingerprint scanner has worked without a hitch too!
Click to expand...
Click to collapse
Yeah, fingerprint to unlock and such.. What about touching (not pressing) home button to return to the launcher? That's what everybody wants to have (and waits for proper kernel)
marcoly said:
Yeah, fingerprint to unlock and such.. What about touching (not pressing) home button to return to the launcher? That's what everybody wants to have (and waits for proper kernel)
Click to expand...
Click to collapse
OK... Thats what I don't have...
Thanks for clarification.
Any idea when there's likely to be a build with this baked in?
brownhound said:
OK... Thats what I don't have...
Thanks for clarification.
Any idea when there's likely to be a build with this baked in?
Click to expand...
Click to collapse
Nobody knows.. No ETA
Hi,
Recently I noticed that the capacitive buttons response time is slower than the on-screen navigation bar.
When I press any of the buttons on the on-screen navigation bar the response is immediate. On the other hand, when using the capacitive buttons there is always a delay, wich is especially noticeable in the recents button.
This is a really irritating issue since I prefer the capacitive buttons, but now I always notice the delay.
Have you guys noticed this? Do you have a fix?
I'm currently on OxygenOS 3.5.4.
Thanks
J.Diogo said:
Hi,
Recently I noticed that the capacitive buttons response time is slower than the on-screen navigation bar.
When I press any of the buttons on the on-screen navigation bar the response is immediate. On the other hand, when using the capacitive buttons there is always a delay, wich is especially noticeable in the recents button.
This is a really irritating issue since I prefer the capacitive buttons, but now I always notice the delay.
Have you guys noticed this? Do you have a fix?
I'm currently on OxygenOS 3.5.4.
Thanks
Click to expand...
Click to collapse
Is there any action defined for double tap on capacitive buttons ? Might just be becoz of that
abijithdas said:
Is there any action defined for double tap on capacitive buttons ? Might just be becoz of that
Click to expand...
Click to collapse
You sir, are a genius! :good:
It's a shame tough... I really love the double tap to open the last used app. Maybe It will be better on 7.0 since that's a native feature there.
J.Diogo said:
You sir, are a genius! :good:
It's a shame tough... I really love the double tap to open the last used app. Maybe It will be better on 7.0 since that's a native feature there.
Click to expand...
Click to collapse
Even if it is native, if double tap is defined, the OS must wait for possible second tap after the first one, so delay for second tap.
serafko said:
Even if it is native, if double tap is defined, the OS must wait for possible second tap after the first one, so delay for second tap.
Click to expand...
Click to collapse
Yup totally understand. But the delay here was very noticeable. I have the "double tap to open last app" feature on my Nexus 5, with the 7.1.1 PureNexus ROM, and there is no noticeable delay. The way Nougat implements this feature seems to be different from what OnePlus did on Marshmallow.
J.Diogo said:
Yup totally understand. But the delay here was very noticeable. I have the "double tap to open last app" feature on my Nexus 5, with the 7.1.1 PureNexus ROM, and there is no noticeable delay. The way Nougat implements this feature seems to be different from what OnePlus did on Marshmallow.
Click to expand...
Click to collapse
Native nougat "double tap" is not a typical one. It's a trick. It's basically a single tap which opens recent apps and moves previous app to the front of recent apps stack at the same time so when you hit the key again, recent apps window closes and app that's first in the stack gets to the foreground.