Database Develop

active display bugs

anyone else have issues with active display where the clock isn't fully showing the numbers or not showing the clock at all?
also sometimes the lock icon isn't there when you swipe down.

tonyb81 said:
...sometimes the lock icon isn't there when you swipe down.
Click to expand...
Click to collapse
It's random and rare, but I have seen this one.

this is what I'm referring to
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my XT1060 using XDA Free mobile app

Had my X since January through VZW and have never seen any issues with active display even through multiple ROM flashes. Very strange?

DANIEL AMBRUSO said:
Click to expand...
Click to collapse
That contributed absolutely nothing to this thread. I've seen plenty of your other posts and they do the exact same thing, they are off-topic of the thread. My apologies if you don't speak English well and simply don't understand what the topic of each thread is, but if you are fluent in English you are simply posting off-topic.
ON-TOPIC: Yes I have this bug happen to me at least 5 times a day. I've only had it not show the clock at all, but I haven't had half-formed numbers, that one is a strange bug.

Haven't had that bug, but I do sometimes get an annoying lag from unlocking the phone to seeing the screen. Seems to usually happen if I've previously swiped away a notification, then later when I unlock the phone.

Weird. I haven't seen that. I'm assuming you've installed the updated "Motorola Active Display" service through Google play?

danny39 said:
That contributed absolutely nothing to this thread. I've seen plenty of your other posts and they do the exact same thing, they are off-topic of the thread. My apologies if you don't speak English well and simply don't understand what the topic of each thread is, but if you are fluent in English you are simply posting off-topic.
ON-TOPIC: Yes I have this bug happen to me at least 5 times a day. I've only had it not show the clock at all, but I haven't had half-formed numbers, that one is a strange bug.
Click to expand...
Click to collapse
Apologies me for my bad English. Just i want to say here my clock is show fully in my display. I have not face this same issue here..

DANIEL AMBRUSO said:
Click to expand...
Click to collapse
How to get the home screen clock widget to show the hour number thicker than the minutes number as shown in the above image?
I mean on my Indian Moto X XT1052, the home screen default clock widget shows both the hour and minute number in a thin font. On all the other Moto X everywhere I see that the hour number is thicker. Why is it not showing that way on my phone?
Sorry OP for the off topic question.

I'm having this exact same issue on my Droid Ultra Maxx. I guess there isn't a solution yet? When the lock screen breathes and it shows the clock, sometimes the numbers are broken.

I've got the problem on my retail UK 1052
But it only happened after I flashed the 1053 4.4.3 update, I did a full twrp backup before flashing so I restored back thinking this would fix the problem but no, its still happening.
I was away during the weekend and the amount of times this happened got more and more then on Saturday evening my display 'inverted' just like looking at a negative image. Everything worked but the screen was negative however pressing power then unlocking worked 3 times out of 5.
Saturday night my phone really really lagged in everything, maps drawing a 2 frames a second, no animation etc and I said to myself when I get back I will revert back to stock.
Later on my display went completely, it was like static or an old tv out of tune. The phone works I.E. rings, bleeps on messages etc but no matter what I tried I could not clear it.
After loosing all hope I eventually managed to power off by guessing the positions of the on screen buttons and Sunday evening I did the stock reflash as described here using rsdlite.
Reflash finished but the screen was the same, just static but squeezing, pressing and holding in various places it came back. Wohoo I thought and reloaded all my apps etc then turned off for the night and switched back on yesterday morning but the static was back.
I have took my phone back to the shop and I am awaiting a replacement but anyone experiencing this behaviour please be on guard because if this happens to you then you are screwed.
Hope yours dont go like mine.
.

