Ok, so this has been really bothering me that i cant fix this myself..so i came for help.. I like both the Quickdesk Beta and Itching Thumb as a kind of in-between for LauncherPro and just getting to apps/widgets, while still in-app. The problem with Droid X is that theres no way to set a third-party app as the default function. Im more interested with getting Quickdesk to work, because that is what i can see myself using more.
I have tried the workarounds that is on the quickdesk site, or where ever the link on it sends you (using titanium backup to freeze the default app you choose for double tap, so nothing would happen except launch quickdesk). The problem with this is that after the first home button press, it exits the current app, to your launcher, then opens quick desk. I have seen/tried the other method using SQL Editor, which i think is the proper route, but dont understand the proper input style. (<Program>/<Activity>)...i do know that the file for quickdesk is (sg.ruqqq.quickdesk) and have tried that, but i think something else is needed for the proper function of it. If someone can point me in the right, more specific direction, it would be greatly appreciated..Thank you
And yes i have searched around and done extensive research first
OK, the fixed buttons to the right of the screen. 2 things. is there a way to put them on the title bar like on other android tabs? I figure it must just be something I'm missing but I'm not sure. there must be some way. without them being backlit if it's dark I can't seem them obviously. TIA.
Look for Button Savior in the android market, it can be placed anywhere on any edge of the screen
Hey, thanks. not bad but not exactly what I was looking for. I have an older generic crap-tab running 2.2, it has only one hard button and all the buttons are on the status bar at the top let of the screen. I really like that and was hoping to be able to do it here. maybe it's not possible but I can't see why. it's a good place for a few buttons, they are out of the way and such. I am wondering also if there is a way to disable the hard buttons on the A7 because somtimes I accidently activate them "sliding" a bit off the screen.
What you are describing is just a status bar modification. It is unique to that particular device, because it involves heavy modification of the Google framework library.
ytain
I've just read/watched the Engadget review.
I'm sold on the device. My concern is around the hardware keys. I much prefer hardware keys to software keys because the SW keys eat up so much of the on-screen real estate, and they also push the keyboard higher and make it harder to reach.
That being said, it seems by dropping the menu key, HTC has taken a step backwards after they mapped the legacy menu key to the HW menu key in recent versions of the One X / X+ build in Sense 4+. From what I've read, the legacy menu is back.
This is *bad* and has me thinking about another direction (although there doesn't seem to be a great device like the One - don't think the S4 will be anything interesting unless they've been setting up a smokescreen!).
I run an alternative launcher because I dislike Sense (other than the Camera!), but it won't solve the missing HW key / legacy menu.
Thoughts?
The two button layout doesn't bother me too much. I removed the soft keys on my Nexus 4 and use PIE so if I can function without any buttons, I'm sure I'll live with two. As for the legacy menu thing, that's an odd on HTC's part. Granted, apps should be updated to have proper menu button support, but it's something I can live with.
The removal of long press back remapping was/is probably a bug, I'm sure it will be back
idk about everyone else but i will root and flash my device just like every other phone ive had. with that we will be able to do almost what we want personalization wise. how long will we have to wait is the question.
eg1122 said:
The removal of long press back remapping was/is probably a bug, I'm sure it will be back
Click to expand...
Click to collapse
Agreed. I heard about this early on but it's not being mentioned in reviews. If nothing else HTC will cave to peer pressure like in the HOX. Long press on back is a passable solution - particularly if we can also get the in-app menu button too.
Otherwise the other idea being thrown about (by non technical people) is if the kernel can be modded to recognise the HTC logo as a button - given that the touch panel should extend over that as well. No idea how possible this is and I presume it couldn't be done until kernel source is out.
M.
Only two buttons doesn't bother me either, i only have one on my iphone!
I'm actually cool with just 2 button too. I rarely use my menu button on my mt4g. I do everything with just the home button and back button. Also rather have capacitive buttons instead of hard buttons.
Sent from my HTC myTouch 4g using xda premium
I use the multitasking and menu options quite a bit, thus my concern
I also use the menu button quite a bit.
I am sure once we get used to it, it will be like anything else and heck, we might even like it more. Who knows till we get to play withem...
Sent from a galaxy far away!
Is it possible to activate soft buttons by editing build.prop on HTC Sense roms ?
CreepyDroid said:
Is it possible to activate soft buttons by editing build.prop on HTC Sense roms ?
Click to expand...
Click to collapse
I guess. It's possible on TouchWiz, so I guess you can add a line in the build.prop in Sense too.
Sent from my GT-N7000 using Tapatalk 2
My main goal would be to deactivate the hardware buttons and go completely nexus wise.
| Back - Home - Recent (small menu button when needed) |
Are stock on screen buttons smart enough to activate the additional menu button when needed?
Also... can long press software home button activate google now?
mickliq said:
I use the multitasking and menu options quite a bit, thus my concern
Click to expand...
Click to collapse
So do I but a long press of the button to bring up the multi tasking menu is hardly a dealbreaker for me. Could prove to be annoying though. Time will tell I guess!
Sent from my XT925 using xda premium
^ I don't mind long-press for multi-tasking (it's what I am using today); the issue is that you can't have home, multi-tasking, Google Now and Legacy menu all on one key! I've been seeing some comments about long-press back used but the legacy menu really needs to be a single-press.
Dun recall where i read it, but the home key on double tap brings up multi tasker and on long press can b configured for google now or menu key. Thats acceptable to me.
I do prefer the 3 keys on my hox, but i realize that htc had to make a compromise to accomodate the logo. The logo could not have been placed elsewhere on the front without adding to the height of the phone.
In the end, its not a big issie and we will get used to it. Moving from 4 keys on dhd to 3 on the hox wasnt pleasing to me in the beginning, but adapted soon.
Sent from my HTC One X using xda app-developers app
i think its great, i never used the other two buttons anyway.
Hello,
So... I successfully remaped the left buttons to hardware Menu and Back buttons, but the top right is giving me headaches. It's set from 4 different places (Settings>Reader, NT Mod Manger, twl4030_keypad.kl file and from Cool Reader itself) to work as page back button, but it still turns the pages forward and I can't get what is forcing it to do so. I've tried to set it as a Menu button just from the twl4030_keypad file and it works as intended, but then again, when I set it to RIGHT_PREVPAGE it goes back to be a < button...
Any ideas how to fix this?
Anyone?
I've tried to bind PREVPAGE to the other buttons, but it doesn't seems to work at all. Am I doing something wrong or what?
Maybe the problem is that too many things are trying to control the button. If you want it to function that way for Cool Reader alone, why not let everything else off the hook and let Cool Reader do its thing? Just a thought. I've not encountered problems with hardware button assignments,but then I've only ever used NTMM to do the work.
nmyshkin said:
Maybe the problem is that too many things are trying to control the button. If you want it to function that way for Cool Reader alone, why not let everything else off the hook and let Cool Reader do its thing? Just a thought. I've not encountered problems with hardware button assignments,but then I've only ever used NTMM to do the work.
Click to expand...
Click to collapse
Thanks for the reply!
It turns out that Cool Reader f*cked up somewhere. I re-installed it before, but I didn't notice that my settings were saved, so I thought the problem was somewhere else. BTW, Cool Reader's button assignment options didn't work at all - something was overriding them. What crossed my mind now was to delete the .cr3 folder and that fixed my problem.
P.S. Aaaaaand the problem is back! And I didn't even touched the Key actions... Interesting.
P.P.S. Changing the tap zones is messing with my hardware buttons... oh well.
P.P.S. So, when I change the left middle tap zone from previous to next page it also changes my top right button. Mystery solved. Right middle is also bugged.
Hi, long time casual forum reader having trouble with my galaxy note 3. I've found so much useful information on these forums it's the first place I decided to ask for help at after unable being to find any answer by searching Google or these forums. The problem:
Whenever I hold down my finger on the touchscreen it is not working properly. I am unable to drag and drop icons on the home screen by holding down then dragging them. I am unable to hold down on a link in Chrome and have the option menu appear which allows you to open in new tab. I CAN hold down and scroll the screen up/down.
I do not know what is causing this problem. I have in the past closed out various unknown/system services in the application manager but haven't ever disabled any. I have restarted my phone multiple times leaving it powered off for over a minute before repowering. I am using a tmobile galaxy note 3. That is not rooted. I have the most recent update from tmobile (installed it hoping that it would fix the problem). Does anyone have any idea what may be wrong or how to fix it? I'd be more than happy to provide more information if required.
Thanks
Correct terminology?
If no one has any ideas for how to solve this problem, does anyone know the correct terminology to use to describe when you press and hold your finger down on the screen then try to drag? I'm thinking part of the problem I'm having with searching for a solution is that I'm using incorrect search terms to describe the problem. I've tried things like press and drag, long hold, drag and drop, and various other similar terms. I'm hoping the correct terminology might yield results related to this issue. Thanks!