Develop Bugs

[Q] Cleaning behind the buttons

Hi,
Is it possible to clean behind the HTC Desire's hardware buttons?
My Menu and Back buttons are getting non-responsive and dirt is the only thing I can think of preventing optimal performance...
Thanx,
B

See link below
http://forum.xda-developers.com/showthread.php?t=1230045:)

Thanx for the help Will go have a look around the shops for this type of cleaners...

Full-screen idea

I enjoy using my phone in fullscreen but not so much the LMT app to navigate since it doesnt work as quickly as the navbar.
My question is, would it be possible to map the back/home/multi-task buttons to be off screen on the bottom but above the notification led?
Does the digitizer sense touch in this area?

No one? Anything? I believe this is a good idea

I'm pretty sure the digitizer stops where the screen does. Your idea would be awesome if possible but its not sadly. I actually was trying to make buttons out of tin foil(obviously just as a test) where the tin foil touches the bottom of the screen and when you touch the foil it would hit the soft keys. It got less and less responsive though the smaller I made the nav bar.

[Q] Add NavBar to unresponsive screen?

Hi Guys,
The bottom of my screen (about 5mm) has become unresponsive to touch. In previous ROM's I've got around this by adding a navbar to the bottom of the screen which I don't use (as in the soft key buttons).
I've just installed a Sense 5 ROM (InsertCoin) and really like the feel of it, however I can't find any way to get the navbar at the bottom of the screen. Obviously as it's a sense rom, there is nothing in the settings, and I've tried putting qemu.hw.mainkeys=0 into the build.prop file but that has also not worked :/
Does anyone have a solution to this or a way to cut the bottom 5mm of the visible screen? Or even better, a way to get the bottom of the screen working?
Cheers,
Tom

[Q] lcd density with on screen buttons?

What lcd density would i need if i added on screen buttons on the stock rom so that everything doesnt look squished? Right now it's showing at 480. Thanks in advance.

Are you serious? No one know what setting would work! I'm starting to regret trading my galaxy s4 for this phone since at least people help out in that forum...smh...

asj2583 said:
Are you serious? No one know what setting would work! I'm starting to regret trading my galaxy s4 for this phone since at least people help out in that forum...smh...
Click to expand...
Click to collapse
Maybe no one is really using the on-screen buttons? I tried them for about an hour before I decided it was a waste of screen real estate when I have a physical home button and capacitive Back and Menu buttons. It's possible no one here knows the answer.

mrfeuss said:
Maybe no one is really using the on-screen buttons? I tried them for about an hour before I decided it was a waste of screen real estate when I have a physical home button and capacitive Back and Menu buttons. It's possible no one here knows the answer.
Click to expand...
Click to collapse
I'm sure i can't be the only one that wants to use the on screen buttons and I'm sure someine knows the answer, this is xda after all.

[QUESTION] - Sweep2Wake Proper?

Hello everyone!
I just purchased the Galaxy S3 as an upgrade from the Galaxy S2 (d2tmo and hercules respectively). Over at the S2 XDA forums, our sweep2wake consisted of swiping across all the capacitive buttons on the device (since, as you know, it did not have hard buttons for menu, home, back, and search).
However, from what I've researched on this forum for the S3, it seems that YOUR sweep2wake is swiping a finger across the screen, or what the S2'ers called swipe2wake.
I know a couple devs, but unfortunately am not one. I do know that only certain devices are capable of waking by capacitive buttons due to keyboard drivers. My question is, does the S3 qualify? I'd love to wake it by touching the menu and back button. I've broken a plenty phones simply by wearing out their buttons, and I find sweep2wake an elegant solution.
However, I don't have the technical skill to port something like this to a kernel just yet. I hope someone can help me clarify this issue.

luxkore said:
Hello everyone!
I just purchased the Galaxy S3 as an upgrade from the Galaxy S2 (d2tmo and hercules respectively). Over at the S2 XDA forums, our sweep2wake consisted of swiping across all the capacitive buttons on the device (since, as you know, it did not have hard buttons for menu, home, back, and search).
However, from what I've researched on this forum for the S3, it seems that YOUR sweep2wake is swiping a finger across the screen, or what the S2'ers called swipe2wake.
I know a couple devs, but unfortunately am not one. I do know that only certain devices are capable of waking by capacitive buttons due to keyboard drivers. My question is, does the S3 qualify? I'd love to wake it by touching the menu and back button. I've broken a plenty phones simply by wearing out their buttons, and I find sweep2wake an elegant solution.
However, I don't have the technical skill to port something like this to a kernel just yet. I hope someone can help me clarify this issue.
Click to expand...
Click to collapse
If you're rooted & running custom ROM, kit kat or lollipop, then flash Neocore kernel & use trickster mod to set sweep to wake & double tap to wake! Both have to be activated at the same time for it to work!

I'm not sure if you read my post, but it specifically ruled out screen-based waking solutions.
I was talking about capacitive button based wake (tap menu, tap back, screen on).