Just as more info, I have a Moto X / no mods / Brazilian with this bug (or related).
Sometimes the first number on my Active Display clock does not show, like, if the time is 16:04 it shows 6:04
Since here we usually use both clock formats (12h and 24h clocks) That can be VERY confusing sometimes (like now, I was so happy It was time to go home, and now I'm sad ).
I see this happening once a day in average.

leparlon said:
Just as more info, I have a Moto X / no mods / Brazilian with this bug (or related).
Sometimes the first number on my Active Display clock does not show, like, if the time is 16:04 it shows 6:04
Since here we usually use both clock formats (12h and 24h clocks) That can be VERY confusing sometimes (like now, I was so happy It was time to go home, and now I'm sad ).
I see this happening once a day in average.
Click to expand...
Click to collapse
Mine is Brazilian Moto x too, and i have the same issue.
The Clock 2 digits issue if the time is 16:04 it shows 6:04
Somethimes, the lock icon desapear too.
And this bug happens after update to 4.4.3. I Already tried a wipe data and a clean installation and nothing. Same thing.

Its happened a few times for me when I'm low on ram.

Any update on this? Happening on my girlfriend's phone. Pic attached.

Has any body found a solution to this problem? I am facing the same problem..

Camera Problems - Cannot connect to the camera and other problems

Hello All,
I am having some issues with the camera. I just got my Nexus 6 64GB on Sunday (2 days ago). I immediately unlocked it and decrypted it.
When I first tried to use the camera, it would freeze the phone. I would try and reload and would eventually get the "Cannot connect to camera error"
I rebooted and it it finally loaded. I can't seem to duplicate the problem now??
I am also seeing issues where the screen will get snowy when using camera. It is pretty sever and covers the entire view finder area. It will last lest then a second. I haven't been able to get a picture of it and can't figure out how to duplicate it.
Ok, happen again this morning and completely froze the phone. I am now getting the "Cannot connect to camera" message.
I just came from a Nexus 6 32 GB and never saw this issue. Any ideas on what may be causing it?
Got a screen shot of it!!
This is an example of what I'm seeing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I flashed completely back to stock and still no luck.
And after the factory reset, the camera doesn't open at all.
I am on the line with T-mobile to get a new phone. I haven't seen anyone else with is problem so this may be a very limited problem.
Update: I am just going to return the phone for a full refund...
I'll try again next year, I am so tired of dealing with this.
-Jason

I have a similar issue sometimes with the camera app not opening especially after taking a bunch of pictures. I've never experienced the snow like screen, sounds like a loose connection of the screen. However if I force stop the camera app it opens fine after.
Lately I have an issue where my phone camera jumps left to right while recording video or when HDR+ is off. Anyone seen a similar issue and is it software related or hardware?
Running stock ROM.

I haven't seen the issues you're talking about. Even when I force close I still had the issue.
Oh well. I'll wait to order again after the new year.

camera left and right
Jnewell05 said:
I have a similar issue sometimes with the camera app not opening especially after taking a bunch of pictures. I've never experienced the snow like screen, sounds like a loose connection of the screen. However if I force stop the camera app it opens fine after.
Lately I have an issue where my phone camera jumps left to right while recording video or when HDR+ is off. Anyone seen a similar issue and is it software related or hardware?
Running stock ROM.
Click to expand...
Click to collapse
I've got the same issue with the screen jumping left and right while recording a video. Has it fixed itself for you or do you still have the issue?

Still have the issue. I have a post open on Motorola forums about it. People there in the forums think its hardware related. I have factory data rest and flash stock ROM but issue continues.

I have the same problem, I received my N6 on 12/19 but I haven't been able to get my back camera to ever work. I can get the front to work that's it, but the back will either freeze the camera app or display can not connect to camera. I ended up calling Moto and did an advanced RMA, just got an email this morning with my replacement's tracking info.

Jnewell05 said:
Still have the issue. I have a post open on Motorola forums about it. People there in the forums think its hardware related. I have factory data rest and flash stock ROM but issue continues.
Click to expand...
Click to collapse
I ended up getting a replacement. The new one doesn't seem to suffer from the jumping camera issue.

Having the same issues. Camera will work fine for a while then boom stays on opening camera screen. After a while it will say cannot connect to camera. Motorola wants me to send it back but will not issue replacement first. I do not have Another phone to use in the mean time. Sucks
Tried multiple factory resets and clearing cache, force closing etc. Only a temp fix.
Forked out $700 for this , shouldn't have to wait for a replacement.
Sent from my Nexus 6 using Tapatalk

jmill75 said:
Having the same issues. Camera will work fine for a while then boom stays on opening camera screen. After a while it will say cannot connect to camera. Motorola wants me to send it back but will not issue replacement first. I do not have Another phone to use in the mean time. Sucks
Tried multiple factory resets and clearing cache, force closing etc. Only a temp fix.
Forked out $700 for this , shouldn't have to wait for a replacement.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
just contact them and tell them you want to do an advanced RMA. They will send you a new phone, but will place a $500 temporary hold on your credit card until you return the defective unit. I did that on Tuesday and my new 64gb Nexus will be here tomorrow

I remember reading somewhere that there is a fix for this, but i havent been able to track it down. I seem to remember seeing it somewhere on a rom page, but i also never was able to verify if the solution was working. If anyone can find a working solution to the camera all of a sudden no longer working after a new rom is installed, any information on this matter would be greatly appreciated.

Jsunn said:
I flashed completely back to stock and still no luck.
And after the factory reset, the camera doesn't open at all.
I am on the line with T-mobile to get a new phone. I haven't seen anyone else with is problem so this may be a very limited problem.
Update: I am just going to return the phone for a full refund...
I'll try again next year, I am so tired of dealing with this.
-Jason
Click to expand...
Click to collapse
Same here, only when I flash liquid smooth rom.

I've been having the same cant connect to camera issue for a few days now. I've tried different roms, different kernels, and different camera apps. No joy. Sent for advance RMA. Tired of fussing with this. Hope the new one doesn't start to fail too. Moto needs to fix this or the nexus6 will turn out to be a bust.

Well, geez. I've been using this phone and its camera for about a week without issues, then suddenly the "Can't connect to camera" error popped up after taking a shot: the screen hung with a blurred view of the picture I just took, there was no aperture sound and the camera app hung. I'm on a virgin stock phone, too.
Force closing and erasing the app's data had it work for another picture, but then it hung after taking the next shot only a few seconds later, with same symptoms as above.
This time, Force Closing and deleting app data didn't solve the issue, so I deleted the app data once more and powered down/powered up. This time, the camera app came back for about five minutes of use - both videos and pictures - until I tried opening it again and it hung on that action (i.e., not in the picture taking action, as when the hang occurred before).
I'm seeing complaints of people losing their camera in the phone with this app since moving to Lollipop and that makes me wonder if there's something flaky with the Nexus 6 related to whatever in the OS controls camera access.
It's disappointing, but guess it's time to contact Motorola tomorrow. What makes this worse is that everything else on this 64GB blue phone has been stellar.
- ooofest

Following up to my prior post . . .
Kept the phone off overnight and have not used the Google Camera app thus far today, which has somehow led to taking pictures via other apps for the past half hour.
I wonder if there's a thermal issue at play, perhaps? This phone is in a dual-layer case and it seemed to work again when I waited a bit yesterday, after clearing the app's data and rebooting. I'm going to keep testing through the day unless/until it breaks again, but avoid the Google Camera.
Still, if the standard app doesn't work for me without eventually locking up - while many others have no such problem - it seems a call to Motorola for help is my next step. *sigh* I really liked how this phone was working, too . . . guess we can't all get lucky.
- ooofest

I requested an advance replacement from moto online last weekend but nothing has happened yet. Still waiting. Camera has not worked once despite various efforts including yours.
Sent from my Nexus 6 using Tapatalk

almahix said:
I requested an advance replacement from moto online last weekend but nothing has happened yet. Still waiting. Camera has not worked once despite various efforts including yours.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
That sucks and sorry to hear.
After clearing the data and cache for Google Camera, uninstalling updates and rebooting, then trying out some other camera apps, I felt that the Google app gave the most clear and quick shots, so upgraded it from Play again and have been taking pictures each day since. Also read that other phones are getting this error under Lollipop, which makes me wonder.
If it happens again, I'll probably call Motorola, but this particular device is otherwise running so nicely.
- ooofest

ooofest said:
That sucks and sorry to hear.
After clearing the data and cache for Google Camera, uninstalling updates and rebooting, then trying out some other camera apps, I felt that the Google app gave the most clear and quick shots, so upgraded it from Play again and have been taking pictures each day since. Also read that other phones are getting this error under Lollipop, which makes me wonder.
If it happens again, I'll probably call Motorola, but this particular device is otherwise running so nicely.
- ooofest
Click to expand...
Click to collapse
I just tried what you suggested and I still can't use the camera. No action from moto re:exchange yet; I'll phone them tomorrow.
Sent from my Nexus 6 using XDA Free mobile app

Called moto re: my pending RMA...they are out of 64gb N6s again. They offered a 32...no thanx. Will wait for 64.
Sent from my Nexus 6 using Tapatalk

almahix said:
Called moto re: my pending RMA...they are out of 64gb N6s again. They offered a 32...no thanx. Will wait for 64.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
In another thread, a Motorola support person mentioned that if the camera still doesn't work in Safe Mode, then it might point more directly to hardware in that case. Might be interesting to test before your phone is shipped out.
- ooofest

Extreme battery drain?? 6.0.1

Has anyone else run into this after 6.0.1 update. It really didn't hit me until last night when I decided to test it. Unplugged my phone at 80% and went to sleep only to wake up to it dropping almost 50%!!!!!....not normal. It looks like something is just not right with everything after the update because after checking everything, nothing seems to fit. And before you say it was my wifi, I just changed that, this happened even if wifi was off. But I can say doze is definitely not working and no app seemed to go "rouge" with wakelocks when trying to check. Going to downgrade back to a previous build of 6.0, but hopefully someone else can chime in. Only found a few articles of people reporting the same thing but no one is actually posting possible solutions, just bashing a legitimate concern. Hopefully I don't run into that here.....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Try a factory rest, fixes 99% of issues.

turn off wifi scannning, in you location settings. notice that your wifi us in the whole time? and i bet that you arent even using wifi.. well, turn it off.

A2CKilla said:
Has anyone else run into this after 6.0.1 update. It really didn't hit me until last night when I decided to test it. Unplugged my phone at 80% and went to sleep only to wake up to it dropping almost 50%!!!!!....not normal. It looks like something is just not right with everything after the update because after checking everything, nothing seems to fit. And before you say it was my wifi, I just changed that, this happened even if wifi was off. But I can say doze is definitely not working and no app seemed to go "rouge" with wakelocks when trying to check. Going to downgrade back to a previous build of 6.0, but hopefully someone else can chime in. Only found a few articles of people reporting the same thing but no one is actually posting possible solutions, just bashing a legitimate concern. Hopefully I don't run into that here.....
Click to expand...
Click to collapse
Only out of place thing I see is that your screen was on at some points but the phone wasn't saying it was awake. That leads me to believe there's a kernel wakelock issue because I had the same thing but on 5.1. The issue turned out for me to be a wakelock called bluesleep which is related to bluetooth and it came about from an app called gasbuddy which silently updated to provide support for bluetooth "beacons" at gas stations to give you deals or some crap like that. If you're rooted you can install BetterBatteryStats to test for kernel wakelocks, you can test for bluesleep wakelock by just turning off bluetooth and seeing if the drain/weird screen-on not awake thing happens, and long press power off to start the phone in safe mode to narrow down whether its a system issue or installed app issue and if rooted use an app freezer like Titanium Backup to freeze your installed apps a few at a time to narrow down what app(s) are causing it(so you don't have to uninstall/reinstall trial and error).

StykerB said:
Only out of place thing I see is that your screen was on at some points but the phone wasn't saying it was awake. That leads me to believe there's a kernel wakelock issue because I had the same thing but on 5.1. The issue turned out for me to be a wakelock called bluesleep which is related to bluetooth and it came about from an app called gasbuddy which silently updated to provide support for bluetooth "beacons" at gas stations to give you deals or some crap like that. If you're rooted you can install BetterBatteryStats to test for kernel wakelocks, you can test for bluesleep wakelock by just turning off bluetooth and seeing if the drain/weird screen-on not awake thing happens, and long press power off to start the phone in safe mode to narrow down whether its a system issue or installed app issue and if rooted use an app freezer like Titanium Backup to freeze your installed apps a few at a time to narrow down what app(s) are causing it(so you don't have to uninstall/reinstall trial and error).
Click to expand...
Click to collapse
Wow thanks for that, I actually use GasBuddy, wish you were here before the factory reset I did, but everything seemed to go back to normal after I did the reset but I wanted to actually try to find out specifics. I haven't rooted just because I use Android pay (I know system less root us out there) but I'll try to keep an eye out for that stuff if it happens again.

