Related
[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 everyone,
First of all, I hope this is the right corner and I've collected enough information - I couldn't find anything closely related to my issue.
Now, I've got the first big problem:
Regarding the support of Tablet devices, some apps just don't offer any possibilty to install them. Now, to avoid this problem, I've changed the LCD density to 240dpi.
The Prime is still able to boot normally and everything is working just fine - except for the Launcher: It crashes every 2 seconds and the buttons on the bottom of the screen are cut away just like the one for the app menu in the upper right section so that I've only reached the settings by some tricks so far.
So far, I own my Prime for roughly 1 1/2 months, my Prime is rooted, NOT unlocked and has the most up-to-date firmware installed on it.
Up to now, I tried to factory reset via settings and wipe data with Volume Down + Power button combo.
Apart from that, I think I heard that the dpi settings are to be found in the build.prop file.
Sorry for letting you read this much, but I think this reduces the overall time to spend on it.
I hope that it's possible to get it back working. I miss the Prime experience
Thanks in advance for any help!
Solved!
So, after some hours, I managed to get the Prime back to life by myself:
The build.prop file was the key to success; With some actions in the ADB-Interface and permission changes, it's possible to revert a bad dpi value to default via USB debugging.
If anyone's further interested, I'll try my best to explain how exactly it's working.
I purchased my SGS3 about 4 months ago from the middle-east.
I have a series of problems (possibly problems cause I am new to Android phones). I am listing them down here in hope that someone will tell me how to solve them.
The flash of blue
This happened once or twice about a month ago. Whenever I pressed the power button to unlock the phone, the complete screen went solid blue for a flash of a second and then I saw the flower on the home screen.
Is this a hardware issue ? Signs of failing hardware ?
The home screen redraw / lag issue
When I press the home button to exit an app, say Chrome, the screen re-draws itself. The icons take some time to show up back on the screen.
Initially I thought it was related to cache being full. However, cleaning it using ES Task Manager was of no help. The re-drawing continues.
I also disabled the SVoice on double-click home button. No
I saw a YouTube video which says that there is a bug fix but it is available only for UK phones.
Here is the video: /watch?v=5uYw3mVhiuY
Again, is it a failing GPU ?
The grainy screen
Title says it all. The screen seems to be grainy. The grains seems to be more visible under low brightness and on grayish backgrounds. I tested the screen using the screen tester that comes with ES Task Manager. When the color goes to whitish-gray, I can see the grains. They are in bands - horizontal and vertical.
Low quality display
This is not related to grainy screen. This is related to the pulling down of notification menu.
I happened to pull it down slowly while goofing around.
I noticed that the quality of the display gradually reduces as I pull it down. When my finger is near the last one-third of the screen, I see that blue color gets split into bands. A little further down, it looks like the background is some very low quality image.
The bit depth seems to be reducing, if that is a proper term.
Low RAM even on idle
Even when I use ES Task Manager to kill the apps, all I usually have remaining is 323 MB of the 800 MB of RAM that is there in the phone.
Why ?
Lag when opening settings
There is also a lag when I open different settings from settings menu.
If I click on the battery settings, there is a visible lag before the actual battery information pop up.
I know that was a lot of rant but being a beginner, I have no clue how to go about solving any of these.
Thanks for reading.
I hope you can help me solve most of these. If not, please let me know if I should return the phone to Samsung.
As for usage, very light use for casual gaming, web browsing, YouTube videos, reading books.
I haven't dropped the phone at all nor have I modded it in any way.
I have tested it using AnTuTu and it gives my phone 16000+ points. Does that indicate phone is fine ?
Basics read first.
http://forum.xda-developers.com/showthread.php?t=2344125
Critical you read the first two posts .
[the reply has been deleted by the OP]
JJEgan said:
Basics read first.
http://forum.xda-developers.com/showthread.php?t=2344125
Critical you read the first two posts .
Click to expand...
Click to collapse
So, sir, you are basically saying that I must root the phone ?
littleandroidkid said:
So, sir, you are basically saying that I must root the phone ?
Click to expand...
Click to collapse
No i am saying read and understand the basics first .as you dont have a clue
Then search for your problems .
Or take the phone to s service centre and let them see multiple problems .
Though your warranty is initially with the seller Samsung warranty is an extra limited warranty .
littleandroidkid said:
I purchased my SGS3 about 4 months ago from the middle-east.
I have a series of problems (possibly problems cause I am new to Android phones). I am listing them down here in hope that someone will tell me how to solve them.
The flash of blue
This happened once or twice about a month ago. Whenever I pressed the power button to unlock the phone, the complete screen went solid blue for a flash of a second and then I saw the flower on the home screen.
Is this a hardware issue ? Signs of failing hardware ?
this happens for everyone no matter what! this just appears randomly and this isn't any problem so far!
The home screen redraw / lag issue
When I press the home button to exit an app, say Chrome, the screen re-draws itself. The icons take some time to show up back on the screen.
Initially I thought it was related to cache being full. However, cleaning it using ES Task Manager was of no help. The re-drawing continues.
I also disabled the SVoice on double-click home button. No
it depends mostly on the background processes! the less they are, the less the lag will be.
I saw a YouTube video which says that there is a bug fix but it is available only for UK phones.
Here is the video: /watch?v=5uYw3mVhiuY
this firmware is way too old buddy! it's 4.0.4! we are already nearer to 4.3! the XXEMG4 and the later firmwares are the latest and there is much less lag when you press the home button like redrawing of apps.
Again, is it a failing GPU ?
The grainy screen
Title says it all. The screen seems to be grainy. The grains seems to be more visible under low brightness and on grayish backgrounds. I tested the screen using the screen tester that comes with ES Task Manager. When the color goes to whitish-gray, I can see the grains. They are in bands - horizontal and vertical.
can't answer this! i have no such problems.
Low quality display
This is not related to grainy screen. This is related to the pulling down of notification menu.
I happened to pull it down slowly while goofing around.
I noticed that the quality of the display gradually reduces as I pull it down. When my finger is near the last one-third of the screen, I see that blue color gets split into bands. A little further down, it looks like the background is some very low quality image.
The bit depth seems to be reducing, if that is a proper term.
this never happened to me and never been reported so far.
Low RAM even on idle
Even when I use ES Task Manager to kill the apps, all I usually have remaining is 323 MB of the 800 MB of RAM that is there in the phone.
Why ?
more free ram? try rooting and use greenify
Lag when opening settings
There is also a lag when I open different settings from settings menu.
If I click on the battery settings, there is a visible lag before the actual battery information pop up.
never happened to me! can't answer this either!
I know that was a lot of rant but being a beginner, I have no clue how to go about solving any of these.
Thanks for reading.
I hope you can help me solve most of these. If not, please let me know if I should return the phone to Samsung.
As for usage, very light use for casual gaming, web browsing, YouTube videos, reading books.
I haven't dropped the phone at all nor have I modded it in any way.
I have tested it using AnTuTu and it gives my phone 16000+ points. Does that indicate phone is fine ?
Click to expand...
Click to collapse
benchmarks vary second to second and they don't mean much.
have a good day :good:
Got the OTA update to L on my 6833. Yes, it has made the already smooth animation slightly smoother but otherwise what is there? The power widgets are gone, I had to install third party Power Toggles app. The new notification swipe down is annoying, having to swipe up when waking device is annoying. The status bar colors are inconsistent. The menus look childish looking.
Without being dramatic, did Sony take all this time to make sure it ran without crashing? Because I notice very few changes (not even improvements, just any changes) on the UI. I must be missing something.
more than that:
can only set one volume at a time.
either portrait or auto, you can't force landscape like in KK.
animations are fluid, but the functionality isn't. My opinion is, if the device has extra power that it can use to make things animate, slide and fade all over the place, better to put that extra power into making the device perform faster. Anyone here who prefers prettier animations instead of faster functionality?
low resolution screenshots in the recents screen. wat. Seriously... wat? Also, the way they've made it it is faster to just go to the apps screen and open whatever app i want, instead of waiting for the recents screen to load and then scroll awkwardly through the programs... Also, you can only see three recent apps. On a device with 6" of screen. three. think about it.
Also... what is the point of having screenshots, anyway? icons are faster, easier to distinguish, take fewer resources and smaller area on screen.
I agree fully on the recent apps screenshots. The blurry images are embarrassing and don't at all go with the clean/sharp theme of everything else. I don't understand why they've made it low res, can't be for performance given no restraint or need anywhere else. Bizarre!
There is over-prettying. For example, the stupid screen swipe up to unlock (after hitting the power button already), the sparkles are just so unnecessary, it is one of the few places the phone actually seems to struggle pulling off the effect.
At the moment my biggest problem is with Yahoo Mail. The account does not seem to auto-sync despite all the settings being correct and even when I force the sync manually the notifications don't show. I've uninstalled and reinstalled, most likely Yahoo to blame, their webmail is always breaking but never ever had a single issue before with KK. This is problematic because it is effectively no longer push email, I have to manually check 50 times a day.
My biggest annoyance is the inability to reclaim the Google search bar area in the Home Screen. I don't want that search button, why can't I use that space, and why a stupid dot to represent the pages of the Homescreen when I only have 1.
Is there actually anything different/new on the backend? My issues aren't severe enough to go back to KK (yet) but seeing what I see, I would have no problem whatsoever buying an Xperia Sony will not upgrade beyond KK.
jess91 said:
Got the OTA update to L on my 6833. Yes, it has made the already smooth animation slightly smoother but otherwise what is there? The power widgets are gone, I had to install third party Power Toggles app. The new notification swipe down is annoying, having to swipe up when waking device is annoying. The status bar colors are inconsistent. The menus look childish looking.
Without being dramatic, did Sony take all this time to make sure it ran without crashing? Because I notice very few changes (not even improvements, just any changes) on the UI. I must be missing something.
Click to expand...
Click to collapse
I agree with you about small changes. I even face some strange problems in my WiFi. the mac address haven't change, but I can't connect to my work WiFi protected network. Sometimes it connects in limited status. One of my friends which updated his Ultra has this problem too.I could connect it to my laptop adhoc wifi netwrok, but for one time. it even can't connect to that network anymore. I rolled back to my stock 14.4.A.0.133 backup. and a'm waiting to fixes from sony.
Agree with you guys. And that stock greenish blueish greyish statusbar color pisses me off! Anybody knows how to change that color?
Quite pathetic attempt by a mod to bury this thread by moving it to this section. If negative feedback on L bothers you so much, delete the thread and censor it outright. Sad day for xda.
I have a strange situation that keeps happening. Every so often the wallpaper on my Pixel 6 will change to a solid color (that resembles the theme of the wallpaper I had active - for example sometimes it is gray, other times brown). From that point I can't seem to get rid of the solid color unless I reboot the phone. After a reboot the correct (previously active) wallpaper is shown. When the solid color is there it is almost like it is on top of the wallpaper because in the wallpaper settings the pixel thinks that the wallpaper is set properly and if I change the wallpaper there the solid color just persists and I never get an updated wallpaper.
Does anyone know how to fix this? It seems to happen most after I have used Android Auto, but happens at other seemingly random times too. I appreciate any help as I have tried many things with no success.
Not sure about you but I have a IFTTT applet that changes my desktop to black if my battery gets low. Well I know that now. I forgot about it though after setting it up. Drove me ****ing bonkers. I spent the better part of my free time in the evenings for a several days coming back to the mystery after work. I was digging into some deep reading in developer forums and official studio documentation after a full stock fresh start and it was still occuring.
Are you using any theming, root, power saving, optimization type apps? Or remote access, docking? Could be a setting or feature of what you're connected to. Can you reproduce it at will? or is it genuinely random. Did you change any settings related to freeform windows, overlays, hardware acceleration, Or systemUI mods, tweaks, or any hidden settings. If you have root, do you have any modules you haven't really tested for compatibility? Does it happen at certain times? only with certain events or places? Do you have assistant set up? automation, tasking? Set up any routines to run in the background that might be failing to do something with the wallpaper and just defaults to best possible match. Have you changed anything to do with locations of your media, where apps are installed, or what folders they have access to? Are you casting to wireless screens? enabled any "second screen" features or settings? Have you modified the DPI beyond stock ranges. Maybe your accidently putting the screen on something with similar conductivity with skin and have smart lock enabled and your getting random input while not using it.
Could be a lot of things.
Identify specifics, change something, track results; rinse repeat.
Thanks for the suggestions. I have tried some and will look into others. Based on lack of activity this does not seem like a widespread issue, so it is likely just some software causing this issue. I will continue to investigate and hopefully find the culprit. Thank you again!