Location icon doesn't go away - Sony Xperia XA2 Questions & Answers

The icon is stuck in the statusbar, even when location is off. I tried evertyhing: changing permissions, uninstalling every app and even a factory reset. It solved the problem for a couple of days but then the icon came back. I went the extra mile and installed a custom rom without gapps, same result. If I reboot the smartphone when location is off the icon goes way, only to pop back as soon as I turn on location services.
Other Sony smartphones had this problem but it should have been fixed, am I the only one experiencing this on the XA2?

Related

[Q] GPS stays on all the time.

it is to my understanding that you should be able to turn on GPS satellites on, and it should only run on demand. aka when you open Google maps it comes on, close maps and it goes off. For some reason my GPS and icon stays on all the time unless I turn it off manually. every time I install a Sense 3 ported ROM, I wiped and never restored anything with titanium. I turned on the GPS and it was activated and wouldn't go off till I turned it off. I froze all system applications with titanium and it still stayed active. Anyone know or know where I can find a fix please. tried Google but most posts about the problem date to 2010 and are irrelevant to fixing my problem.
If your using a pure Sense 3 rom, CoolSensation or what ever it's called, expect bugs. The only way to tell if it's a rom related problem is flash another rom and see if that works fine.
Well it turned out be an application as to why it came on after a full wipe and no restore I can't say but I uninstalled it and re-installed it again from the market and problem is fixed. thanks for your reply.

Phones freezes for 2 second then reboots, once a day, immediately after waking up

I've had this problem sometime over a month now, can't remember if I did anything to make it like this. I made a post somewhere about it happening the 17th of May, so it started somewhere before that.
My phone will freeze for 2 seconds and then reboot itself.
It started while I was on stock 4.0.2 and now I'm on stock 4.0.4 IMM761. I have a GSM Galaxy Nexus.
It only happens just after the phone has been woken up and something is started. The most common (as it's my go-to-way of forcing it, to see if it's still there) is after waking up the phone, sliding down the notification bar and pressing "settings", which doesn't open but the phone freezes and reboots itself. I first discovered this when I wanted to go in there to change screen brightness. It's also happened when I went into the notification bar and pressed a battery app there. It doesn't matter if I'm doing it in the lock screen or after the lock screen.
It's also happened when I wake up the phone and enter the camera through the lock screen.
It also regularly happen if I set an alarm in the morning. When my alarm is suppose to play it freezes and reboots, and when it's rebooted, the alarm has been cancelled without ever playing.
It doesn't need to wake from deep sleep to do this, I've had it happen mere minutes after trying to see if it's there.
I don't know if it has something to do with this, but the 21st of April I tried to do the "clear google services framework" trick to force 4.0.4 ( I was on yakjuxw), but it did not work and I remember my phone acting janky and I was scared it messed something up, but I seem to remember it getting better. I can't remember what exactly it did though.
I've read that 4.0.4 would fix the reboots that a lot of people were having (don't know if it was the exact same kind of reboots as mine) so I did this to make my phone a yakju (translated from Danish):
http://translate.google.dk/translat...at-modtage-opdateringer-til-din-galaxy-nexus/
I did that the 8th of June, and it worked flawlessly and I was on 4.0.4 IMM761 in no time. Unfortunately it did nothing to stop these reboots.
As part of the process of making my phone a yakju I, of course, did a complete factory reset, although I did make a copy of my entire SD and transferred everything over again after the process.
These past two weeks I've tried the following to fix it:
Clear cache partition in recovery.
Clear google services framework.
Clear media storage.
Tried to uninstall many apps, 2-3 a day, to see if they were causing it, re-installing them when I still had the same problem. If it's an app causing this I've yet to find it, but I find it weird that an app could be causing this.
It happens once a day, but never close to each other. It seems that some time has to pass before it can happen, and it only ever happens just after the phone is woken up, either by my alarm or by me opening the notification bar and pressing something there.
Please help me, this is unbearable.
Another thing, yesterday I tried to let it run without me pulling down the notification bar and pressing "settings", which would set off the freeze-reboot. I found that my phone would not freeze-reboot but very often it would "reload" app icons and widgets when I went around my homescreens. Where I can only see my wallpaper for half a second and then the icons/widgets appear. It would do this very often throughout my 1day 5hour uptime, and a couple of times I would try to force the reboot (by pressing "settings" in the notification bar), after the icons/widgets did the invisible/load thing and it didn't reboot. This must have something to do with it?
hi,
experienced this on my nexus s back then what i did is from recovery>mount and storages>formatted system, boot, and everything else except sd card.then it was all gone.btw you will have to flash your rom and kernel again as this is a full wipe.hope i helped and do this on your own risk
daff
bump
did it cure your reboots?
daff
dark06 said:
did it cure your reboots?
daff
Click to expand...
Click to collapse
I haven't tried that yet. I'm trying a "RAM booster" app to see if that helps, but that doesn't sound too stable even if it does.
I'm going to do a full factory reset and installing nothing, or moving anything to the SD, and just let it run like that to see if it works.
Just writing an update for anyone googling themselves here with the same problem, I had it resolved.
I found out that if I didn't force the reboot (by turning on the phone and quickly pulling down the tray and pressing something there) it could last a long time with just the launcher resetting, but it would lead to complete freezes (anywhere I was on the phone) and would require a battery-pull.
My plan was to wait for jelly-bean before doing another factory reset, I got the JB update and it completely removed the problem. I still don't know why the problem suddenly started or what caused it, all I know is that the JB update fixed it, and the update is fantastic, my phone's never been better.