simms22 said:
turn off wifi scannning, in you location settings. notice that your wifi us in the whole time? and i bet that you arent even using wifi.. well, turn it off.
Click to expand...
Click to collapse
"and before you say it was my wifi, that was off with the same issue".....

A2CKilla said:
"and before you say it was my wifi, that was off with the same issue".....
Click to expand...
Click to collapse
i have only what you gave us, about your issue, and no more. as i see it, you HAD YOUR WIFI ON, but werent using your wifi. you didnt give me anything contrary to that.

simms22 said:
turn off wifi scannning, in you location settings. notice that your wifi us in the whole time? and i bet that you arent even using wifi.. well, turn it off.
Click to expand...
Click to collapse
I wondered where this went.. didn't it used to be in advanced under wifi settings?

lazer77 said:
I wondered where this went.. didn't it used to be in advanced under wifi settings?
Click to expand...
Click to collapse
yup. now its in location settings, three dots at the top right.

simms22 said:
i have only what you gave us, about your issue, and no more. as i see it, you HAD YOUR WIFI ON, but werent using your wifi. you didnt give me anything contrary to that.
Click to expand...
Click to collapse
Not trying to be rude but.....
A2CKilla said:
Has anyone else run into this after 6.0.1 update. It really didn't hit me until last night when I decided to test it. Unplugged my phone at 80% and went to sleep only to wake up to it dropping almost 50%!!!!!....not normal. It looks like something is just not right with everything after the update because after checking everything, nothing seems to fit. And before you say it was my wifi, I just changed that, this happened even if wifi was off. But I can say doze is definitely not working and no app seemed to go "rouge" with wakelocks when trying to check. Going to downgrade back to a previous build of 6.0, but hopefully someone else can chime in. Only found a few articles of people reporting the same thing but no one is actually posting possible solutions, just bashing a legitimate concern. Hopefully I don't run into that here.....
Click to expand...
Click to collapse

