Turn HTC logo into a capacitive button

Search This thread

Switchbitch

Senior Member
Aug 2, 2009
223
37
I 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.
 

godutch

Senior Member
Jun 29, 2009
2,558
374
www.burgerforumeu.nl
It would have been nice to make it a home button + notifications colors,but HTC lacks creativity sometimes...
It would have been better if HTC made it the home button and the home button the multitask button but I hate having a home button logo which would act as multitask and a logo which would act as home button. Anyway it doesn't really matter if we figure out how to make a button out of the htc logo we can use any set up we like.
 
  • Like
Reactions: Fruktsallad

Tetsumi06

Senior Member
Dec 17, 2012
634
164
Bangor
And, might I add, that whilst turning the branding into a button, swipe2wake might be a good idea as well. That little button also houses the ir blaster so the less it is abused the better :)

Sent from my HTC One using xda app-developers app
 

duke24

New member
Apr 2, 2009
2
0
I am sorry, but I think the HTC logo is not inside a touchable area. I just connected my ONE via "adb shell getevent -lt"
an then without any presses on the touch screen the following is repeating:
Code:
/dev/input/event8: EV_SYN       SYN_REPORT           00000000            
/dev/input/event8: EV_ABS       ABS_X                fffffff6            
/dev/input/event8: EV_ABS       ABS_Y                00000036            
/dev/input/event8: EV_ABS       ABS_Z                00000100

If I hit the HTC logo, no other lines appear.

best regards
Daniel
 

Rekoil

Senior Member
May 17, 2008
1,143
497
Göteborg
www.idroidproject.org
Holy smokes if we can get this working i guess im buying this phone lol.

You're buying this phone based on the HTC logo being mappable?

In other news, having a separate touch panel for the buttons doesn't make any sense from an engineering or economic perspective, not only is it harder and as a result more expensive to install one big and two small panels versus one slightly larger panel, it is obviously more expensive to purchase 2 extra panels per phone. I would say that based on this bit of fact and from their previous choices in hardware design, that the whole panel below the screen is most likely part of the same touch panel as the screen. It is not only possible, but in fact very easy to make the kernel ignore clicks within a certain set of coordinates resulting in get event not returning any presses, but the idea that the HTC logo wouldn't be mappable is completely ridiculous.
 
Last edited:

show-p1984

Inactive Recognized Developer
Jul 30, 2011
3,700
11,805
Show-p can do that. He did this before. Show where are you :)
Here I am! :) (...rock you like a hurricane...)
This is just not true. On the lockscreen, I can drag the ring down into the bottom bezel and across all three buttons without losing control of the ring.
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.
 

Tetsumi06

Senior Member
Dec 17, 2012
634
164
Bangor
Here I am! :) (...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.

Good to have you on board. Wasn't planning on rooting until the weekend but if you need any tests running that require su I don't mind jumping earlier (apart from anything else every day that goes by adds more stuff to my phone that dev unlock will blow away!)

Sent from my HTC One using xda app-developers app
 

m00moo

Senior Member
Jul 19, 2008
1,033
75
Here I am! :) (...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.

No offence but I don't know you or of you. BUT, you already sound awesome :good::good::good::good: My HTC is on Order and already this changes it all. Initially I was dissapointed at the lack of a menu button as I hate the way the on screen menu buttons move around depending on apps. This will be a must! Thanks in advance!
 

djbenny1

Senior Member
Apr 9, 2011
1,299
311
so what are we looking at here - im assuming it should be customisable, but for me i think keeping back as back and home as home are obvious.

that would then leave the HTC button to be menu?
 

sr1ks

Senior Member
Jul 15, 2010
394
132
London
I would assume.. if we do remap the buttons.. it would make sense to make the HTC Button do.. Home/Google Now..

the Home Button for Multitasking/Menu

and the back from back\kill app
 

sr1ks

Senior Member
Jul 15, 2010
394
132
London
I guess we could have an app/settings in the later stages of development to customize all button functions :) since one solution will not make everyone happy...

but i guess first priority is to get the htc logo to work.. (and somehow get htc to do this officially..)
 
  • Like
Reactions: nike1

Top Liked Posts

  • There are no posts matching your filters.
  • 56
    Show-p can do that. He did this before. Show where are you :)
    Here I am! :) (...rock you like a hurricane...)
    This is just not true. On the lockscreen, I can drag the ring down into the bottom bezel and across all three buttons without losing control of the ring.
    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
    so , show-p, do you think it will work? can you verify whether the HTC is touch sensitive?

    According to
    This is just not true. On the lockscreen, I can drag the ring down into the bottom bezel and across all three buttons without losing control of the ring.
    it is possible to make it possible, which is my job I guess :p
    8
    I bet my ass...

    The phone has a touchscreen (capacitive) over the display (what u can see) i dont think they implemented three single drivers into the glass (display, homebutton and backbutton).

    Check wiki to see how a capacitive digitizer works...

    Im sure the buttons were defined as x-y axis, every other way is.... Crazy...

    And all that sh*t with my last anniversary shool english :screwy:

    one'ed....

    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 =(
    7
    I 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.
    4
    I'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! :)