Related
i saw a post about ringer delay for AT&T user and they just need to disable the dialer and the problem solve but what about us sprint users? Here is the original post about that http://forum.xda-developers.com/showthread.php?t=449417
i tried to disable the dialer on registry but still get 2-3 second delay before my Touch Pro actually ring.
Download and install DiamondTweaks. There is an option to disable the ringer delay. Works well.
convert your ringer to .wav file
temperamentalman said:
Download and install DiamondTweaks. There is an option to disable the ringer delay. Works well.
Click to expand...
Click to collapse
The ringer delay that this changes is the pause between when the ringtone ends and it repeats. Not the delay from when the LED starts flashing (because a call arrived) till the phone actually starts ringing.
If you wish to turn off the HTC dialer and use the WM Dialer, simply goto the following registry entry,
[HKEY_LOCAL_MACHINE/Security/Phone/Skin]
"Enabled" = dword:1change the Enabled value from 1 to 0 which will disable the HTC dialer.
I vote for converting to WAV files as well.
If you would like to complain to Sprint about it, the following is the thread I started on Sprint's forum regarding this very subject.
http://forums.buzzaboutwireless.com/baw/board/message?board.id=SmartPhones&thread.id=5304
Thanks smotrs...
Know anyway to get the light sensor to turn off the screen when on a call (Sprint) other than S2U2?
temperamentalman said:
Thanks smotrs...
Know anyway to get the light sensor to turn off the screen when on a call (Sprint) other than S2U2?
Click to expand...
Click to collapse
Depends on what you may have done (adding programs, etc..) to your phone. By default, our devices will turn the screen off to conserve battery while a call is in session. However, if you have added one of the S2A dialer GSM versions which was taken from the Touch HD, that feature was disabled because of the InCall curtain. The CDMA versions (my signature and others) were taken from the Sprint Diamond ROM that was released and still contains the necessary code to turn off the screen display while the call is in progress.
Smotrs...just HR'd and installing now. I haven't tried that one, and actually think I ended up with the GSM version I WAS using.
I'll let you know how it works.
Thanks...
Well, it still sits there while the screen "times" out. I thought the light sensor was supposed to dim the screen almost immediately. I'm on the call for 30-40 seconds before it dims, and then cuts off.
Is this a Sprint thing?
temperamentalman said:
Well, it still sits there while the screen "times" out. I thought the light sensor was supposed to dim the screen almost immediately. I'm on the call for 30-40 seconds before it dims, and then cuts off.
Is this a Sprint thing?
Click to expand...
Click to collapse
It should Dim after about 10 seconds (or whatever you have in the backlight Advanced setting under Battery). After about 40 seconds or so (same location) it should turn off the screen.
At least that's what mine does, just verified it again. Sounds like maybe your values are too high. After a HR they usually are by default.
Somehow it was at 30 (dim) and 1 min (off). That is a little high. Changed it to 10 / 40. We'll see what that does.
Thanks for the tip. I'll keep you posted.
Seems to now be working the way you explained!!! Thank you for the help!
Is there anything else out there, other than S2U2 that allow FULL SCREEN Caller ID pictures??? I don't want to reinstall that because the dialer is actually working right. I just miss full screen caller ID.
Thanks again.
That I don't know, sorry.
Eh...it's ok. I'd much rather have a dialer that works than a full screen picture of my ignorant brother.
you can also change the Slot Cycle Index in the epst settings... you'll need your MSL though
it's under "Modem Settings"
What is slot cycle and where are these settings? How do I find my MSL? I don't see "Modem Settings".
not trying to be an ass, but i suggest you do some searching. there is plenty of info on the subject
check out this thread - http://forum.ppcgeeks.com/showthread.php?t=48775&highlight=epst+poll
or here - http://forum.ppcgeeks.com/showpost.php?p=625185&postcount=14
and here - http://forum.ppcgeeks.com/showthread.php?t=42730&highlight=epst+poll
I don't think you are an ass...I'm thinking thanks for the threads!
I know search is my friend LOL
lol, no prob man...
Changed the SCI to 1. We'll see if that helps. There is always "0"!
I'm also seeing mixed reports/opinions on ACCOLC - Access Overload Class. Mine was defaulted at 8 on Sprint. People say leave it alone. People say set it lower. Others say set it higher.
i found that setting SCI to 1 is good enough, i'm able to catch my calls and haven't noticed decreased battery life from it so that's where mine stays.
I've put this in the Development section because whilst it is almost fully functional, it still needs a lot of development. Please be aware of this when you download it. I am not to be held responsible for anything that may happen as a result of running this app.
Requirements:
Root Access & a Custom ROM (StreakDroid 1.8.0 recommended (CONFIRMED WORKING ON 1.8.0))
Built under a 2.2 framework. If you are running anything pre-2.2 please be aware it may not work.
Please remember to remove all previous versions of the app before installing.
Simply open the app and press the "Menu" button. I hope you can figure the rest out! Enjoy!
"LED Notification FREE" has been uploaded in the Market. It has full functionality and it Ad Supported.
Please be aware that this version includes an "AdBlocker Check". This will block the app from opening if you have an adblocker installed on your phone. Sorry about this but i hate adblockers Alternatively, you can just remove all instances of Admob from your Hosts file.
Code:
[I][B][COLOR="blue"]QUICK HANDCENT FIX[/COLOR][/B]:
Open Handcent, press 'Menu > Settings > Notification settings > Popup settings'.
[B]MAKE SURE[/B] 'Screen on for popup' is [B]UNCHECKED[/B].
Handcent wont interfere with my app from then on :D[/I]
NEW TO 2.0.1
Asks for SU Access when the app first loads Fixes some weird error that happens every now and again.
Completely re-coded the SMS receiver. Much smoother now!
SMS and Gmail Notifications can be turned on or off
New settings page - done properly now, wont save anything to sdcard [you can delete your STREAKLED folder now!] Press the 'menu' button when you open the app for settings.
Permissions tweaked (should be less LED problems)
KNOWN BUGS
Changing orientation during the pattern causes problems. Just don't do it!
Notifications overwrite each other. So if an SMS message arrives and then a Gmail, only the Menu button will be lit, and vice versa.
Services cannot be stopped (only by uninstalling) FIXED - 2.0
Sometimes all the buttons will end up being lit, not sure why. [SHOULD BE FIXED]
TODO
Add options for turning the SMS and Gmail notifications on and off DONE - 2.0
Have different patterns for each DONE - 1.3
Improve the UI (sort of) DONE - 2.0
Improve the pattern flashing sequence (sort of) DONE - 2.0
Clean up the code (WIP )DONE - 2.0
Fix orientation issue
This will ALWAYS be available for free on here, on Modaco and on my website (see sig) but i have uploaded a 'donate' version on the Android Market Place priced at £1.50, just incase you fancy buying me a beer
Enjoy
Meltus said:
I've put this in the Development section because it is not fully functional and still needs a lot of development. This is basically a proof of concept app.
Requirements: Root Access (tested on 2.1 but build under a 1.6 framework so it should work on 1.6)
All you have to do is run the application, hit the home button and receive a text (or send yourself one). If your phone is locked it will wake up and dim the screen and flash the home/menu/back LEDs in a nice pattern and then keep the screen dimmed until you unlock the phone manually.
The only problem is that you will receive a Force Close error message and you will then have the re-open the app for it to work again. I am trying to fix this but will not be able to look into it for a few days so i thought i would release what i've done so far.
I will be adding settings and more patterns as soon as i can fix this FC error.
Enjoy
Click to expand...
Click to collapse
Well... GREAT!!! Thanks! It works... Was searching this kind of app for weeks. Thanks again!
Great little app. Can't wait for thenext update
Nice work.
Just out of interest though, what's the dangers of having the screen on dim all night if I get a text message at stupid o'clock?
Wouldn't want to burn anything on my screen if that is possible.
Amdathlonuk said:
Nice work.
Just out of interest though, what's the dangers of having the screen on dim all night if I get a text message at stupid o'clock?
Wouldn't want to burn anything on my screen if that is possible.
Click to expand...
Click to collapse
Screen burn is an issue on LCD screens, hence why i set it to do a dim wake lock instead of a full brightness one. Saying that, i have absolutely no idea whether screen burn would still occur but ill test it tonight and report back
On a positive note i have fixed the FC error and will release the fully working version tomorrow!!
Nice work dude ! Look forward to a full release tomorrow.
Any way to make this compatible with non rooted steaks on 1.6?
Sent from my Dell Streak using XDA App
jdmnash said:
Any way to make this compatible with non rooted steaks on 1.6?
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
No, i'm afraid not.
Without Root Access it will probably just force close.
Currently in the process of adding more LED patterns
It also now wakes the phone, unlocks the phone and displays an "SMS Message Received" popup which it then hangs at until you close it.
Do you guys think this is better or should I make it lock the screen instead?
What else should i add/change?
Meltus said:
Do you guys think this is better or should I make it lock the screen instead?
What else should i add/change?
Click to expand...
Click to collapse
I'd prefer it stayed locked, also if I read this thread correctly, it leaves the screen on (but dimmed?) is that true? I would need it to kill the screen, because as noted, it could kill your battery if you went a long time w/o clearing the alert.
Nice work so far though...
a042349 said:
I'd prefer it stayed locked, also if I read this thread correctly, it leaves the screen on (but dimmed?) is that true? I would need it to kill the screen, because as noted, it could kill your battery if you went a long time w/o clearing the alert.
Nice work so far though...
Click to expand...
Click to collapse
Yeah, that's the only problem.
unfortunately, killing the screen freezes the LEDs in whatever state they're in, completely defying the point of the app
What i could do though, is wake up the screen, flash the LEDs but leave one on and turn the screen back off. This would turn everything off apart from that 1 LED and you could use different LEDs for different notifications. I'll try that out later.
Yeah, that seems like a good idea. Maybe the Back LED for missed SMS, the Menu LED for missed call. Something like that.
That would be cool, I'll await your work and give it a try.
Well, it turns out that works miles better than what i was trying before.
Basically, it now turns the screen on, keeps it locked, flashes the LEDs, turns the screen back off and leaves the home LED on.
Give me about 10 mins and i'll put up a working version. No FC error this time
Can't wait for this!
Sent from my Dell Streak using XDA App
First post updated with a working version
None of the options work on the main screen yet, but they will.
Enjoy
I haven't tried this yet, but I just want to say THANKS! No notification light was driving me crazy! I'm gonna install it now. I like that it would kill the screen but leave the LED light on. That's perfect!
**EDIT**
Well, it didn't work perfectly. Here's what happened on my Beta Streak....
With locking disabled (I use the 'NO LOCK' widget), it turned the screen on and said 'SMS received' and the home LED was on, for about 1-2 minutes, then both went off. When I turned back on the screen and read the msg, the LED went out.
With locking enabled, like most people would be using the app, the screen turned on for a few seconds while the LED pulsed, then both went out. No notification. When I unlock and read the msg, the home LED stays on. I have to 'clear' the app in the notification tray and lock then unlock the screen to make the home LED go out.
Seems like they're little tweaks that could be needed. If you can make this work and be functional, I'll donate to your Paypal! Again, thanks for your work on this project!!
Yeah, it's still pretty much in it's 'Alpha' stage
Cheers, for the feedback, i'll look into the errors.
I know that if the screen is unlocked the Home LED will stay on until you lock/unlock the screen, but that should be an easy fix (hopefully), and i've not set up the Thread's quite right i don't think which could be causing the timing errors.
I'll be spending all of tomorrow getting this thing working so i'll report back
Awesome! You are the man!
A thought for down the road development:
Earlier today when I was thinking about this, I imagined an interface where the user could "record" their own flash sequence for each type of notification they had - email, sms, mms, missed call, etc. Just choose which notification they want to specify, click record, then tap the capacitive buttons in the sequence you want them to light up, then end the recording. Interval timing could be recorded or specified manually. Just a few ideas!
Thanks so much for this. I'll give it a run soon.
Awesome work. Wanted something like this. I hope you will be able to add notifications for misssed calls and gmail as well. Keeping my fingers crossed.
[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.
hello,
newbee here. I have acquire a sansung galaxy S2, and have a lot of fun with it.
trouble started when it rebooted at night. I figured out that some update or application crashes were the cause of it.
I think i rid of most of the issues, and got it pretty stable.
To avoid future complication, I even rid of the startup sound, but I can not rid off the vibration (especially the one when shutting down....)
I think it is part of the basic settings, and I did a lot of researches... no luck
Apps like Silent boot would not work either....
Do anyone know if it's even possible ?
If impossible, is ICS having the same issue, or can this be tuned ?
(i just can't believe no one thought of making that optional ...)
Please help me...
I'm on ICS and don't have that. It is part of system settings - sound. It usually is affected by the mode you have your phone set to (like if you have sound set to Sound and Vibrate or just Vibrate, etc). Try changing to just sound and see if that stops it from vibrating (or just silent mode with no vibrate).
Can also try to untick Vibrate on screen tap.
ICS is sweet... can't go back to GB... what you waiting for?!
Sorry, but this does not work (phone is rooted)
. tried vibration off no luck
. tried silent mode no luck
Is there someone who knows where is configured the vibration settings ?
I mean in which filesystem (full path if possible) ... ?
note: Official Samsung ICS for Unlocked Phones will come soon... unless there is a safe ROM and method to install it. For now I would concentrate on my Vibration issue.
Firstly, be patient. People will try to help you, doesn't mean the first answer fixes your problem.
As I stated... ICS does not have this problem. Phone makes no sound and no vibrate, if you set it that way on ICS.
How about give us more information. You said you're rooted but on GB. Are you using any different type of kernel other than stock? Like Siyah 2.xx?
As the filesystem where you can doodle with removing vibrations... I will leave someone with more experience to deal with that (even if I know the path)... in case I advise you something that can screw things up after.
*you might want to reset the phone - as the system notification/vibration settings should have done the trick.
hello
I upgraded to 4 versions of ICS.
Each one of them did not correct the issue : it still vibrate when shutting down the phone. (darkyrom, OCA, Pure and a "4.0.4" version having a clever 3 way option to launch (Nova, TW and Apex)).
I did not reset the settings yet but I will give it a go.
I will the thread updated.
That's a very strange bug then. The settings to control that though, is not with the launchers but with System Settings.
Maybe try this:
System Settings - Volume <inside there you have 4 settings. Try changing System to very low or all the way off. Then go to the whatever mode you have it set to (like Silent Mode or whatever)... and select Mute.
Then the lower categories of System... uncheck all of them: Keytones, Touch sounds, Screen lock sound, Vibrate on screen tap.
See if that works. If it does, then can narrow it down to one of those settings.
Thank you very much
The simplest things are not always obvious to the common....
It works, the vibration disappeared when /SOUNDS/VIBRATION SETTINGS/Vibrate on touch was set to the lowest. Meantime, the little vibration at startup disappeared as well. Now the phone can crash, update and reboot at night without waking me up ! .. a good logcat reader (just in case) running in background will help cleaning up when some error occurs....
Once again, thank you: that drove me mad.
Glad that worked. You're right, sometimes the simplest things are not always obvious, for everyone ;-)
LeFrog1310 said:
Thank you very much
The simplest things are not always obvious to the common....
It works, the vibration disappeared when /SOUNDS/VIBRATION SETTINGS/Vibrate on touch was set to the lowest. Meantime, the little vibration at startup disappeared as well. Now the phone can crash, update and reboot at night without waking me up ! .. a good logcat reader (just in case) running in background will help cleaning up when some error occurs....
Once again, thank you: that drove me mad.
Click to expand...
Click to collapse
I have chinese copy of Nexus One phone, android 2.2.1 and I don`t have VIBRATION SETTINGS tab in my menu, I can only turn vibrate on and off,
and I don`t have SOUNDS on SETINGS, I enter in AUDIO PROFILES to menage vibration,
how to turn off vibration on power on and off?
i got i9100g with cm9.1 stable on it.
there are two problems: after turning the touchkey backlight OFF in advanced settings, they stay off until i reboot my phone. they are turned on again even if the settings still show theyre off. i always have to tick and untick it. if i do that every morning, itll steal time of my life
second "problem" is that after underclocking my device to max 150mhz it rings but doesnt directly show the screen which shows whos calling. means i cant take the call directly. could someone link me a modded or maybe the stock phone.apk? with modded i mean a lite one. maybe without that big dummy pics as i wont ever use pics on my contacts...
Pushpushpush ???
donothurtme said:
i got i9100g with cm9.1 stable on it.
there are two problems: after turning the touchkey backlight OFF in advanced settings, they stay off until i reboot my phone. they are turned on again even if the settings still show theyre off. i always have to tick and untick it. if i do that every morning, itll steal time of my life
second "problem" is that after underclocking my device to max 150mhz it rings but doesnt directly show the screen which shows whos calling. means i cant take the call directly. could someone link me a modded or maybe the stock phone.apk? with modded i mean a lite one. maybe without that big dummy pics as i wont ever use pics on my contacts...
Click to expand...
Click to collapse
do you turn off your phone every night? well, anyway, i guess it's by default when you use CM..
2nd, i don't think its because of the underclocking.. you can check out some mods at the Themes and App section there are lots of mods there and it's hard for me to do it for you