A2CKilla said:
Not trying to be rude but.....
Click to expand...
Click to collapse
oh, no. I understand that's it fixed your issues. I was just saying, that was all the information we had, what you had left :angel:

simms22 said:
oh, no. I understand that's it fixed your issues. I was just saying, that was all the information we had, what you had left :angel:
Click to expand...
Click to collapse
Lol, it's all good, but yea, that wasn't the issue, doing now with wifi always on and battery drain is normal and doze is working properly, so probably a bad flash and factory reset fixed it, although I really wish there are ways around that

Maintenance update - gyroscope issues.

Hi
Does any of you experience gyroscope not working after a while on the new firmware 1.275 with maintenance update?
I turn the phone off and leave it for a minute and back on and it works.
Sent from my F8131 using XDA-Developers mobile app

Yes, i notice the issues too. It comes with latest update, and appears in random time every day

Hi.
Yes, I notice it too and find it annoying. As far as I can tell, this is a software issue and not hardware and to think that Sony would make such an error is incredible.
A reboot and it works for a short while, then back to not working again.
*shrugs*
kekePower

Is there somewhere to log the fault on phone or has anybody tried to do something with pc companion or do just have to what for them to fix it

Hi
I am on sw 1.238 only apps were updated no system update has been installed and i have the rotation issue as well.
I think one of the apps (i think one of the sony apps) is causing the problem.

