I don't know if this is related to the app itself or the phone so I don't know if this is the correct place to ask. I'm using Sony's Lifelog app on my Z1 and it works as a total s**t. It measures everything but when I enter the app to see results, I have to press Refresh lots of times before it gets refreshed. Sometimes I even have to close the app and reopen it or just wait. There were several updates but the problem isn't fixed. Sometimes it starts working normally and after some time, same problems again. Now I'm trying to see my results but it won't refresh again. I keep pressing refresh, I get the "Refreshing" message which disappears after few seconds and that's it. I tried reinstalling the app, it sometimes fixes the problem for a short time and later it appears again.
It should be refreshed instantly. Is there a problem with my phone or this app is done by the worst programmers ever? I just can't understand how something like this can happen.
PS. Yes, my 3G/4G is on and fast enough. The same is with WI Fi.
Sent from my Sony Xperia Z1 using Tapatalk
Related
anyone experience Xperia V cannot wake up or hang in standby?
it happens at nite after i sleep. but when i wake up, i press the power button several times but the screen doesnt on. notification light is working and blinking.
only way is to remove battery. its been happening everyday. even alarm is not working. checked my backup(sms, call log), it didnt backup. :crying:
I at least dont have that problem. Is your phone stock? Rooted etc?
Sent from my LT25i using xda premium
I have this problem too. Not rooted. Probably, while charging this problem not appears.
Wrong section. This belongs in Q&A.
And for your problem, few users with.XT and XTX also reported similar problems. They are known as SoD (Sleep of Death).
There is no known fix yet. One users took it back to the store and the the Sony tech guru told him it's an isolated problem and he got a new one. So I suggest you go back to the store.
For anyone using adw launcher, one user reported that that caused his SoD. When he uninstalled that it was gone. Can be an app.
Try factory reset, and start first day without installing apps. And day by day add a new app, this way you can rule out if apps cause the problem.
Also format internal and external sdcard. Don't just empty them by wiping, you should really format, so no traces of possible app malfunction can be found back by the system.
Sent from my LT30p (Xperia T) using XDA Premium.
Did I help? please press thanks button
after several days of testing, it doesnt hang on mine for 3 days already.
i guess its because there is a additional line in build prop "dalvik.vm.heapsize=36m" that cause this? this also cause my Need For Speed Most Wanted to force close too.
i also increase min clock freq to 594MHz.
also run TempMonitor(paid) on my notification bar.
not sure the above method works for most of u.. but try if it works.
I've got this problem since the first day. Got the phone, booted it up without even installing a sim card/downloading anything, plugged it into the charger, and it froze.
Since then it would go a few days without freezing, or it would freeze 3 times a day. The freezing always happen in standby mode.
Since it froze on a fresh system with no apps installed, it can't be app-related. There are users who have never experienced this problem, so I suppose the only way is to return the phone or take it to your local sony service center.
Normally it would just hang there and you'd have to pull the battery out. There was once where it hung and the phone got incredibly hot, and battery would be drained really fast.
Currently I am experimenting with keeping WiFi OFF, and surprisingly the phone has been fine for 4 days straight without freezing now. Its just something I'm trying and by no means this is a fix, but returning the phone to a sony store isn't an option for you, you might want to see if this works for you.
for those still having SOD, maybe u can try this. not sure it helps or not. because before i install jellybean, i review the code in build.prop first. so that is why it didnt happen on me for 2 weeks. well, i test it out yesterday.
use either ES file explorer or Root explorer, go to system -> build.prop.
find this line dalvik.vm.heapsize=36m, put a # in front of it to disable this code.
it could be because there is another similar code, thus conflict. u can find another similar line at the bottom of build.prop.
hope it helps!
Have you had anymore sod since disabling that?
Sent from my LT30p using xda app-developers app
scythekain said:
Have you had anymore sod since disabling that?
Sent from my LT30p using xda app-developers app
Click to expand...
Click to collapse
before i install custom rom jellybean, i already disable that. didnt had any SOD since than.
but of cos 1 day i decided to test it out, and it SOD the next morning.
Hi,
I am trying to find a solution for a problem with the Xperia T camera, I tried looking through the forum but couldn't find what I had exactly.
When the camera app starts if you do nothing and just look around with it, it will just shut down suddenly, sometimes after only 5 - 10 seconds. The amount of time varies but is normally very quickly, and it is becoming very annoying with the app vanishing just as you are about to take a photo. There is no black screen, freezing, slow down during or after and no problem starting it straight back up.
It was on T_9.1.A.0.489 (Three) and I tried repairing it. The problem is still there after flashing 9.1.A.1.140 today.
Anyone have any ideas? Thanks.
wyterabitt said:
Hi,
I am trying to find a solution for a problem with the Xperia T camera, I tried looking through the forum but couldn't find what I had exactly.
When the camera app starts if you do nothing and just look around with it, it will just shut down suddenly, sometimes after only 5 - 10 seconds. The amount of time varies but is normally very quickly, and it is becoming very annoying with the app just vanishing just as you are about to take a photo. There is no black screen, freezing, slow down during or after and no problem starting it straight back up.
It was on T_9.1.A.0.489 (Three) and I tried repairing it. The problem is still there after flashing 9.1.A.1.140 today.
Anyone have any ideas? Thanks.
Click to expand...
Click to collapse
How are you starting the camera app? via the camera button or via the app icon in the app drawer?
gregbradley said:
How are you starting the camera app? via the camera button or via the app icon in the app drawer?
Click to expand...
Click to collapse
It happens after starting it from the lockscreen and from the camera button. I can't be sure about the app icon, I haven't really checked. It is my gf new phone, but I was using the camera recently when I needed to take some pictures and video at uni so I was the one who noticed it and she had pretty much not used the camera yet. She always gives anything that needs fixing to me, so that is why I am now looking.
I can try from the app icon later, don't have the phone with me just now.
Edit: Apparently it does not happen when launched from the icon, is this a feature then I take it?
I did actually wait and try it with my Xperia Z I got on Wednesday before posting here, in what was now a failed attempt at not looking stupid, and thought the Z was free of it but I have gone back and checked and it is happening but with a longer time before closing (Xperia T normally around 15 seconds although has been shorter, Xperia Z is around 30 seconds so I did not notice at first - and both are fine from the icon).
Is there any way to stop it, I would like to launch the camera conveniently without it timing out on me so fast (and the same for my gf who has an actual button like my last phone the Arc that did not do this).
I'm using the Xperia V running the latest Jelly Bean stock firmware (see my signature). I while ago, my phone started to spontaneously reboot itself, sometimes during standby, sometimes while I had the screen on. I know that others had this issue as well, but none of the threads I found were really helpful.
I can't really explain this, as I didn't change anything in he past couple weeks. The only thing that happened was that I once dropped from about 1m in our living room, but I doubt that that would cause such a problem.
As for software, I'm using the Aviate launcher, and I have Android Tuner installed which helps to keep my memory free and reduce battery usage. AT is set to kill background processes when the screen is turned off, and important processes are all excluded from that. But again, I haven't changed anything in the past couple weeks before the reboot issue suddenly appeared, so I doubt it's any of the software I use.
So, does anyone have any ideas as to what might be the cause of this? It seems to happen less frequently when using WiFi instead of 3G. Might 3G be the cause? (I'm just guessing wildly, I really have no clue as to what causes what in an Android phone.)
My xperia t reboots whenever I switch it off and I have to force turn it off. Try a software repair
Sent from my LT30p using XDA Premium 4 mobile app
OK say I have paired it with a Sony Xperia Z1 compact.
As soon as the screen turns off it loses connection with the phone. It still thinks it's connected (there is no cloud with a line through it on the watch face screen) and when you say ok google it tries to interpret but then I get the screen that says
disconnected and to the right is a little icon of a cloud with a line through it and underneath there are options for built-in functions like "show my steps", show me my heart rate" , etc
If I manually disconnect and reconnect using the Android Wear app on the phone it works again straight away.
Anyone else seeing this behaviour?
I had that problem right at the start. Can't remember how I fixed it
Restart both devices? Uninstall and reinstall wear app on phone? Update to latest watch firmware?
Do you have stamina activated which us turning your Bluetooth off on screen off?
Sent from my D6503 using XDA Premium 4 mobile app
skitty said:
Do you have stamina activated which us turning your Bluetooth off on screen off?
Sent from my D6503 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey that could be it. I do have stamina enabled because the battery in my phone is going down rapidly with the watch connected. I'll turn stamina off and see what happens. Cheers!
EDIT: I think this might be fixed now after turning off stamina mode. I'll need to test furtehr thugh. Thanks skitty
I'm still getting this quite a bit. Is anyone else still experiencing random bluetooth disconnects? It still thinks that they're connected until I try to do a google now search and then it tells me they're disconnected. I tried uninstalling the wear app on the phone and reinstalling. I also cycled bluetooth and that seems to fix it in the short term. Suggestions?
shadeofgrey said:
I'm still getting this quite a bit. Is anyone else still experiencing random bluetooth disconnects? It still thinks that they're connected until I try to do a google now search and then it tells me they're disconnected. I tried uninstalling the wear app on the phone and reinstalling. I also cycled bluetooth and that seems to fix it in the short term. Suggestions?
Click to expand...
Click to collapse
I'm pretty sure, for me, the answer was to disable stamina mode on my xperia phone. I very very rarely see the disconnected message any more.
Cycling BT also used to help for me but all that was doing was temporarily foxing the stamina setting. It always switched itself off again.
I'm having the same issues, here's my post in the general android wear help forum
"So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?"
I have also tried running stock faces vs custom with no change
hasn't happened since 9:00 this morning.. today... yesterday I missed almost every notification
disconnect
Not sure if this is related or if anyone can give advice but for me (HTC one max) whenever my Samsung gear live is disconnected from phone...phone randomly restarts all by itself. Tried factory reset, was fine until I set it up again. Made sure android wear was off...just tried turning off Google now see if that helps.... Anyone else experiencing the restarts? Sorry on phone so messy post...
Woah sorry i forgot about this post. My issue was the stock kernal for cm11. When i switched to another kernal, my issue vanished.
I am having the issue where if my phone is asleep I cant do any searches. Now I know or at least I'm pretty sure that its not the watch or the app but something on the phone. Phone is a galaxy note 3 sprint version running temasek's unofficial cm12 rom. The watch is stock of course. When I get a notification the watch will happily wake up and tell me about it, but when I try to tell the watch a command with the phone sleeping is where the problem presents itself. The issue appeared after a few of the rom updates (happens even with a clean install) and I know he's a busy guy (temasek) but I would like to see if anyone here could help me figure it out to be able to provide a solution to others that are having my same issue. Any and all help is appreciated.
Hey guys,
I am using my Moto X (XT1052) for almost 2 years now. It is/was the best android phone I've had so far. It was smooth, had no hangs and just did what it was supposed to do. Since I received the Update to 5.1 I keep on having real strange issues and it really bothers me because it really renders the phone useless at times. And since I couldnt find another thread with all bugs collected in one place, I am going to start my own thread.
So which bugs did I find so far?
1.Youtube and other video services don't work all the time
(They work sometimes, but the the video stops, tries to resume and ends up in a loop trying to load the video. Often only a reboot helps.)
2. Battery consumption in general has become way worse (cell-standby)
3. Random "Optimizing apps" after a reboot
4. No Active Display with handsover (I know this isn't a feature anymore, but to me this is a bug as well)
5. Missing energy widget
6. Wifi range has reduced significantly and seems to be buggy at times (can't always tell if it's my router or the phone, but mostly it's the phone)
7. Sometimes the phone uses mobile data instead of wifi, even if connected
8. Vibration mode (important notifications only) doesnt always end properly and the phone doesn't start vibrating again after the set time or alarm
I think that's it for now. But this clearly is enough for me.
So please Moto guys do something! If you need logcats or anything else, let me know and I ll help out as good as I can. I was one of those who patiently waited for an update instead of crying for one, because I wanted a stable one rather than a fast and unstable one. So either fix it, or I ll have to return my Moto X. The phone in its' current state is useless for me. Especially as I can't even downgrade without having to risk a full brick. So please do something and push an update to either allow downgrading, or fix the existing bugs!
Sent from my XT1052 using XDA Free mobile app
N00BY0815 said:
Hey guys,
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
I miss this very badly
"No Active Display with handsover"
Now I have to tap or take my phone to see notifications... :crying:
I switched over to CM and all is going great of course at a small cost of losing Moto voice feature but I can most certainly live without it. I've got very decent battery life of 5-6hours of screen time over a span of 13hours. No over heating issues and usually cell standby sits at 2% usage which is absolutely fine for me.. Even the hand wave gesture works with active display. I'm so happy with how stable it is with CM. Living with a bug free phone for now.
Sent from my Moto X
Random Crashes followed by optimization boot
I have been getting random crashes that lead to the phone shutting off. When I turn it back on, it takes FOREVER to optimize 92 apps. I don't have even 30 apps on the phone!
I did a factory reset and still have this problem. It's happening every couple of days. It's making my experience with this phone very frustrating!
Some more issues I've found:
Soundproblem, sometimes when I switch e.g. from twitch to spotify and then try to increase or decrease the volume, I get a crackling sound every time I push the button. Sometimes it disappears after a certain time of not playing anything, but mostly again only a reboot helps.
The phone unlocks itself more often in my pockets for no obvious reason.
The unlock on the ActiveDisplay unlockscreen often only leads to the normal unlocking screen instead of the homescreen. Same thing when I try to open notifications. Mostly those apps run, but I get to see the normal lockscreen, instead of the app with the notification.
Sent from my XT1052 using XDA Free mobile app
I think I found a fix for the YouTube problem.
Press the power button and keep it pressed till you feel another vibrate ie. After the power menu pops up.
That seems to solve it
Sent from my XT1052 using Tapatalk
adity said:
I think I found a fix for the YouTube problem.
Press the power button and keep it pressed till you feel another vibrate ie. After the power menu pops up.
That seems to solve it
Sent from my XT1052 using Tapatalk
Click to expand...
Click to collapse
Well that's not exactly what I would call a fix it appears to work sometimes though. I also noticed that simply changing the video quality from let's say 720p to 480p often resolves the issues. I mostly get the video bug, when I am trying to watch things in 720p or above. Maybe it is a codec problem? A broken lib?
Sent from my XT1052 using XDA Free mobile app
For YouTube, you could get another app. I stopped the cell standby issue by turning off carrier internet when not needed. Install greenify, servicely, battery saver, and power nap. 1 I too have random optimizing of apps. 2 pocket dials have increased, 3 if I tap on the phone icon from messaging app to make call to that person, I have to exit out of the SMS app before I see the call screen. 4 sometimes when I'm multi tasking I go back to another app but the app reloads and doesn't take me to where I was. 5 Google now voice only responds 30% of the time when i say hello google. Some other problems I have noticed but can't think of right now
---------- Post added at 12:41 PM ---------- Previous post was at 12:38 PM ----------
Good thing I waited for a version that I could go back to kit kat because it didn't update the bootloader to lollipop. This is the thread if anyone is interested. I flashed this rom for xt1053 on my Rogers xt 1058, with only speaker phone not working away from WiFi for some reason, but that's if you flash on another moto x besides xt1053. http://forum.xda-developers.com/showthread.php?t=3155843
1. Battery drain (cell standby) makes the phone unusable.
2. WiFi does not connect or only works rarely now.
- download two times on whatsapp
- dialler doesnt dial a call
Sent from my XT1052
Cell Standby Battery drain is the worst..
Randomly restarting and optimizing apps has been a huge problem as well.
I miss the wave to wake for active notifications...
But what I really hate about 5.1, is that when using wifi my mobile radio keeps active all the time...
This drains the battery while being on wifi...
Funny enough, when I'm on mobile data, everything is ok and mobile radio is active only when needed by the apps...
On wifi on the other hand, oh man... it's active all the time...