Database Develop

Super shaky Gyroscope. Is there any fix for this? Somebody can confirm this issue?

Hello, I recently bought the "Google Cardboard" and I noticed that all apps I tried were shaking a lot (Even if I just leave the phone on the table). It seems to be an Gyroscope issue.
Noticed the same in Google Camera (360º Picture Mode). It doesn't happen in Google Street View as it seems to apply some kind of filtering. Is there any fix for this?
I've been told that the Samsung Phones doesn't suffer from that kind of shaking
Is there any way to calibrate the Gyroscope? Or at least to apply some kind of shaking filter globally to all apps?
Can somebody please confirm if they have the same issue (And if this issue has been fixed on Android L)? [I'm on Android KitKat]
Greetings.

Remove

I have the same problem.
Interface of Google cardboard is very shaky.
Google camera's lens blur doesn't work for me; it says device moved too quickly whereas i didn't even move it a cm. (Kitkat)

Everyone should have this problem I think so.
I think the gyroscope is not calibrated correctly

Remove

ErixGamer said:
Nvm its all fixed. remove please.
Thank you,
Click to expand...
Click to collapse
Fixed? Where? In Android Lolipop?
I have Moto G 2014 European version so I still haven't received the Update.
Or is there some other fix? I'm very interested in this.

Okay that message was because a thought this was solved. Anyways it works on lollipop very well. Its very steady but if i try to hold steady it shakes a little. On KitKat my gyroscope reacted very sensitive (slightest movement even registers) So my suggestion is maybe use lollipop? or try this app: A thread about how to recalibrate the gyroscope sensor
Anways hope it works wish you much lucky
Greetz ErixGamer

I am using lollipop on my moto g 2014, and videos are still shaky!

RK_DROID said:
Interface of Google cardboard is very shaky.
Google camera's lens blur doesn't work for me; it says device moved too quickly whereas i didn't even move it a cm. (Kitkat)
Click to expand...
Click to collapse
I'm having the same problem. Mine was working, but I flashed a new ROM and it stopped. I deleted that ROM and went back to stock, but the problem is still there.
When I start moving left, the phone thinks I'm moving right and vice-versa. It hardly detects any movement, even if I do a full 360 rotation.
I am also unable to view VR photos in Google Cardboard correctly. This is really frustrating and I have no idea how to fix it.
Have you had any luck?

I found the same, infuriating problem in all the ROMs I tried.
I read in another thread (possibly another forum, I can't remember now) a post from a Moto dev who acknowledged the issue and stated they would fix it in the next update. I installed the latest 6.0 soak test and the first thing I checked was the gyro, which appears to have been fixed.
Google cardboard runs as smooth as butter, with no shaking or anything.

In CM13 devs have fixed the sensors also added some new ones.
gyroscope is working correctly on CM13 too

Screen flicker poll G Watch R.

Hi,
I've started this poll for ALL owners of the LG G Watch R.
The question is: does your G Watch R flicker after charging it to full 100% when you take it off the charger?
After selecting yes or no on this poll, can you check your build number on your watch and post it here?
If you post the info, please also note if your watch does flicker or not to keep the results clean.
something like this:
Does flicker:
Software version: 5.0.1
Build number: LWX48P
Serial starting with: 412KPGS0139XXX
or
Does not flicker:
Software version: 5.0.1
Build number: LWX48P
Serial starting with: 412KPGS0139XXX
What I'm trying to figure out by starting this poll, is if it's hardware related or not.
To check your build:
Go to "Settings" on your watch.
Then press "About".
in the about section you will find the following info:
Software version: 5.0.1 (This will change after a new update.)
Build number: LWX48P
Serial starting with: 412KPGS0139XXX (Just replace last 3 digits with XXX, we don't need to know your exact serial number.)
Above info is from my own LG G Watch R.
Thanks for participating
Treborov.
Results so far:
All watches posted so far have Build number: LWX48P. I wonder if there are other build numbers out there? If anyone has a different build number please post it here
Serial ranges: 410KP series, 411KP series and 412KP series.
Everyone so far is running software version 5.0.1 (Which is the latest update.)
Remarks by users about what might cause the flickering effect:
Screen brightness settings: 1x
(Google calendar event) notifications: 1x (Could be any notification because I had the same problem with multiple notifications that all tried to pup up at once)
Watchmaker app: 2x (installed on 2 watches that have the flickering effect.)
Hardware related:
Loose display ribbons: 1x

I have had the snow-crash in one and the flickering in my second watch, now on my third. that one seems all right at the moment. what makes me suspect hardware in stead of software is that the LG G, does not show this problem. and both are technically quite close related.
If my watch shows the flickering again, i will partake in your experiment, as i am quite curious as to what is causing this. I also noticed the much brighter flickering as brightness was down to 1.
As i read the posts concerning this problem, i also noticed that the part that flickers is not always the same, on my watch it was the lower half blinking, others have mentioned the upper half.
It still reminds me of what a led does when power goes below a certain threshold.
Good luck in your project!

RoosW said:
I have had the snow-crash in one and the flickering in my second watch, now on my third. that one seems all right at the moment. what makes me suspect hardware in stead of software is that the LG G, does not show this problem. and both are technically quite close related.
If my watch shows the flickering again, i will partake in your experiment, as i am quite curious as to what is causing this. I also noticed the much brighter flickering as brightness was down to 1.
As i read the posts concerning this problem, i also noticed that the part that flickers is not always the same, on my watch it was the lower half blinking, others have mentioned the upper half.
It still reminds me of what a led does when power goes below a certain threshold.
Good luck in your project!
Click to expand...
Click to collapse
Thanks for leaving a comment, I did read all your comments in the other post about you sending your watch back to LG.
So you're on your third LG G Watch R now right? Not exchanged it for an LG G Watch?
If you got another Watch R. would you mind posting the build number?
Let's just hope your 3rd watch doesn't go all "disco" on you like the other two

Disco time haha. Half of the screen flickers, same as the OP explained. Really annoying, happened 2x already within 3 weeks of owning the watch
Does flicker:
Software version: 5.0.1
Build number: LWX48P
Serial starting with: 411KPZK0129XXX

Software : 5.0.1
Build : LWX48P
Serial starting with : 411KPPB
---------- Post added at 16:39 ---------- Previous post was at 16:32 ----------
So you're on your third LG G Watch R now right? Not exchanged it for an LG G Watch?
Click to expand...
Click to collapse
I had a Pebble before i had an LG G, my wife now has that one, i decided to stay with the LG G R, because the recessed screen helps in preventing random contact with my sleeve (thus interrupting the music playing on my headset), and i like its looks a lot more then the LG G, the screen above the bezel like the 360 has, is why i did not got that one (besides the poor hardware and battery) until someone writes an app that kills the touchscreen until the crown is pushed once or say 2 times, all other options are just to annoying

Hmmm.. 2 days straight of flickering every morning when I tried to check the watch right after I wake up.
I noticed that after I restart the device, a Google calendar event notification will pop up. Then the flickering will stop
Looks like a Calendar Event notification bug in Android wear, could someone confirm this?
Update : It flickers again, no calendar event notification. Maybe this is a hardware problem
Sent from my Nexus 5 using XDA Free mobile app

Does flicker:
Software version: 5.0.1
Build number: LWX48P
Serial starting with: 410KPVH0010XXX
thought the 5.0.1 solve the flicker but it came back after few days

O.K. Update on my watch.
I did a factory reset yesterday on my LG G Watch R.
I haven't touched the watch as in, changing face plate installing software etc.
This morning when I took it off the charger it didn't start flickering like it did the last two days. (So it was working as it should.)
Things I had installed on my watch when it was flickering: (before factory reset)
Multi Calculator
Instaweather app.
Intellicom Watch faces app.
Luxury watch faces app.
WatchMaker free app.
Facer app.
After factory reset, the only thing that automatically popped up on my watch when I checked watch faces, was the Facer app. The rest of the apps wern't showing on my watch anymore.
However, I didn't uninstall those on my phone.
I uninstalled the Facer app on my phone.
After checking the Watch Face options this morning, all the installed programs are back on my watch.
It seems they all got synced again between my phone and my watch.
Maybe I checked to soon yesterday after the reset and these programs weren't synced yet.
I'll take a closer look after next factory reset.
Thanks everyone who has participated so far in this thread :good:

@unclebor
In your app list, we only have 1 common app installed.
I also installed watchmaker, and as far as I remember the flickering started after i installed that! I will uninstall watchmaker and delete the data folder because I already tried uninstalling it but the data folder was not deleted.
Hopefully this is the culprit, if not maybe this is a hardware issue.
Sent from my Nexus 5 using XDA Free mobile app

The flicker is most likely due to a loose display ribbon connector and stops after a while because the watch warms up, the connector expands and makes better contact, but it will remain intermittent since it's not pressed all the way in. You need to open the watch and press in all the connectors (there are 4) and the flicker will likely stop.
For the record, I'm on 5.0.1, LWX48P, 411KPSL0096XXX, no flicker.

Mine does the same with LWX48P. It happends since i started using it with always On screen. Can we return it and exchange to a new one? I like pebbles warranty since they have issues about flickering screens too. Returned and sent me a new one.

Since update 5.0.1 the display flickers sometimes after fully charged. Power off and power on the watch helps for me (no reboot!)
Software version: 5.0.1
Build number: LWX48P
Serial starting with: 410KPNY0036XXX
cheers
Manfred

Update on my watch day 2 after factory reset.
I took it off the charging cradle this morning and again, no flickering.
It seems the factory reset helped so far. (Crosses fingers.)
my current settings are:
Adjust Brightness = 4 (stock after reset)
Always-on screen = off
Face plate = suit
Installed apps:
Intellicom watchfaces (did not select any face plates after reset)
Luxery watchfaces (did not select any face plates after reset)
Watchmaker (did not select any face plates after reset)
InstaWeather (did not use this after reset)
I'm going to change one setting today, and that's the Adjust Brightness = 4 to Adjust Brightness = 1 and see what it will do tomorrow when I take if off the charger.
If indeed it flickers again tomorrow (which I surely hope it won't), I'll change the setting back to 4 and recharge it to 100% and check again.
After tomorrow (if the brightness setting isn't the issue), I'll put the brightness level back to 4 and select a 3rd party watch face.
Yes, this is going to be a slow testing process, because I want to check only after a whole night of charging to not manipulate the charging time.
When I can trigger the flickering process by changing some setting, I'll just recharge it on the fly. Check if I can make it "un-flicker" by undoing the last change I made on the watch.
if that doesn't help, uninstall the program that made it flicker in the first place and check after that. (if it's a 3rd party app and not a Google Wear 5.0.1 setting)
If that doesn't help, factory reset, one more night charging on default settings, if that doesn't make the watch flicker, re-install the program that caused it to flicker and retest the last procedure that triggered the "disco" effect.
Makes sense? LOL for me it does
I wish I had like 10 of these watches, would make the testing process go much faster.
Thanks again for everyone participating in this poll and posting serials and such :good:

It flickers again this morning without the watchmaker app. So that's not the culprit, really annoying, i will return this for warranty.
Sent from my Nexus 5 using XDA Free mobile app

Why don't you guys return the watch? Sod the testing the watch was not designed to flicker! When I get mine on Xmas day, if it flickers.. Back it goes
Sent from my Nexus 5 using Tapatalk

There's a reply on the other thread, he returned it ang LG fixed it. But flickering still persist. So looks like LG doesn't really know how to fix this. But I sent mine for warranty.
No official statement from LG regarding this issue.
Sent from my Nexus 5 using XDA Free mobile app

wicked1683 said:
There's a reply on the other thread, he returned it ang LG fixed it. But flickering still persist. So looks like LG doesn't really know how to fix this. But I sent mine for warranty.
No official statement from LG regarding this issue.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Here are my 2 cents about the flickering on the watch:
Quick summary,
Got the watch (day 1), it was fully charged 100% when I turned it on, paired it and played with the stock settings and options.
Didn't flicker the first morning after full charge (day 2).
I played with it a lot, installed apps, changed face plates, (Also tried out some MOMO 360 face plates through the 3rd party app to see what they looked like on this G Watch R, didn't like them, chose another one), played with the weather app..etc.
Flickered after full charge! (day 3).
Played with it a bit, didn't really pay attention to the flickering because it was working normally after a reboot, just thought it was annoying. However put it in the back of my head for the next morning to check.
Flickered after full charge! (day 4).
Thought it was pretty annoying and checked the web for possible solutions and if other people had the same problem with this "disco effect".
After reading the threads here, I decided to do some testing myself.
I did reset my watch to factory settings.
Didn't flicker after full charge (day 5).
Didn't flicker after full charge (day 6).
Changed display settings to brightness level 1 (was on 4).
If the watch was broken, hardware related, the flickering effect would be there all the time right? (Broken = broken, no matter what the settings).
If it was a loose wire, it wouldn't only flicker after charging. (Unless the watch heats up to a certain level on the charger which would cause a bad connection in the watch itself which makes it flicker only after recharge.)
Therefore I think it's either software related OR the combination between the brightness/always-on settings and hardware.
There might be something in one of the installed (3rd party?) apps OR in the brightness/Always-on settings that triggers the "disco" on your watch.
Maybe if the brightness level is put below stock settings, there is a condenser that regulates the screen brightness? (Going to put this to the test.)
IF tomorrow morning my watch flickers, I know it's the hardware that can't cope with the low brightness setting. If not, I'm going to change the brightness back up to 4 and install a 3rd party watch face.
I still think, because Dersie changed his brightness settings through another app, it is software related.
if it was hardware related, it would always flicker after recharge, no matter which app you use to dim the screen. (condenser/hardware goes all stressed when it has to power up the screen in dimmed mode).
It's like searching for a needle in the haystack, but hey.... I like finding needles in haystacks.

It gotten worse! After charging I decided to turn it off, I slept, when I woke up I turned it on, then seconds later flickering happends. Restarted it, but still the same. I turned it off for a couple of times. Until I decided to just leave it on until flickering dissapears. Did factory reset but still the same. Sick and tired of this, $300 watch and its defective I dont wanna deal with this everyday, Im gonna return it to newegg since they have 30 day return/replacement warranty. But my watch has a lil dent on the bezel already. I hope they still accept it.

unclebor said:
I still think, because Dersie changed his brightness settings through another app, it is software related.
if it was hardware related, it would always flicker after recharge, no matter which app you use to dim the screen. (condenser/hardware goes all stressed when it has to power up the screen in dimmed mode).
Click to expand...
Click to collapse
Mine started flicking after 4 weeks, batt at 42% 2 day after charged, on a table since 1H, so no movement to move hardware screen connector, no after full charge. No issue the last 2 days after using brigntness setup with SWApp....
condenser problem is maybe a way for the problem. It happen only from screen OFF to ON for me, never when screen is already ON for awhile. So only after condenser can be not charged.

Time to let you guys know about what's going on with my watch.
Didn't have much time to post anything the last couple of days :/
All I can say is, so far so good.
The last 3 days it didn't flicker at all.
I am running a 3rd party watch face now, brightness settings set to 1. No flickering after full recharge.
I don't know what caused it in the first place.
Maybe it was a MOTO 360 face watch I tried on my watch to see what it looked like, I don't know.
I will do some more testing after these busy days at the end of the year.
I will post again in this thread when the flickering returns or when I find out how to trigger it.
If I can find out anything else about the "disco effect" on the G Watch R series on other sites, I'll post a link here.
I'm sure this isn't over yet, I guess I am just lucky at the moment that it doesn't flicker.
However, knowing hardware /software it will probably come back since I already experienced the affect on this watch.

Bluetooth audio streaming issue with CM roms

Does anyone have a clue why the above issue persists with Cyanogen Mod roms? I have tried several and still get the same problem.
What I'm talking about exactly is, when I try to play music in my truck via Bluetooth, the music will play for about 3 seconds then the audio will mute for 1 second.
I have tried several different things to get it to stop but it appears that it is a CM problem. When I go back to an aosp rom it works just fine.
My Bluetooth issue is a big deal to me. And for the record this problem is with my 2015 Tacoma.
Does anyone know of a fix for this? If any devs have any ideas and would like me to test anything for a fix I would be glad to help.

konaman said:
Does anyone have a clue why the above issue persists with Cyanogen Mod roms? I have tried several and still get the same problem.
What I'm talking about exactly is, when I try to play music in my truck via Bluetooth, the music will play for about 3 seconds then the audio will mute for 1 second.
I have tried several different things to get it to stop but it appears that it is a CM problem. When I go back to an aosp rom it works just fine.
My Bluetooth issue is a big deal to me. And for the record this problem is with my 2015 Tacoma.
Does anyone know of a fix for this? If any devs have any ideas and would like me to test anything for a fix I would be glad to help.
Click to expand...
Click to collapse
Well... if you're playing with CM, you're bound to get burned. There are a couple of reasons;
1) Everybody (and I mean *everybody*) throws stuff at the CM gerrit server (sometimes, even for comedy/trolling purposes), these bits being thrown at it are mostly independent and generally NOT tested in conjunction with all the other bits that get thrown at it. So what happens, is one of the maintainers sees a commit they like and adds it, sometimes not realizing the consequences of it, and major breakage happens.
2) Sometimes in the aforementioned situation, minor breakage happens, and it can persist for months, or even forever.
3) CM12 is very young, with lots of changes still flying. It is by no means stable, or even settled.
4) The CM definition of "stable" is that which nobody bothers working on any more. I.e., everybody right now is interested in Android 5.0, so 4.4 is not getting much attention... it is "stable" -- despite being horribly broken in many many ways.
If it works well with the factory system image, then you pretty much have the answer... it is a defect that has been introduced to CM. I think that CM has their own bug tracker that you can use, but I'm not sure if they have even opened it up to receive reports against 5.0 yet.
BTW: Sweet truck eh? I have a 2011. Pay some attention to the front cab mounts. If you look up into the cab mounts with a flashlight, you will notice that at the back where they are welded onto the main frame rails, there is a huge opening to the inside of the boxed section. When you drive through salty road slime in the winter, all that salt crap that flies off the front wheels gets sprayed up and into the INSIDE of the boxed section of the frame. Get a tube of roof repair tar from HD, and a couple of old CD's. Cut the CD's down to a diameter of 3.5 inch. Stick the cut down CD's up into the opening of the cab mounts and tar them in really well. While you are at it with the tar, plug up all the other holes into the frame around the front wheels (you may need some plastic plugs for this). That will keep the road sludge out of the frame, so it won't rust from the inside out.

I am running LiquidSmooth/franco kernel. I am running the 1/19 build because it was the last with the nice Dark UI and have no problems with Bluetooth in my Prius. I mainly use Pandora.

@ doitright
Thanks for the reply. I have a better understanding about cm roms from it and I have been searching this issue all over. It is definitely a cm problem.
As for my truck, yeah I love it. I have the double cab TRD off road 4x4 model. When the weather clears/warms up I will check the areas you mentioned. I know the history on Toyota frames all too well.
@ prod
I had the same issue with that rom as well.

Are you still having issues with this on nexus 6? I am on s5 and willing to buy a nexus 6 to fix it but i'm starting to wonder if it will matter.
konaman said:
Does anyone have a clue why the above issue persists with Cyanogen Mod roms? I have tried several and still get the same problem.
What I'm talking about exactly is, when I try to play music in my truck via Bluetooth, the music will play for about 3 seconds then the audio will mute for 1 second.
I have tried several different things to get it to stop but it appears that it is a CM problem. When I go back to an aosp rom it works just fine.
My Bluetooth issue is a big deal to me. And for the record this problem is with my 2015 Tacoma.
Does anyone know of a fix for this? If any devs have any ideas and would like me to test anything for a fix I would be glad to help.
Click to expand...
Click to collapse

jd603 said:
Are you still having issues with this on nexus 6? I am on s5 and willing to buy a nexus 6 to fix it but i'm starting to wonder if it will matter.
Click to expand...
Click to collapse
I had constant problems with this phone. I am not new to flashing roms or modding phone by any means but this phone had me beat. CM roms had the Bluetooth issue and I never got it fixed. Normal roms worked pretty good but the phone was still buggy.
I got so sick of it that I sold it. Though it has been a few months ago, maybe they got the bugs worked out, idk. I couldn't take it anymore.
I went got a 128gb iPhone 6 plus now and have never been happier. I haven't had an iPhone since the 4 and I forgot how flawless they operate out of the box.

Xperia X Performance (F8132) Accelerometer failure & Screen Auto-rotate irresponsive

Xperia X Performance (F8132) Accelerometer failure & Screen Auto-rotate irresponsive
Hi All,
I got an issue bothering me since I bought Xperia X Perfomance (F8132) Mid June.
The auto rotate function failed after a while but everything goes fine after reboot.
When it fails, I use "Xperia Service Menu" -> "Service Tests" -> "Accelerometer",
then all X,Y,Z are zero and the ball just sticks and freezes at mid.
I bought from Taiwan and I can find 15 more people having the same symptom with me on 2 forums
( http://mobile01.com and http://gamer.com.tw ).
Hence I don't think it's only me and it's a common issue or common yield problem for Xperia X Perfomance.
I post here because I'd like to find more people with the same issue and raise the attention of SONY in order to find the root cause (i guess it's either over-heat causes this or accelerometer yield issue) and give a patch.
Now I'm using a APP "Rotation Control" to workaround this, but all photos cannot records correct orientation data and no auto-rotate is kinda inconvenient.
For a flag-ship and high-priced cellphone for SONY this year, it is very disappointing to me. :crying:
Version: 35.0.A.1.227 and 35.0.A.1.238 both occur

huangjs said:
Hi All,
I got an issue bothering me since I bought Xperia X Perfomance (F8132) Mid June.
The auto rotate function failed after a while but everything goes fine after reboot.
When it fails, I use "Xperia Service Menu" -> "Service Tests" -> "Accelerometer",
then all X,Y,Z are zero and the ball just sticks and freezes at mid.
I bought from Taiwan and I can find 15 more people having the same symptom with me on 2 forums
( http://mobile01.com and http://gamer.com.tw ).
Hence I don't think it's only me and it's a common issue or common yield problem for Xperia X Perfomance.
I post here because I'd like to find more people with the same issue and raise the attention of SONY in order to find the root cause (i guess it's either over-heat causes this or accelerometer yield issue) and give a patch.
Now I'm using a APP "Rotation Control" to workaround this, but all photos cannot records correct orientation data and no auto-rotate is kinda inconvenient.
For a flag-ship and high-priced cellphone for SONY this year, it is very disappointing to me. :crying:
Version: 35.0.A.1.227 and 35.0.A.1.238 both occur
Click to expand...
Click to collapse
I also have that problem. No more auto-rotation after a while (1-2 days) . Only a reboot fixes that

DiLeon said:
I also have that problem. No more auto-rotation after a while (1-2 days) . Only a reboot fixes that
Click to expand...
Click to collapse
Thank you for letting us know.
It shows it's not a regional FW issue but a global HW or FW one.
I wonder if SONY knowing this. If not, we need to address this and push SONY to work it around.
And if it is not workaroundable, SONY will have a big problem.

I have the same issue on my Xperia X (F5121) bought in Sweden. Haven't checked the accelerometer but the behaviour is the same and reboot is only fix.

I have not had any problems with auto rotation, my accelerometer works fine but my touch screen is messed up
Sent from my F8131 using XDA-Developers mobile app

HellRoot said:
I have not had any problems with auto rotation, my accelerometer works fine but my touch screen is messed up
Click to expand...
Click to collapse
Same

HellRoot said:
I have not had any problems with auto rotation, my accelerometer works fine but my touch screen is messed up
Click to expand...
Click to collapse
Can you specify "messed up"? I've had issues with the touch screen also, mostly that it registers a tap while I'm scrolling resulting in involuntary tapping on links. Also it often takes a while to start scrolling, as if the screen has a hard time recognising the swipe.

I have the same problem. The accelerometer stop working 15 minutes after reboot.
Help me verify if is caused by a third party app or not.
Use your phone in safe mode for a while.

I'm from Hong Kong, the accelerometer and its auto-rotation of my x performance has the same problem that it won't work until i reboot my phone.
I dont think that is caused by a app crashing when the problems occuring in all around the world.
The issue didnt come to me when I was not yet update to 35.0.A.1.282. Please notice this problem SONY. It seriously affected the satisfaction from user of the phone from your brand.

There is a topic on the Sony support forum - see here: http://talk.sonymobile.com/t5/Xperia-X-Performance/Accelerometer-stops-working/m-p/1158490#U1158490
At least they are aware of the problem. As soon as it happens again on my phone, I will send them my logs. I will report any development...

It seems that I uninstall the AR effects in my phone and reboot, it works again

Rotation fails
Hello guys,
I have the same problem. Yesterday it worked fine, but today, the auto rotate don't work. Very disappointing. Only a reboot can help but not every time.
Sony has to do something with it.

Gyroscope/Auto-Rotation Issue
Hey everyone,
I'm also having this same issue, but only since the most recent update from late September. When trying to make a pic display as fullscreen by rotating the phone, nothing happens, unless I reboot the phone. Then within day or two, it starts happening again. When I go to camera it loads up and STAYS in landscape mode, no matter what I do, even closing it out and clearing out the cache & force stopping it then reactivating it. It seems like a software issue that Sony needs to address PRONTO!
It appears another thread here on XDA is dealing with the same issue. I tried shenlong85's idea and it seems to have fixed the issue, but I need another day or so to make sure. If you don't hear from me by Sunday (10/23), assume it's been fixed. Hopefully the Nougat update we're all about to get any day now will permanently fix it!

The memory uninstall updates only prolong the issues. Seems like the firmware issue earlier on.
Nougat... When are u coming?

shenlong85 said:
The memory uninstall updates only prolong the issues. Seems like the firmware issue earlier on.
Nougat... When are u coming?
Click to expand...
Click to collapse
Well, we'll see. I am giving my XP 'til Sunday........if no more auto-rotate issues by then, then I will consider your idea to be gold. lol Of course, once we get Nougat, I'm hoping it will ensure that the issue never comes back period. As of this time, the issue has NOT returned.

I bought my Xperia X Performance from Kogan who sells imports in Australia from Asia and I have the exact same issues with my orientation and touchscreen. However my jumpy touchscreen only seems to occur while charging.

RockStar2005 said:
Hey everyone,
I'm also having this same issue, but only since the most recent update from late September. When trying to make a pic display as fullscreen by rotating the phone, nothing happens, unless I reboot the phone. Then within day or two, it starts happening again. When I go to camera it loads up and STAYS in landscape mode, no matter what I do, even closing it out and clearing out the cache & force stopping it then reactivating it. It seems like a software issue that Sony needs to address PRONTO!
It appears another thread here on XDA is dealing with the same issue. I tried shenlong85's idea and it seems to have fixed the issue, but I need another day or so to make sure. If you don't hear from me by Sunday (10/23), assume it's been fixed. Hopefully the Nougat update we're all about to get any day now will permanently fix it!
Click to expand...
Click to collapse
I tried shenlong85's idea, but less than 24 hours after trying it, I switched my phone from Portrait to Landscape to view a 16:9 widescreen pic I had in my Album, and it WOULD not auto-rotate the pic. So unfortunately this "trick" doesn't work either.
Just have to hope Sony includes a fix with the Nougat update we're about to get any day now from them.

I'm noticing now too that once the Auto-Rotate function stops working, so does Smart Call Handling. Have to swipe screen once again to take calls. Hurry up Nougat!! lol

I'm having the same issue and the only help I'm getting from Sony support is to factory reset my device :\ I'm hoping Nougat makes it's way to our devices soon. I really like this phone and this is a pretty big issue to have.

SpencerElliott said:
I'm having the same issue and the only help I'm getting from Sony support is to factory reset my device :\ I'm hoping Nougat makes it's way to our devices soon. I really like this phone and this is a pretty big issue to have.
Click to expand...
Click to collapse
I agree Spencer. And yes Sony Mobile told me the same thing. I'll do a repair (which yes, includes a factory reset) only IF Nougat doesn't fix it. They say we're getting it "in or close to October", so I'm guessing it's gotta be coming any day now. Hopefully they include a fix with Nougat though and I don't have to do that. Getting tired of this BS with Sony. My Z3 had an issue where if I turned on Stamina Mode, it would 1) mess with my MMS (group/pic/video) text messages.........you don't know how many times I had to ask ppl to resend those to me and how much that sucked lol 2) Cause a "random" battery drain. Only fix was a factory reset. I FINALLY got wise and realized it was SM and kept it off. Found a great app called 360 Hibernation Master that did what SM was supposed to do but better, MINUS the buggy BS. But OF COURSE it doesn't work on any X series phone (at least not my XP), so I'm stuck with SM now. At least Sony Mobile FINALLY fixed that bug with SM so that's not an issue anymore. lol
It is a big issue, and it makes me not want to keep buying their phones.

Android Auto car display is mirrored horizontal

Hi guys,
I've got a new phone and tried to connect it to my Mazda 3 BM. Everything worked, but the whole display is mirrored horizontal somehow. How can I fix this? Are there any props or something to edit? My phone is rooted, so maybe there is something I can do about it.
My phone is a Kingrow K1 (a very niche smartphone with e-ink screen) and sideloaded Gapps. I'm very surprised that after all Android Auto is booting with that phone. But I think there is only a small part wrong with the handshake between my phone and the Cars Entertainment System, so this could be fixed through myself.
Nevertheless Android Auto on my car worked perfect with my Pixel 2XL before.