HellRoot said:
Hi
Does any of you experience gyroscope not working after a while on the new firmware 1.275 with maintenance update?
I turn the phone off and leave it for a minute and back on and it works.
Click to expand...
Click to collapse
I just did the gyroscope diagnostic and I still pass. The ball just moves slightly more jerky than usual. I have not had any functional issues while in use. The phone has been on for 3 days currently.

Thanks for the feedback people... I was about to break my phone as I got pissed over this bad quality phone.
This being said, this will probably be my last Sony phone, they have made errors on every phone and lies regarding quality and photo.
A reboot helps, for a while
Sent from my F8131 using XDA-Developers mobile app

Same issue here.
Really annoying when taking photos...

chrisyuhc said:
Same issue here.
Really annoying when taking photos...
Click to expand...
Click to collapse
Sonys answer would be like..
You can restart our performance phone and open the camera again, you might miss the moment but trust in Sony... If you are able to take a picture then you are lucky as our touchscreen is a piece of cheap ****.
Enjoy our x performance, unmatched quality.
Sent from my F8131 using XDA-Developers mobile app

It is strange. I had this issue once. Since then there were these updates and I disabled a few apps, for example AR effect or lifelog (preinstalled "system" apps, which cannot be uninstalled without root).
My last restart was four days ago - meanwhile I took quite a lot pictures - no issues so far. If it helps by any means I can post my list of disabled apps - it might be at least a workaround...?!?