Google Nav crashing with flashing white/black screen

got an issue with the google nav app crashing on me.
a little background first though.
had this issue on the std rom, and tried flashing the current ARHD 31.3 rom in the hope of fixing it, it hasnt!
from a fresh boot, i can go into the google maps app, choose a location and then use the nav app go to there, no issues at all.
next time, i open maps, no issues at all, choose my location, and as soon as i hit start navigation, the nav screen opens, showing the next turn to make at the top, the voice is telling me where to go, but the main map screen, is flashing black and white.
it flashes like that for 5 or 10 seconds before crashing, the only way to restore navigation to a working state is to reboot the phone.
its getting rather annoying now, as i dont use the nav very often, i tend to need it occasionally, and its irritating to have to reboot the phone just to get the nav working.
as far as i am aware, the GPS works fine in everything else, (Maps, strava, gps test) it just seems to be nav thats causing the issue.
i've already tried clearing the cache from settings, apps, clear data, but i still get the same issue
any ideas on what might be causing this
cheers
sning said:
got an issue with the google nav app crashing on me.
a little background first though.
had this issue on the std rom, and tried flashing the current ARHD 31.3 rom in the hope of fixing it, it hasnt!
from a fresh boot, i can go into the google maps app, choose a location and then use the nav app go to there, no issues at all.
next time, i open maps, no issues at all, choose my location, and as soon as i hit start navigation, the nav screen opens, showing the next turn to make at the top, the voice is telling me where to go, but the main map screen, is flashing black and white.
it flashes like that for 5 or 10 seconds before crashing, the only way to restore navigation to a working state is to reboot the phone.
its getting rather annoying now, as i dont use the nav very often, i tend to need it occasionally, and its irritating to have to reboot the phone just to get the nav working.
as far as i am aware, the GPS works fine in everything else, (Maps, strava, gps test) it just seems to be nav thats causing the issue.
i've already tried clearing the cache from settings, apps, clear data, but i still get the same issue
any ideas on what might be causing this
cheers
Click to expand...
Click to collapse
Had this too on CM, thought it had something to do with the ROM but after reverting to stock exactly the same issue. You're not alone
http://forum.xda-developers.com/showpost.php?p=46517908&postcount=15438
Any update on this issue? I have exactly same issue on stocked One X with Sense 5.0, Android 4.2.2.
I have exactly the same problem. I'm wondering if it's a Sense or app issue. Either way, I submitted a bug report.
Sent from my HTC One X using Tapatalk
I turned off the hardware overlay in the Developer section, and it seems no problem anymore... Not thoughtfully tested yet, tho...
Still flashing and crashing HTC One X+
Google maps to navigation is still flashing and crashing - even after turning off hardware overlays.
Works 1st time after reboot. If I swipe the app away from recent apps screen, then it starts failing.
3rd time I start it, working again, but I figure it's going to happen again.
AT&T HTC One X+ phone,
Android 4.2.2, Sense 5.0,
SW number 2.15.502.1,
HTC SDK API level 5.41,
Kernel 3.1-10-gf4d5f91
build number 2.15.502.1 CL280456
Anyone ever get an answer to this? Last post I found was December 2013 and still nothing.
delete this
I think I've found a kind of workaround to prevent this problem.
When you search the location you want to reach, and you are faced to the tile with these info:
8 min (3,1 km)
some info about trip
[MAP]
Start navigation
Instead of click on "Start navigation", click on "8 min (3,1 km)", then when the map is open, click on "Departure" and maps should not crash.
I hope the explanation is enough clear, I've translated texts from the italian app so I'm not sure if I've did it in the right way.
fez vrasta said:
I think I've found a kind of workaround to prevent this problem.
When you search the location you want to reach, and you are faced to the tile with these info:
8 min (3,1 km)
some info about trip
[MAP]
Start navigation
Instead of click on "Start navigation", click on "8 min (3,1 km)", then when the map is open, click on "Departure" and maps should not crash.
I hope the explanation is enough clear, I've translated texts from the italian app so I'm not sure if I've did it in the right way.
Click to expand...
Click to collapse
Totally works! Thanks!
HTC One X
Cyanogen 10.2.1
I was so annoyed with this...
I have had this problem for the last year using the stock, rooted AT&T Rom for my HTC One X + My wifes phone that is an HTC One X does not seem to do this. I found when I removed the maps update it worked well. When it updated it seemed to work a few times then the flickering and crashing started up again.
I tried the other suggestion above.
Finally I noted that when I clicked on start nav and as soon as it tried to open the map if I hit the power button and waited a second and turned it back on the image was stable. Sometimes I couldn't catch it before it crashed but if I did it would do the trick.
Why doesn't google fix this?
Same here. One X with rooted stock ROM.
When the flickering starts, i turn off the screen and then back on. This works for me in most situations. Still really annoying.

