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 Droid Geeks & Devs, a sincere advice/help needed .. just fed up off two major issues with my N4. Already tried many of the things available on forums but still the problem persists since 3 months now. So it's time I share my saga and possibly get the suggestions/fix or atleast a workaround.
OK, I'll start from the beginning.. I was and still am fully stock on Kitkat 4.4.4 and bootloader locked. I guess it was September during which i
updated my Google camera app from play store. And since this small update my N4 is ruined, my camera stopped working after a few hours ..only solution was to do a reboot & it would work fine for few hours and again "can't connect to camera". I thought a update might fix it but it didn't ..just forgot i had a camera in my phone for few months.
But guess what since October,the camera not working cycle was as it is, but the added problem was sudden infinite awake times in battery stats showing the cause of drastic battery drains (40% drain in nights to wakeup to drained dead phone in morning).again the temp fix was a reboot. But when i closely looked at the trends, I found the relation that while my camera is working the wake-locks are just fine, but the moment the cam stops working the continuous long Awake starts till it eats up all the battery and eventually lead to a reboot to be back to normal.Screenshots attached.
The upcoming Android 5.0 update in Nov was a major hope for me, that this should fix the bug.I happily sideloaded the lollipop update but still no luck ..in fact i have got added lollipop bug of WiFi drops for no reason.Also trying my luck with the new 5.0.1 lets see how it turns out.
Please help me with this issue. Thanks in advance.
Still no luck with 5.0.1
Please Anyone can suggest something ??
Sent from my Nexus 4 using Tapatalk
HI Guys,
i Updated my Phone via factory image to Android 5.1 all worked well during the update.
I spotted that with the stock 5.1 my phone got hot when active and the battery went down very fast (and by active i mean just doing normal stuff).
So i decided to go to cm12.1, installation also worked well, but had the same problems here.
Then i went back to stock 5.1 but still the same problems, my phone is getting hot and battery life is getting low when i use it.
When not in use its ok, it baerelly uses battery then.
I searched in forum and google also, but couldnt find anything rly helpfull, i think of going back to 5.0.1
TL: DR
Since Update to 5.1 Phones runes hot and the battery is going low very fast when in use.
Does anyone know this issue and has some advice to solve them?
Gretz from Germany
I was on Stock UK 30B Firmware flashed yesterday evening, everything was fine and after a couple of hours later WiFi and Bluetooth did not work.I tried factory resetting and flashing KDZ of Lollipop,jellybean and no avail,tried Dorimanx Kernel and now on resurrection remix,nothing working,i have seen many have faced this issue in various OEM,but did not find any particular solution.
Is this a hardware issue,are WiFi and Bluetooth chips differentiated from the board or inbuilt,so i can replace in minimal cost without going to SC.
You have found a way solve your problem with Wi-Fi?
@RedDiablo
No i wasnt able to solve,it seems like an hardware issue,my phone is also getting too heated up and battery life was worse too,100-0 in 5-6 hrs,so it is completely useless now..
Hello guys,
Tonight i flashed and worked on the Android P GSi on our Z2 Pro. As of now there are "only" some issues left which I'm working on.
Not working:
- Fingerprintscanner
- VoLTE
- Some chargers didn't charge (the original one is working, S9 charger doesn't work, same problem as some pixel users have)
Antutu Score is 163.000
Thanks a lot, those are good news. Hope you will solve at least fp issue without great deal of work needed. Fingers crossed.
Thank you bro.... :good:
Try this:
PrakarshRocks said:
How to fix fingerprint sensor on most devices:
Go to build.prop (vendor/build.prop) and look for fingerprint persist.qfp, if it says false, make it equal to true. Reboot. Go to setting and add a fingerprint and wait 1 minute after that the finger sensor should work as it was intended to Even after a reboot. Click thx (like button) if this method helped you. Cheers!
Click to expand...
Click to collapse
Hello, thank you for you courage to do it.
I also thought about it. But much more I read much unsure I was that it works.
Can you tell us how you done it?
Have you flashed P GSI image then the GSI image? (for A or A/B)?
What about the kernel?
Have you tried the tip from PrakarshRocks ?
Thanx in advance for keeping us in touch...
Hello guys,
I'm still working on/debugging the problem.
There was a problem with root on the gsi image. Now it's working. After work i will test the solution from @meDAem.
After some days of usage i can say it is way more stable than any other rom in the past for it's very early stage. I didn't have any fc's so far. Synchronisation is working perfectly, Google Apps are working.
And there is some progress which i reached on the weekend (can only do it when my gf is sleeping) but after some time the function of the fp disappears.
Now with telegram group to share results from android development.
https://t.me/joinchat/Dp-JJAengw2zTAkef_L7TA
thank
Thank you very much for your contribution, I would like to ask when can you release it for us to use?
It's done when it's done ??*
Did anyone try the new AOSP build yet ? https://forum.xda-developers.com/pr...vice-development/aosp-9-0-phh-treble-t3831915
Co.okie4u said:
Hello guys,
Tonight i flashed and worked on the Android P GSi on our Z2 Pro. As of now there are "only" some issues left which I'm working on.
Not working:
- Fingerprintscanner
- VoLTE
- Some chargers didn't charge (the original one is working, S9 charger doesn't work, same problem as some pixel users have)
Antutu Score is 163.000
Click to expand...
Click to collapse
battery and camera ? good ?