I found the following problem with most cooked ROMs (also including the last official one from HTC) /I tried that on fresh installations in every case/
I like AutoLock feature. So I made a small .reg file to modify one small entry in registry.
The moment this feature is on - if the device becomes locked, the screen goes dim. Problem is - it stays dimmed forever. I tried thousand different solutions - many combinations of registry values, power options, etc. nothing helps. If I lock the device manually - no problem. only with autolock. Anybody knows how to make it work?
Regards,
Vojtek
Maybe you should post your script, so that someone can have a look. Did this work on some previous ROM? Or has it been an ongoing problem?
Try using SmartLock, found on this site.
jmckeejr said:
Maybe you should post your script, so that someone can have a look. Did this work on some previous ROM? Or has it been an ongoing problem?
Click to expand...
Click to collapse
The official HTC ROM that I used to have before recent official update from HTC - worked very fine with this little registry mod.
The modification is as follows:
HKCU->ControlPanel->Backlight->AutoDeviceLockEnable
default value = 0
I change it to 1. This is all I do after totally fresh ROM update. that causes the dim to go permanently on from the next lock (doesn't matter if it was caused by auto or manual). even If I get back with the value to 0 in registry - problem stays. soft reset (and value set to 0) eliminate the problem.
one more thing - I never use auto-light sensor. My backlight level is always set to 2. with auto-light sensor - autolock works OK. however I loose a lot of battery life since auto-light sensor never allows backlight levels lower than 4.
Regards,
Vojtek
check out Lumos, it'll let you backlight go as low as you set it to
http://forum.xda-developers.com/showthread.php?t=450318
GldRush98 said:
check out Lumos, it'll let you backlight go as low as you set it to
http://forum.xda-developers.com/showthread.php?t=450318
Click to expand...
Click to collapse
Thank You for the tip. The tool itself is great. However it is affected same way by the autolock. Autolock causes device to stay dimmed permanently - even with Lumos running.
Regards,
Vojtek
First off... I'm new around here & still a little flabbergasted by everything WinMo, but this site has already helped me tremendously.
Secondly, I can confirm the AutoLock bug. I updated my Touch Pro to the latest official rom last night. While running through AdvancedConfig (i think...) I noticed the AutoLock option & enabled it. 10 minutes later I was freaking out that I had stuffed up my expensive new toy...
Disabled, rebooted & all is OK again.
First of all - Advanced Config has nothing to do with it (to defend the author).
Second - thank You for support. I could not find a solution for this problem anywhere and I spent hours googling. For the moment I thought that my TP is failed. Seems that nobody uses AutoLock these days. I don't know how everybody's doing it, but without locking, my TP calls to different people (especially from Favourites tab) from time to time...
Vojtek
vojtek11 said:
I don't know how everybody's doing it, but without locking, my TP calls to different people (especially from Favourites tab) from time to time.
Click to expand...
Click to collapse
I require a password/passcode level of security on my device - which the Lock/Unlock feature doesn't provide. Unfortunately, the current security implementation in WinMO 6.x doesn't allow the Today screen to be seen like the Lock/Unlock feature.
As a result of these shortcomings, most folks tend to use a 3rd Party lock application such as: S2U2, mLock, etc. as they provide the desired flexibility.
HTH,
very familiar with this issue. I'm working on it too. It affects the WM6.5 lockscreen for sure and I thought it was a problem with only that. Bugger that it affects official ROMs as well. Good info though, I can stop concentrating on the lockscreen and start looking at power mgmt.
mindfrost82 said:
Try using SmartLock, found on this site.
Click to expand...
Click to collapse
SmartLock all the Way!!
Related
01/26/09 - This is just a minor update to fix some issues and add a couple small features.
Feel free to give comments or ask questions.
Thanks!
This program is a touch driver to handle the touchscreen presses and vibration. A settings program exists to configure how the vibration works.
Since this is a touch driver, there is no program you need to run to start it.
It has been tested on an HTC Touch and HTC Touch Pro for several days with several stability issues corrected. I am only releasing this now that I feel comfortable that you will experience no major issues. However, I cannot guarantee that it will work flawless for you. I cannot be held responsible for any loss of data or time you may experience while using this.
If you are experiencing problems after installation, please let me know so I can fix these issues.
Features
Global enable/disable option
Vibrate on touch/release
Variable duration of vibrate
Disable during Phone Call option
Disable when device is silent
Disable when device is locked
Disable when stylus is out (for devices that support this option)
Enabled for On-Screen Keyboard only (Temporary option until full include/exclude list is incorporated)
Settings Program->Settings->System->TouchResponse Settings
AppToDate support
Coming Soon
Include/Exclude list for vibration
Different vibration patterns
Resolve any software conflicts
Vibration tweaks
Sound on touch
Vibrate on hardware button press
Multi-language support in Settings program
I'm open to suggestions...
Known Issues
May or may not play well with touchflo/ftouchsl. If TouchResponse isn't working for you, try disabling those if they are enabled.
Disable when device is silent may not work on some devices. Let me know what kind of device you have if this is the case for you.
Donate
This is a free program and I plan on keeping it that way. If you enjoy using it and would like to support its development, please consider donating by clicking here:
Donate $ | Donate €
Change Log
.3.2 (01/26/09) - Minor update
- Option to disable vibration when device is locked
- AppToDate now supported - Download AppToDate to be informed of the latest updates
- Fixed issue when SIP Only didn't work as expected in landscape mode
- Fixed issue when Stylus Out still resulted in vibration when that option was set.
.3.1 (01/14/09) - Minor update
- Should properly upgrade when built into a custom rom
.3 (01/13/09) - More features
- Option to vibrate on release of touch
- Option to disable vibration when stylus is out
- Option for vibration to only be enabled for on-screen keyboard
- Better auto-detection of device model/vibrate id
.2.2 (11/27/08) - More Minor Updates
- Can increment the duration by one instead of five now
- The chance for a longer than usual vibration should be reduced if not eliminated altogether
- Disable while silent option should work a little better now
- Settings program allows for more Vibrate IDs in the Advanced tab
.2.1 (11/26/08) - Minor Update
- Windows Mobile 5 is now supported
.2 (11/26/08)
- Attempt to resolve suspend issues with certain phones - Let me know
- Disable while silent option added - may not work perfect
.1 (11/24/08)
- Initial Release
Questions and Answers
Q. How to I change the settings?
A. Start->Settings->System->TouchResponse Settings
Q. Why do I not see the settings program?
A. For some phones, the settings program does not appear in the control panel. Until I figure out a fix, you can run the program by going to \windows\TouchResponseSettings.cpl
Q. Why is it not vibrating when I touch the screen?
A. Go to the Device tab in TouchResponse Settings. It will display information about your device. If it says to select your vibrate id then find the one that causes the vibrate to work. Send me a PM with the name of your device model along with the vibrate id that works for you and I will incorporate that into future releases.
Q. Will this drain my battery life?
A. I don't have any statistics to show the before and after battery usage. However, I personally have not experienced any significant increase in battery usage. It all depends on how long the vibrate duration is and how often you touch the screen.
Q. Why does the vibrate last longer than it's supposed to sometimes?
A. This should hopefully be resolved as of version .02.2. If you experience this after this version, please let me know when it happens and how often.
Q. Why is the vibration always the same duration no matter what the settings are set at?
A. Use a registry editor to go to HKEY_LOCAL_MACHINE>Software>OEM>VIB and set STRENGTH_LOW to 0. Thanks to agdaniels for pointing this out.
Please don't post this cab on any other site. Let's keep all discussion here. I appreciate your cooperation.
Thank you for your support!
Ill try it and let ya know how it compares
Nice idea, thanks for sharing.
I read about a phone (I think it was LG Incite?) where some people complained about vibrating even when entering text with the soft-keyboard.
Could you give us an option to dis-/enable vibrating when entering text ? Maybe there´s an event you can use when the soft-keyboard flips up...dunno
regards,
Martin
m.schmidler said:
Could you give us an option to dis-/enable vibrating when entering text ? Maybe there´s an event you can use when the soft-keyboard flips up...dunno
Click to expand...
Click to collapse
Since the driver has first crack at the touch event, I should be able to determine which window is being touched and either vibrate/not-vibrate depending on how it's configured. For example, I can see that the SIP is being touched and not vibrate. I'll add that to the list, Thanks!
Just as Martin said.
When typng on the on screen keyboard. Vibrate on every button of the keyboard we pressing. That would be awesome.
Gonna test this on the X1i
It works great on my HTC touch PRO.
Yea Man !!
I love this Apps !!!
Thanks so much
all feature Works like a charm in my Kaiser (HTC TyTN II)
Well I guess I will put my suggestion here as I did with the other 2 programs like it. Would you consider creating a setting to were it is only active on SIP Keyboard AND when SIP keyboard is active I have choice between a vibration or a sound or both?
I know I can get a sound by going to the general settings of winmo but when it is on it makes a noise for all screen taps...annoying!!
CuriousG
curious george said:
Would you consider creating a setting to were it is only active on SIP Keyboard AND when SIP keyboard is active I have choice between a vibration or a sound or both?
Click to expand...
Click to collapse
Since this is a similar comment among everyone I will focus on this next. Thanks everyone for your feedback!
how about different types and lengths of viberations like the old motos used to have? dash-dash-dash-buzzz haha
maybe different intensities if possible?
I've always wanted 'heptic feedback' on my KS20 but non works for me. I've tried Heptick Feedback, Vibration Feedback and now TouchResponse, none work for KS20. Duh....
Can these options be added?
1. Not to vibrate when on silent?
2. Change buzz length (make it shorter/less intense)
3. An "use only when SIP activated" option.
richabi said:
how about different types and lengths of viberations like the old motos used to have? dash-dash-dash-buzzz haha
maybe different intensities if possible?
Click to expand...
Click to collapse
This is something I've been wanting to experiment with. I'll add that to my list, Thanks!
stutzedward said:
I've always wanted 'heptic feedback' on my KS20 but non works for me. I've tried Heptick Feedback, Vibration Feedback and now TouchResponse, none work for KS20. Duh....
Click to expand...
Click to collapse
You may have tried something similar with the other programs you have tried, but you can try changing the Led Id in the Settings program under the Advanced tab. Be sure to press ok to make the settings to into effect. Hopefully it is just a case where the KS20 doesn't use the default Led Id for vibrate.
derekwilkinson said:
Can these options be added?
1. Not to vibrate when on silent?
2. Change buzz length (make it shorter/less intense)
3. An "use only when SIP activated" option.
Click to expand...
Click to collapse
1. Yes, this is something I want to add! It's sometimes hard to go unnoticed when I use my phone in meetings at work when the vibration is loud.
2. Did you see the Settings program in the System tab of the "Control Panel"? Or do you mean a something like a longer buzz but less intense?
2. I'm going to be focusing on that with an include/exclude option next.
Thanks for your feedback!
Snailslug said:
You may have tried something similar with the other programs you have tried, but you can try changing the Led Id in the Settings program under the Advanced tab. Be sure to press ok to make the settings to into effect. Hopefully it is just a case where the KS20 doesn't use the default Led Id for vibrate.
Click to expand...
Click to collapse
Hey hey, it works for KS20 for the first time!!!!
I set the LED from 0 to 3 and hey, 3 works.
0 - LED displays green
1 - LED displays red
2 - LED displays blue
3 - it worked!
Thank you soo much! I gotta spread this on the KS20 thread because a lot of KS20 users are wanting this like me. I'll link them here.
very good work.
i have mine set to 25ms and the vibrate is a perfect length and silentness.
i agree on only sip active and/or blacklist
Just want to echo what's already said. What most ideally want is for vibration to be active ONLY on keyboard when text entering and to be as brief a buzz as possible. Some owners type very fast and we want the buzz to keep up and not still lag on the previous tap while tapping on the next key. It has to be super quick and not miss a key press when typing quickly. Thanks!
Ok, found the settings app, my bad
The other two requests would be awesome if they were to be fulfilled!
whats the difference between this program and this one : http://forum.xda-developers.com/showthread.php?t=425063 ??
Hey Ive seen issues with people having trouble with the distribution of LEDs on the keyboard with not seeing keys and others to bright and thats not me haha. I was wondering though if anybody knew a registry hack or something that would let the backlight on the keyboard stay on longer than 5 seconds? That is the biggest annoyance of this phone that ive seen so far.
aaron580 said:
Hey Ive seen issues with people having trouble with the distribution of LEDs on the keyboard with not seeing keys and others to bright and thats not me haha. I was wondering though if anybody knew a registry hack or something that would let the backlight on the keyboard stay on longer than 5 seconds? That is the biggest annoyance of this phone that ive seen so far.
Click to expand...
Click to collapse
Do a search for a utility called Advanced Config, it has a setting to change the backlight timeout, among a lot of other things. You'll need to have the ARM4i version of ppc .NET 3.5 installed also.
BEWARE: Use the tool at your own risk. Don't turn menu animations and start menu animations on, as it has caused my start menu to go really wonky (all the colors are jumbled and its impossible to read) Turning this off made it behave as expected. Just a warning
Hey thanks man. I didnt even know that setting was in advanced config and ive used since the mogul lol.
Doesnt work
I have tried the tweak in advanced config and nothing changed, has anyone else had luck with this?
oldquser said:
i have tried the tweak in advanced config and nothing changed, has anyone else had luck with this?
Click to expand...
Click to collapse
it can not be changed
This is one of the most annoying things about the TP. Anytime you pause for 5 seconds the keyboard backlight goes off! Grrr!
No kidding. I completely disabled the light sensor on my P4000, it was always on as long as the slider was open. I even watched an hour long episode of top gear while I sat in a Mazda dealership while having an oilchange done on my car.
I too have been equally frustrated with this. With no solution in sight, I think I might have thought of a program that could save our sanity. The only problem is that i've only THOUGHT of it and it doesn't exist yet. I've started a thread in the 'Development and Hacking' section. Here's the link http://forum.xda-developers.com/showthread.php?t=490267
Add comments, add ideas, just add support
First of all, thank you for your interest and feedback! Mostly due to your request I want to present you a new version.
Version 1.25 changelog:
1. Added Connections on/off
2. Added alarm - poor one
Version 1.20 changelog:
1. Added new profiles: WiFi on/off, Bluetooth (BT) on/off, Phone on/off. Added also Soft Reset.
2. Some minor changes.
Version 1.10 changelog:
1. Added half-hours (I think quarters are too much).
2. Hour format (24 or 12) is automatically changed depending on your regional settings.
3. I don't have VGA device, but I think now the screen is squeezed a bit so it can fit to VGA square screen. Please, try and tell me what happens.
4. Added sound profiles - low, medium, high and very high.
5. Number of settings increased from 4 to 15.
Please, download TProfiler120.CAB for latest version.
Automatically switches device sound mode(available profiles - sounds on, sounds off, vibrate, volume low, medium, high, too high), turns on/off wifi, bluetooth, phone mode and soft resets at selected hour and weekday and thus saves your battery power. Simple application, doesn't occupy memory. Tested only on HTC HD2 but should work on other devices too (TP2, Touch HD/Blackstone - tested thanks to replies to this thread).
It works fine on TP2
Great application.
It would be great if it had also a 24-hour mode .
It would also be great if we could set the device to change to a certain volume on the Ring and System. I like to turn my phone down to 2 notches on both of those and crank it back after 5pm.
digiblur said:
It would also be great if we could set the device to change to a certain volume on the Ring and System. I like to turn my phone down to 2 notches on both of those and crank it back after 5pm.
Click to expand...
Click to collapse
+1 on this request.
Would be also great if one could change profile on headset plug-in/plug-out.
When I softreset the phone it gives me a non signed error.
VGA please
scabbard1 said:
VGA please
Click to expand...
Click to collapse
+1
looks very promising as of this is really important to have because i tend to forget to switch my phone to silent when im at school
ill be watching this thread
Great application !
Feature request: time in quarter/half hours too.
You might want to add some additional 'rules'. If you have a different time schedule for every day in the week, 4 just aren't enough...
Awesome
Been waiting for a free app like this. The Connective Tools one is nice, but I love the continuing user driven development of XDA. The suggestions on here are great and I echo the setting the volume to a custom level and the quarter/half hours things.
zharptitza said:
Been waiting for a free app like this. The Connective Tools one is nice, but I love the continuing user driven development of XDA. The suggestions on here are great and I echo the setting the volume to a custom level and the quarter/half hours things.
Click to expand...
Click to collapse
+1 though 5 min time slots would be better. Are going to try and integrate the App so it will switch on calendar appointments?
just installed 1.10 on my HD, but when I start the app it alerts "Doesn't exist", and after tapping 'ok' the app doesn't respond anymore, actually the complete screen doesn't respond. Using the hardwarebuttons I can go back to my homescreen and then using the system taskmanager I can shut the app down after that everythings fine..
anybody got an idea? because it looks like a useful app to me
Dear Xsite3,
I think you had to wait for a while - when started first time the application takes more time (1-2 minutes).
Just installed v1.1 on my HD2 and i get the message attached. Any ideas?
When I try to start up TProfiler I get a message box that simply says "Doesn't Exist". After that I can click on the TProfiler icon all day long but nothing happens. Wonder what doesn't exist?
V 1.10 crashes for me
I was using version 1.00 with no problems on my HTC Fuze running WM 6.5. But version 1.10 crashes on startup with this error:
TProfiler.exe
InvalidCastException
at
Microsoft.VisualBasic.CompilerServices.Conversions.ToInteger()
at
DeviceApplication1.Form1.Form1_Load()
at
System.Windows.Forms.Form.OnLoad()
at
System.Windows.Forms.Form._SetVisibleNotify()
at
System.Windows.Forms.Control.set_Visible()
at
System.Windows.Forms.Application.Run()
at DeviceApplication1.Module1.Main()
The app appears to draw at least a portion of it's window, and then crashes, though it goes by too quickly to see just how much of it is drawn
I really like the app. I especially like the addition of half hours in this version, if I can get it to work.
Hypermommy said:
When I try to start up TProfiler I get a message box that simply says "Doesn't Exist". After that I can click on the TProfiler icon all day long but nothing happens. Wonder what doesn't exist?
Click to expand...
Click to collapse
Hmm same here
Phone: TOuch HD
Rom: Xannytech 1.9B (+maxManila)
Cheers
Problems
Fellows, sorry for keeping you waiting - Please, try now - it should work.
[Solved] TS FREEZE FIXED / Orientation offset calibration & G-SENSOR CALIBRATION FIX
UPDATE: (13/11) A patch has been developed that completely eliminates TS FREEZE for good.
Thanks to mdebeljuh and jdivic, I tested it and it seems to be working perfectly.
Check post 140 on page 14:
http://forum.xda-developers.com/showpost.php?p=9194473&postcount=140
UPDATE: (20/11)A new patched 8.2 kernel without logging (better for daily use) is available.
Check post 234 on page 24:
http://forum.xda-developers.com/showpost.php?p=9304396&postcount=234
-----
EDIT: If you did autocalibration and messed your g-sensor, read post 10 & 11 to see a fix for it. (before going through post 1)
EDIT 2: Freezes of sensors and touch screen seem to be related to offset values. See post 10 & 11
Post 1 is for orientation offset. Check post 10 & 11 for g-sensor and ts freeze fix.
----
If your orientation is off when you lay your phone on a level surface and can't calibrate it in Android (because many people found it gets corrupted after auto calibration), this is one way to do so. (Winmo g-sensor calibration does not seem to affect android orientation)
Install an app that displays sensor information along with pitch and roll. (such as SensorDebug from Android market)
Put your phone on a level surface such as the floor or a table.
Note your pitch and roll values.
Use rootexplorer or similar file manager to edit /data/misc/AK8973Prms.txt file. (open in text editor) (For ASTRO CHECK POST 70 in page 7)
You will see AOFFSET.x and AOFFSET.y at the bottom. (May be on top if you autocalibrated previously)
y affects pitch and x affects roll, there is about 4 to 1 ratio.
What you are trying to do is make pitch and roll 0 with minimum flicker.
Press and hold home button to switch between rootexplorer and sensordebug. Your changes will be reflected in realtime (with most builds). Go back and forth a few times to get perfect result. (You can press and hold home button to go back and forth) If you think changing values don't have an affect, try to temprorarily change AOFFSET.x=90 and return to your app. When phone is on the table, your leveling bubble or pitch/roll must be way off. This way you can see if with your build changes are reflected in realtime or not. If not try restarting, use different sensor app and give feedback please. (After that revert AOFFSET.x to 0 or other value your want to fix back orientation)
For example:
If pitch is 3 and roll is -1
you may start by
AOFFSET.x=4
AOFFSET.y=-12
Then adjust with 1 increments to get rid of flicker.
It is best to adjust one value at a time.
EDIT: IF YOU WANT TO CALIBRATE Z AXIS, CHECK POST 61 in page 7
Calibrated AOFFSET values for my phone are x=2 y=-9 z=12
You can use gpsstatus or bubble app (to find bubble app search the market for bz.ktk.bubble and enable "show angle" from bubble apps settings.) for visual check of orientation calibration. Because of the protruding camera lens of hd2, there can be 1 degree difference between sideways and normal orientation. (It seems you can adjust in about 0.25 degree increments by each 1 increment of AOFFSET and compansate by lowering AOFFSET=y by 2 that gives 0 degrees in both normal and sideways orientation in bubble app)
- You don't need to reboot for most builds (if there is no affect check post 11)
- You don't need to kill/restart akmd
- You don't even need to close sensor app
- Because of not perfect kernel/build support for sensors, you may see them freeze when you move the phone (TS will also freeze). With evo kernels, just wait a few seconds and it will resume. (With nexus kernels they may freeze until sleep/wakeup) Interestingly the values of AK8973Prms.txt affect shake/move freezes. I wrote about this in post 10 and 11.
IT IS A GOOD IDEA TO BACKUP COMPLETE ANDROID FOLDER BEFOREHAND just in case something goes wrong. Chefs say you shouldn't auto calibrate your g-sensor under Android because with many people it gets messed up. Also good idea to backup your /data/misc/AK8973Prms.txt
You may have trouble accessing data folder with a file manager other than rootexplorer. Your build must be rooted. (most are) It is a good idea to update your su binary inside superuser app settings TWICE. If you change permissions of /data /data/misc folders you may access them even with standart astro file manager. Try chmod 777 /data from terminal emulator.
This procedure is also possible with adb or droidexplorer. But my way of doing is practical and it is in realtime. If your build has different file name, please tell us.
This IS a development thread, please don't tell me to post in generic section or clutter.
This is manual workaround for non-working auto calibration. If auto-calibration works in the future, it may very well fix your freezes.
Values of AK8973Prms.txt file may solve touch screen/sensor freeze problems with your games. Feedbacks are always welcome. We should find out what the other values do exactly. Also check post 10 & 11
Wow, thank you. I will certainly try this when I am sober (tomorrow morning).
I appreciate your taking the time to share this.
Have a good weekend!
Thanks! worked great....
thanks! worked perfectly
haha.. funny, this is the RIGHT way to do it: (credit goes to me )
1) put your phone on the surface and then
2) Gscript to stop gsen.
3) Go to callibration tool and press callibrate..
4) activate Gsensor through Gscript.
thats it and gsensor is fully callibrated to your way. no need to mess with system files.
eeeeeee said:
haha.. funny, this is the RIGHT way to do it: (credit goes to me )
1) put your phone on the surface and then
2) Gscript to stop gsen.
3) Go to callibration tool and press callibrate..
4) activate Gsensor through Gscript.
thats it and gsensor is fully callibrated to your way. no need to mess with system files.
Click to expand...
Click to collapse
Don't you think I already knew that? I wrote this long procedure because calibration tool corrupts calibration and doesn't work with many people. With many builds, chefs write don't calibrate your sensor. You need the gsensor script to be able to stop gsensor (kill akmd) since you didn't share it, people won't be able to do it anyway.
I suggest backing up complete Android folder before attempting to auto calibrate g-sensor within Android. Forum is full of people who calibrated under android and everything is messed up.
memin1857 said:
Don't you think I already knew that? I wrote this long procedure because calibration tool corrupts calibration and doesn't work with many people. With many builds, chefs write don't calibrate your sensor. You need the gsensor script to be able to stop gsensor (kill akmd) since you didn't share it. People won't be able to it anyway.
I suggest backing up complete Android folder before attempting to auto calibrate g-sensor within Android. Forum is full of people who calibrated under android and everything is messed up.
Click to expand...
Click to collapse
gsensor calibration tool causes nothing.. in my way -> t does exactly what you do..
i know that with the evo kernel the gsensor callibration is kinda corrupted, but it still works perfectly when following my orders.
although i would suggest not doing this with gsensor on.
as long as the gsensor is off when calibrating, there is no risk to mess the gsensor up.
although when callibrating with gsensor on messes the whole thing up, you can fix it following my orders again.
although its still nice that you edited the beginning of your tutorial:
memin1857 said:
If your orientation is off when you lay your phone on a level surface and can't calibrate it in Android (because many people found it gets corrupted after auto calibration), this is one way to do so. (Winmo g-sensor calibration does not seem to affect android orientation)
Click to expand...
Click to collapse
eeeeeee said:
gsensor calibration tool causes nothing.. in my way -> t does exactly what you do..
i know that with the evo kernel the gsensor callibration is kinda corrupted, but it still works perfectly when following my orders.
although i would suggest not doing this with gsensor on.
as long as the gsensor is off when calibrating, there is no risk to mess the gsensor up.
although when callibrating with gsensor on messes the whole thing up, you can fix it following my orders again.
Click to expand...
Click to collapse
I have made extensive tests and found out that you are actually doing no proper calibration. You are breaking other things.
- If you disable g-sensor before you open your sensor app (calibration tool) than you get no data from the g-sensor (since you disabled it) and can't calibrate.
- Phone must be very still while you disable g-sensor or the orientation data will get frozen at wrong values. And sensor app must be open beforehand.
If you fail calibration (y axis) will get messed up badly and won't work again. It wil flicker between full up and full down and further calibration attempts will make compass constantly spin.
- Still if you could do it all, nothing changes, offset is still there and calibration is wrong after following your instructions. (Try bubble app or sensor app with real sensitive degree values and you will see)
I searched your posts and saw that you are complaining about touch freezes. Maybe if you don't do auto calibration you may get less freezes?
Also please DO share anything you know. It is not enough to just say -disable g-sensor with gscript- People don't know that script, and if you don't share they can't do it. I saw your thread, you got 0 replies in 20 days, maybe because it doesn't work.
I advise against doing autocalibration. And remember, this is not a pissing contest. We are not doing this for the credit. We should be doing this for helping community. (You should have written nicer, instead of looking like showing off how genious you are and how fool we are. We know some things too.)
My way of doing it is NOT direct calibration. It is providing offset to g-sensor data that many people can do without the risk and can be restored back easily.
Note: I have found out that calibration tool generates a file named AccPrmsF.ini in the same folder with extreme z value. Sometimes a bma_result.txt gets created again with wrong values. Its content is input to AK8973Prms.txt again with extreme z value. If you restore your original AK8973Prms.txt g-sensor starts working properly again. (see post 10 & 11)
eywallah bro
How to restore g-sensor
If you calibrated with android calibration tool and your g-sensor freaked out. Here is how to fix it:
Use rootexplorer to
Delete AccPrmsF.ini and bma_result.txt file in /data/misc (if they exist)
Edit AK8973Prms.txt in /data/misc folder with rootexplorer to these values:
[AK8973]
HDOE_STATUS_SLIDER_OPEN=1
HDOE_STATUS_SLIDER_CLOSE=0
HDOE_SUCTEMP=114
HDAC_SLIDER_OPEN.x=128
HDAC_SLIDER_OPEN.y=135
HDAC_SLIDER_OPEN.z=4
HOFFSET_SLIDER_OPEN.x=250
HOFFSET_SLIDER_OPEN.y=593
HOFFSET_SLIDER_OPEN.z=175
HDAC_SLIDER_CLOSE.x=0
HDAC_SLIDER_CLOSE.y=0
HDAC_SLIDER_CLOSE.z=0
HOFFSET_SLIDER_CLOSE.x=0
HOFFSET_SLIDER_CLOSE.y=0
HOFFSET_SLIDER_CLOSE.z=0
ASENSE.x=256
ASENSE.y=256
ASENSE.z=256
AOFFSET.x=0
AOFFSET.y=0
AOFFSET.z=0
(These values may not solve freezes, check post 11 for different values that may fix freezes)
Some nexus based builds don't have slider open/close lines.
No need to reboot, just save and it should work instantly with most builds. (If it doesn't check post 11) If you delete AK8973Prms.txt or it may get recreated with wrong values (full zeroes) and freak out again. AOFFSET.z=xxx seems to be the culprit of calibrate tools vertical corruption. (Becomes full up or full down like digital when z=veryhigh). Only editing it to zero may solve the problem.
These values may change in time, or between builds. Those were my values, you may try to boot a new version of your android build and rip the file from it and use that instead.
If your g-sensor does not work at all after reboot you may need to restart it. Open terminal emulator and enter these commands:
su
/system/bin/akmd
Now it should be working.
Please tell if it worked for you. By comparing values and working on these values we may as well make g-sensor much better. (Accelerometer doesn't seem to be calibrated) If your build has different file name, please tell us. The instructions in post 10 may not be perfect and I am still working on this and will post if I find anything new. Of course kernel support is also required for getting less flickers, no freezes, proper poll intervall, correct i2c frequency and proper calibration.
EDIT: The values keep changing by itself. Interesting part is I am getting less shake/move freezes (or freezes in only one direction) in sensor apps or games now! I am experimenting with different values and it definitely affects how often freezes happen. I am trying to get the values of what a real calibration would do. Maybe sensor freezes happen when values are out of range. I am sure a proper calibration will get rid of these freezes but since with the current kernels we can't do proper auto calibration, maybe we can do manual one for now. Seems usual x y z accelerometer values are between 10 and -10. When freezes happen they seem to be more than 10 or less than -10. ASENSE values change the range of x y z (minimum working asense is 45 and the more you set the less range x y z has). Also ppp data seem to freeze/restart when sensor freezes happen. If freezes are eliminated even ppp data might work better! Some of the findings might be wrong, of course.
It seems you can update AK8973Prms.txt in realtime with droidexplorer and changes are reflected in realtime when you reopen, switch to the sensor app or sleep/wakeup. This makes testing easier.
It seems I have found non freezing values. Check next post. (Post 11)
Freezes are fixed now.
EVEN IF YOU ARE NOT GETTING TOUCH SCREEN / G-SENSOR FREEZES WITH USUAL USAGE OF YOUR PHONE, INSTALL SENSOR DEBUG, BUBBLE, COMPASS APP OR GAMES AND TRY IF THEY FREEZE WHEN YOU SHAKE/MOVE THE PHONE OR WALK WITH THE PHONE IN YOUR HAND. Bubble app is the most freezing app. To find it ssearch the market for bz.ktk.bubble. Enable "show angle" from bubble apps settings. Game example: Teeter
Make sure it has been at least 2 minutes since Android has booted. (Or it may fool you as it is busy when first home screen appears after boot)
Freezes have been mostly eliminated with newer builds/kernels, but they are not completely gone.
I am no longer getting any freezes in any app now. Not in compass apps, not in games, not in sensor displaying apps, not in calibration tool. I am also not getting freezes while I am walking with the phone.
I am not yet sure how this exactly happened (as I always had freezes in those apps when the phone moved) but currently my android build updates the AK8973Prms.txt file every minute by itself (doesn't change very much, but quite different from the beginning) and the current values have absolutely no freezes.
These values have no more freezes. (since they keep changing it may not last for days) Please try:
[AK8973]
HDOE_STATUS_SLIDER_OPEN=2
HDOE_STATUS_SLIDER_CLOSE=0
HDOE_SUCTEMP=111
HDAC_SLIDER_OPEN.x=4
HDAC_SLIDER_OPEN.y=135
HDAC_SLIDER_OPEN.z=8
HOFFSET_SLIDER_OPEN.x=-849
HOFFSET_SLIDER_OPEN.y=1179
HOFFSET_SLIDER_OPEN.z=-653
HDAC_SLIDER_CLOSE.x=0
HDAC_SLIDER_CLOSE.y=0
HDAC_SLIDER_CLOSE.z=0
HOFFSET_SLIDER_CLOSE.x=0
HOFFSET_SLIDER_CLOSE.y=0
HOFFSET_SLIDER_CLOSE.z=0
ASENSE.x=256
ASENSE.y=256
ASENSE.z=256
AOFFSET.x=0
AOFFSET.y=0
AOFFSET.z=0
Seems
A low HDAC_SLIDER_OPEN.x value
A large negative HOFFSET_SLIDER_OPEN.x value
A high HOFFSET_SLIDER_OPEN.y value
A large negative HOFFSET_SLIDER_OPEN.z value
and along with some other thing I did/happened fixed my freeze problems.
Some nexus based builds don't have slider open/close lines.
Change the AOFFSET.x y and z values to your device to level it on a table. (check post 1)
I am not attaching the file itself to this post because of differences between windows and linux with text files, just to be safe. (Paragraphs get messed up)
Also using the calibration tool with the phone face down gives better results with z axis. (to be able to tap on calibrate, put your phone on the table and make it just go over the edge of the table and tap from underside)
We need some feedback from other people now. Devs are welcome to use this information to open up ways to fix g-sensor in kernel.
I am using mdeejay desire hd 3.4 build. These may be different in other builds. If you find out please share.
Freezes returned after reboot. I am trying to find out how refix again.
I AM ASKING EVERYBODY TO TELL
1) If they have the freezes with their default configuration with bubble/sensor app moving/walking etc.
2) If my values fix the freeezes
3) If their filenames etc is different
4) Please also write your build and kernel type/version/base winmo rom and radio
Example: (copy paste and edit in your post please)
Default configuration have freezes: YES
New values fix freezes: YES
Different files: NO
Build/Kernel: mdeejay desire hd 3.4 / huanyu #21 evo base miri WM6.5 (21916) v19.1 (3.14 base) 2.15.50 radio
This is not over yet, with feedback we might find exact long term fix for everyone.
EDIT: These values work with some people. If they don't work you, experiment with different values. Since the results are reflected in realtime for most builds (no reboot required) it is much easier. Also don't edit the file on windows pc, it may get messed up. Some builds auto update the values when sensor app is reopened/switched to.
IMPORTANT: Try to temprorarily change AOFFSET.x=90 and return to your app. When phone is on the table, your leveling bubble or pitch/roll must be way off. This way you can see if with your build changes are reflected in realtime or not. If not try restarting and give feedback please. (After that revert AOFFSET.x to 0 or other value your want to fix back orientation)
EDIT 2: My sensors seem to be working perfectly since I also calibrated the z-axis. (post 61 on page 7) I need confirmation on this.
wow! thank you very much!
will try and post results soon.
Default configuration have freezes: YES (from time to time, not always)
New values fix freezes: YES. Post 11
Different files: NO
Build/Kernel: hyperdroid 1.6 / michyprima R11
before, using a live wallpaper called shake them all, the phone would insta-freeze on me.
using your values from post 11 (simple copy paste), no more freezes. And i really abused the wallpaper!
If this changes, i'll report here
EDIT: new answers
Post 1 is not for freeze fixes.
The solution is not long term.
I am extensively trying to find out what exactly made the freezes go away.
Because while it worked for many hours. After reboot freezes came back. I will hopefully find out why. Also the reason why the values change every minute is mistery. Contents of the file (values) change after you start or switch to any app that accesses the sensors. After android has booted it won't get updated unless the sensor reading apps are working.
I have been trying with many builds and kernels for theese freezes and they were never gone before. This time it never froze for several testing hours till I rebooted. That must be something.
Fixing the g-sensor after calibration corruption is ok. Adjusting level offset is also ok. But freezes need some more testing.
new answers in my above post.
you said that after the reboot freezes would happen. i change the permissions to read only on the AK8973Prms file, rebooted and no freezes.
crawlingcity said:
before, using a live wallpaper called shake them all, the phone would insta-freeze on me.
using your values from post 11 (simple copy paste), no more freezes. And i really abused the wallpaper!
...
new answers in my above post.
you said that after the reboot freezes would happen. i change the permissions to read only on the AK8973Prms file, rebooted and no freezes.
Click to expand...
Click to collapse
I am glad it worked for you and we are making progress.
I also had tried changing permissions before but after one minute permissions revert back to writable and the files is updated by the system.
just tested again. restored the default file (with the default values) and as soon as the little droids (or homers in my case) start moving - freeze.
Changed again to your values in post 11, changed permissions to read only, rebooted, played with the phone, i even juggled my HD2! No freezes. I think i won't change anything, unless i need to correct the pitch and the roll.
crawlingcity said:
just tested again. restored the default file (with the default values) and as soon as the little droids (or homers in my case) start moving - freeze.
Changed again to your values in post 11, changed permissions to read only, rebooted, played with the phone, i even juggled my HD2! No freezes. I think i won't change anything, unless i need to correct the pitch and the roll.
Click to expand...
Click to collapse
How are you changing the permissions?
I change permissions to readonly with rootexplorer and after I switch to sensordebug or bubble or phone tester app, the file reverts its permissions back to writable and gets updated.
BTW bubble app freezes more frequently than other apps. But when my freezes were gone, even bubble app never froze even when abused.
I'm just using root explorer. Select the file, uncheck the "write" option, close root explorer. Open sensor debug or whatever, check the file, untouched.
crawlingcity said:
I'm just using root explorer. Select the file, uncheck the "write" option, close root explorer. Open sensor debug or whatever, check the file, untouched.
Click to expand...
Click to collapse
I am doing the same but it becomes writable again. Must be because of different sensors.xxx.so file and build or maybe because you are trying with a wallpaper and not an app.
BTW editing the file on windows pc may not work because of paragraphing difference between windows and linux. If this happens, my phone just adds new zero values to the end of the file.
I am dying to reproduce the fix. I will test with some different builds. That constant file updating is killing me.
This ROM is working very well on my UK Rhod 100. Very stable & fast and since the latest update I have the correct HW keyboard layout. Battery life is limited but carrying a second battery is an easy solution.
The previous problems where the screen would not turn on after several pushes of the power button almost never occurs. However when the battery runs down to about 30% the screen always changes such that a red overlay occurs visible mainly on screens with a white background (see pics). Also when the screen changes ghost images remain from previous screens. Also at this point sometimes the screen will not turn on despite repeated use of the power button. Strangley, even though there is nothing visible on the screen I can unlock the phone by swiping in the expected area (and get haptic feedback) and long press the power button and turn off the device by pressing in the expected areas. Upon a reboot the screen will initially be back to normal but then if the battery is below 30% the problem will return. These issues never occur if the battery is above 30%. If I take screenshots with shootme the pics captured look normal when viewed after a reboot before the problem recurs. Not sure what the system does when the battery falls to this level but the screen is definitely affected. This problem also occurs with a fresh install with no apps installed.
If anyone has any ideas as to what could be the cause (and even better a solution) it would be most welcome. Thanks to all those behind this project.
Sorry you are having troubles. Unfortunately as noted in the first post for that thread we only have RHOD400s to test with. No one else has reported any similar issues. The 100s are known to be the problem children of the RHOD family. If you come up with a fix let us know, and we will try to include it in any future releases.
wizardknight said:
Sorry you are having troubles. Unfortunately as noted in the first post for that thread we only have RHOD400s to test with. No one else has reported any similar issues. The 100s are known to be the problem children of the RHOD family. If you come up with a fix let us know, and we will try to include it in any future releases.
Click to expand...
Click to collapse
Did you look at ACL's work on RE'ing that panel code...?
He said something about the panel power up/power down sequence on the 100's (the AUO panel specifically) to be quite a bit different.
arrrghhh said:
Did you look at ACL's work on RE'ing that panel code...?
He said something about the panel power up/power down sequence on the 100's (the AUO panel specifically) to be quite a bit different.
Click to expand...
Click to collapse
arrrghhh, I noted your post in the ROM development thread regarding the start up sequence in the OMGB kernel for the AUO panel. Perhaps this would solve my issue as well. If this change could be added to the next edition of this ROM my device would be virtually bug free.
As noted in the thread, we do not have any RHOD100s to test with. It is very unlikely that this will happen. If you would like to make your own kernel with these changes I can post it.
issue or not?
hi,
thanks a lot, first of all.
I've been trying to figure out how to get an Italian keyboard layout.
any suggestion?
-p.
paolora999 said:
hi,
thanks a lot, first of all.
I've been trying to figure out how to get an Italian keyboard layout.
any suggestion?
-p.
Click to expand...
Click to collapse
try using AItype Keyboard Plus which supports multiple languages and keyboard layouts
Sorry I didn't express myself properly. I meant the physical keyboard. In other thread I read something about a startup.txt file, I don't know if it applies to this ROM (and moreover I can't find it).
paolora999 said:
Sorry I didn't express myself properly. I meant the physical keyboard. In other thread I read something about a startup.txt file, I don't know if it applies to this ROM (and moreover I can't find it).
Click to expand...
Click to collapse
startup.txt files are only for the SD card versions of the android roms.
You would need to edit the keyboard map. Here is generic android keyboard map info.
There may be apps out there than can change your keyboard map, but I don't know any details about that.
Also in the future it would be best to start your own thread, rather than using an unrelated one. Better yet, post the questions about the rom you are working with in the thread for that rom.
i am having also a screen problem with that Rom and Kernel:
My screen is not calibrated. When i press it's being pressed on somewhere else on the screen.
P.S.
My RAM is not 100 +- this rom showing me 33 for usage on the device :S.
Can someone help me with those two ?
MTN_Cool said:
i am having also a screen problem with that Rom and Kernel:
My screen is not calibrated. When i press it's being pressed on somewhere else on the screen.
P.S.
My RAM is not 100 +- this rom showing me 33 for usage on the device :S.
Can someone help me with those two ?
Click to expand...
Click to collapse
Did you read the link that covered screen calibration listed under related goodies, or did you search for the threads that cover screen calibration under android? Tell us what you have tried, but didn't work.
No idea what you mean by the ram is not 100.
What the heck is going on here? Is this just the thread to jack?
Let's focus on the display issues please folks, as in your response should be related to the original post.
arrrghhh said:
What the heck is going on here? Is this just the thread to jack?
Let's focus on the display issues please folks, as in your response should be related to the original post.
Click to expand...
Click to collapse
idc if they will move my question the the original one...
but i can't fix my calebration points...every time i need to launch the HTC program :\
Problem resolved?
akk29 said:
This ROM is working very well on my UK Rhod 100. Very stable & fast and since the latest update I have the correct HW keyboard layout. Battery life is limited but carrying a second battery is an easy solution.
The previous problems where the screen would not turn on after several pushes of the power button almost never occurs. However when the battery runs down to about 30% the screen always changes such that a red overlay occurs visible mainly on screens with a white background (see pics). Also when the screen changes ghost images remain from previous screens. Also at this point sometimes the screen will not turn on despite repeated use of the power button. Strangley, even though there is nothing visible on the screen I can unlock the phone by swiping in the expected area (and get haptic feedback) and long press the power button and turn off the device by pressing in the expected areas. Upon a reboot the screen will initially be back to normal but then if the battery is below 30% the problem will return. These issues never occur if the battery is above 30%. If I take screenshots with shootme the pics captured look normal when viewed after a reboot before the problem recurs. Not sure what the system does when the battery falls to this level but the screen is definitely affected. This problem also occurs with a fresh install with no apps installed.
If anyone has any ideas as to what could be the cause (and even better a solution) it would be most welcome. Thanks to all those behind this project.
Click to expand...
Click to collapse
In an attempt to bring this thread back on topic I thought I'd report back that the original problem has not happened for a few weeks. My setup is essentially unchanged, the only change is that I have been using One Power Guard to try and improve battery life, which by the way seems to be effective. Managed 13hours with light use (few calls/occassional data for email web browsing)
Anyway it could be coincidence but it is possible that one of the tweaks performed by the app has sorted this issue. Since nobody else has reported the same problem I'm not sure how useful this info is but hopefully it may be of use to someone.