Sorry to raise a thread for this because I know this info is on the forum as I've read it in the past and done it, but I cannot find the post/thread in question and have already gone through loads of volume related stuff already while looking for it.
This was a tweak that enabled the volume transition from quiet to loud or vice versa do move really quickly when you hold the volume key up or down (in Sense in general rather than a specific program). I think it was a registry tweak rather than a feature in a cab (or a cab specially for this) but I may be wrong.
So for example the default is that if your phone is on Silent/Vibrate mode and you hold down the volume up key it steps up over a second or two until it reaches full volume. This tweak meant that you don't have to hold the key for as long to make it move quickly up or down.
I don't mean that it enables the volume to jump instantly from one end of the scale to the other, it still moves in steps, but it just moves a lot quicker.
I used to have it on my phone but I flashed it the other day and cannot find out how to get this back and I miss it - it's a nice touch!
Can anyone help? Thanks if so!
Bump! Surely someone must know how this is done? Well, I 'know' someone does since I previously had it set up like this but you know what I mean!
Would really appreciate being able to do this.
Hi,
I'm looking for this too. But no answer until now. I think (but I'm not an expert) that this should be easy to do.
I found it tonight by accident and I'm amazed no-one else has said the answer.
It's simply in windows>settings>personal>buttons as stepping speed.
Related
I want to map the green "phone" ("send") button to work as speakerphone with long keypress when phone is used, but I can't find any info.
OTOH I notice most ROMs use long press for this button and map usually wireless managers, which would be fine if it would work that way only when phone is not in use (and 'restore' the speakerphone function for long press when phone is in use) but I have not seen such solution yet. Has anyone done/try this?
-888- said:
I want to map the green "phone" ("send") button to work as speakerphone with long keypress when phone is used, but I can't find any info.
OTOH I notice most ROMs use long press for this button and map usually wireless managers, which would be fine if it would work that way only when phone is not in use (and 'restore' the speakerphone function for long press when phone is in use) but I have not seen such solution yet. Has anyone done/try this?
Click to expand...
Click to collapse
Hi,
Deleting Long_Send.lnk might restore original function of long press send key sir,.
Hope it help,.
Regards
Unfortunately, I don't think you can have two different functions based on context. AdvancedConfig has an option to map pretty much anything to the long send.
Garmin said:
Hi,
Deleting Long_Send.lnk might restore original function of long press send key sir,.
Hope it help,.
Regards
Click to expand...
Click to collapse
Thank you, Sir
blue_94_trooper said:
Unfortunately, I don't think you can have two different functions based on context. AdvancedConfig has an option to map pretty much anything to the long send.
Click to expand...
Click to collapse
Well, I was thinking about something more complex than I can do myself, hence my post here.
Idea is to make a small applet which will switch the function of the button based on the processes running (or other ways to determine it) and assigning different shortcut to this button. I.e. when the phone is connected it will assign speakerphone to the "send - long press", when phone is not in use it would redirect "send - long press" to the wireless manager, if you know what I mean (sorry my english); so virtually mapping the "green" button to this app could achieve that, no?
intersted also in your send key LKP!!
-888- said:
Thank you, Sir
Well, I was thinking about something more complex than I can do myself, hence my post here.
Idea is to make a small applet which will switch the function of the button based on the processes running (or other ways to determine it) and assigning different shortcut to this button. I.e. when the phone is connected it will assign speakerphone to the "send - long press", when phone is not in use it would redirect "send - long press" to the wireless manager, if you know what I mean (sorry my english); so virtually mapping the "green" button to this app could achieve that, no?
Click to expand...
Click to collapse
Bump....
I also want exactly the same setup! Great minds think alike!
Your mention about the wireless manager sounds a handy idea also, and I am at present having to use a long keypress on the left hand hardware 'record' button. This is fine, but I also have it mapped to normal press = audio record. But want to use it for something else at some point.The more buttons free the better. To be able to have the sent button act on a long key press to work the speakerphone seems to me like something that should actually be in place by default. I mean, what better way to start the speakerphone!!
I do hope someone is able to shed some light on this, or you manage to pull it off yourself you can count me in to try the fix etc.
PS:: Would a MORT SCRIPT help in this situation I wonder? I am not familiar with MS but sure someone may know a way round it.
Regards
Nick-UK
Thanks for your kind support
I wrote about this year or more ago on another forum, but few responses I got were discouraging at best.
I think if we could do such "app", we could use it for all the buttons and change their "assignments" based on the currently running apps...
With scripts we can do things like rename "Long_Send.lnk" into "Long_Send.disabled" (for example) instantly, and rename it back to "Long_Send.lnk" when i.e. pressed again. But the problem is that I don't know how to "detect" and use it in the scripts what is currently running and discriminate between foreground and background processes that are currently running?
Because what if you have two (or more!) programs that are using the same button assignments but for different purposes and both are running in the same time? say you are on the phone talking - thus long_send is assigned to speakerphone, and you also run (for example) windows media player where you assigned same green button to fullscreen display? The scripts cannot tell which one is running in the foreground by themselves, and (in this example) holding green button could bring the WMP to fullscreen instead of turning on speakerphone. Beforewe use mortscript to "activate" apropiate script, we need to know which process was started last (so - per my example - we would know that the phone was last started and not the WMP, and mortscript would run "speakerphone script for green button" instead of "fullscreen wmp script for green button"... and there is another problem: the phone is always ON on our PocketPCs since boot, and it is running all the time in the background, so it will have to differentiate between phone being active and phone in the "waiting" state...). Apologies if I sound incomprejensible, I tried to make it clearer but I don't know is it less gibberish
to cut it short: I don't think it can be done with simple scripts. But of course I may be wrong.
In theory it should work this way:
1 Long_Send.lnk -> starts our "app"
2 "App" checks what program is currently running on the screen (in the forground, or last started etc)
3 "App" executes apropiate action assigned for this program (i.e. speakerphone for active phone call, or wireless manager for today screen, etc etc)
4 "App" releases/removes/disables the action from previous step and changes it back to the state it was before when the foreground program is closed (i.e. changes back long_send from assignment to speakerphone back to default once the phone call ended)
sounds simple, doesn't it?
I'm slowly learning my way around the Fuze but have a few questions for those who are more familiar with the device.
1. Is there any way to change the color scheme of TouchFlo? I don't mind the AT&T symbol but the gray title bars are a little depressing.
2. Is there any way to wake up the Fuze by hitting any button other than the power button?
3. To AT&T, who's the genius that decide to only have one customizable button? Not everyone will use PTT so it would have been nice to see that button customizable. Maybe even the back button (which is better suited on the side of the device than front facing by the way) could be customizable.
4. Is there any way to keep the screen on during call?
5. Is anyone else having problems at times when they press the right directional arrow, the back button is activated?
Any information is appreciated.
to answer all ur questions..all i can honestly say is : "search"
im not tryin to be a wang or nothing..but i had just about those same exact questions no less than 2 days ago when i got my device..and just typing in the minimal brang me to my answers.
so yea..just search and undoubtably (sp) u will find every answer and then some.
Late,
Jstar
I know the title sound complicated but i don't think the idea is. I either saw this in a dream or in another forum and haven't been able to find it again. Anyways my idea is pretty simple:
When the phone is turned up to it's proper position as if your holding it in your hand (the screen is facing up) the phone automatically unlocks it self without the need to press the damn menu button twice or do a silly pattern. When you put it down on a surface, you put it screen down and then when you pick it up and turn it over, it wakes up easy as that. If the phone is facedown and rings it wakes up. And you want the parameters of the phone tilt to be strict enough the phone won't wake up when it's in your pocket. Also, when you put it facedown, the phone will go to sleep.
I sadly don't know if you can overwrite the unlock of the phone (that has no pattern lock) nor do i have the porgraming skills to do this. If it's not possible to bypass the lock screen with a program, maybe u could emulate the menu button being pressed twice? Just my idea. If there is something like this out there already, just post the link. Thank you!
This app already exists. You can download it in the Market. Unfortunately I can't remember the name...it was one of the first apps I installed on my phone.
OK--I looked it up, and the app I was thinking of is not what you asked for. The app is Ring Control, which focuses on controlling the ringer based on position.
However, it uses the same inputs that yours would, so maybe you should contact the programmer? He has a long post about the programming of it here, and it doesn't seem to far from what you want:
http://fognl.blogspot.com/2008/11/android-ring-control.html
Bump!!! come on guys...make this happen.
I finally customized my mega the way I wanted it to be when I initially bought it. I'm also running a 6.5.5 rom. Unfortunately I still have some issues with it and I was wondering if someone knew anything about them. First of them is if it would be possible to remove the start soft key in the bottom left corner of the screen. That would be nice since the mega already has a hardware start key and the one on the screen becomes redundant. It would be nice if we would just have two soft keys in the bottom corners
Also, I looked for a solution for the ugly volume manager in these last builds but couldn't really find one. I tried other volume managers like setvolume but that one is buggy even with answering phone calls. I find that unacceptable because most of all, it's a phone. So maybe if we could restore the default one or use another one without so many bugs that would be great. I saw somewhere that a solution was already available but for vga phones. Maybe that could be ported to qvga
I am with you on this. Would love to see these fixes.
I need theses fixes too!!! WM 6.5.5 has bad interface...
Why does the volume control must be so fat and ugly??
The most important thing is volume control in the youtube app sucks!
I wish someone can fix the volume control to use back the original HTC one.
Erm ok, the problem is even when the default HTC Volume control is implemented in the ROM, for some reason WM 6.5.5 overwrites that. I tried a few times. I think that sucks cos I'm a student , and my phone needs to be on silent. But the new volume control can be activated on the lockscreen so I'm afraid it would turn silent off. Any suggestions for this?
tlkh said:
Erm ok, the problem is even when the default HTC Volume control is implemented in the ROM, for some reason WM 6.5.5 overwrites that. I tried a few times. I think that sucks cos I'm a student , and my phone needs to be on silent. But the new volume control can be activated on the lockscreen so I'm afraid it would turn silent off. Any suggestions for this?
Click to expand...
Click to collapse
There's a nice app called SetVolume that does the trick quite nicely. Also, there's a cab that can remove the start button. I lost the cab but there's a registry tweak that does the job. You can search for it.
Hey all,
I've tried everything that came up in my searches, but I have yet to find a working solution. What I want to do is get the Volume Rocker long presses to change from just increasing/decreasing volume automatically to changing the tracks while music is playing. It'd make my life a lot easier at work and was one thing I loved about CM7.
I've tried modifying the Edison keylayout file to no avail, and all the patches offered for various other Moto phones won't install. I don't think this is something kernel-specific, but if anything, could someone guide me to a place where I could learn how to make a patch for the A2? I imagine I am not the only one that would appreciate such a mod, and seeing as I'm on break, I have time to try and make one myself.
Thanks for reading, any information is helpful!