Random reboots

Status: stock rom, rooted, elementalx kernel.
I've been facing random reboots at least once a day. One way I can force a reboot is opening up Android Device Manager on my phone and it will reboot while looking for location.
I feel the Adm problem is relevant as the few times I caught my phone before a random reboot is a "G" logo icon in the notification bar which i'm guessing is Google now icon.
Can someone confirm that is the icon as I'm unable to Google for it.
I've tried freezing the Google Now app in titanium backup today, a few hours later I got into a bootloop where my apps were suddenly being re-cached "optimizing apps 1 out 100".
Anyone facing a similar problem?
Bump
queerquirks said:
Status: stock rom, rooted, elementalx kernel.
I've been facing random reboots at least once a day. One way I can force a reboot is opening up Android Device Manager on my phone and it will reboot while looking for location.
I feel the Adm problem is relevant as the few times I caught my phone before a random reboot is a "G" logo icon in the notification bar which i'm guessing is Google now icon.
Can someone confirm that is the icon as I'm unable to Google for it.
I've tried freezing the Google Now app in titanium backup today, a few hours later I got into a bootloop where my apps were suddenly being re-cached "optimizing apps 1 out 100".
Anyone facing a similar problem?
Click to expand...
Click to collapse
Is this something you can replicate while using the stock software? Fastboot flash the factory images and test that out. I cannot replicate this using Android Device Manager. I use Ex kernel on stock and see no random reboots.
I don't recall ever seeing a "G" icon in my notification bar. From memory, the only times I have a Google Now notification are from my sports teams, weather, and traffic updates. Long press on that "G" icon and see where that is coming from.
SlimSnoopOS said:
Is this something you can replicate while using the stock software? Fastboot flash the factory images and test that out. I cannot replicate this using Android Device Manager. I use Ex kernel on stock and see no random reboots.
I don't recall ever seeing a "G" icon in my notification bar. From memory, the only times I have a Google Now notification are from my sports teams, weather, and traffic updates. Long press on that "G" icon and see where that is coming from.
Click to expand...
Click to collapse
I suspected it was Groupon and I uninstalled that app, so far no more reboots.
I can't press the icon notification even if I wanted to, all I saw was the G logo appearing in my notification bar and then a reboot right after.

Can't setup internet after factory reset (stock MM H815T)

I had been playing with some settings in the hidden menu and developer options sometime before this problem began but AFAIK I returned everything back to default and the phone was working fine for a while afterwards. So I am not sure exactly why the Wifi and bluetooth stopped working. When I dragged down the notification bar to toggle the Wifi icon it just flashes like a strobe light and never turns on. If I go to toggle the slider in the Settings menu, it's either greyed out, or immediately slides back to Off. Discovered that the bluetooth also did the same thing, but Data connection still worked. Also for some reason the phone now took a solid 60 seconds to boot up when it used to take 30 or less.
I did a factory reset in case I had overlooked changing some option back to default, and when that didn't work I flashed stock ROM H815-20g-00-1023 (I'm ~ 95% sure it was running 20g to begin with but it might have been another letter instead) with LGUP. But the problem still persists --- I can't complete the LG setup process because the page for setting up the internet connection is either completely blank or if it does come up the checkbox for Wifi is greyed out... and even if the mobile data option is able to be selected the setup wizard will not let you proceed without Wifi.
Any idea what might be the problem and how to fix?
Many thanks!
I've looked every which way on Google for possible solutions but none of them match the scenario I'm describing. Is this really a problem that no one else has ever had? :-O

Categories

Resources