I had the same problem.
Did a sofware repair through companion and after the maintenance update again the accelerometer and compass stop working. Really seems to be a software bug with the new maintenance update.

webwude said:
It is strange. I had this issue once. Since then there were these updates and I disabled a few apps, for example AR effect or lifelog (preinstalled "system" apps, which cannot be uninstalled without root).
My last restart was four days ago - meanwhile I took quite a lot pictures - no issues so far. If it helps by any means I can post my list of disabled apps - it might be at least a workaround...?!?
Click to expand...
Click to collapse
Hi,
Please share your disabled apps. I would like to try to disable them.
Edit:
I have foun your list on sony support forum, thanks.
I will try to disable these apps one by one. Let's see which is causing the problem.
As i am still on 35.0.A.1.238 and never installed system update just the apps were updated i think one of the apps is causing the problem.

Hopefully it fixes your problem as well - maybe it was just coincidence, but I didn't have this problem for quite a while now...

Thanks.
My phone is still ok for like 15 hours without issue.
I have 2 apps disabled.
Avg since i bought the phone so this ia not a problem.
Playstation app
And the whats new is the factory version.

norberto_ said:
Thanks.
My phone is still ok for like 15 hours without issue.
I have 2 apps disabled.
Avg since i bought the phone so this ia not a problem.
Playstation app
And the whats new is the factory version.
Click to expand...
Click to collapse
:good:
It might be the combination. I did not touch "What's new" so far... as long as the issue seems to be solved, it's fine - but it might be interesting for our fellow guys, what exactly caused and / or cured it

I think this is caused by maintenance update provided a few days ago.
This updated system "memory" app, and uninstalling the update may fix the issue.
Go to: setting>app>all app>memory>uninstall update

My accelerometer stopped working.... but gyro working fine..... I tried service tests using *#*#7378423#*#*.....
just noticed this issue while I was trying to see the images in landscape mode.... waiting for 7.0

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!

shenlong85 said:
I think this is caused by maintenance update provided a few days ago.
This updated system "memory" app, and uninstalling the update may fix the issue.
Go to: setting>app>all app>memory>uninstall update
Click to expand...
Click to collapse
How to do this when it's like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Or is it wrong memory app
Thanks in advance
Sent from my F8131 using XDA-Developers mobile app

sfkaudi said:
How to do this when it's like thisView attachment 3911473
Or is it wrong memory app
Thanks in advance
Click to expand...
Click to collapse
You find the uninstall updates option in the top right corner menu. Click the three dots.
I just tried it. Keeping my fingers crossed...

Compass problem on Nokia 8 + Pie at SPL 1 Jan 2019

