Related
In case you missed this from the Opera 9.5 Build 1957 thread, build 2392 is available from the link below.
http://forum.xda-developers.com/showthread.php?t=401643
This one has the zoom button in the lower left, which I've found is a bit annoying using the VGA buttons on 96 dpi - a lot of screen area is taken up by the two buttons (zoom and the menu button on the lower right). I might try the QVGA buttons to see if that works better, but then I'll loose easy non-stylus access. The zoom function itself is VERY nice, much better than the double-tap with a fixed zoom setting.
This one feels very stable, it hasn't crashed on me, unlike 1957 which crashed all the time even with few tabs and a low cache.
Unfortunately, the screen orientation problem is back and the can't-use-the-keyboard-to-enter-a-web-address problem is also back (both were fixed on 1957 and have been problems since 1409).
Some people are reporting success with Flash Lite 3.1 and this build, but I'm on AP4 and still can't get Flash to run. Some think its due to the older Flash Lite 2.1 being cooked in.
However, the advangates so far are better than the 2 problems, so I'm going to keep this one for now.
1184 is still the best version. 2392 has too many problem still.
Funny that the more they 'improve', the worst it becomes.
edit: sorry, I got mixed up between 2392 and another version.
Yes, I have to agree that this version is really good. Better than 1184.
this build is really good, better than 1957 and 2123, I use portrait mode all the time,so opera switching to portrait mode on exit doesn't bother me, plus i can't tell the last time i used the hardware keyboard to type, so the address thing don't bother me at all. i use TouchPal as my keyboard all the way. this is well improved, even though there's a lot left to be done, its still a good build.
Also, flash3.1 works with this build on Michyprima's rom, the thing is flash3.1 has to be installed first then opera after, soft reset and it's good to go.
1957 v. wins
For me 1957 version is the best. Before, I used 1184, but since 1957 was released, I am on this version and I like it.
1. It works with no crushes, at least for me.
2. Flash 3.1 works for YouTube(original x7510 rom).
3. No problems with keyboard and screen rotation.
4. Zoom works not only by double-click, but also with zoom scale in top right corner, which appears if you slide your finger there. More, text wrap works as well with this zoom.
Tadeusz said:
For me 1957 version is the best. Before, I used 1184, but since 1957 was released, I am on this version and I like it.
1. It works with no crushes, at least for me.
2. Flash 3.1 works for YouTube(original x7510 rom).
3. No problems with keyboard and screen rotation.
4. Zoom works not only by double-click, but also with zoom scale in top right corner, which appears if you slide your finger there. More, text wrap works as well with this zoom.
Click to expand...
Click to collapse
Can you point me to where your 1957 comes from? My 1957 does not have the zoom at the top right corner.
It also no longer gives me the ability to activate links in zoom out mode. In addition, the text overlaps unless small fonts are used (I use medium size font so 1957 version can't support that correctly). The display is also blurrly in zoom out mode.
I was confused and mistakenly believe this was another version that I've tried.
Yes, I have to agree that this version is the best ever version to date.
- Tengo types smoothly, unlike most versions where Tengo behaves wierdly.
- display at all zoom level are clear, unlike many versions, where displays are distorted at zoom out mode.
- texts flow correctly, or rather reflow correctly. Unlike some versions, where reflow does not take place at all.
- able to change minimum overview zoom to 85 so that links could be activated without zoom in.
- variable zoom bar works flawlessly.
- Connection is quick with minimal pause
- youtube works nicely.
- pictures are sized correctly, unlike some versions where the pictures are oversized.
The screen orientation issue has never bothered me.
Keyboard pop up issue is only a minor annoyance.
Only issu so far is that it is unable to download files. The usual download bar does not appear, so download seems to be happening in the background. Also, only part of the file is downloaded. Any idea?
eaglesteve said:
I was confused and mistakenly believe this was another version that I've tried.
Yes, I have to agree that this version is the best ever version to date.
- Tengo types smoothly, unlike most versions where Tengo behaves wierdly.
- display at all zoom level are clear, unlike many versions, where displays are distorted at zoom out mode.
- texts flow correctly, or rather reflow correctly. Unlike some versions, where reflow does not take place at all.
- able to change minimum overview zoom to 85 so that links could be activated without zoom in.
- variable zoom bar works flawlessly.
- Connection is quick with minimal pause
- youtube works nicely.
- pictures are sized correctly, unlike some versions where the pictures are oversized.
The screen orientation issue has never bothered me.
Keyboard pop up issue is only a minor annoyance.
Only issu so far is that it is unable to download files. The usual download bar does not appear, so download seems to be happening in the background. Also, only part of the file is downloaded. Any idea?
Click to expand...
Click to collapse
I would guess you're talking about build 2392, Downloads show up in the downloads manager, I've been downloading with it all morning so I know.
In config I also set image to 4 instead of the default 3, this seems to give better image clarity.
I also set update delay to 0 instread of the default 2000.
I also set tabs to 8, I don't need any more tabs than that at any 1 time
those are a couple of my default tweaks when I install.
lennie said:
I would guess you're talking about build 2392, Downloads show up in the downloads manager, I've been downloading with it all morning so I know.
In config I also set image to 4 instead of the default 3, this seems to give better image clarity.
I also set update delay to 0 instread of the default 2000.
I also set tabs to 8, I don't need any more tabs than that at any 1 time
those are a couple of my default tweaks when I install.
Click to expand...
Click to collapse
Yes, was talking about 2392.
My download manager definitely does not appear. Tried it so many times already. The files does get downloaded though, even if not always completed. Did you perform any tweak to make this happen because I can't get it to appear.
I can't seem to detect any differece after setting image to 4. Do you can a website that illustrates its impact?
Do you mean INITIAL update delay? I'm still trying to figure out what difference this would make.
eaglesteve said:
Yes, was talking about 2392.
My download manager definitely does not appear. Tried it so many times already. The files does get downloaded though, even if not always completed. Did you perform any tweak to make this happen because I can't get it to appear.
I can't seem to detect any differece after setting image to 4. Do you can a website that illustrates its impact?
Do you mean INITIAL update delay? I'm still trying to figure out what difference this would make.
Click to expand...
Click to collapse
the version I have is the one for main memory (I always have programs with the SD version)
its weird that it doesn't show up....what I can say is to uninstall it and delete the opera folder after uninstall, then reinstall, check if you get the download manager (I don't have flash3.1 installed so maybe thats causing the problem). I do remember on a build I wasn't getting the download manager I don't know which it was, I think it was 2123.
In User Prefs there's two update delay
in the quick search box type in delay and both will show up.
"First Update Delay" to 0
and then "update Delay" to 0
lennie said:
the version I have is the one for main memory (I always have programs with the SD version)
its weird that it doesn't show up....what I can say is to uninstall it and delete the opera folder after uninstall, then reinstall, check if you get the download manager (I don't have flash3.1 installed so maybe thats causing the problem). I do remember on a build I wasn't getting the download manager I don't know which it was, I think it was 2123.
In User Prefs there's two update delay
in the quick search box type in delay and both will show up.
"First Update Delay" to 0
and then "update Delay" to 0
Click to expand...
Click to collapse
Yes, uninstall and reinstall brings back the download manager. Thanks for the suggestion, Lennie.
eaglesteve said:
Yes, uninstall and reinstall brings back the download manager. Thanks for the suggestion, Lennie.
Click to expand...
Click to collapse
I'm glad to hear that it worked
lennie said:
I'm glad to hear that it worked
Click to expand...
Click to collapse
I can't get it to work, any suggestions ??
Here is what I did :-
1.) from your previous posts found that you are using SD version so downloaded it and downloaded flash lite3.1 cabs.
2.) installed flashlite 3.1 , reboot.
3.) installed opera SD , reboot.
now when i start opera, its splash screen opens , progress bar gets stuck at the initial 5-10% position and opera doesn't opens,
i tried reinstalling, both in micro drive, device same problem, any advices ??
paranoid1288 said:
I can't get it to work, any suggestions ??
Here is what I did :-
1.) from your previous posts found that you are using SD version so downloaded it and downloaded flash lite3.1 cabs.
2.) installed flashlite 3.1 , reboot.
3.) installed opera SD , reboot.
now when i start opera, its splash screen opens , progress bar gets stuck at the initial 5-10% position and opera doesn't opens,
i tried reinstalling, both in micro drive, device same problem, any advices ??
Click to expand...
Click to collapse
I install both on device memory. These are some of the very few programs that I don't install on my microdrive.
eaglesteve said:
I install both on device memory. These are some of the very few programs that I don't install on my microdrive.
Click to expand...
Click to collapse
I also installed both on the device, and it didn't worked
EDIT : NON SD version worked
I'll have to try uninstalling and reinstalling with Flash lite 3.1 first, then Opera. Installed it the other way around.
techntrek said:
I'll have to try uninstalling and reinstalling with Flash lite 3.1 first, then Opera. Installed it the other way around.
Click to expand...
Click to collapse
yes you have to install flash first to get it to work with opera properly. and I've always had problems with SD version, if it's not being able to enter passwords its me not able to post here on xda, and a whole lot more problems and i stick to the device version.
[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.
ok here is the problem my screen wont rotate did a soft and hard reset and all only time it switches view are when i'am in the andriod market ,netflix and so forth ,but at the home screen everything is the long way now it cool when iam reading my book or my comic books and i think i can deal with it but i do like it when its the other way too any help with this problem would be great
Did you check settings, screen and auto rotate?
Or did you lock your screen with a setting in one of the launchers?
And how did you get your market and Netflix to rotate? Mine doesn't.
Sent from xda premium app
What ROM are you running?
phillytye215 said:
ok here is the problem my screen wont rotate did a soft and hard reset and all only time it switches view are when i'am in the andriod market ,netflix and so forth ,but at the home screen everything is the long way now it cool when iam reading my book or my comic books and i think i can deal with it but i do like it when its the other way too any help with this problem would be great
Click to expand...
Click to collapse
You need to be a bit more informative about the problem brother. Things like what model do you have( wifi only, 4G...) are you running a stock unrooted Tab or are you rooted and running a custom rom, if so which rom and are you using the stock launcher or a 3rd party one??? It'll help us to figure out what's going on.
Now after rereading your post a few times this is what I'm understanding. When you say "long ways" I'm assuming you mean portrait... right? That would mean that your Tab is stuck in portrait (longer from top to bottom and shorter from side to side) and the only time it jumps to landscape is when you go to Apps that are written to automatically switch to landscape when opened, like the Market and Netflix. You also say that you've done a soft rest (meaning completely powered off your Tab) and did a hard rest (meaning you did a factory rest) am I right so far???
If I'm on the right track with what I've posted above and this is assuming that your running a stock unrooted Tab and the stock TW launcher you could very well have a bad accelerometer. That's the sensor in side of our Tabs that tell it how your holding it. If you did a factory rest (hardrest) then that should have reset your Tab it exactly how it was when you took it out of the box. And auto rotation would be set on by default.
Go to settings> screen> and make sure you have "auto rotate screen" checked.
Hit us back with some more info so we can try and help out a bit more.
Sent from my Galaxy10.1 TouchWiz/ADWex equipped Starship.
So far your right on...
Hey SouthPhilly...
I noticed this thread suddenly stopped.
I am having the exact same issue, and have done a reset to factory on my device and the screen still does not rotate unless forced to by an app.
Just wondering if you were going to launch in to a possible solution.
thanks.
CaptivateRookie said:
Hey SouthPhilly...
I noticed this thread suddenly stopped.
I am having the exact same issue, and have done a reset to factory on my device and the screen still does not rotate unless forced to by an app.
Just wondering if you were going to launch in to a possible solution.
thanks.
Click to expand...
Click to collapse
I'm wondering the same thing here. I have the same issue with my GTab 7510..bleh!
wipe cache.
sometimes it works
To the people of Turl's and Jokersax' CM9.
I have a touchscreen re-calibration app, I just tested it out and it seems to be working perfect. Don't hold me to it, but i think this is a pretty good temporary fix.
I'd love feedback, i didn't code this but after a few searches i was able to realize this is a universal fix for touchscreens that have been acting up.
Special thanks to gojimi. At least i hope.
Can you link the source please.
Cheers!
Just a question, do we actually need touch calibration after flashing cm9? Cause AFAIK, when I tried the jokersax rom, the only problem I had was app incompatibility and APN errors...
helmy96 said:
Just a question, do we actually need touch calibration after flashing cm9? Cause AFAIK, when I tried the jokersax rom, the only problem I had was app incompatibility and APN errors...
Click to expand...
Click to collapse
Sometimes, it will act up.
Ouh. Ok, didn't think it would happen... hope u don't think n
that I a newb thru this question, I'm well informed, just not very active due to sch...
helmy96 said:
Ouh. Ok, didn't think it would happen... hope u don't think n
that I a newb thru this question, I'm well informed, just not very active due to sch...
Click to expand...
Click to collapse
I know what you mean, sometimes homework takes away most of my time too. But just use CM9 as your daily driver, and you'll be well informed on any issues that will occur.
This actually screwed up my touchscreen..anyway to uninstall?
Hi,
I have a software issue with my touchscreen :
1/ Got stock ROM, then CM7, then CM7-Neutrino-2.2 => screen was OK
2/ Installed CM9-Turl-v8 => an unresponsive horizontal line appeared, around 100px high
3/ Tried to come back to CM7, CM7-Neutrino, CM9-Joker-0.4 => bug still there
4/ Tried this calibration app, but couldn't click the button because it was under the unresponsive line, so turned the phone into landscape or upside-down to execute => bug still there
5/ Flashed PDS fix => bug still there, fear of a hardware issue
6/ Installed CM9-Joker-0.5 with awesome Installer => touch screen goes totally crazy (phantom-touches), BUT the line is finally responsive !! So, le wild idea appears
7/ Retried this calibration app, this time in the right way => SCREEN FINALLY OK !!!...
8/ ... For about 2 hours... Now my phone combines 2 issues : a new horizontal line is unresponsive (thinner than the old one), and crazy phantom-touches happen really often...
I was desperate, but now I know my problem is software, I see hope ! Am I the only one to have this problem ?
Thank you in advance
David Guillot said:
Hi,
I have a software issue with my touchscreen :
1/ Got stock ROM, then CM7, then CM7-Neutrino-2.2 => screen was OK
2/ Installed CM9-Turl-v8 => an unresponsive horizontal line appeared, around 100px high
3/ Tried to come back to CM7, CM7-Neutrino, CM9-Joker-0.4 => bug still there
4/ Tried this calibration app, but couldn't click the button because it was under the unresponsive line, so turned the phone into landscape or upside-down to execute => bug still there
5/ Flashed PDS fix => bug still there, fear of a hardware issue
6/ Installed CM9-Joker-0.5 with awesome Installer => touch screen goes totally crazy (phantom-touches), BUT the line is finally responsive !! So, le wild idea appears
7/ Retried this calibration app, this time in the right way => SCREEN FINALLY OK !!!...
8/ ... For about 2 hours... Now my phone combines 2 issues : a new horizontal line is unresponsive (thinner than the old one), and crazy phantom-touches happen really often...
I was desperate, but now I know my problem is software, I see hope ! Am I the only one to have this problem ?
Thank you in advance
Click to expand...
Click to collapse
You are not the one who have this problem I had nottachtrix at first and touchscreen was working well when I instal MIUI 2.4.27 from there started my problem now my buttons sometime stop working when I bloc and then unblock phone buttons start working sometime it need restart phone I didn't try this ap yet but I think it's software because when buttons stop working my touchscreen is working full only buttons are not responsive is there some fix pleas PM me
After using nottachtrix arora installer to calibrate my touch would have random deadzones and w,e,s,z didnt work. Tried recalibrating with installer to only make it randomly worse or slightly better. This did the trick thoough. Thanks very much!!
help me
i was used gingermod rom and change to aokp milestone 6 suddenly yesterday seen that there are area in screen didnt work i have tryied to back to gingermod still not work try this software but also didnt work what i have to do please help me
hi help me
hi help me
i have one tablet eken w70 wiht the touch invsted help me
this touchRecelibrete not succes
help me
[email protected]
Can you please give us the correct way for Re calibration
Sent from my MB860 using xda app-developers app
i'll try it, my screen not responding now
...yes I STILL use the Lapdock
Anyway, after I remove my phone from the Lapdock it freezes and goes crazy for a few seconds as usual, but this time as well as others it seems to have left the wallpaper in a landscape orientation, even when I turn my phone upright for protrait orientation.
Have a look:
http://i.imgur.com/nbCcBtA.png
http://i.imgur.com/RjZsXsk.png
What is especially wierd is what you see on the second .png when I try to change the wallpaper to see if that does anything, the selector square has turned into a rectangle as if the phone was still on landscape. The icons, widgets and all else do rotate, just not the wallpaper. I am left with no other options as the settings for wallpaper on stock 2.3.6 leaves me only the option to change the backgroind image and it seems that I am the only one on the interwebs that is posting this issue.
The ROM and kernel is stock, I am using ADW Launcher but I am certain that that is not the culprit, I removed it but the problem persisted. I am also using Ubuntop 1.1 something or other but I doubt that is a culprit either.
Any ideas? Thanks so much in advance.
mynameisj said:
...yes I STILL use the Lapdock
Anyway, after I remove my phone from the Lapdock it freezes and goes crazy for a few seconds as usual, but this time as well as others it seems to have left the wallpaper in a landscape orientation, even when I turn my phone upright for protrait orientation.
Have a look:
http://i.imgur.com/nbCcBtA.png
http://i.imgur.com/RjZsXsk.png
What is especially wierd is what you see on the second .png when I try to change the wallpaper to see if that does anything, the selector square has turned into a rectangle as if the phone was still on landscape. The icons, widgets and all else do rotate, just not the wallpaper. I am left with no other options as the settings for wallpaper on stock 2.3.6 leaves me only the option to change the backgroind image and it seems that I am the only one on the interwebs that is posting this issue.
The ROM and kernel is stock, I am using ADW Launcher but I am certain that that is not the culprit, I removed it but the problem persisted. I am also using Ubuntop 1.1 something or other but I doubt that is a culprit either.
Any ideas? Thanks so much in advance.
Click to expand...
Click to collapse
What happens after a battery pull?
Are you able to access recovery with the stock rom? just thinking about a dalvik wipe or a data wipe/factory reset? (maybe some bits of software not acting properly and a reset might help)
I don't have any experience with the Lapdock but maybe it is a software glitch?
barry_ said:
What happens after a battery pull?
Are you able to access recovery with the stock rom? just thinking about a dalvik wipe or a data wipe/factory reset? (maybe some bits of software not acting properly and a reset might help)
I don't have any experience with the Lapdock but maybe it is a software glitch?
Click to expand...
Click to collapse
The problem persists after a battery pull and re-insertion. Since it wasn't the VERY first thing I did, recovering the img of the current rom didn't work as the problem occurred BEFORE I saved a backup, although the problem DOES go away when do a from-scratch recovery using a fruitcake system/kernel/webtop img.
So would wiping the Dalvik cache not mess up my setup or anything? I may consider doing that as I'm not looking forward to doing a clean wipe every time this problem happens, and it happens VERY easily.
Thanks
Wiping Dalvik won't change any settings or cause any problems and it might help.
I am still thinking that your problem is a software glitch - one workaround might be to fix the wallpaper in the 'horizontal' position by unticking the 'auto-rotate' setting (not sure if this would effect your lapdock experience though )
One last workaround would be to reinstall your Rom without a data wipe (so all your settings/apps are still there) and see if that helps.
barry_ said:
Wiping Dalvik won't change any settings or cause any problems and it might help.
I am still thinking that your problem is a software glitch - one workaround might be to fix the wallpaper in the 'horizontal' position by unticking the 'auto-rotate' setting (not sure if this would effect your lapdock experience though )
One last workaround would be to reinstall your Rom without a data wipe (so all your settings/apps are still there) and see if that helps.
Click to expand...
Click to collapse
Dalvik cache is wiped and the wallpaper orientation option was ticked and un ticked but the problem STILL remains. I suppose my next step is to re-flash the ROM, but I'm hoping that doing so won't wipe and restore webtop to stock (it's on Ubuntop instead).
Here's another kicker! I don't have this problem on LIVE wallpapers, orientation works just fine there, only on static wallpapers am I seeing this issue.
Anyway, I've looked into debugging the display on the native OS to try to a fix together, I'll see how that goes...
How do other apps behave? Also stuck on landscape or not?
I'm thinking it could be a launcher issue after all if that's the only place where this is happening.
ravilov said:
How do other apps behave? Also stuck on landscape or not?
I'm thinking it could be a launcher issue after all if that's the only place where this is happening.
Click to expand...
Click to collapse
Thanks for the feedback,
The behavior of the other apps are good, no issue with them whatsoever.
I have already uninstalled ADW launcher and stayed stock for a few hours and that didn't resolve the issue. I shall do it agin but this time reman in stock for longer.
I got the launcher BECAUSE the stock home screen doesn't rotate and I prefer to mount my phone sideways in my car. What is baffling is that it DOES go to landscape orientation when I plug the phone onto the Lapdock. Weird.
I was wondering if anybody else had this problem but the more I search the more I find that I may be the only one with the isssue, thus I'm thinking it can be due to my personal phone setup rather than a glitch. If I DO find a fix, I'll put it up nonetheless...
I have the exact same issue with Atrix 4G and ADW launcher
I have the exact issue you described and I did the same but ni good results so far. The only difference is that i was using the multimedia dock instead of the laptop dock (which I was thinking to buy). I just got the phone yesterday and the dock today and when testing for the 1st time i got the wallpaper wrongly oriented.. any help?
I installed after that the wallpaper wizardii app to see if it could fix it but no luck..
Thanks a lot.
Elomx said:
I have the exact issue you described and I did the same but ni good results so far. The only difference is that i was using the multimedia dock instead of the laptop dock (which I was thinking to buy). I just got the phone yesterday and the dock today and when testing for the 1st time i got the wallpaper wrongly oriented.. any help?
I installed after that the wallpaper wizardii app to see if it could fix it but no luck..
Thanks a lot.
Click to expand...
Click to collapse
Buggy wallpaper configuration. Try this, it might help.
- Install GO Launcher EX and set your wallpaper.
- Every time after undock the phone, press menu > wallpaper > press lock and and unlock for few times.
It work for me.
Just to chip in that I had the same (or very similar) problem: Nottachtrix ROM, ADW Launcher, multimedia dock. Swapping out the launcher to GO Launcher EX per AeroMiku's suggestion has worked for me ... for the moment!