After installing of ICS 4.0.3, my LV does not show plugins until I recover them with TitaniumBackup.
I can install all LV apps and plugins from the market but they are invisible in LV.

Originally Posted by Tippfehler

After installing of ICS 4.0.3, my LV does not show plugins until I recover them with TitaniumBackup.
I can install all LV apps and plugins from the market but they are invisible in LV.

Are they visible within the updated LiveWare-Manager app? (There is a brand new list function)

Yes, they are visible in the LiveWare-Manager app.
I have tested it with the non working (in ICS 4.0.3) Calender plugin.

Nearly all plugins are not working in ICS (beta).
(gmail, calendar, camera)

Originally Posted by ran495

1. I read that the connectivity issue has been resolved (more or less) as compared to before, but is it compatible with LG phones? I'm using a P500 Lg optimus one.

2. Anyone know the standard battery life on this thing? I read somewhere if you kept the screen on it doesnt last for more than a hour?

I would strongly refute any claims that the connectivity issues have been solved. It's variable, some people have more luck than others but it's certainly not what you'd call "solid". In my own case (HTC Desire S with rooted but otherwise stock Sense 3/Android 2.3.5 and the 3rd party LiveView Manager app) I've got it more or less usable IF I keep the phone in my shirt or jacket pocket. If I put the phone in my trouser pockets it will disconnect at some point as the Bluetooth range is too short, then the LiveView app will close on the phone preventing reconnection. Sometimes the LiveView Manager will restart it, sometimes I have to manually launch it, sometimes it still won't work but will start working again after a few minutes!

As for battery life, it depends on what notifications you have and how often it polls. When mine's working and connected I charge every other day. If it disconnects the battery drains quicker, and the battery meter is useless. If it gets down to half you can be sure it will be completely dead very shortly afterwards.

Only one problem left

---

Thanks to everyone who has contributed to this thread! I have a Kyocera Echo (the dual screen phone) and I only have one problem left to get my Live view working properly.

Like most I get disconnected from time to time and the problem occurs during reconnection (like everyone else it appears).

I have rooted my phone and I am running 2.3.4 on it.

Changing the Linkkeys file by modifying the last two numbers for the LiveView doesn't appear to work on my phone. If I change them to 0 4 then I can't pair with the LiveView at all. In fact the only way to fix this is to delete the linkkeys file and then reboot and start the pair process all over again.

Since changing to 0 4 won't work it appears, does anyone have any additional suggestions to supress the pairing notification that requires me to click "ok" on?

If I didn't provide enough info please let me know. Taking a shot in the dark and seriously considering I'M Watch....just want to see if I can get this little guy to work.

I appreciate any help i receive.

Originally Posted by tj80

I would strongly refute any claims that the connectivity issues have been solved. It's variable, some people have more luck than others but it's certainly not what you'd call "solid". In my own case (HTC Desire S with rooted but otherwise stock Sense 3/Android 2.3.5 and the 3rd party LiveView Manager app) I've got it more or less usable IF I keep the phone in my shirt or jacket pocket. If I put the phone in my trouser pockets it will disconnect at some point as the Bluetooth range is too short, then the LiveView app will close on the phone preventing reconnection. Sometimes the LiveView Manager will restart it, sometimes I have to manually launch it, sometimes it still won't work but will start working again after a few minutes!

As for battery life, it depends on what notifications you have and how often it polls. When mine's working and connected I charge every other day. If it disconnects the battery drains quicker, and the battery meter is useless. If it gets down to half you can be sure it will be completely dead very shortly afterwards.

So its still a persisting issue? man, and the battery thing is not very encouraging... maybe i will just wait for the smart watch.

Originally Posted by ran495

maybe i will just wait for the smart watch.

But even the smartwatch will be connected via bluetooth - including all the connection issues and so on. For me as an xperia pro user I have no real problems with this. Sometimes the LiveView needs some seconds for fresh polling but afterwards it's running just fine. Especially by having the music player running the connection won't be lost.

Originally Posted by siyman

But even the smartwatch will be connected via bluetooth - including all the connection issues and so on.

It's the LiveView's implementation of Bluetooth that causes the problems, not Bluetooth itself. My phone will reliably link to my Mac Mini from the other side of the house; my car connects to my phone perfectly and instantly every time with a rock solid connection; my laptop connects to my phone perfectly every time for file transfer. I appreciate that all those devices are bigger than a watch and probably have better aerials/more powerful BT systems but a reliable range of a few feet really shouldn't be impossible in a watch!

i like Sony Ericsson. But my BF bought one for me not with this brand. From the apperance, it is pretty. But the quality is not good. Just a little dissapointed.

Dell Streak 5 "on the device using DSC 0.7 Prerelease v2 (Gingerbread 2.3.3) rom.

SE MN800 and SE MW600 When used in connection with the problem and the MW600 music function problems. I tested 24 hours and no problems were encountered.

Paired the two devices;

data> misc> bluetooth> incoming_connection.conf file;

58:17:0C:EA:91:09,1,1326572326784-1000 ------> MW600
00:21:9E:94:AD:23,-1,1326587152292-1000 ------> MN800
consists of rows and is causing the problem. MW600 row was entirely erased and only the MN800 row changed (edit: -1 to 1 (sorry i'm forget);

00:21:9E:94:AD:23,1,1326587152292-1000 ------> MN800

saved and exit after reboot.

In addition to the applied methods Drakosha and timspb (thanks drakosha and timspb).

Now is working smoothly.

Sorry bad English.