May be it is a well known feature, I just discovered it : just turn the ATHENA face down and the screen goes OFF an it stays OFF even if connected via USB and charging..
Leaving it face down on my desk the PC-USB charge is faster and leaving it face down after any use save the battery!
I disabled HTCSENSOR (ATHENA) SERVICE
sergiopi said:
May be it is a well known feature, I just discovered it : just turn the ATHENA face down and the screen goes OFF an it stays OFF even if connected via USB and charging..
Leaving it face down on my desk the PC-USB charge is faster and leaving it face down after any use save the battery!
I disabled HTCSENSOR (ATHENA) SERVICE
Click to expand...
Click to collapse
sorry this does not work for me
edit: nevermind i got it
irus said:
sorry this does not work for me
edit: nevermind i got it
Click to expand...
Click to collapse
I don't get and it is not working for me.
lpsi2000 said:
I don't get and it is not working for me.
Click to expand...
Click to collapse
if you goto gsconfig the last line of text is #fdxxxxx(0) the 0 should be 1 and make sure to disable the athena dll in post 1
irus said:
if you goto gsconfig the last line of text is #fdxxxxx(0) the 0 should be 1 and make sure to disable the athena dll in post 1
Click to expand...
Click to collapse
Or use GSEN to manage this feature too
sergiopi said:
Or use GSEN to manage this feature too
Click to expand...
Click to collapse
I used GSen and did what irus said "if you goto gsconfig the last line of text is #fdxxxxx(0) the 0 should be 1 and make sure to disable the athena dll in post 1"
I didn't even need to reset the phone, it started working right after I made the change and saved it.
For some reason I cant turn of the Gsensor on my device. I'm going to the right value and changing it to 0 but everytime I soft-reset it, turns back to 1. What is the trick to this?
I'm using Resco reg edit......(unregistered still in trial). Would that make a difference?
Kenjari said:
For some reason I cant turn of the Gsensor on my device. I'm going to the right value and changing it to 0 but everytime I soft-reset it, turns back to 1. What is the trick to this?
I'm using Resco reg edit......(unregistered still in trial). Would that make a difference?
Click to expand...
Click to collapse
after you turn it off...even if it changes back to 1 automatically, install GSen and run, if you get no error message about it unable to find sensor then you're alright.
sometimes if you make a registry edit and softreset the device right after, the changes won't stick. A good rule to follow after making a registry change is to put the phone on standby (turn off screen) wait a could of seconds (I wait 6), take the phone out of standby then softreset.
Okay,
You guys have managed to completely baffled me on the correct procedure now. Let me document this once and for all, and please correct me as I go along. I will keep coming back to this post to edit it until it is correct.
As I understand it. This is what you do.
1) Make sure auto-rotate is working first, since Gsensor will not work if auto-rotate if off. So, if you have used irus's auto-rotate toggle to disabled it before, we need to enable it first. As a way to check, the \HKLM\AutoRotate\Off\Toggle value should be 0 in the case of Irus's ROM. In the case of base ROM that has not used irus' auto-rotate toggle script before, check that the registry entry is as follows:
HKLM\Services\HTCsensor\Flags= 0 (dword)
HKLM\Services\HTCsensorathena\flag=0 (dword)
2) Then you install Gsensor. This would put three icons in the start/program folder: GsenCFG, GSen, and GSenToggle.
3) Then you go into use the GSenCFG program and change the last line from #fdscreenoff(0) to #fdscreenoff(1).
4) Then you use one of the following methods. Either a) or b)
a) Change the registry entry to
HKLM\Services\HTCsensor\Flags= 4 (dword)
HKLM\Services\HTCsensorathena\flag=4 (dword)
Soft reset
b) Use irus's AutoRotateToggle program so that \HKLM\AutoRotate\Off\Toggle value become 1 followed by the soft reset
I placed the device face down, but it does not switch off automatically, so my steps must be wrong, but where did I go wrong?
Irus and Sergiopi, please help me get the procedure correctly documented.
Thanks.
Edit: the above steps are incorrect. See my post # 11 to understand this whole thing.
Form the base ROM, with all the features enabled:
1) Download and run FDCSOFT task manager 3.1 http://www.dotfred.net/TaskMgr.htm (is just a simple .exe file, unvaluable IMO)
2) Services>HTC Sensor Service (Athena)(SEN1) tap and wait the menu.. STOP it, and set startup to "manual"
3) Tap GSEN until you have the "Unload program?" answer NO
4) check in the cfg the entry #fdscreenoff(1)
5) save and exit
6) copy gsen.lnk from \windows\start menu\programs into \windows\startup
Restart GSEN : done
I finally understand how this whole things works.
First of all if we're using GSEN application, then make sure the HTC Sensor Service (SEN0: ) service is active. Also, if you're going to use SKKV GSEN, it would make NO sense in keeping the HTC Sensor Service (Athena)(SEN1: ) service alive, so you might as well kill it. This should improve performance and eliminate potential conflict between SKKV's auto-rotate and HTC's own auto-rotate.
Next, I installed Gsen. this put into the Program start directory the GSenCFG, GSen, and GsenToggle programs.
I Used the GsenCFG to change the last line to #fdscreenoff(1). This basically tells Gsen that I wish to have the screen blanked out if I place the screen face down.
Next, come to the interesting part of what I discovered - GSenToggle and its behaviour/effect.
Let's start with the scenario where I have deleted the Gsen from the Start Up folder.
\\\\\\\\\\\\\\\\\\\\ Auto Rotate works?/Auto blanking works?
Initially Yes/no
Then toggled to yes/yes
Then toggled to yes/no
Then toggled to yes/yes
Then toggled to no/no
Then toggled to yes/yes
Then toggled to yes/no
Then toggled to yes/yes
Then toggled to no/no
Then toggled to yes/yes
Then toggled to yes/no
Then toggled to yes/yes
Then toggled to no/no
Next, let's consider the scenario where Gsen has been included in the auto start folder
\\\\\\\\\\\\\\\\\\\\ Auto Rotate works?/Auto blanking works?
1) Initial behavour: Yes/Yes
2) Click GsenToggle: Yes/No
3) Click GsenToggle again: Yes/Yes
4) Click GSenToggle again: No/No
5) Click GSenToggle again: yes/Yes
6)Click GSenToggle again: Yes/No
7)Click GSenToggle again:Yes/Yes
8)Click GSenToggle again:No/No
9)Click GSenToggle again:Yes/Yes
10)Click GSenToggle again:Yes/No
11)Click GSenToggle again: Yes/yes
12)Click GSenToggle again: No/No
13)Click GSenToggle again:Yes/Yes
14)Click GSenToggle again:Yes/No
15)Click GSenToggle again:Yes/Yes
16)Click GSenToggle again:No/No
EDIT: Okay the above toggling pattern does NOT make sense. It was happening because I kept both the HTC Sensor Service (Athena)(SEN1: ) and HTC Sensor Service (SEN0: ) alive . The wierd toggling pattern must be due to conflict between HTC' s auto-rotate and SKKV's auto-rotate.
If I first kill HTC Sensor Service (Athena)(SEN1: ), keeping only the HTC Sensor Service (SEN0: ) alive, then I get the following toggling pattern:
/////// Auto Rotate works/ Blank screen works?
Toggle Yes/yes
Toggle No/No
Toggle Yes/yes
Toggle No/No
Toggle Yes/Yes
Toggle No/No,,, etc. The sensible way...
[FONT=Verdana, sans-serif]Very interesting, will go for it this week end.[/FONT]
[FONT=Verdana, sans-serif]Thanks all for the step by step.[/FONT]
sergiopi said:
Form the base ROM, with all the features enabled:
1) Download and run FDCSOFT task manager 3.1 http://www.dotfred.net/TaskMgr.htm (is just a simple .exe file, unvaluable IMO)
2) Services>HTC Sensor Service (Athena)(SEN1) tap and wait the menu.. STOP it, and set startup to "manual"
3) Tap GSEN until you have the "Unload program?" answer NO
4) check in the cfg the entry #fdscreenoff(1)
5) save and exit
6) copy gsen.lnk from \windows\start menu\programs into \windows\startup
Restart GSEN : done
Click to expand...
Click to collapse
I know I followed this point by point.
3) do I change the #fdscreenoff(1) to (0) or just leave it (1)
Restart GSEN....does that mean "Unload program?" answer YES at this point!
I'm sorry for the confusion on my part...but I have followed this exactly point by point......and I remain with the front screen rotating. I'm correct by saying that the goal of this trick is to disable autorotate on the today screen but still keep active in the other programs right? This also increase speed some correct?
Not happening for me
EDIT: I'm sorry ..... it does work! I had the wrong idea for this tweak. If I lay it down flat screen face down.....it turns the phone off. You may began to through the tomatoes at me now!
GSensor Explained
GSensor and SKKV GSEN explained
Since my post # 11, I have done more testing and come up with a more complete understanding on sensors, auto-rotate, Gsensor, bubble-level/calibration related applications.
When you first install the Sogarth base ROM, there following three services will be installed:
- GSensor Service (AP11)
- HTC Sensor Service (Athena)(SEN1: )
- HTC Sensor Service (SEN0: )
The first item, GSensor Service, appears to be the overall control, which could not be stopped. That leaves us to only have to understand what the second and third items, HTC Sensor Service with almost identifcal name but each controlling a specific behaviour of our device.
The HTC Sensor Service (Athena)(SEN1: ) is the service that must be active for the device to auto-rotate with HTC's own software (i.e, without the help of third party software such as the GSensor from SKKV). If you disable or stop this service, then auto-rotate will also be disabled (unless you use the approach will I'll explain later).
The HTC Sensor Service (SEN0: ) on the other hand, is not needed for auto-rotate to work. However, it is needed for applications such as the Bubble Level, Calibrator (not sure of the name, but I think you know which one), and GSensor SKKV to work. If you try to start BubbleLevel with the HTC Sensor Service disabled or stopped, then you will not get the measurement at the top right hand corner (instead you will see the word "NaN" degree). If you try to use the SKKV GSEN program without this service running, you will get the "Cannot conect to GSensor(3)" message. These third party softwares does NOT require the HTC Sensor Service (Athena)(SEN1: ) to be active.
Therefore, the procedure for improving performance depends on what you want to achieve: Let's cover a few scenarios.
1) If all that you're interested is to be able to run the BubbleLevel program and to play GSensor controlled game but you do not want auto-rotate to slow down the system, then you should Disable HTC Sensor Service (Athena)(SEN1: ).
2)If all that you want is the auto-rotate, but nothing else, and you do not mind auto-rotate working in all applications, then you should enable HTC Sensor Service (Athena)(SEN1: ) but disable HTC Sensor Service (SEN0: )
3) If you want to automatically blank the screen by placing the device face down then regardless of whether you want auto-rotate to work globally, not at all, or just for specific applications), then you should also disable Sensor Service (Athena)(SEN1: ) but enable HTC Sensor Service (SEN0: ).
SKKV GSenCFG allows you to say what you want to do. For example:
- do you want to enable or disable the FaceDownScreenOff function?Enter #fdscreenoff(1) to enable, and #fdscreenoff(0) to disable. Note that this blanking of screen gives an illusion that the device has been switched off, but it isn't. If you're connected via active sync, and you place it face down, the screen will blank but active sync connection will stay alive. So it is not the same as switching off the device.
- do you want to list the program to be included or excluded from auto-rotate? If auto-rotate is to EXCLUDE those listed in the config file, then enter #onlyfor(0). If auto-rotate is to only work for those in the config file, then enter #onlyfor(1) in the configuration file.
- To list the program in the configuration file, first start that program, then start GSENCFG and if you click Edit/Select Window Name, you will easily recognise the window name. Just click on that for the line to be inserted into the configuration file.
- specify how fast you want the blanking /rotation to work in the #timeout(nnn) line. The smaller the number the faster the device will rotate. I tried #timeout(50) and had good result. You might want to experiement with this yourself
Hope this makes the whole concept crystal clear. Note that I have made some edit on post 11 to correct some earlier misinformation.
Finally, I have a piece of bad new: The above is true only for the Sogarth Base ROM. The vanilla does does not seem to allow my BubbleLevel to run at all. Irus, you might want to look into this.
nice job on explaning it. i will look and see what i took out. does the gsen work at all on the vanilla?
irus said:
nice job on explaning it. i will look and see what i took out. does the gsen work at all on the vanilla?
Click to expand...
Click to collapse
yes. However, the pattern of toggle is strange. Not sure if it was because I did not disable htc auto rotate or the ROM.
With Irus's 0MB Page Pool Version, I have all the gsen apps working except BubbleLevel, I get this error when i try to execute the app, although it does install fine.
an unexpected error has occurred in bubblelevel.exe select quit and restart this program, or select details for more information
file or assembly name "microsoft.windowsmobile.status,Version=1.0.0.0, Culture=neutral,PublicKeyToken=31BF3856AD364E35", or one of its dependencies , was not found
clicking on details shows the same info plus: MissingMethodException
ok, now im kinda in a pickle....I decided to try a couple mroe diamond apps, Caver, and the lightsaber app, that both use the gsen. No go on either, both gave the same error as the bubble app. So i uninstalled them and then I noticed that my autorotate is dead. All my services are still configured correctly with fdtask, gsen is started, and I cannot get any rotations at all....what could be up?
eaglesteve said:
GSensor and SKKV GSEN explained
Since my post # 11, I have done more testing and come up with a more complete understanding on sensors, auto-rotate, Gsensor, bubble-level/calibration related applications.
When you first install the Sogarth base ROM, there following three services will be installed:
- GSensor Service (AP11)
- HTC Sensor Service (Athena)(SEN1: )
- HTC Sensor Service (SEN0: )
The first item, GSensor Service, appears to be the overall control, which could not be stopped. That leaves us to only have to understand what the second and third items, HTC Sensor Service with almost identifcal name but each controlling a specific behaviour of our device.
The HTC Sensor Service (Athena)(SEN1: ) is the service that must be active for the device to auto-rotate with HTC's own software (i.e, without the help of third party software such as the GSensor from SKKV). If you disable or stop this service, then auto-rotate will also be disabled (unless you use the approach will I'll explain later).
The HTC Sensor Service (SEN0: ) on the other hand, is not needed for auto-rotate to work. However, it is needed for applications such as the Bubble Level, Calibrator (not sure of the name, but I think you know which one), and GSensor SKKV to work. If you try to start BubbleLevel with the HTC Sensor Service disabled or stopped, then you will not get the measurement at the top right hand corner (instead you will see the word "NaN" degree). If you try to use the SKKV GSEN program without this service running, you will get the "Cannot conect to GSensor(3)" message. These third party softwares does NOT require the HTC Sensor Service (Athena)(SEN1: ) to be active.
Therefore, the procedure for improving performance depends on what you want to achieve: Let's cover a few scenarios.
1) If all that you're interested is to be able to run the BubbleLevel program and to play GSensor controlled game but you do not want auto-rotate to slow down the system, then you should Disable HTC Sensor Service (Athena)(SEN1: ).
2)If all that you want is the auto-rotate, but nothing else, and you do not mind auto-rotate working in all applications, then you should enable HTC Sensor Service (Athena)(SEN1: ) but disable HTC Sensor Service (SEN0: )
3) If you want to automatically blank the screen by placing the device face down then regardless of whether you want auto-rotate to work globally, not at all, or just for specific applications), then you should also disable Sensor Service (Athena)(SEN1: ) but enable HTC Sensor Service (SEN0: ).
SKKV GSenCFG allows you to say what you want to do. For example:
- do you want to enable or disable the FaceDownScreenOff function?Enter #fdscreenoff(1) to enable, and #fdscreenoff(0) to disable. Note that this blanking of screen gives an illusion that the device has been switched off, but it isn't. If you're connected via active sync, and you place it face down, the screen will blank but active sync connection will stay alive. So it is not the same as switching off the device.
- do you want to list the program to be included or excluded from auto-rotate? If auto-rotate is to EXCLUDE those listed in the config file, then enter #onlyfor(0). If auto-rotate is to only work for those in the config file, then enter #onlyfor(1) in the configuration file.
- To list the program in the configuration file, first start that program, then start GSENCFG and if you click Edit/Select Window Name, you will easily recognise the window name. Just click on that for the line to be inserted into the configuration file.
- specify how fast you want the blanking /rotation to work in the #timeout(nnn) line. The smaller the number the faster the device will rotate. I tried #timeout(50) and had good result. You might want to experiement with this yourself
Hope this makes the whole concept crystal clear. Note that I have made some edit on post 11 to correct some earlier misinformation.
Finally, I have a piece of bad new: The above is true only for the Sogarth Base ROM. The vanilla does does not seem to allow my BubbleLevel to run at all. Irus, you might want to look into this.
Click to expand...
Click to collapse
Good explanation and I also finally got it. I just installed the apps and tried and it works nicely.
Thank you.
touchlasvegas said:
ok, now im kinda in a pickle....I decided to try a couple mroe diamond apps, Caver, and the lightsaber app, that both use the gsen. No go on either, both gave the same error as the bubble app. So i uninstalled them and then I noticed that my autorotate is dead. All my services are still configured correctly with fdtask, gsen is started, and I cannot get any rotations at all....what could be up?
Click to expand...
Click to collapse
May be you have just simply toggled to the auto rotate=no and blanking =no cycle? Study post #11 again. One more toggle may bring both back.
If this has been posted before, go ahead and /dev/null this mods.
Stolen from another board.
VIEW/USE/MODIFY AT YOUR OWN RISK!!!
*#*#4636#*#* for battery and other general setttings like GSM/CDMA
*#*#8255#*#* for Gtalk service monitor
*#*#7780#*#* for factory data reset
*#*#34971539#*#* for information about phone camera (be very careful hitting options here)
*#*#7594#*#* change the "Power" button action in your phone.
*#*#197328640#*#* service mode
*#197238640# service mode
*#0*# testing mode
*#06# view IMEI number
*#1234# display phones current firmware
*#*#1472365#*#* gps test
For those wondering, the "Change action of the power button" simply changes a long-press of the power button to shut down, as opposed to the choosing b/w Airplane mode, Shutdown and Silent.
These are pretty cool. Thanks
Most of these are linkable via Better Cut as well.
Codes - How to
For those wondering what these programmer (or developer) codes are and how all this done:
These are programming codes and "support" or service dept. codes to get to various menus and interfaces on the Vibrant.
All phones have these and they are typically only known to developers, tech support and even some customer service reps for use when people call in a panic to say the phone is on the fritz.
WARNING: I WOULD NOT ENTER CODES UNTIL YOU HAVE READ THE BELOW AND KNOW WHAT THEY DO. (Some codes are harmless if you screw things up, others may brick your phone, perform a hard reset, delete apps, render the phone and parts of it inoperable, or negatively affect functionality.)
For example, where the OP says "Information on camera" code, be careful on hitting certain menu options on that interface. I don't see a need, at this stage anyway since the Vibrant is so new, to enter that code, so why not avoid problems by not entering it.
After all, the camera code does not do that much for the end user (that's you). Two of the menu options do in fact give you info on what camera software version is running your camera but until Samsung provides a camera firmware update, what good does it do you to know what is running the camera.
But two of the options that you might be tempted to press say:
"Update camera firmware in image" - that's on the ROM.
"Update camera firmware in SD card"
You might think those check the Net for an update, similar to what can be done in Android Settings. But pressing those menu items does NOT access the Net.
If you press either of those it will DELETE the existing camera software on your ROM. It will then look for the update. Since you don't have one, the update will be incomplete and your camera will be inoperable because you deleted the software required to operate it.
Then you're stuck with making a warranty claim saying "My camera stopped working" and hoping they don't discover that you deleted the software and refuse the claim (or charge you for the software reinstall.) Note: I don't know if reinstalling the ROM that's on the Vibrant will reinstall the camera software.
So be careful.
____________________
Still adventurous? (I know you want to enter some codes, just for the fun of it.) Well here's how it all works:
1. You enter these codes via your phone dialer, enter the numbers as if you are going to make a phone call. (I have had some people ask me that, where do I type in the numbers.)
2. On all code entries you will always type a *#*# at the beginning of the code entry. This tells the Samsung Galaxy S that a code is about to be entered (that is, the numeral after the last #).
3. At the end of the entry you will type combinations of the #*# or whatever is indicated. This is to get you out of the phone dialer and into menu interfaces of whatever you are trying to do or to activate the command.
4. On entering the last character of the code a menu will pop up, where I say it should or the command will be executed.
Here's a teaser code, I will enter all kinds of them later.
This one is harmless if you screw it up entry wise.
This is the code that the OP mentions, but I will explain it a bit more.
____________________
You are probably aware that when you press the power button on the right side of the Vibrant a menu comes up with choices of putting the phone in airplane mode, silent mode, and power off.
Well this code can change the power button's function to just turn off the phone when you press it, that is, rather than a menu popping up. This basically saves you the additional step of having to press a menu item to turn off the phone.
(You can enter the same code and change it back to where the pop-up menu appears when pressing the power button.)
Here is what you do.
1. Go to your phone dialer.
2. Enter this code: *#*#7594#*#*
3. On entering code a window/graphic will pop up that says
"Shutdown - Enable to Shutdown on End call long press." (Note: Although it says "end call" what it means for the Vibrant is the physical power button on the top right side of the phone. There is no physical "end call" button on the Vibrant. End call is performed with a touchscreen command.)
4. There will be a box to check and uncheck. On accessing this the first time the box should be unchecked.
5. Check the box. A green check mark will appear.
6. Back out of the page by pressing your back button until you get to your home page, or simply press the Home button.
7. You do NOT have to reboot for the change to take affect.
8. You can try it out by pressing the power button. If you did things right the phone will automatically power off.
Bonus Tip: You can enter the codes in your contacts, with a descriptive name and the code in the phone number field. While you can't "dial" the codes from the contacts menu you will at least have reference to them. (And you can sometimes perform a copy and paste.)
I would like to add that *#*#7412365#*#* brings up a Camera Firmware page that includes both the phone and camera firmware information, as well as the ability to flash new camera firmware.
I did the power button one yesterday and it's nice but out kills my lock screen too. I like the way the puzzle thingy and the lock screen in general is set up so I'm torn.
Sent from my SGH-T959 using XDA App
gravis86 said:
I would like to add that *#*#7412365#*#* brings up a Camera Firmware page that includes both the phone and camera firmware information, as well as the ability to flash new camera firmware.
Click to expand...
Click to collapse
Yes, that's what I mentioned in my perhaps way-too-long post.
That's the code I say to avoid because it does not serve any purpose, because:
1. At this time, since the Vibrant is so new, it does not matter what version software the camera is using. We have to assume it's the latest. Even if it's not, we can't change it since Samsung has not provided a camera firmware upgrade. And,
2. Pressing the update (flashing) camera options will "brick" the camera since the operation will first delete the camera firmware and then search for an update. Because you don't have one, the camera will be rendered inoperable.
I bought a Chinese smartphone from DX.com. I wasn't expecting great quality, but I was expecting it to at least give me a workable system out of the box. Instead, upon first powerup it gives me a lock screen - and I'm not told what the lock key is. I requested help on DX's forum, but as they don't themselves manufacture it I expect the answer to take a long time to arrive, if it ever does.
By powering it up with various buttons pressed I've managed to get it to boot to what I'm assuming is some kind of debug/recovery menu. It's interesting that it isn't the usual Android recovery, but it's something running within the system itself.
In this mode the lockscreen is disabled, but so is most of the operating system. I did manage to get to the settings/language menu, but when I access it I get this error.
I tried accessing the developer options in the hope of enabling debugging and accessing the filesystem via ADB, but the whole submenu is inaccessible in this weird testing mode.
As for the obvious idea - accessing the security menu and disabling the lockscreen - even in this mode it still wants the previous combination before it'll let me disable it.
The debug menu itself. I tried accessing a few options at random, but I get a lot of text I can't understand and large buttons with red/green colouring that look menacing. What little is written in Latin alphabet (stuff like RECALIBRATION) makes me think I could easily screw the phone up by experimenting with the various options without knowing what I'm actually doing. In general it seems like a hardware test app, though; one of the options I did dare test makes colors appear if you push the non-touchscreen buttons. I'm not sure anything in this can be used to bypass anything.
I tried posting to the /r/chinese subreddit to see if they can make sense of those menus. Is there anything I can do in the meantime? I don't know, does Android 4.3.3 have a default combination for that accursed lock screen? Getting to the default Android recovery and doing a factory wipe would probably solve the problem, but so far I've only managed to get the weird testing mode by booting with buttons pressed.
After an immense driver headache, I have managed to gain ADB access to the filesystem. However, "adb reboot recovery" doesn't show a recovery menu - I get the Android animation with the rotating whatsitsname, then a red exclamation mark.
Edit: I have changed the language to English via ADB. The lockscreen is still stubbornly in place.