Nothing I can do will make screen rotation work correctly. Have tried all the usual fixes:
1. Turned on in settings.
2. Done GPS Status calibration.
3. Done figure of eight calibration.
4. Tried various kernels.
5. Tried various ROMs.
6. Done *#0*# and the graph shows everything moving correctly on all three axes.
However, when I do "gyro self test" I sometime get big red FAIL.
Here are two results:
Normal 0 0 -1
SelfTest -437 435 -460
PASS
Normal 0 0 -1
SelfTest -437 434 -460
FAIL
Anything left for me to try?
Looked up some more possible solutions including this one: http://www.techbeats.co.in/2012/12/samsung-galaxy-screen-rotation-problem.html
No dice.
Sometimes the screen does rotate but it is about 30 seconds too late and then doesn't' return back to portrait. Sometimes it gets stuck upside down. Anyone have any clue about this issue?
How can I fix this?
Related
I upgraded from a mogul to touch pro and unlocked with Raphael_CDMA_HSPL_037
I have loaded about 5 roms on my device and each one hangs at the screen calibration setup dialog (where you press + 5 times on the screen to proceed)
if i attempt to press the + it does not work but if i move my stylus around the screen it will eventually proceed through the steps but restarts calibration screen in an endless loop. its like the drivers arent properly loaded..?
anyone have any thoughts?
EDIT - lllboredlll_1.3-B_SP.exe
seems to have worked. it bypasses the calib screen.
loaded a few more roms and hard reset a few times. now any rom i load seems to work perfectly.
This phone has never been modified, no custom ROMS, never rooted, using the latest OS from AT&T ...
And today, for whatever reason, when making originating a phone call, and once I've hit "dial" ... the phone screen goes completely black except for the status bar at the top (the one you can swipe down). I'm saying that whereas usually, after hitting "dial" and as the phone dials, you can actually see a screen full of information (hang up botton, number/name of who your dialing, etc.) ... in this case and now, there is just a black screen.
Though there is a black screen (other than the status bar at top), I can still hear the phone ring and even have a conversation should somebody answer. But when the call is over (the person on the other end has to end the connection because I have no screen interface to do such), the screen remains blank (other than the status bar at top) and none of the bottom, permanent keys are operative either ("home" / "back" / settings / etc.). To get back to the home screen, I have to pop the battery and re insert it and re start the phone. But even then, it's acting weird: when booting, at the "Reimagine Possilbe" screen (I think that's what it says) it hangs there for about 45 seconds (usually only about 5 when functioning correctly) and will eventually end up at the home screen.
But if I originate a call, the cycle repeats.
I've completely reset the phone to factory defaults at least three times, formatted the USB storage and the whole nine yards but it remains glitched as described above.
...
So... has anyone seen/heard of this?
I'm thinking of just warrantying the phone as it's only about 5 months and I figure AT&T should have no issue as it's such a replicable problem and it certainly doesn't seem to be software related as it's completely stock and multiple factory resets have not worked but wanted to put a line out here first to see if anyone else has experienced this.
Thanks in advance for any information.
Best,
Joel.
I think the network is fugazi right now, as I had issues with the phone, and read about another user having same troubles. I'd give it a little time.
rangercaptain said:
I think the network is fugazi right now, as I had issues with the phone, and read about another user having same troubles. I'd give it a little time.
Click to expand...
Click to collapse
I sure hope so. Even though I've reset the phone (which sucks) ... I'd prefer that over having to go to the store and all...
Odd that a network problem could cause such, though ....
Thanks for the word ...
Best.
.joel
Just a llittle update ...
I changed the "Proximity Sensor" to OFF and now the normal iin-call screen appears but it never goes away, which can be problematic.
In general, I've always had the proximity sensor set to ON as this allows the in-call screen to blank after a few seconds (complete blank with no status bar at top) and then reappear when I remove the phone from my ear.
But when I re enable the proximity sensor, now ... the screen blanks immediately (excepting the status bar at the top) and never comes back ... even after my call recipient ends the call ...
I'm just gonna warranty at at the local service center; at this point (two days now with all my friends AT&T phones working fine) I'm pretty sure something is glitched with the internal sensor that manages the proximity settings ...
Thank God for warranty.
I need to use an app that scans the screen, however it doesn't work properly with changed colours in night mode (read mode).
The problem is that the night mode is turned off by default, but the screen still goes to night mode! I switched it on/off, changed everything I could including colours and the only workaround is to set time back to day (e.g. 3 PM).
On my previous phone I did not have this issue since the "orange layer" was on the top of everything. Now it seems it's "under" everything. No matter how orange the screen is/isn't, every screenshot taken by the app has the same orange colour.
Any idea how to turn it off and where the problem is? Thanks for your suggestions
SOLVED! It was probably problem bewteen MIUI and Google (Android?) default settings.
It's just two steps through debugging:
adb shell settings put secure night_display_activated 0
adb shell settings put secure night_display_auto_mode 0
The orange overlay is gone, yet I still have the night mode. Worked as a charm! Big thanks to lessthanzach
Hi Matt, I am having trouble while turning off the night mode. Even if I turn it off the night mode the screen is still in orange colour. I saw your post in XDA in a browser. It seems you have solved the problem
Could you please help me resolve the issue?
Thanks
hello
how can i reload / refresh the screen without rebooting my phone? the frames appear black. but after restarting the phone, they disappear. appear again when you flip the screen (for example, when starting a game). after that, the frames do not go away until you restart the device
maybe there is a way to quickly turn off the screen so that it refreshes, but this does not have to reboot the entire device
found a solution. first you need to put LADB, it is paid. then enable wireless debugging (there are many tutorials on the network). connect and when the frames appear, for example after the game, I just enter the command
"settings put secure sysui_rounded_size 0"
and that's it, they disappear. But keep in mind if you entered 0 at the end, then the next time you need to enter 1, more 2, 3 and ..... at the end, and so on.
I've been documenting my struggles with my lock screen in another thread. But I just had a major breakthrough and didn't want this to get buried.
To recap, my lockscreen has been a buggy mess from day one. The fingerprint sensor barely works, the fingerprint icon randomly disappears, and the gray border that's supposed to appear around the fingerprint icon simply doesn't show up. The lockscreen doesn't light up when I pick up the phone either (it stays dimmed). Also, wallpapers don't show up on the lock screen, and the big ugly clock sometimes disappears or moves itself to the top-left.
I've tried just about everything to fix this. As a last-ditch effort, I added a new user profile only to find that the lockscreen works perfectly well for this new profile (but still not for my main one).
Here's my main profile with the unusable lockscreen:
broken lockscreen of main profile
Watch "broken lockscreen of main profile" on Streamable.
streamable.com
And here's what it looks like when using the other profile:
working lockscreen on new profile
Watch "working lockscreen on new profile" on Streamable.
streamable.com
So there's clearly some obscure bug that most people aren't experiencing here. I'd love to just figure it out so I can move on.
When I didn't have the "always on display" turned on, the phone was very consistant about turning on properly when I picked it up. I ran it this way for 3-4 days without any issues.
After reading some articles on the P6, I realized that it has an AOD and that it was turned off. So I turned the AOD on while leaving all the other settings set the same. At first, the finger print icon wouldn't appear consistantly, but that is because I had adjusted the animation scale settings in the Developer settings. Changing that back to stock fixed the issue with the finger print icon not showing up.
That beings said, I have experienced the same "unresponsive" screen many times over the last couple of days that I have had the AOD turned on. The screen stays dimmed (or even turned off if I pull the phone out of my pocket) and the finger print reader is inactive (even though the icon is displayed). The screen is suppose to turn on when I lift the phone up, but it doesn't always do it. When this happens, I have to either manually turn the screen on using the power button, or double tap the screen to wake it. This is clearly a bug in the system somewhere. I probably need to report it to Google, but hopefully it is fixed soon.
After spending way too long on this, I've determined that the bug occurs consistently with these specific settings (although it may also occur for similar ones):
Lock after screen timeout: 30 minutes (or anything high enough to prevent it from locking between tests)
Power button instantly locks: disabled
Lift to check phone: disabled
Tap to check phone: disabled
Always show time and info: enabled
Replication steps:
1) Enter the above settings
2) Press the Power button to go to the lockscreen
3) Set your phone down for a couple seconds
4) Pick your phone back up and try to use the fingerprint sensor
Result: The fingerprint sensor won't work the first time.
I think all the other issues I had were actually stemming from this one issue.