Related
Guys,
I know there have been many posts relating to WiFi and Sleep Mode (I've read them!) but regardless of what settings I use and whether or not I use an application like Wi-Fi Keep Alive, I still cannot keep wireless on when my screen is off.
I have tried starting the copy of a big file from my PC to my android wirelessly. Then when I turn off the screen, the file continues for about 15 seconds and then dies. I have also tried streaming music over the internet....again this works for 15secs after the screen has been turned off and then dies, only to reconnect when I turn the screen back on.
Can ANYONE help me with this. I have tried Wi-Fi Keep Alive, Wi-Fi Fixer, and the stock settings all with no success.
I have a stock 2.2 Nexus One.
EDIT: Just realised that this should be in the Q&A forum - apologies.
Please help me - I miss being able to stream net stations on the move!
Tried a non-stock ROM? There is a fix that should be in any recent AOSP ROM.
Thanks for the reply - I don't particularly want to flash a custom ROM. Is there any other fix for this issue that can be applied to the Stock ROM?
I've had this problem with every rom I've tried, its frustrating and it looks like there is no hope.
Ya I have this problem been annoying for stream with Pandora, its a hardware problem and nothing has worked for me. But I use screen on widget from the market to keep the screen on temporary until I don't need wifi, and also I use the stock clock app dim the screen even more than normal while streaming to waste less power on the screen. But there no way to fix it atleast for me.
Sent from my Nexus One using XDA App
Hi, with stock 2.2.1, I experience phone having blackscreen. How it happen. I press on the wake button, nothing happen. Press again, the phone wake, and sleep... lol. I have no problem in auto reboot and shut down, only this problem...
Anyone face this too?
Sent from my LG-P990 using XDA Premium App
Isn't this the BSOD everyone always goes on about?
Apparently it happens to a lot of people.
Meltus said:
Isn't this the BSOD everyone always goes on about?
Apparently it happens to a lot of people.
Click to expand...
Click to collapse
Is it? i thought everybody was experiencing reboot and shut down...
xxdoggyxx said:
Hi, with stock 2.2.1, I experience phone having blackscreen. How it happen. I press on the wake button, nothing happen. Press again, the phone wake, and sleep... lol. I have no problem in auto reboot and shut down, only this problem...
Anyone face this too?
Sent from my LG-P990 using XDA Premium App
Click to expand...
Click to collapse
i also had this problem with Stock ROM when i bought my phone, 2 hrs later i flashed MCR ROM - no problem anymore
How come you have 2.2.1??? update to 2.2.2...
Sent from my LG-P990 using XDA App
xmoo said:
How come you have 2.2.1??? update to 2.2.2...
Sent from my LG-P990 using XDA App
Click to expand...
Click to collapse
No idea... I bought my phone at the earlier earlier batch, where it is pack in bubblewrap... LOL!
Anyway, at 2.2.2, still same problem. Doesn't want to get custom rom, as after my exam, i'm going down to LG and get some servicing or shyt out from them...
The problem exist especially when you are charging. It occur also when you put your phone to sleep while running on GPS. Very fedup with it.
It is categorized in Freeze and Reboot Problem
It's the first stage of that problem, if you continue using it, you will suffer the reboot problem
xxdoggyxx said:
Hi, with stock 2.2.1, I experience phone having blackscreen. How it happen. I press on the wake button, nothing happen. Press again, the phone wake, and sleep... lol. I have no problem in auto reboot and shut down, only this problem...
Anyone face this too?
Sent from my LG-P990 using XDA Premium App
Click to expand...
Click to collapse
Sorry to hear that for you but, it happens to a lot of us the Freeze called BSOD (Black screen of Death)
Welcome to the happy LG owners club called BSOD...
also known as sleep of death
Welcome to join BSOD.
Sent from my LG-P990 using XDA App
Oh. BSOD. Haha
Maybe you just can change the rom and wait LG update.
Sent from my LG-P990 using XDA App
black screen on wake up after sleep... lcd display hardware fault
i have two optimus 2x
one works perfectly ,The second has this problem ..when the light goes out and pressed the power button to wake up screen is black... can see only light
i open both and i change motherboard between them
the problem remained at the same display whit the other motherboard from the one who work perfectly
conclusion...i ordered another lcd
ali_alex said:
i have two optimus 2x
one works perfectly ,The second has this problem ..when the light goes out and pressed the power button to wake up screen is black... can see only light
i open both and i change motherboard between them
the problem remained at the same display whit the other motherboard from the one who work perfectly
conclusion...i ordered another lcd
Click to expand...
Click to collapse
Damn you crazy!
I had this issues once. Never after.
xmoo said:
Damn you crazy!
I had this issues once. Never after.
Click to expand...
Click to collapse
i had this issue after flashed mcr rc17 never before,in the first time i belive that this rom has the issue but ...flased back to stock and the problem remain the same,tried different 11 stock rom and no way !
after i make the change !
i have still the original dual and have all of the reportet problems.
Reboot, Shut down and Black screen
net
solution to some bsod models. Tested, working!
Many p990 bsod models have faulty soldering of some sort. A solution which have worked for many is to simply plug in your charger. When your phone goes to sleep and doesnt wake up when you hit the power button, just leave it be for 12+ hours. Place your phone on something soft as well, like your bed. This will heat up the device and fix the faulty soldering. If it does not work, try longer period of charging. Good luck. (I will take no responsibility if this does not work as planned)
This was tried on a bsod model which went to unresponsive sleep every 5-30 minutes. After this procedure it was faultless
killacan said:
Many p990 bsod models have faulty soldering of some sort. A solution which have worked for many is to simply plug in your charger. When your phone goes to sleep and doesnt wake up when you hit the power button, just leave it be for 12+ hours. Place your phone on something soft as well, like your bed. This will heat up the device and fix the faulty soldering. If it does not work, try longer period of charging. Good luck. (I will take no responsibility if this does not work as planned)
This was tried on a bsod model which went to unresponsive sleep every 5-30 minutes. After this procedure it was faultless
Click to expand...
Click to collapse
Lol... Solder have melting point of at least 90℃. I don't wanna melt my phone..
Sent from my Optimus 2X using XDA Premium App
have u tried not to sleep your device when charge?? settings->applications->development->stay awake
I've had my LG for quite some time now and I still trying to figure it out. So, if you're patient enough, please, just bare with me for a while as I explain what I've tried so far what what were the results.
A lot of people complains about this phone... unstable, crashes, reboots, BSOD, etc...
The first problem I had, came with the stock ROM... after a while the Wi-Fi just stopped working and it would display "Error..." as a message. The only solution was to reboot. 3 or 4 days after I had bought it, this was already killing me... so I started trying other ROMs but all seemed to suffer from some sort of problem except for one (see phone info below), which I've been running since June and I find it impeccably stable I can basically keep my phone running for as long as I want, as long as the battery doesn't run out (obviously), which brings me to a second point... battery drain!!
The battery drain was the only problem I didn't manage to find a solution for... and after a certain while, even though my phone was stable, having to charge my phone every single day was becoming very annoying.
Since I live in a different country than my GSM operator, it doesn't come as a news flash that network look-up has a big impact on the battery life, specially because I live close enough to the border to be able to keep the signal but in some parts of my house the signal is lost forcing the phone to search for a new network, which sometimes it finds (roaming) and sometimes it comes back to the original network and so on... However, what I find, unarguably, to have the biggest impact on the battery is having the Wi-fi enabled when there's no available network, it's just huge, it can suck up the battery in a few hours...
So, I decided to try some of those power management apps such as Locale, Green Power and some other, in order to minimize these problems, but curiously, they all caused the same problem... BSOD within a matter of minutes. I installed the app, configured it, waited for the phone to go into sleep and puff... it was gone. The only way out of it was removing the battery. I uninstalled the app, and the phone was stable again... this happened with every single app of the kind, that I have tried.
At the moment my phone is as stable as it gets but if I don't pay it enough attention, the battery dies in a blink of an eye.
Model number: LG-P990
Android version: 2.2.2
Baseband version: 1035.21_20110614
Kernel version: 2.6.32.28-mck-r14-ocuv
Build number: FRG83G
LGE version: 19/5-11 MoDaCo FR17 Fear Edition 10
Any suggestions will be more than welcome.
Cheers!
As stated, screen will not go off via timeout or power button tap. Power button is recognized and will bring up shut down menu like normal.
Device is rooted (thanks DG) and had been running well for over a week. Defrosted all apps from tibu in case I got over zealous but no better. A factory reset has not cleared it up either. Hoping the oneclick from the root package will correct the issue, but thats not until I get home later this evening.
Has anyone experienced / recovered from this issue?
Smart stay is turned off
I've had noticeable lag like a few seconds and sometimes I wonder if it's going to shut off but it always does. Better set a dark lock screen wallpaper to conserve your battery
Sent from my SAMSUNG-SM-N900A using xda app-developers app
I know this is kind of basic, but what is your setting here:
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Thanks for the thoughts.
I had already gone through the standard - double check the settings, remove recent apps. When all that failed and a factory reset still didn't clear it up I was beginning to worry about some kind of hardware damage (don't see how since I treat it better than my child ).
Fortunately the one click from the root seems to have restored proper operation. Back to rooting and rebuilding!
3496255310
papashex said:
Thanks for the thoughts.
I had already gone through the standard - double check the settings, remove recent apps. When all that failed and a factory reset still didn't clear it up I was beginning to worry about some kind of hardware damage (don't see how since I treat it better than my child ).
Fortunately the one click from the root seems to have restored proper operation. Back to rooting and rebuilding!
Click to expand...
Click to collapse
I'm having the same problem, I rooted through vroot.... what do you mean one click fixed it little my incite would be helpful....
thank you
Mine just did this, scared the hell out of me It also didn't go into deep sleep before it started. (Not rooted).
Pulled the battery, waited 30 seconds, plugged it back in.... same thing. Waited a few minutes, seems to have sorted itself out.
Scary....
This is definitely a software bug and it is related to the Headphone detection bug that people are having too (it's actually the same bug causing both issues). This happens to me quite often after I restart my phone. It's kind of like the phone hangs during the startup process. I've also noticed that the wifi/bluetooth status that was present before restarting the phone (i.e. whether they on/off) doesn't get applied until the bug sorts itself out.
For me sometimes this works: open an app like Chrome and then hit the home button to get back to your launcher. This works 95% of the time for me. I'm wondering if it has something to do with not having Touchwiz set as the default launcher.
I'm experiencing this same problem. If I don't manually turn the screen off by tapping the power button, the screen will not timeout.
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.
So I'm on 5.1 stock and this is really annoying me now. Wi-Fi switches off randomly when screen is off. Wi-Fi always on is checked. Any suggestions?
Sent from my XT1095 using XDA Free mobile app
Is the battery saver option turned on? If so is it starting up to save your battery and killing wifi?
I'm also having this problem. My wifi is configured to aways on, I'm not using any battery saver and even initialized my device in security mode, but the problem continued, so it is not a 3rd party program problem. I even posted on official Motorola forums (and on a lot forums through the internet), but no one could help. I guess it is a bug on 5.1 because I didn't have this problem on 5.0.
I installed a program to solve this problem, but it needs to keep running:
https://play.google.com/store/apps/details?id=com.roamingsoft.manager
Use the wifi repair option. This is the only way that I find to solve this problem. I hope they fix it on the next version.
Sorry for my english.
muiriddin said:
Is the battery saver option turned on? If so is it starting up to save your battery and killing wifi?
Click to expand...
Click to collapse
Nope. No battery saver mode.
Sent from my XT1095 using XDA Free mobile app
pulley06 said:
Nope. No battery saver mode.
Sent from my XT1095 using XDA Free mobile app
Click to expand...
Click to collapse
I tried a few things to investigate this and without root on my device I'm potentially unable to get to logs that we could then compare. So since that approach didn't work, I have some environmental questions. Does the problem occur when you are carrying the phone in your pocket, or when it sits on a table unused for a period of time (or both). I'm trying to eliminate shaking causing the issue. You also mention that it happens with the screen off are you sure that it only occurs in that situation (that is a strange detail).
I can confirm this. It is as if the Wifi Always On setting did not work. When screen sleeps, 3G/LTE kicks in. When you wake the phone up, it'll go from 3G/LTE to Wifi. This has indeed arrived with 5.1, as 5.0 did not have the issue.
muiriddin said:
I tried a few things to investigate this and without root on my device I'm potentially unable to get to logs that we could then compare. So since that approach didn't work, I have some environmental questions. Does the problem occur when you are carrying the phone in your pocket, or when it sits on a table unused for a period of time (or both). I'm trying to eliminate shaking causing the issue. You also mention that it happens with the screen off are you sure that it only occurs in that situation (that is a strange detail).
Click to expand...
Click to collapse
Yeah it only occurs when the screen is off. The minute I switch on the screen I can see that it goes from mobile data to Wi-Fi even if Wi-Fi is on. Also, it is irrespective of where my phone is pocket or on a table top.
Sent from my XT1095 using XDA Free mobile app
I have a XT1094 (Moto X 2014) and have not noticed this. Based upon a post above you have the XT1095. We have the same Android version, just a different carrier version of the hardware. It sounds like when your device is going into one of the lower power states (the screen going off etc), the wireless is erroneously included in that transition. On my tablet I had a similar issue in that going to a lower power state would kill the sdcard which would then not properly reconnect when coming out of that lower power mode. If you prevented the tablet from going into that lower power state, the sdcard problem would not occur. Unfortunately the side effect was worse battery life in that case.
Do you have root on the device? If you do you might be able to do do a test similar to what I did on the tablet, however it would only prove the theory not solve the problem since worse battery life is an ugly trade off for a phone and the only way to actually change the sleep state transitions was to build a modified kernel that changed the sleep state itself (for my LG tablet one of the developers solved the issue and I just used the custom kernel provided)
Info on the "Sleep State" C-State is here https://plus.google.com/+PaulReioux/posts/9R8fjQdHDXD
For the tablet I had to disable the C3 (power collapse) sleep state, my post over there: http://forum.xda-developers.com/showpost.php?p=57719782&postcount=138
No idea if this will help...
I have an XT1095 stock 5.1 un-rooted, and I do not have this issue. I remember reading a similar thread here when 5.0 came out, so this is not a problem specific to 5.1. I don't know what is causing it, but it is clearly not a universal problem.
muiriddin said:
I have a XT1094 (Moto X 2014) and have not noticed this. Based upon a post above you have the XT1095. We have the same Android version, just a different carrier version of the hardware. It sounds like when your device is going into one of the lower power states (the screen going off etc), the wireless is erroneously included in that transition. On my tablet I had a similar issue in that going to a lower power state would kill the sdcard which would then not properly reconnect when coming out of that lower power mode. If you prevented the tablet from going into that lower power state, the sdcard problem would not occur. Unfortunately the side effect was worse battery life in that case.
Do you have root on the device? If you do you might be able to do do a test similar to what I did on the tablet, however it would only prove the theory not solve the problem since worse battery life is an ugly trade off for a phone and the only way to actually change the sleep state transitions was to build a modified kernel that changed the sleep state itself (for my LG tablet one of the developers solved the issue and I just used the custom kernel provided)
Info on the "Sleep State" C-State is here https://plus.google.com/+PaulReioux/posts/9R8fjQdHDXD
For the tablet I had to disable the C3 (power collapse) sleep state, my post over there: http://forum.xda-developers.com/showpost.php?p=57719782&postcount=138
No idea if this will help...
Click to expand...
Click to collapse
Don't have root. And have never rooted the device either. Somehow I'm just massively dissapointed with 5.1
Doesn't seem like a finished product at all. Battery life has plummeted from 3.5-4 hours sot easily to barely making it 3 hours
Sent from my XT1095 using XDA Free mobile app
Had this problem suddenly in 5.0 and continued in 5.1, the only fix was back to 4.4.4.
This has been posted before.
http://forum.xda-developers.com/mot...d-5-1-bugs-t3075232/post61724472#post61724472
http://forum.xda-developers.com/moto-x-2014/help/wifi-off-phone-idle-sleeping-t3053603
Here is the link to Motorola Forums that I've posted:
forums.motorola.com/posts/791e7e30c7
Hopefully this bug gets fixed in Android M.
Same problem that I'm getting. I'm sending mine back to Motorola and you guys can try that too to see if they can fix it. Apparently there's a speical dedicated team working on Moto X faults in Germany.
Anybody have any news?
Is there a way to fix this problem without going back to 4.4.4?