Hi, please be kind and redirect me to the right forum if I am in the wrong place.
I have a new Nokia 8 (TA-1012) automatically updated to Pie (SPL: 1 Jan 2019) when networking enabled.
Its compass points wrongly making it impossible to use Google Maps - I move sideways or backwards on it.
I spent several hours with the Nokia help-line clearing various system storage caches and data (I don't have record of what now) and finally doing a factory reset, all to no avail.
Then from Nokia help-line email suggestions, resetting app preferences, uninstalling Maps updates, stopping and disabling Maps, clearing Maps cache and data, and after restarting phone and enabling Maps again, updating Maps.
None of their suggestions, or re-calibrating the compass, seem to have fixed the problem.
Another compass app from Google Play also shows the compass pointing wrongly, often by 180 deg.
I've read of others with similar problems, have searched several XDA forums, but found no help yet.
So I'm starting this thread to collect together any knowledge that others may have on this issue.

Plz share all procedures and provide links ...
I also wanna downgrade to nougat

Same problem here, factory reset did not fix anything

There's discussion of the compass problem and reports of failed help from Nokia online-help on the Nokia Community Forum, but no sign of a fix from Nokia yet.
Some say a fix should come soon, others doubt it will come at all.
HTML:
https://community.phones.nokia.com/discussion/33528/compass-not-working-since-pie/
Unfortunately, although the help-line try hard, this problem is beyond them, it needs a proper coder to sort it out.
I remember a similar problem with CyanogenMod on the Samsung Galaxy SII, years ago.

Hi guys i can help us to get back to nougat, pie is HORRIBLE

HippyTed said:
Its compass points wrongly making it impossible to use Google Maps
Click to expand...
Click to collapse
All Nokia's community have been waiting for such fix since November 2018.

It's a known issue. There is nothing to do but wait until hopefully HMD releases a fix.
This, alongside the fingerprint scanner bug and the fact that the bootloader cannot be unlocked on Pie, made me lose all faith in HMD.

abelcowl said:
It's a known issue. There is nothing to do but wait until hopefully HMD releases a fix.
This, alongside the fingerprint scanner bug and the fact that the bootloader cannot be unlocked on Pie, made me lose all faith in HMD.
Click to expand...
Click to collapse
Just downgrade to oreo (see thread in this forum) and do the bootloader unlock. Afterwards upgrade back to Pie and voila. Done that already several times and always worked.

abelcowl said:
It's a known issue. There is nothing to do but wait until hopefully HMD releases a fix.
This, alongside the fingerprint scanner bug and the fact that the bootloader cannot be unlocked on Pie, made me lose all faith in HMD.
Click to expand...
Click to collapse
Well I finally received the next update for android Pie, to V5.140, SP2019-02, in the UK today and updated all my apps. The compass is still all over the place. And shame on Nokia, I sent two emails to Nokia Mobile Care <[email protected]> three weeks ago and have had no reply from them yet. What a disappointment, the phone ticks most of the boxes for me, but without navigation using a compass its going back for a full refund.

Sums up Nokia in a nutshell
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
HippyTed said:
Well I finally received the next update for android Pie, to V5.140, SP2019-02, in the UK today and updated all my apps. The compass is still all over the place. And shame on Nokia, I sent two emails to Nokia Mobile Care <[email protected]> three weeks ago and have had no reply from them yet. What a disappointment, the phone ticks most of the boxes for me, but without navigation using a compass its going back for a full refund.
Click to expand...
Click to collapse

We all here are waiting for compass fix since January!

HippyTed said:
Well I finally received the next update for android Pie, to V5.140, SP2019-02, in the UK today and updated all my apps. The compass is still all over the place. And shame on Nokia, I sent two emails to Nokia Mobile Care <[email protected]> three weeks ago and have had no reply from them yet. What a disappointment, the phone ticks most of the boxes for me, but without navigation using a compass its going back for a full refund.
Click to expand...
Click to collapse
The 5.140 version was released in February. It doesn't fix the compass or anything. We're waiting for the March/April update to (hopefully) fix the compass.

The March update fixed the compass issue. It's working properly now

That is good news for you. Here I still experience the same issue even after the update.
Model TA-1012

atsimeri said:
The March update fixed the compass issue. It's working properly now
Click to expand...
Click to collapse
you are the only person i have seen saying the march update has fixed the issue, everyone else is saying still not fixed.

Got March update today.
Not fixed confirmed.

I received the "March update" but the compass is still not working. Some days ago I rolled back to Oreo (following the steps found here on XDA) and the compass is working again. So definitely it's a Pie problem.

Have you guys tried to recalibrate the compass via engineering mode? *#*#372733#*#* then e-compass test
Literally was using it then the compass flipped south as north vice versa. Then after recalibrate, it's going back to normal.
I'm on TA-1004 though

Mine was inverted, the North kept on changing its position while rotating the phone.

As it turns out, recalibrating was just a temporary fix. Yes, it changes the north position all of the time.