Hi,
I recently flashed my HTC HD2 with the nand Android 2.2 (HSPL is 2.08.000)
I'm experiencing problems with the G sensor. Sometimes the screen won't flipp within the Browser market place mail client ect. The only app where everythng works fine is Teeter.
Do I have to instell a bug fix? Or is it a known problem with no fix available?
Thanks
Cuerly
It's hard to say without knowing which build you flashed. depending upon which kernel you are using, you might be able to calibrate the sensor.
I suggest that you ask this question in the relevant development thread... once you have 9 more posts under your belt.
Hi Guys, my first post! I'm having a troubles with my Blade. The rotating sensor axys isn't working, to be honest it never been working, even with the stock rom. I'm now running Cyano Gingerbread 7 and the situation looks always the same. Tried to switch the button on the menu off/on many times and tried also to move fast the phone in my hands... There is a way to check it? Somebody haves the service manual of the Blade, or help me in some way.
Thanks in Advance.
my auto rotation doesnt seem to be working. it just stop working and sometimes comes back if i reboot and sometimes doesnt. i first experienced it on a touchwiz rom, so i decided to flash an aosp rom and still the issue persists. i also tried some solutions i found after searching but none worked either.one thing i do knw is i dropped my phone a few days ago. could it be possible that the drop damaged the sensors that control phone orientation? any one have any suggestions on how to fix it?
Sent from my SM-N900T using XDA Premium 4 mobile app
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
as per title really?
I've googled around a bit and not found anything definitive to explain the root-cause.
A few sites and threads claim to fix or provide a workaround, but from what I've read these are not 100% guaranteed to fix on all variants , all ROMs
I personally have tried latest versions of:
RamRom
DN
X-Rom
Norma
...with none having any fingerprint functionality before or after trying various "fixes"
What gives?
Edit: Yes, we know fp is pretty crap on N4 out of the box anyway, but please, can someone provide detail on why the N7 ports often fail in fp function ?
Well actually the fingerprint reader is really great on my N910C, and I have yet to find any Marshmallow rom that offers fingerprint log-on after a cold boot. They all work for apps and stand-by on/off log-on, but not at boot.
I think, as per usual, the hardware support for developers is crap by Samsung.
In Lollipop roms the fingerprint reader works like a charm.
I'm using nemesis Rom, using 3rd party app work like a charm.
Name of d app called (applock) pro version from play store.
Sent from my SM-N930F using Tapatalk
Finger scan lock is working flawlessly in RamRom here on latest version (6) for N910F/G. It was pretty smooth on the last version (4) too.
jult said:
Well actually the fingerprint reader is really great on my N910C, and I have yet to find any Marshmallow rom that offers fingerprint log-on after a cold boot. They all work for apps and stand-by on/off log-on, but not at boot.
I think, as per usual, the hardware support for developers is crap by Samsung.
In Lollipop roms the fingerprint reader works like a charm.
Click to expand...
Click to collapse
Fingerprint Enabler xposed module can be used to enable fingerprint log-on after boot.
And if one wishes to bypass the fingerprint log-on, No Lock Home xposed module can be used, works when connected to wi-fi.
If you're talking about Note 7 ports, the reason why fingerprint is not working, the same reason as to why AOD is not working, is because of hardware differences.
The reason why Ramrom manages to get fingerprint working is because it's not really a port but more of a stock Note 4 rom with a Note 7 skin and apps available on it.