Hi guys, I'm having this extremely annoying issue with my S4.
EVERY SINGLE TIME I open "Gallery" on my phone with my TV on, it turns the TV off immediately. Now, this happens:
- whether I'm sitting 2 feet accross the table or if I'm pretty far away in a different room
- whether or not I unlink WatchOn from my TV set
- whether I use my S4 or another S4 (my wife's for example), which seems to mean that it's not related to my specific handset.
I looked everywhere online and can't seem to find anyone having the exact same issue, let alone a solution.
Yes, the IR Remote feature on the S4 is great per se, but this is a major problem. If my kids are watching a cartoon in the living room and I'm in my bedroom trying to check recent pics I took using my phone, it turns the TV on instantly.
I have a S4 i9500 (international version, still running on original firmware I9500XXUAMDK) and my TV set is a 42 inch Samsung plasma.
PLEASE HELP !!!!!!!!!
senghorchild said:
Hi guys, I'm having this extremely annoying issue with my S4.
EVERY SINGLE TIME I open "Gallery" on my phone with my TV on, it turns the TV off immediately. Now, this happens:
- whether I'm sitting 2 feet accross the table or if I'm pretty far away in a different room
- whether or not I unlink WatchOn from my TV set
- whether I use my S4 or another S4 (my wife's for example), which seems to mean that it's not related to my specific handset.
I looked everywhere online and can't seem to find anyone having the exact same issue, let alone a solution.
Yes, the IR Remote feature on the S4 is great per se, but this is a major problem. If my kids are watching a cartoon in the living room and I'm in my bedroom trying to check recent pics I took using my phone, it turns the TV on instantly.
I have a S4 i9500 (international version, still running on original firmware I9500XXUAMDK) and my TV set is a 42 inch Samsung plasma.
PLEASE HELP !!!!!!!!!
Click to expand...
Click to collapse
i would update the rom first and see if that solves your issue.
FIXED !
gee2012 said:
i would update the rom first and see if that solves your issue.
Click to expand...
Click to collapse
I updated ROM to XXUBMG1. Problem fixed. THANKS !
Question : is there a more recent firmware for i9500 ?
XXUBMG9 is the latest i9500 firmware update.
Done
krico said:
XXUBMG9 is the latest i9500 firmware update.
Click to expand...
Click to collapse
Updated to latest firmware. Thx.
Hi,
I have a samsung galaxy express i8730 with cyanogenmod 11 (4.4.4).
Does cyanogenmod work with android wear?
Sebastiaan
sebastiaann said:
Hi,
I have a samsung galaxy express i8730 with cyanogenmod 11 (4.4.4).
Does cyanogenmod work with android wear?
Sebastiaan
Click to expand...
Click to collapse
So far i know it works
Sent from my LG-D855 using XDA Free mobile app
I have an S4, and I haven't gotten mine to work on CM 11. I mean it does, but not very well. Gonna switch to a TW rom tonight.
S4 running CM11 and no issues with my LG g watch. Everything comes through with no disconnects.
Sent from my GT-I9505 using XDA Free mobile app
sebastiaann said:
Hi,
I have a samsung galaxy express i8730 with cyanogenmod 11 (4.4.4).
Does cyanogenmod work with android wear?
Sebastiaan
Click to expand...
Click to collapse
I'm using CM 11 (4.4.4) on a S4 with Android Wear. No issues that I can see so far.
On Nexus 5, anything other than stock doesn't work well. Watch disconnects too often to be usable (bluetooth stack is dodgy on aosp or CM).
The fix is to flash Elemental kernel. Problem solved. This kernel is available for both aosp and CM.
Even in stock rom, if you flash another kernel, like franco kernel, the watch becomes unusable.
Again, the fix is to flash Elemental, with gives you the added bonus of enabling screen calibration for nice poping colors.
It took me time to discover all this. And frustration.
lost network connection
Hello I installed cm 10.2 through flash recovery. Onti my galaxy ace 2GT I8160 was gingerbread 2.3.6
Now its team conja jls361 if ive looked in the rite plce i still have iemi number and can recieve messages
But when i try and send or call it say no network ive been on to 3 my provider and they say its the phone
Please could you help with thi ive read it happens alot with this release of cm.. Would installing cm 11 sort it out im a newbie to being root ive already soft bricked it once so can see it being a bumpy ride so all the help i can get the better thank you
Also I looked at the build list and the radio and boitloader are unknown the biitloader has been like that when i got the phine that's bootloader not biitloader or bout loader dam key pad lol
My kernal is a i8160xxlk8 or it was I dunno if it still is
Connecting, running sync loop
Latoc said:
On Nexus 5, anything other than stock doesn't work well. Watch disconnects too often to be usable (bluetooth stack is dodgy on aosp or CM).
The fix is to flash Elemental kernel. Problem solved. This kernel is available for both aosp and CM.
Even in stock rom, if you flash another kernel, like franco kernel, the watch becomes unusable.
Again, the fix is to flash Elemental, with gives you the added bonus of enabling screen calibration for nice poping colors.
It took me time to discover all this. And frustration.
Click to expand...
Click to collapse
Any ideas for running CM on the galaxy s3? Android wear will not switch to connected, shows, "connecting, running sync loop". Most functions work OK but the watch is dying terribly quick. I know the moto 360 battery is supposed to be iffy, but I should get more than 4-5 hours....
Garrett 77 said:
Any ideas for running CM on the galaxy s3? Android wear will not switch to connected, shows, "connecting, running sync loop". Most functions work OK but the watch is dying terribly quick. I know the moto 360 battery is supposed to be iffy, but I should get more than 4-5 hours....
Click to expand...
Click to collapse
I don't know about s3, but you should try a few kernels and see what works...
FIXED
Latoc said:
I don't know about s3, but you should try a few kernels and see what works...
Click to expand...
Click to collapse
Well,
I tried a different kernel and still same issue. I flashed a TouchWiz based rom and it WORKED. Shows "connected". Battery life on moto 360 also vastly improved. Went from dead at 3:30 PM to 45% at same time!
I'm on DarkCM(11) for the xperia z1 and can't get it to work either.
Tested on my brothers stock xperia and that worked just fine. Il try downgrading to stock as well. :'(
If anyone gets CM on the z1 running with android wear please let me know.
I have a Oneplus One CM 11S works great on my old Gear Live and my new Sony Smartwatch 3
I read that MOTO 360 has (had) issues ?? Maybe the watch not the phones OS
Hi. My first post here and very New to all this. I have Samsung S4 with cm11 just got an Samsung galaxy gear2 neo and now i have to figure out how to get it to work with cm11 ? Can some body help
TechieInAK said:
I'm using CM 11 (4.4.4) on a S4 with Android Wear. No issues that I can see so far.
Click to expand...
Click to collapse
Sorry for bringing up an old post. I wanted to check in on your Android Wear connection to CM ROMs. I have a Sprint S4 (jfltespr) running CM12. I will be getting a LG G Watch R in a few days but someone else on our ROM thread was having issues with his Moto 360 and the CM12 ROM. Have you experienced any issues not connection or remaining in a sync loop?
Has anyone else experienced Android Wear issues with CM 11 or CM 12 on S4 phones? Particularly jfltespr?
Cant speak for the S4 but my LG G3 has had nothing but issues with my G Watch R since I flashed CM12. I reverted back to CM11 (recent build) and its working great, never disconnects. With CM12 it would disconnect at least 10-20 times a day its unusable.
I just installed the Google Play Edition Lollipop on my GS4 and it paired perfectly with my ASUS ZenWatch. Lollipop AOSP is AMAZING and i am so stoked it works so great!
Garrett 77 said:
Any ideas for running CM on the galaxy s3? Android wear will not switch to connected, shows, "connecting, running sync loop". Most functions work OK but the watch is dying terribly quick. I know the moto 360 battery is supposed to be iffy, but I should get more than 4-5 hours....
Click to expand...
Click to collapse
"Connecting, running sync loop" is just a different message for the same thing - it is activated on some ROMs(?) apparently when you have Developer mode enabled. But it works the same, and this message in itself doesn't indicate there should be any battery drain.
Of course something in the ROM might be causing this problem - a logcat from the watch would help in that case, but my guess is you just need to let everything install, settle down and then reboot both devices, and the drain will be gone...
My Zenwatch works perfectly with my Oneplus One running the latest CM11S. Having bluetooth on all the time does drain a bit more battery, but that's it.
I am having an issue with google wear (zenwatch) completing some tasks:
It fails to launch a phone call from google wear (my watch simply says "try again using your phone")
It fails to launch google play for music (it gives the same error as above)
Setting reminders using google keep (same error)
Text messages sent from android wear are NOT working.
Starting navigation on my watch using voice commands works.
Other basic apps appear to be working as well.
So far I've only noticed the above listed (maybe a few others) google apps and dialer that fail to launch when initiated from the watch, I have tried another dialer to see if that was the issue.
Anyone have any suggestions or insight on what I might be able to do in order to get google wear working 100% with this ROM?
Any help is greatly appreciated.
Mine works well
I have OnePlus One with CM11 and everything works quite well so far with my G Watch R
Hello all,
It appears my NFC sensor has quit working on my T-Mobile Galaxy S5. To provide some back story in hopes of finding a solution, here's what's going on:
A few days back, everything was running fine. I flashed an unofficial CM12 ROM (Albinoman887's) to my phone, which at the time had broken hotspot and no Netflix support. NFC worked for me at that point, as I used it to 'Tap n Go' when setting up my account to transfer everything to my S5 from my N7.
The next build that was released fixed Netflix for me, but since then I haven't been able to get any functionality out of NFC. According to the ROM developer, NFC works on his device, as it also does for several other T-Mobile S5 owners. I definitely believe that it works for them, but it's super frustrating to me that it won't for me -- even though I rarely use NFC. I'm just irritated at the thought that my sensor may have died and I have no idea why/how. The phone has never been dropped, so it shouldn't be shock damage.
It's also worth noting that I Odin'd back to my stock firmware, just to test NFC, and I couldn't get any NFC functions to work once I started fresh.
I'm not sure what my options are at this point, but I was hoping someone might have some input to help steer me in the right direction.
Quick update: I flashed a CM 11 ROM (Bliss Stalk, to be exact), and my NFC sensors now work like normal. I'm glad to see it's not dead, but I'm completely baffled as to why it doesn't work on CM 12, when the ROM developer is running the same device and it works for him.
Ahh, the perils of Android development. I'm still glad Lollipop is coming along so smoothly, and I apologize to @albinoman887 for being such a pain in his butt!
Hi, I recently had to reset my Nexus 4 and took the opportunity to try a custom ROM.
I chose Pure Nexus 6.0.1 and I like it, but I have a very annoying issue: when I do not reboot my phone for a few days (can be 1 days, can be 3 days) it starts getting sluggish, until it freezes - generally the moment when I open a more intensive app like a car navigation app.
If I reboot it everything works fine and smooth for a while.
I never had this problem before with official ROMs, and I'm using the same apps as always.
Is there a solution to this, or maybe can anyone suggest a different ROM?
I need a ROM which is complete and 100% stable, and I do not have the time to do much testing myself...
I do not care if it is bleeding edge, Marshmallow is enough , but I really do not want to get crazy with bluetooth or wifi issues, crashes, slowdowns...
Thank you very much for any pointers!
Marco
Hey,
So the thing when the phone had stock rom and everything it worked perfectly until one moment when the device decided to present messages such as:
(the name of the app/service) stopped working. It was like this for a long time so I decided to change rom. SO basically I tried to put every single rom out there, none of them worked except resurrection one that eventually had problems too.
The phone was never dropped or something like that, and when the problem appeared I took the phone to the lab and that said they "fixed" it, they didn't.
So my question is, what is the possible problem for this annoying shutting down, deleting apps on its own and only one possible working rom?
Feel free to help
Do any apps utilise data from the micro SD card?
If that fails or failing can cause issues that your experiencing
Just a thought
Sent from Samsung S7 Edge [Oreo]