Related
Hi there,
I have the following little prob with my Polaris:
whenever I make a call the display will go dark after a couple secs (which by itself isn't bad). However, seems like the polaris enters the standby-mode after acouple more secs, since I won't be able to touch the display to bring it up again-instead I will have to press the green or red button. This is a little annoying since I'm not able to easily access, e.g., the contacts during a call or press a key to, say, delete a message when checking my voicemails.
Any suggestions on how to tackle this?
Thanx
Two things you can do:
When you are in a call you can always press the power button and the screen will switch back on giving you access to all your applications and contacts, etc..
Better solution is to install the Backlite application. See http://forum.xda-developers.com/showthread.php?t=360657
This will stop the backlight switching off during a call. Works fine for me.
reteb said:
Two things you can do:
When you are in a call you can always press the power button and the screen will switch back on giving you access to all your applications and contacts, etc..
Better solution is to install the Backlite application. See http://forum.xda-developers.com/showthread.php?t=360657
This will stop the backlight switching off during a call. Works fine for me.
Click to expand...
Click to collapse
Thank you!
Yap, I knew about the power button but think hitting this one is a little annoying, too. What I'd aktually like is that - during a call - the display IS indeed turned off or at least dimmed down to very dark in order to safe battery. However, I'd like it to stay touch-sensitive and come back on if I touch it. Will the Backlite application do this for me?
Thanx again!
Elvez said:
However, I'd like it to stay touch-sensitive and come back on if I touch it. Will the Backlite application do this for me?
Click to expand...
Click to collapse
I think the point of making the screen "non touch-sensitive" during a call is that it is easy to touch it with your face during a call and you could end up disconnecting the call or doing other unexpected things.
anonimo said:
... and you could end up disconnecting the call or doing other unexpected things.
Click to expand...
Click to collapse
Hooray to unexpectedness!!
HKLM\Drivers\BuiltIn\RIL\EnableFastDormantDisplayD uringCall by "1" to "0"
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?
FYI These codes have been obtained by decoding various .apk files present in the phone firmware.
*#*#4636#*#*
This code can be used to get some interesting information about your phone and battery. It shows following 4 menus on screen:
Phone information
Battery information
Battery history
Usage statistics
*#*#7780#*#*
This code can be used for a factory data reset. It'll remove following things:
Google account settings stored in your phone
System and application data and settings
Downloaded applications
It'll NOT remove:
Current system software and bundled applications
SD card files e.g. photos, music files, etc.
PS: Once you give this code, you get a prompt screen asking you to click on "Reset phone" button. So you get a chance to cancel your operation.
*2767*3855#
Think before you give this code. This code is used for factory format. It'll remove all files and settings including the internal memory storage. It'll also reinstall the phone firmware.
PS: Once you give this code, there is no way to cancel the operation unless you remove the battery from the phone. So think twice before giving this code.
*#*#34971539#*#*
This code is used to get information about phone camera. It shows following 4 menus:
Update camera firmware in image (Don't try this option)
Update camera firmware in SD card
Get camera firmware version
Get firmware update count
WARNING: Never use the first option otherwise your phone camera will stop working and you'll need to take your phone to service center to reinstall camera firmware.
*#*#7594#*#*
This one is my favorite one. This code can be used to change the "End Call / Power" button action in your phone. Be default, if you long press the button, it shows a screen asking you to select any option from Silent mode, Airplane mode and Power off.
You can change this action using this code. You can enable direct power off on this button so you don't need to waste your time in selecting the option.
*#*#273283*255*663282*#*#*
This code opens a File copy screen where you can backup your media files e.g. Images, Sound, Video and Voice memo.
*#*#197328640#*#*
This code can be used to enter into Service mode. You can run various tests and change settings in the service mode.
WLAN, GPS and Bluetooth Test Codes:
*#*#232339#*#* OR *#*#526#*#* OR *#*#528#*#* - WLAN test (Use "Menu" button to start various tests)
*#*#232338#*#* - Shows WiFi MAC address
*#*#1472365#*#* - GPS test
*#*#1575#*#* - Another GPS test
*#*#232331#*#* - Bluetooth test
*#*#232337#*# - Shows Bluetooth device address
*#*#8255#*#*
This code can be used to launch GTalk Service Monitor.
Codes to get Firmware version information:
*#*#4986*2650468#*#* - PDA, Phone, H/W, RFCallDate
*#*#1234#*#* - PDA and Phone
*#*#1111#*#* - FTA SW Version
*#*#2222#*#* - FTA HW Version
*#*#44336#*#* - PDA, Phone, CSC, Build Time, Changelist number
Codes to launch various Factory Tests:
*#*#0283#*#* - Packet Loopback
*#*#0*#*#* - LCD test
*#*#0673#*#* OR *#*#0289#*#* - Melody test
*#*#0842#*#* - Device test (Vibration test and BackLight test)
*#*#2663#*#* - Touch screen version
*#*#2664#*#* - Touch screen test
*#*#0588#*#* - Proximity sensor test
*#*#3264#*#* - RAM version
NOTE: All above codes have been checked on Google Android phone Samsung Galaxy I7500 only but they should also work in other Google Android phones.
Atleast say thanks
Great list of codes thanks for sharing it.
thank you
but some codes not working!
You can also enter the following code while in the lockscreen to get to most of the above mentioned service pages:
Menu, Back, Back, Menu, Back, Menu, Menu, Back
Good set of information, thanks for the post. gonna try some now.
Thank you..
Thank you for the codes...
Thanks for the codes, I'm going to add them to my wiki.
thanks for sharing
Just tried these out, and it turns out that the earpiece can actually get pretty damn loud... so it is a software problem after all (in-call volume).
Clyzm said:
Just tried these out, and it turns out that the earpiece can actually get pretty damn loud... so it is a software problem after all (in-call volume).
Click to expand...
Click to collapse
which code u use to make volume louder?
I've tried a number of these codes and nothing happens (except the phone information code).
I have a rooted x10a from Rogers 024 firmware
Thanks for the list though!
swapniladsure said:
which code u use to make volume louder?
Click to expand...
Click to collapse
Didn't make it louder, but I used the lockscreen code in the fourth post to test the speaker:
beno1 said:
You can also enter the following code while in the lockscreen to get to most of the above mentioned service pages:
Menu, Back, Back, Menu, Back, Menu, Menu, Back
Click to expand...
Click to collapse
great list of codes! ive been meaning to get all these together and save them somewhere....here i come, copy and paste!
thank you guys
Clyzm said:
Didn't make it louder, but I used the lockscreen code in the fourth post to test the speaker:
Click to expand...
Click to collapse
hey dude its only increase the volume on testing time...but when u actually make call than earepice volume is less....
any ways i tried to give my best code...
if in future if i find any new code than i will update it soon..
thank you u guys for all your replys
swapniladsure said:
hey dude its only increase the volume on testing time...but when u actually make call than earepice volume is less....
any ways i tried to give my best code...
if in future if i find any new code than i will update it soon..
thank you u guys for all your replys
Click to expand...
Click to collapse
...that's what I just said. All it does is test the speaker, it doesn't change any settings in the phone. All I said was that the speaker has the potential to have louder call volume.
About earpiece volume. This didn't work for me, but so far none of the codes are. Give it a try and let us know if it works for you.
Taken from the following website...
http://androidforums.com/1263586-post1.html
Earpiece volume to low? I'm talking about the earpiece speaker built into the phone, the part you hold to your ear. You can increase this volume beyond maximum factory setting. When you change this, please change it slowly, meaning 1 increment at a time, you don't want to blow your speakers out. Thank you to the user over at xda-developer forums who showed me how to do this. update: it seems if you do a reboot of your phone, the settings revert back to factory for this volume fix...working to try to figure out a way to lock in the new volume settings.
Okay, lets begin. Go to your dial pad. Dial in *#*#197328640#*#*
Next, tap your finger onto the following, in the following order:
[5] Audio
[1] Handset
[1] Volume
[1] SRS Speech RX Volume
next notice the following defaults that pop up.
[0]0_lvl:63
[1]1_lvl:68
[2]2_lvl:73
[3]3_lvl:78
[4]4_lvl:83
[5]5_lvl:88
This basically means, that your volume up and down keys have 5 clicks, starting from the lowest setting, and click your volume up 5 times, takes you through the sequence of volumes listed above. You can change each click to be a new volume setting. For me 1-4 are fine, I just wanted max volume, which is click number 5, to be something higher. The phone does not let you to put in half increments, meaning 88.5 is not possible. So you have to use 1 increments. Please please do this carefully, dont suddenly jump to 95, you could blow out your speaker possibly. So I tried just 1 increment above 88, went to 89, and perfect, much louder now! okay so this is how you do it:
Once you get the list above, do the following:
Click your finger on [5]5_lvl:88
Next, a screen pops up asking for input. On the bottom of your phone, tap the menu button, this is the button next to the little home button.
Next tap "key input"
Next tap 1 increment at a time, lets start off with 89 so where it says enter value, tap this, your keyboard pops up, type in 89
Next Tap your menu button again
Next Tap "end"
you are now finished, make a phone call and see how 89 works for you, when your volume is set to max
Clyzm said:
Didn't make it louder, but I used the lockscreen code in the fourth post to test the speaker:
Click to expand...
Click to collapse
I tried this and the volume was much louder! the issue was it really stared to disort and sound sh#t on the piano spot. So the reason why the volume is so low is the dam speaker is ****! Increasing the volume will cause more distortion and make things worse. I be happy to live with this for the next few years till my contract is over...
let me see this...
Terul said:
About earpiece volume. This didn't work for me, but so far none of the codes are. Give it a try and let us know if it works for you.
Taken from the following website...
http://androidforums.com/1263586-post1.html
Earpiece volume to low? I'm talking about the earpiece speaker built into the phone, the part you hold to your ear. You can increase this volume beyond maximum factory setting. When you change this, please change it slowly, meaning 1 increment at a time, you don't want to blow your speakers out. Thank you to the user over at xda-developer forums who showed me how to do this. update: it seems if you do a reboot of your phone, the settings revert back to factory for this volume fix...working to try to figure out a way to lock in the new volume settings.
Okay, lets begin. Go to your dial pad. Dial in *#*#197328640#*#*
Next, tap your finger onto the following, in the following order:
[5] Audio
[1] Handset
[1] Volume
[1] SRS Speech RX Volume
next notice the following defaults that pop up.
[0]0_lvl:63
[1]1_lvl:68
[2]2_lvl:73
[3]3_lvl:78
[4]4_lvl:83
[5]5_lvl:88
This basically means, that your volume up and down keys have 5 clicks, starting from the lowest setting, and click your volume up 5 times, takes you through the sequence of volumes listed above. You can change each click to be a new volume setting. For me 1-4 are fine, I just wanted max volume, which is click number 5, to be something higher. The phone does not let you to put in half increments, meaning 88.5 is not possible. So you have to use 1 increments. Please please do this carefully, dont suddenly jump to 95, you could blow out your speaker possibly. So I tried just 1 increment above 88, went to 89, and perfect, much louder now! okay so this is how you do it:
Once you get the list above, do the following:
Click your finger on [5]5_lvl:88
Next, a screen pops up asking for input. On the bottom of your phone, tap the menu button, this is the button next to the little home button.
Next tap "key input"
Next tap 1 increment at a time, lets start off with 89 so where it says enter value, tap this, your keyboard pops up, type in 89
Next Tap your menu button again
Next Tap "end"
you are now finished, make a phone call and see how 89 works for you, when your volume is set to max
Click to expand...
Click to collapse
let me see this it gona work or not
Hi,
also these codes are not working for me, except the *#*#4636#*#*.
The quoted post is related to Samsung Phones (Vibrant) and this is most probably the reson why it doesn't work on SE X10.
However, does someone know another set of codes for X10? The Service Menu, entered by the Menu/Back combination, shows a list item "Service settings" but with "No Item" in the next menu level. Is there any known trick to unlock this settings? Maybe there could be a option to adjust in-call volume...
All the Best
Peter
EDIT: X10i, R2BA026 rooted
no not yet solution for speaker volume increase
no solution yet..
let me try to replace speaker on my x10i
i will try to put any other speaker from other sony to my x10i..
same for loudspeaker also..
replace the ringer for mp3 volume increase of phone
but let me try this and than i will post u all
Anyone else share my enthusiasm for this feature, the 'phone goes to sleep while I'm on a call and I can't do anything unless I hit the power button and hang up' trick! This is my favorite. Works great in conference calls with your boss and clients who are bidding on multi-million dollar contracts! Need to check an email while on the conference call? Can't. Want to answer another call? Can't. Want to turn the speakerphone off because your 4 year old comes running into your home office? Can't. I'm not sure if it's a Sense Fail or Google Fail but it's a major f'ing fail in my book. Hopefully it's just me being an idiot and missing a setting, but the phone comes out of the box doing this. Still a fail.
Pretty sure its a YOU fail. Works fine here dude. I check emails, text, look up map directions while on the phone. What 'battery saver' apps do you have running?
Sent from my HTC One XL using Tapatalk 2
You probably configured to use power button to end the call (that option should never existed, IMO). So, that means you can't access other phone features without hand up the call.
IIRC, out of box, power button is not configured to hand up the call for this exact reason. You probably enabled it.
When Android goes into sleep (or turn off the screen), only power button can wake it up. So configure power button to end the call is nothing but ask for trouble.
Pirateghost said:
Pretty sure its a YOU fail. Works fine here dude. I check emails, text, look up map directions while on the phone. What 'battery saver' apps do you have running?
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
None. I can do all of those things as well, while the phone is on, but talking for more than 2 minutes (which is what I have set under Display and Gestures/Sleep) and the screen goes to sleep. Nothing brings it out except the power button. I've only had it for 4 days, I'm trying to keep it 'native' until I figure everything out.
tomviolence said:
None. I can do all of those things as well, while the phone is on, but talking for more than 2 minutes (which is what I have set under Display and Gestures/Sleep) and the screen goes to sleep. Nothing brings it out except the power button. I've only had it for 4 days, I'm trying to keep it 'native' until I figure everything out.
Click to expand...
Click to collapse
Read Foxbat's post and verify you didn't turn on the 'power button end call' feature
Sent from my HTC One XL using Tapatalk 2
foxbat121 said:
You probably configured to use power button to end the call (that option should never existed, IMO). So, that means you can't access other phone features without hand up the call.
IIRC, out of box, power button is not configured to hand up the call for this exact reason. You probably enabled it.
When Android goes into sleep (or turn off the screen), only power button can wake it up. So configure power button to end the call is nothing but ask for trouble.
Click to expand...
Click to collapse
You put me onto the correct path, there is an option under Accessibility for 'Power Button ends call'. By default it is on. As for the wake from sleep, I can't find that one.
tomviolence said:
You put me onto the correct path, there is an option under Accessibility for 'Power Button ends call'. By default it is on.
Click to expand...
Click to collapse
Turn it off and your problem solved.
As for the wake from sleep, I can't find that one.
Click to expand...
Click to collapse
There isn't one. Only power button can wake the screen.
Also, you can flip the phone over while on the call to automatically turn on speaker phone. Flip back, it will automatically turn off speaker phone. Quite handy if you do meetings a lot. It is configurable in call settings. This is HTC only feature that can't be found on other brands.
I have a bluetooth speaker that I use on occasion. I have tasker set up so that when I connect the speaker it automatically loads pandora on my phone, waits a few seconds, then sets media volume to max (15). However, it doesn't seem to be able to set the volume up high enough and I think it's because of the volume limit and the warning. Is there any workaround for this without rooting right now?
I am having the same issue and am also looking for a way to get rid of the high volume warning message.
Thanks!
You can use autoinput. It is a tasker plugin. You can set it to hit ok when the warning message comes up, then repeat the max volume when the message is gone.
dschachm said:
You can use autoinput. It is a tasker plugin. You can set it to hit ok when the warning message comes up, then repeat the max volume when the message is gone.
Click to expand...
Click to collapse
Thanks for the tip. Definitely going to check it out.
dschachm said:
You can use autoinput. It is a tasker plugin. You can set it to hit ok when the warning message comes up, then repeat the max volume when the message is gone.
Click to expand...
Click to collapse
I've installed it and tried to get autoinput going, but I can't figure out exactly which options to put. I see it as an option in tasker as a plugin, but then I have to choose between action, global action, modes, root, screen capture, UI query or unlock screen. I've tried some different combinations, mostly with action, but can't seem to figure it out. Any specifics would be appreciated.
You want to go to auto input action. Then select configure.
You want to select click for action
Text for field type
The I think field text would be "ok" so that is the field that is clicked when the box comes up.
dschachm said:
You want to go to auto input action. Then select configure.
You want to select click for action
Text for field type
The I think field text would be "ok" so that is the field that is clicked when the box comes up.
Click to expand...
Click to collapse
Thanks for the help. I finally got this to work. I tried it your way and it didn't seem to work, but, after messing with it (for a log longer than I'd like to admit), I hit the easy setup button at the top, then after swiping away a couple of windows I was able to press volume up until the volume warning came up and I hit "OK". When I went back into tasker it asked me if I wanted to choose the field coordinates or the text field "OK". I just chose OK and the rest was just setting up timings.
If anyone is curious how I got it set up I've attached a screenshot of the tasker screen. Unfortunately it doesn't show anything about the OK screen since that was done through the easy setup.