Turn HTC logo into a capacitive button
- Thread starter godutch
- Start date
Quite possible since the whole touch screen extends to where the capacitive buttons are, you can test this by going to a webpage and draging your finger down to the logo and see if it keeps scrolling
If it does then its very likely that someone could turn the logo into a button
Sent from my One X using Tapatalk 2
AW: Turn HTC logo into a capacitive button
Check it out with adb get event.
That way we would know it for sure if it triggers an event when being touched.
Sent from my HTC One X using xda premium
Check it out with adb get event.
That way we would know it for sure if it triggers an event when being touched.
Sent from my HTC One X using xda premium
im new to android so dont know what that is. But in developer options i enabled Show Touches and Pointer Location and they both show nothing happens when touching or dragging to that point.
Last edited:
AW: Turn HTC logo into a capacitive button
That won't work as it can't show any touch on the logo as it's not a display.
Adb get event command is the best way to check it out.
Someone should do it
Sent from my HTC One X using xda premium
That won't work as it can't show any touch on the logo as it's not a display.
Adb get event command is the best way to check it out.
Someone should do it
Sent from my HTC One X using xda premium
AW: Turn HTC logo into a capacitive button
The buttons are part of the digitizer, so its possible to map any point to a button, it has nothing to do with browser scrolling (it ends where the display ends)
insertcoined....
The buttons are part of the digitizer, so its possible to map any point to a button, it has nothing to do with browser scrolling (it ends where the display ends)
insertcoined....
Put two fingers on the screen to Zoom in or out (on a photo or webpage), once you start zooming, slide both fingers to the capacitive buttons area & see if the zooming action still works.
On my One X, the whole area for the buttons still responds to the zooming in/out.
On my One X, the whole area for the buttons still responds to the zooming in/out.
Last edited:
I've got use to it quite quickly and I'm starting to make mistakes when I go back to using the ONE-X. I like what they've done with the buttons.
Sent from my HTC One using xda premium
Sent from my HTC One using xda premium
on our one x, we can customize s2w swipe distance to wake/lock the phone.
this is actually plausible IF the logo area is touch responsive
this is actually plausible IF the logo area is touch responsive
AW: Turn HTC logo into a capacitive button
Yes, but someone has to find it out. I can check it tomorrow when I get my phone but maybe someone is faster
Sent from my HTC One X using xda premium
Yes, but someone has to find it out. I can check it tomorrow when I get my phone but maybe someone is faster
Sent from my HTC One X using xda premium
This is quite an interesting idea, i didn't know that the whole area was a touch area and could be mapped, i hope someone manages to make the HTC logo a functional button
so confirmed the whole area is registering touches?
if so, ladies gentleman, we will have a central home button soon
OK - not sure if this helps or not - not started hacking phones yet, not rooted or su the One either.
adb shell getEvent -lt
(then lots of stabbing at the htc logo)
[ 22313.540611] /dev/input/event8: EV_SYN SYN_REPORT 00000000
[ 22313.610564] /dev/input/event8: EV_ABS ABS_X 00000018
[ 22313.610594] /dev/input/event8: EV_ABS ABS_Y 00000053
[ 22313.610594] /dev/input/event8: EV_ABS ABS_Z 000000fb
[ 22313.610594] /dev/input/event8: EV_SYN SYN_REPORT 00000000
[ 22313.680578] /dev/input/event8: EV_ABS ABS_X 00000017
[ 22313.680578] /dev/input/event8: EV_ABS ABS_Y 00000054
[ 22313.680608] /dev/input/event8: EV_ABS ABS_Z 000000eb
[ 22313.680608] /dev/input/event8: EV_SYN SYN_REPORT 00000000
[ 22313.751202] /dev/input/event8: EV_ABS ABS_X 0000000e
[ 22313.751202] /dev/input/event8: EV_ABS ABS_Y 00000055
[ 22313.751202] /dev/input/event8: EV_ABS ABS_Z 000000f4
[ 22313.751232] /dev/input/event8: EV_SYN SYN_REPORT 00000000
[ 22313.820574] /dev/input/event8: EV_ABS ABS_X 00000016
[ 22313.820574] /dev/input/event8: EV_ABS ABS_Y 00000052
[ 22313.820574] /dev/input/event8: EV_ABS ABS_Z 000000f9
adb shell getEvent -lt
(then lots of stabbing at the htc logo)
[ 22313.540611] /dev/input/event8: EV_SYN SYN_REPORT 00000000
[ 22313.610564] /dev/input/event8: EV_ABS ABS_X 00000018
[ 22313.610594] /dev/input/event8: EV_ABS ABS_Y 00000053
[ 22313.610594] /dev/input/event8: EV_ABS ABS_Z 000000fb
[ 22313.610594] /dev/input/event8: EV_SYN SYN_REPORT 00000000
[ 22313.680578] /dev/input/event8: EV_ABS ABS_X 00000017
[ 22313.680578] /dev/input/event8: EV_ABS ABS_Y 00000054
[ 22313.680608] /dev/input/event8: EV_ABS ABS_Z 000000eb
[ 22313.680608] /dev/input/event8: EV_SYN SYN_REPORT 00000000
[ 22313.751202] /dev/input/event8: EV_ABS ABS_X 0000000e
[ 22313.751202] /dev/input/event8: EV_ABS ABS_Y 00000055
[ 22313.751202] /dev/input/event8: EV_ABS ABS_Z 000000f4
[ 22313.751232] /dev/input/event8: EV_SYN SYN_REPORT 00000000
[ 22313.820574] /dev/input/event8: EV_ABS ABS_X 00000016
[ 22313.820574] /dev/input/event8: EV_ABS ABS_Y 00000052
[ 22313.820574] /dev/input/event8: EV_ABS ABS_Z 000000f9
you definitely didn't hit anything else by mistake?
im sure someone who knows will be able to interpret properly, but it looks like it is registering an x y and z co ordinate with each time you pressed the "button"
It was throwing a constant series of event so I got ready to ^C with one hand and stabbed at HTC with the other and posted up a few events from the end of this session. If anyone has a more reliable command to test with I'll give that a go.
Sent from my HTC One using xda app-developers app
Sent from my HTC One using xda app-developers app
Similar threads
- Locked
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
56
Here I am!Show-p can do that. He did this before. Show where are you
(...rock you like a hurricane...)
This proves that it is possible, I just have to define a new touch button in the kernel source and we are good to go.
PS: I plan on getting the dev edition of the HTC One once it is available.8
According to
it is possible to make it possible, which is my job I guess8
As I already said earlier, it's only one big touchscreen, not like the one s with underlying capacitive buttons + touchscreen digitizer.
Why do I know that? The info pulled from the phones suggests that. (There is only one touchscreen driver used in the kernel)
However it might be possible that the digitizer is not extending into the middle (hTC button), which would be nonsense in my opinion (but wouldn't be the first time hTC does sth like this).
There is also no chance that those two buttons aren't handled as a touchscreen but as buttons (like the one s) because they are defined as on touchscreen buttons in the kernel and in the ROM.
The module I posted a few pages earlier tries to overwrite some kernel pointers to allow setting new values. So far it doesn't seem that I have hit the right pointer yet. It's an Assembly guessing game since we don't know how the source exactly looks like (which would make this far easier).
The replacement images however do suggest something else:
It might be that the touchscreen has those two areas defined as single point of contact areas (like a capacitive button on your tv or monitor would work).
IF I had the device I could give you a definitive answer, but the dev editions aren't being sold yet =(7I don't have an HTC One but here's my 2 cents anyway.
You're probably all aware that capacitive screens use a conductive matrix on the digitizer layer to sense the position of finger presses. Presumably, when a digitizer is manufactured it is most cost effective to lay the conductive matrix down across the entire surface of the digitizer, and not bother 'missing it out' in areas that are not required to be touch sensitive, i.e. across the HTC logo. Since there are touch sensitive areas to the left and right of the HTC logo, it seems sensible to assume that the conductive grid is present across the HTC logo also.
There's an easy way to check whether this is the case.
The conductive matrix is visible on the surface of the digitizer when viewed at the correct angle in bright light. It usually looks like a criss-cross of almost invisible tiny dots or squares across the screen. If you hold the HTC One at the right angle in a bright light (with the screen off), you should be able to determine if the conductive matrix is indeed present across the logo. If so, it would be logical to also assume that this area of the digitizer can receive an input.4I'm not a developer, but I definitely think there is reason to be hopeful. I have an Evo LTE and have been running MeanRom/MeanBean almost since I got it. There was a period of time, I think just before MeanBean was released, when Mikeyxda, the developer of the rom, had created two extra phantom buttons between the existing 3 capacitive buttons. He had them mapped to do different things based on whether the screen was on or off. It was very cool. I think all we need is a developer with the skills to make it happen (oh, and kernel source). Heck, maybe in addition to the logo button, there would be room to add one more on either side of the existing buttons, for a total of 5!
