So I recently received my SE LiveView, and like a true geek I did tons of reading during the 5 days I waited for it to get here. As soon as I received it, the first thing I did was charge it fully and then update the firmware via SEUS.
Before I go into what I did to fix it, i'll list my hardware/software:
Phone: Motorola Droid on Verizon Network running CM 6.2.2
Software used for fix: Tasker
So after extensive reading and testing, I've determined that the #1 main cause of disconnect is low memory on the phone. If I have a lot of apps running in the background on the phone, the chance of my LV disconnecting increases greatly. As a matter of fact, I don't get any disconnects sans moving out of range of the LV that don't fall under the "low memory" category.
Testing Done: LV connect/disconnect testing using the LV app; opening the app, connecting via the LV; disconnecting the LV, closing the app, then trying to connect via the LV; having the LV connected, then opening up and using different apps until the LV disconnects, then trying to reconnect via the LV.
Results: I can always reconnect via the LV if the LV app is open, or hasn't been closed by the OS to free up memory. If the LV app has been closed via Android to free memory, the LV disconnects and can't be reconnected until the LV app is reopened. This means that the closure of the LV app is causing the disconnect, and a reconnection isn't possible until the LV app is back in a running state on Android.
Fix: Since Sony hasn't programmed a high priority "ongoing" state into the app (like tasker), it's prone to close if Android gets low on memory and it hasn't been opened via the user in awhile. So knowing the results of the testing, I came up with a work around. Using tasker to track when the LV is connected or disconnected, I can keep the LV app in the memory.
I created the following in tasker:
Condition = State >> Bluetooth Connected >> LiveView
Task = Misc >> Say >> "Liive view connected" (I put two i's in live because with just one the TTS says live i.e. "live and let live", not live i.e. "live from NY it's saturday night!")
Exit Task = Misc >> Say >> "Liive view disconnected"
App >> Load App >> LiveView
In doing this, whenever my LV connects to the phone, my phone announces it. this isn't too important, but it's good notification. The real bread and butter here is that when the LV disconnects from my phone, not only does the phone announce it, but it also automatically opens up the LV app into the forefront of the memory, so I can always reconnect via the LV. Also, until I get back on my phone to do something, the LV app will be "opened" and on screen (of course not actually on screen, since the screen is off) and have the highest priority, so Android won't automatically close it when it needs memory, since it's the highest priority app.
I'm going to add another task to Tasker, that whenever I turn off my screen, it loads the LV app too, so the only time I will ever have to worry about the LV disconnecting, is when i'm using the phone extensively and run out of memory.
Questions? Comments? Soliloquies?
I just ordered mine im excited and will for sure try this
Sent from my SGH-T959 using XDA App
Have set this up, will see what happens!
I'm sorry to report that it's no good for me.
In fact, it nearly rendered my phone unusable.
I had managed to stay connected since I wrote my last post, and I was quite pleased about it. Out of the blue my phone shouted "LiveView Disconnected".
Fair enough, I thought, so I went to check the phone, and sure enough the liveview app had loaded and was waiting to connect, so I hit the button on the liveview, which was followed about 2 seconds later by a "Liveview Connected" message and everything sprung to life.
However, after another couple of seconds I got another "LiveView Disconnected" and the app loaded again...and then straight after a "Liveview Connected" and then disconnected, and then connected...and it just carried on. Every time I went to try and turn off the tasker app the Liveview App popped up and I had to hide it again, but it was connecting and disconnecting so quickly I could barely turn off the tasker task...
Also it was annoying the hell out of everyone in the office as it bellowed it's information at me.
I hope others have more luck.
I think you were missing the point of Tasker opening up the LV app when it disconnects. It's for two reasons. The first is so you can properly reconnect. The second is so the app will stay in the forground (i.e. when you're not using the phone, the LV app stays open). You're going to get poor results if you take the LV app out of the foreground once it connects, as Android will close it completely if your system gets low on memory.
For this to work, the only time you should take the LV app out of the foreground is when you're actively using the phone. when it's not in your hands in use, keep the LV app open in the foreground and you won't get any disconnects.
I'm going on 3 days now without a disconnect.
PCTechNerd said:
I think you were missing the point of Tasker opening up the LV app when it disconnects. It's for two reasons. The first is so you can properly reconnect. The second is so the app will stay in the forground (i.e. when you're not using the phone, the LV app stays open). You're going to get poor results if you take the LV app out of the foreground once it connects, as Android will close it completely if your system gets low on memory.
For this to work, the only time you should take the LV app out of the foreground is when you're actively using the phone. when it's not in your hands in use, keep the LV app open in the foreground and you won't get any disconnects.
I'm going on 3 days now without a disconnect.
Click to expand...
Click to collapse
No, I completely understood the point of Tasker opening it to the foreground - I still got disconnects and once I did it would go up and down like a Yo-yo. I only tried to remove the LV app from the foreground to switch the Tasker app off as all I was getting was "LiveView Connected"..."LiveView Disconnected" every 3 seconds which was annoying and obviously the LiveView wasn't going to work at that point.
I completely get what you're trying to achieve here - but it did not work for me.
and what about battery life? mine shut down after only three hours without a huge use of it.... :-(
is it the same for U?
Mini_Jack said:
and what about battery life? mine shut down after only three hours without a huge use of it.... :-(
is it the same for U?
Click to expand...
Click to collapse
Have you updated the firmware of the LV device yet? Once the firmware is updated, somehow the battery greatly improves. I can go 2 full days of moderate use and still have a little less than half the battery left.
I have made the update when I received it, 10th February, so I hope it's the last firmware?Where can I see which version I have?
Did U use some plugins?
I try tp deinstall all of them to increase battery life.
without plugins work approximately 4 hours.... Better but not enough!
i just got mine today, will test tomorrow to see if this method works...
on a samsung galaxy s (vibrant)
this method seems to work for me on my samsung galaxy s (vibrant)
works like charm on my samsung galaxy tab
I have still one problem
Delay of showing the caller's name for 5 Sc
Is there a solution to this problem
I do this 3 steps:
-1º step
-Using Root Explorer, apply the Fivef Process (this seems to be needed only for non-Sense 2.3.x ROMs - looks like Sense in 2.2 builds allows LV to connect without confirmation).
fivef said:
I have found a solution for the repairing problems occurred on my desire HD with cyanogen 7 RC 1.
copy this file with e.g. root explorer to your SD card. edit it with e.g. astro as described below and then copy it back with root explorer. Restart your device.
/data/misc/bluetoothd/[device bt id]/linkkeys
your linkkeys file has to look something like that:
00:1D:BAD:8C:57 FF579860A41CD5A627D9D1596526715C 0 4
00:01:95:08:20:6F 809CC84592E6C1B06AB750170C365812 0 4
6C:23:B9:9B:4A:85 5AF503E766858EA7916D46C16DD31A34 0 4
The last entry is my liveview.
I just changed the last two numbers from I think
-1 0 to 0 4 so that it looks like the other entries.
The 0 is the linkkey type and the 4 the pin lenght.
But I don't know what the 0 stands for.
Have no time for futher research.
I just know that now the liveview automatically reconnects without an annoying pairing prompt.
Click to expand...
Click to collapse
-2º Step
- Find in the market & install the BEST Android program I've seen yet - "AutomateIt!"
- Create the following rule in this program:
-TRIGGER: BLUETOOTH DEVICE CONNECTED (LIVEVEW)
-ACTION: START APPLICATION (LIVEVIEW)
Using this incredible program, you can completely control every aspect of your phone's behavior - for example, automatically start PlayerPro and disable WiFi when wired headset is connected, automatically start WiFi when GPS detects that you have entered your home or office (!) and do million other cool things.
-3º Step
-Install liveviewcharm from market:
This application will maintain processes from "liveview app" always on, preventing android system to kill them.The LiveView app needs to put itself in the Notifications bar in order to keep from getting killed when it's in the background.
I think that guide will fix all liveview connection problems with all compatible devices and CM7/MIUI/STOCK.
thanks to Drakosha Old, fivef, ishii.
Related
Hi everyone!
I'm using OpenDesire 4.0.4, and while it's more or less the perfect ROM for me, I'm getting a little annoyed at the WiFi. As the ROM is based on CyanogenMod, it has the same WiFi behaviour: When the screen turns off, the WiFi enters power saving mode, regardless of the apps that are active at the time, or the amount of traffic over WiFi at the time.
The problem here is that any application that's using WiFi pretty much just stops as soon as you turn the screen off.
1. Sipdroid during a call: Massive packet loss as soon as the screen turns off. You may hear a garble or two, but nothing intelligible.
2. SwiFTP and other FTP servers: Connecting to the FTP server and navigating to folders takes ages when the phone is in standby. Transferring files is more or less impossible (times out)... Everything's fine when the screen's on. If you transfer a big file and turn off the screen during the transfer, you basically pause the transer - turn the screen back on and the transfer goes back to full speed
3. Market: If you turn off the screen while a lot of apps are going to download, like after pressing "Update all" for a few apps, more often than not they'll just fail in the background.
Now, I could beg and ask the ROM developers (Kali for CyanogenMod on Desire, or AdamG for OpenDesire) to just change this behaviour, but it seems that most people are happy with the situation, as it causes the WiFi to use very little battery on standby... so I'm asking if anyone knows how I could change this myself. Is it even possible to do this at runtime without baking it into the ROM directly?
Or am I SOL until (or rather unless) AdamG or Kali takes pity on me?
I'd love to hear some input - hell, maybe I'm just doing it wrong ... Thanks in advance!
PS: Yes, my WiFi Sleep Policy is set to Never, and the Desire DOES stay connected when the screen is off. Just in a very low power mode...
-edit- Should have searched, sorry: http://forum.xda-developers.com/showthread.php?t=752856
-edit2- Looks like there really isn't a fix for this... Anyone found a way to completely disable PSP on the Desire/Nexus WiFi?
I'm on the same ROM as yourself. What value is your "screen-off lock screen delay" set to?
In my observations, the transfer in the state you mention still persists albeit at a very slow rate and the WiFi chip is certainly placed in the LOW power state, although on.
I'm unaware of any workaround but what I use myself when transferring bulk 1-7GB files through WiFi from my PC/Laptop, which is to change the value of the screen lock delay at screen off under Settings>OpenDesire>User Interface>(last option) to a high figure, like 10-30m, depending on how long I'm expecting the transfer to take. It's a trade-off but you'll still save over 95% of the power since your screen is off but the WiFi/SD/CPU remain working as when the screen is on. Maybe you've tried this already?
-----------------------------------
- Sent via my HTC Desire -
That's not a bad idea... brb testing .
-edit- Didn't work
As soon as the screen times out, my transfer speed drops to nearly 0 - even with the lock delay set to 30m... :'(
OK, that's confusing. I'll be back by tonight or morning... I have much testing to do on this since for sub-20mins, my connection runs plus 200Kbps according to the PowerTutor log in such a state. Usually it would drop to 0.3-8Kbps when the screen switched off.
-----------------------------------
- Sent via my HTC Desire -
th3 said:
OK, that's confusing. I'll be back by tonight or morning... I have much testing to do on this since for sub-20mins, my connection runs plus 200Kbps according to the PowerTutor log in such a state. Usually it would drop to 0.3-8Kbps when the screen switched off.
-----------------------------------
- Sent via my HTC Desire -
Click to expand...
Click to collapse
Mine drops to practically 0. So low that due to overhead, FTP transfers pretty much stop completely...
I've seen that the linked kernel module provides a temporary workaround for you guys now. During the course of my testing your concern I basically found my WiFi module isn't ever turning off nor switching any connections off - it's always awake and can always transfer some data. Even in the LOW state it is connected at 24Mbps. Whatever I did I couldn't change this behavior on 4.0.4. Time for another wipe...
OD has many user preferred options baked in working fine alongside the conventional options so it'd probably be best suited for a toggle of this feature to be implemented for you guys (if at all possible). Not sure if that WiFi module power state behaviour is write-able and changeable on-the-fly before a reboot, should be, as it's only changing a hardware state.
-----------------------------------
- Sent via my HTC Desire -
The new Wifi module is working perfectly here. No more performance problems, and my power consumption has actually gone DOWN. Probably because I have a bunch of connected apps running in the background and PSP is very inefficient for that.
Also, the delays in Chrome To Phone and Appbrain web installs are gone...
I'm loving this fix...
I see that when a task killer stops a program (cityid, stocks,etc) I can look right back in there and see it running again and in a minute the page is full again of the same apps that I just killed. Even with autokill on they start while the screen is off. I want to know if anyone has figured out what file or service keeps starting these and if there is an edit to it to tell them to quit it ? I am not comfortable with a device that I do not have control of stuff that starts and goes online by itself. Thanks.
madman34 said:
I see that when a task killer stops a program (cityid, stocks,etc) I can look right back in there and see it running again and in a minute the page is full again of the same apps that I just killed. Even with autokill on they start while the screen is off. I want to know if anyone has figured out what file or service keeps starting these and if there is an edit to it to tell them to quit it ? I am not comfortable with a device that I do not have control of stuff that starts and goes online by itself. Thanks.
Click to expand...
Click to collapse
If you're not comfortable with a device you do not have full control of, looks like rooting is for you
Seriously though, rooting your device is the ONLY way to remove City ID, Stocks, etc. from your device. HOWEVER.
You should probably break yourself of the task killer habit. Lifehacker explains it all here: http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them.
In a nutshell, Android is actually really good at preserving memory, and killing apps that will keep popping up drains battery faster. The reason they keep popping up is Android is trying to predict what you're going to use next based on what you just did (or something like that), so potentially anything you have installed that is there on startup will hit that list.
I tried using Watchdog as the article said, but honestly I found in the end I just wanted more control. unrevoked 3.21 and several ROM tries later I'm happy with where I'm at
EDIT: I see by your sig that you have rooted your Dinc.. therefore, it's a very simple process if you want to get rid of the app entirely. If you want to leave it installed, you're not going to find a solution to the constant opening - Android is what Android is.
Most of the apps you see in the task list are not active. They're just loaded in memory so they can launch faster when you need them.
Like the previous poster pointed out, task killers are counter productive. You just get a continuous cycle with the app launching and being killed. Launching again and being killed again. And on and on.
Best just to leave android alone to do what it was designed to do.
If you still feel the need to be more in control use app autostarts. It allows you to block the initial app launch and block based on events.
________________________________
Unrevoked forever
SkyRaider Sense 3.3.2
KiNgxKernel BFS (#5)
Radio 2.15.00.07.28
Mostly what I want to do is,,,,
,,,To stop applications that come on by themselves and log in even when you set in their settings to not do it, like Skype. I do use Skype to do a calll with a bunch of friends from school, but I want to start it when I want to use it, I am all the time having skype calls come in when I have not even launched the app. I figure that if it is listening for a call then it is useing power needlessly. I do not want to have to log out every time I want it to stop, I just want to close it and it behave and stop useing power. Many apps do that and I think it is a major reason for low battery life. My battery will not hold up a full shift at work, but if I kill the GPS and the 3G the thing has been up for 22 hours and is still at 66% and I have talked for over 2 hours today on the phone, so I think that if more control is gained over app behaviour then we can be happier with our batteries ;-)
madman34 said:
...but if I kill the GPS and the 3G the thing has been up for 22 hours and is still at 66% and I have talked for over 2 hours today on the phone,
Click to expand...
Click to collapse
You hit the nail on the head there. It's not the apps killing your battery, it's the 3g and gps.
I leave my wifi on all the time but have it set to disconnect if the phone is idle for 15 min. Bluetooth, gps, and 3g are always turned off except when I need them.
________________________________
Unrevoked forever
SkyRaider Sense 3.3.2
KiNgxKernel BFS (#5)
Radio 2.15.00.07.28
So I have xdandroid running pretty good now without any major problems except for this. When I leave my phone idle for a long period of time, usually when I go to sleep, and come back to it I loose service as soon as I go to make a call. I tried playing with the airplane mode but it wouldn't allow me to disable the radio. Is anyone else having this problem and is there a solution? Thanks.
What phone? RHODxxx?
Build info would be helpful as well. Kernel, rootfs and system image version/date.
I quite often lose service, but there is no pattern to it! Sometimes it come back, sometimes it doesn't. If it has gone, then it won't go into airplane mode either - it seems to need to say goodbye to the network!
This is different to the scenario where I lose data connection, dispite having signal. In this situation the airplane mode trick does the job. When in this state, ifconfig doesn't display a ppp network.
Rhod100_uk, latest everything!
Well that makes me feel better, that GSM guys are experiencing the issue as well
Im also using RHOD100_uk and having this same problem aswell.
Only thing i have done that fixes it is to restart Android.
Sent from my MSM using the XDA mobile application powered by Tapatalk
I have ATT tilt2 and i seem to have this issue from time to time. Sometimes i can toggle "airplane" mode and it will reconnect. If not its a full reboot.
Yup, I see this issue from time to time on my Rhod400 as well. It will show as connected to 3G but then unable to actually transmit data. I always have to reboot to resolve this.
My bad for taking so long to reply to my own thread, things got a little busy.
Anyway, I have the Rhod210, tmobile US version. Rebooting the phone wouldn't be much of a problem, accept for the fact that this usually happens when I'm asleep, and I don't realize I need to restart it, but rather think I'm not getting any calls lol. Is there a way I could rig it to reboot every so often maybe?
manekineko said:
Yup, I see this issue from time to time on my Rhod400 as well. It will show as connected to 3G but then unable to actually transmit data. I always have to reboot to resolve this.
Click to expand...
Click to collapse
maybe once a day here with a rhod 400 on the latest frx03 build updated with sov's tool. i notice that the available memory in the advanced task killer will go from 102 when everything is running fine to 80 or 85 when is starts goin to crap. the only 2 apps i leave "alive" are task killer and juice defender.
jab73180 said:
maybe once a day here with a rhod 400 on the latest frx03 build updated with sov's tool. i notice that the available memory in the advanced task killer will go from 102 when everything is running fine to 80 or 85 when is starts goin to crap. the only 2 apps i leave "alive" are task killer and juice defender.
Click to expand...
Click to collapse
Well, for one... you're *not* supposed to use "task killer" apps in 2.2+. Feel free to keep using them, just be prepared for data loss.
Two, the mystery process you're looking for is system_server. Every time I've had complete and utter unexplainable slowness, it was this process stealing 90+% of the processor cycles.
We still have some bugs to work out
so what should i be using for such an app?
Sent from my MSM using the XDA mobile application powered by Tapatalk
jab73180 said:
so what should i be using for such an app?
Click to expand...
Click to collapse
The way Linux and Android handle applications, you shouldn't need to... At all. The only time you really *need* to kill an app is if it's misbehaving and it's frozen.
Hi!
Since the first (official) upgrade to Android 7, and even now with the new 7.1, I've been having this issue everytime I use any of these apps.
I always used runkeeper to track my mtb trails and it always worked perfectly. When this started to happen once, twice, etc, I decided to change to Strava, as I assumed it was an app problem.
The same thing happened on strava!
This situation happens on a random time (it happened once after 10 minutes of use, it happened other time after 2 hours of use, completely random). I have kept with strava as, after a force close, when I open the app again, it recognizes that a problem has happened and it restarts from the last recorded place.
Anyhow, this is a very annoying situation, as if I don't notice that the app closed, I will loose most of the trail.
I have disabled "Agressive doze & app hibernation".
Any other ideas?
Thanks
I have the same on 8.0. Compleate stopper for using OP.
All fitnes apps that use gps stop after 10 or 20 or 30 min of bacground work.
Also i use heart rate sensor and it does not restarts itself. It stales Bluetooth and you can not reconnect hr sensor without rebooting device
Considering to swith to Samsung)
Try turning battery optimization off in settings for those apps. I am not sure if this works but give it a try.
Hi all,
I'm running several apps that should run all the time (AdGuard, Network Speed Meter) or for a long time (speed trap warner,...) but OxygenOS kills them after a certain period. Some of them restart automatically, some don't. Of course all of these apps are 'not battery optimized'. Is there any chance to prevent OxygenOS from killing them?
Are there custom ROMs that can overcome this problen?
I'm on the latest OxygenOS Pie Beta, but the behavior was similar on Android O...
Thanks a lot,
W
Did you try locking the app via recents menu?
Thank for the info, didn't know that.
Unfortunately it doesn't help, Adguard and the network monitor don't appear in recents. The speed trap warner automatically starts and stops when I'm in the car, i don't want to open recents manually every time.
Battery - Battery optimisation - Don't optimise
safwankatharudheen said:
Battery - Battery optimisation - Don't optimise
Click to expand...
Click to collapse
This is not changing anything,e ven with disable battery disabled, even with adaptative battery disabled.
I have the same problem. I have not found any solution whatsoever. This is really frustrating. I've made sure apps aren't optimized. Advanced optimization is disabled. Developer options background limit is at standard. I've pinned the apps in recent apps and it still happens. Apps get killed all the time.
For example,
1. I use Google Fit to start tracking a run. Within 10 minutes of tracking, the app is closed and workout not tracked. Its not even like i touched the phone and opened other apps during this.
2. I have VoIP account setup in the default dialer. Calls come through only 50% of the time cause the dialer is closed.
3. YouTube Music, constantly gets closed if i simply pause the music. Within 2 minutes, the app is closed.
4. Trying to transfer 15GB of files through Explorer app from phone to file server, never succeeds if i don't watch the app and keep the screen on.
5. Plex gets closed and therefore my photos don't auto backup with the phone is plugged in.
This is absolutely ridiculous! Why the hell a phone with 8GB of RAM is killing apps is beyond me!
Custom ROM on the same phone, like Lineage OS, no issues. Can have optimization on, battery manager on and all. In fact, battery life is better on custom when its not killing the apps! Seems to be the only solution until OOS can stop killing apps so aggressively.
M3drvr said:
I have the same problem. I have not found any solution whatsoever. This is really frustrating. I've made sure apps aren't optimized. Advanced optimization is disabled. Developer options background limit is at standard. I've pinned the apps in recent apps and it still happens. Apps get killed all the time.
For example,
1. I use Google Fit to start tracking a run. Within 10 minutes of tracking, the app is closed and workout not tracked. Its not even like i touched the phone and opened other apps during this.
2. I have VoIP account setup in the default dialer. Calls come through only 50% of the time cause the dialer is closed.
3. YouTube Music, constantly gets closed if i simply pause the music. Within 2 minutes, the app is closed.
4. Trying to transfer 15GB of files through Explorer app from phone to file server, never succeeds if i don't watch the app and keep the screen on.
5. Plex gets closed and therefore my photos don't auto backup with the phone is plugged in.
This is absolutely ridiculous! Why the hell a phone with 8GB of RAM is killing apps is beyond me!
Custom ROM on the same phone, like Lineage OS, no issues. Can have optimization on, battery manager on and all. In fact, battery life is better on custom when its not killing the apps! Seems to be the only solution until OOS can stop killing apps so aggressively.
Click to expand...
Click to collapse
My app is not killed when i lock it in the switch app menu
There's a whole website regarding that issue on several devices, maybe it helps: dontkillmyapp(dot)com/general#user-solution