Database Users

Screen mirroring and root

Evening all, I've just been using screen mirroring for the first time and every 10 minutes roughly it just stops and the TV goes back to a channel. I have rooted and wonder could that cause this?

mark2222 said:
Evening all, I've just been using screen mirroring for the first time and every 10 minutes roughly it just stops and the TV goes back to a channel. I have rooted and wonder could that cause this?
Click to expand...
Click to collapse
Hmm could this be a setting on your tv? I cannot find a setting on my phone which would cause this. Are you using a stock rom?

mark2222 said:
Evening all, I've just been using screen mirroring for the first time and every 10 minutes roughly it just stops and the TV goes back to a channel. I have rooted and wonder could that cause this?
Click to expand...
Click to collapse
I've had the same thing happen to me stock or rooted it looses sync and just stops after 5 minutes. I think it's because samsung doesn't really care about casting with all the other viable and way cheaper options out there i think the left it just because. The reason I'm saying this is because there's been no improvement since the s3. It's still as laggy. That's just my opinion. I might be wrong.
Sent from my SM-G900W8 using Xparent Cyan Tapatalk 2

Stock rom, annoying thing is that it wasn't lagging on my ue46f6670, just stops after a while.
Sent from my Nexus 10 using Tapatalk

Screen Mirroring for me has not worked at all even on stock, doesnt even find the TV in scan, the few times it has found my samsung smart TV it cannot connect or it says connected but nothing is shown on TV, whereas my Z1 connects instantly. In fact only my Z1 works all other devices I have tried do not.

WhatsApp card notification

My Moto360 has started not displaying a card notification when receiving a message via WhatsApp. All other notifications are vibrating and switching on the display with card, but WhatsApp it just vibrates.
I have tried uninstalling and re-installting whatsapp, tried re-syncing the apps, but WhatsApp continues not to switch the screen on ... any ideas?

You haven't blocked whatsapp from showing notifications on your 360? Its easily done by accident. You might have swiped then clicked on block this app. If you go into your wear settings, then blocked apps, check to see whatsapp isnt there.
Sent from my SM-G920F using Tapatalk

Nope, checked that .. nothing in the Blocked Apps. The phone vibrates, so it is getting the notification, but unlike all the other apps which vibrate and switch the screen on, this just vibrates. When I wake the screen, the notification is shown

Yeh, sorry, when I re-read your post I realised you couldn't have whatsapp in the blocked list if you are getting the vibration. #facepalm ?.
I had a similar issue with not receiving cards for my outlook work emails on a different device to my 360 a while back, it turned out to be an app I had used to set a custom vibration pattern for my outlook notifications. Im guessing that if you had a similar app installed you would have checked that.. also Im sure you would have tried a restart of your 360..
I think the problem is with your 360 as your phone is clearly pushing the notification to your 360 if you are getting the vibration. I know an app resync usually fixes most issues but as you've tried that what about a factory reset of your moto 360? I know its a bit drastic but I don't know what else to suggest.
Sent from my SM-G920F using Tapatalk

Tried a reset as well ... the funny (annoying part), is that the screen on notification did work for a while, and then just suddenly stopped, withouth me installing anything, so not so sure it is an issue with the Moto 360, as all other notifications pop up ..... WhatsApp is the only one that does not

Yeh thats really odd. Maybe someone else will have a suggestion that can fix it. What version of the 360 do you have? Ive got the smaller mens 2015 version. I'm at the end of my tether with it tbh for other reasons. The lag on the the device is so bad for me its virtually unusable by the end of my working day. Im gonna sell it and get the watch urbane instead.
Sent from my SM-G920F using Tapatalk

I have the 1st Gen, and to be honest I am more than happy with it, even with the outdated processor in there, don't really get that much lag with it .... and taking it off charge at 7 in the morning, and putting back on around 10pm ... still gettng about 40%+ battery left.
Surprised the 2nd gen (2015) version that you are having lags with it, have heard it was supposed to be rock solid
What other issues you having?

I get "android wear has stopped working" at least twice a day. Which means it can crash without me knowing so i miss notifications and calls throughout the day. Thats my biggest gripe at the moment. Then the lag progressively gets worse throughout the day, the only way i can fix it is to do a reboot but at its worst it can take 2-3 minutes for me to get into settings then another few minutes for each option in settings to load before i can choose restart device. I tried a factory restore last night but its already crashed 3 times today..
When i compare it to my other smart watch my 360 doesn't have that 60fps smoothness when navigating the interface. I did read that if you disable ambient then the lag isnt so bad but i like having ambient on.
I'm planning on making a YouTube video of how bad it is over weekend.
Sent from my SM-G920F using Tapatalk

I initially had the android wear stopping issue with mine, what I tried was a reset of the watch, removed all pairing with the phone, and then installed an older version of Android Wear .. think it was 1.1 (do a search on google, you will find a load of links). Then reset my watch up to the phone .... but .... tried running on Android Wear 1.1 for a few days, and it was stable. I then upgraded the Android Wear 1.4 through the Play Store (make sure to disable auto update, whilst testing, otherwise off it will go), and mine has been rock solid

albie999 said:
I initially had the android wear stopping issue with mine, what I tried was a reset of the watch, removed all pairing with the phone, and then installed an older version of Android Wear .. think it was 1.1 (do a search on google, you will find a load of links). Then reset my watch up to the phone .... but .... tried running on Android Wear 1.1 for a few days, and it was stable. I then upgraded the Android Wear 1.4 through the Play Store (make sure to disable auto update, whilst testing, otherwise off it will go), and mine has been rock solid
Click to expand...
Click to collapse
Thanks for the reply. I think I'll try out your suggestion now. Need my watch working, I've come to really rely on my watch for notifications as I can't have my phone on during working hours. It got so bad today with the lag and crashes I had to use my Razer Nabu instead of my Moto360.
Fingers crossed, I'll let you know how it goes [emoji106]
Sent from my SM-G920F using Tapatalk

The 2nd Gen really should not be that bad, as said, I have the 1st Gen and to be honest, hardly any lag, so hope this workaround works for you

albie999 said:
The 2nd Gen really should not be that bad, as said, I have the 1st Gen and to be honest, hardly any lag, so hope this workaround works for you
Click to expand...
Click to collapse
As the moto 360 2015 doesn't have a cable, its wireless charging only, how would you reflash a previous version of wear? Im kinda stumped lol
Last night I did another factory reset and i uninstalled a lot of apps that i didn't want running on my moto. Some apps seem to have a companion wear app for their mobile equivalent that automatically install.. Well ive taken a lot of crap off and i have seemed to have fixed the stability issue. Also i can use my device albeit with a small amount of lag. This i can live with for now, it seems that moto knows about "always on" causing lag on some devices. I'll hold out for an update to fix it [emoji106] [emoji3]
Sent from my SM-G920F using Tapatalk

Ah, should have said .. it is not Android Wear on the watch, but the companion android wear on the phone that I installed an older version. Don't believe you can actually change the version on the actual watch
I have ambient mode off, wifi off (dont really see the point) and tilt to wake off ... as it kept coming on when I changed gear in the car lol

install quick for wear

i know it's an old thread, but i still have the problem in android wear 2.0.
whatsapp notifications are extremely unreliable. it's like the developers do every single thing their own way.
i set my watch to show notifications until i swipe it away or down, the very few times whatsapp actually shows the notification it goes away after a few seconds.
the notifications do work, as i can manually swipe to the notifications and they're there. they just refuse to show automatically.
i'm not a heavy user, so i get few notifications of which most of them are from whatsapp. so my watch functions more like a normal watch.

Whattsapp issues wear 2.0
I too get a buzz but no card till I manually swipe up anyone managed to fix this whattsapp support are useless auto gen email each time

Android wear & MM

Hi
This is really a warning to anyone who has an Android wear (or probably any other kind of smartwatch)
My Gear LIve and LG Watch R worked perfectly with KK and Lollipop but with MM 522 it just would not work properly at all
i worked with a dev of one of the apps and it was only the Huawei with MM that caused any problems and notifications were just not getting to the watch
MM on a samsung worked no trouble and going back to 5.1.1 on the M7 again worked perfect
I liked MM but i didnt see that much difference to being worth keeping without the watch
So if you are planning on Upgrading and have a smartwatch then you will have issues
I am now back on 5.1.1 and rooted and all works fine

I have Asus ZenWatch 2 and it works with B522 properly. Only issue I have noticed is infrequent unconnecting, about twice a week. But I just run Android Wear app and watch is connected again.

I must admit I'm surprised that's is working OK for you add the tests we got when trying to resolve the issues were all down to huawei and the non standard calls they make and the permissions issues that were occurring
The doze feature in mm seemed to be conflicting with huawei's own features and stopping a lot of the notifications getting through even though those apps were set to protected.
It also seemed to be an issue with 1 app calling another appointment and again even though that permission was granted it still gave us issues.
But I suppose in the end every setup is different and in all honesty I don't think mm was a great step up grim lollipop anyway or at least not on the huawei
Sent from my SM-N920C using XDA-Developers mobile app

I have a Samsung Gear S2 Classic and since I installed MM on my MT7-L09, Samsung Gear app will not not load, it just opens and closes in a flash.
The only way to make it work is to switch off the Bluetooth on the phone, then open the Samsung Gear App, and press connect from the app. This will switch the Bluetooth back on, connects to the watch and the app works.
Weird and very frustrating until I figured out a workaround!
Sent using Tapatalk

I have a moto 360 2nd gen and works with no issues what so ever with MM, if anything it has become more reliable so it may just be a conflict with particular manufacturers?

sthentic said:
I have a moto 360 2nd gen and works with no issues what so ever with MM, if anything it has become more reliable so it may just be a conflict with particular manufacturers?
Click to expand...
Click to collapse
I've got the first gen Moto 360. when I updated to MM my watch at didn't receive any notifications (even the test ones). I did a factory reset and everything works fine now. The only issue I have is that sometimes the Gmail app pushes a ton of notifications for the same email.

Android Wear issue - no call indication

Hey,
I have a weird issue where i don't get call notifications (other apps work fine) on my GWR.
i just get "sim1" notification and it doesn't even vibrate ! just shows.
i added a pic.
Already did a full wipe of the phone and watch, not working !
HELP

I'm not having call notification issues on both Zenwatch 3 and Gear s3 Frontier.
Seems some kind of compatibility issue between your smartwatch and the smartphone.
Since you did both hard reset the watch and the phone I can figure out other solution.
But hey getting vibration during notification is up to the watch if has that feature and not the phone.
Sent from my iPad using Tapatalk

Im sure its the phone, tried another watch today.
Maybe ill try again with b27....are you running b29 ?

Got it, permission problem !!
Go to app settings - android wear - permissions :
Phone
Contacts
Hura !!

Good to hear.
Btw I'm on B08 A2017G version.
Sent from my iPad using Tapatalk

Making a call reboots my phone

Good morning XDA,
Situation: My Galaxy Note 4 (SM-N910A) died. Wouldn't turn on or anything, got a replacement N910A and it wouldn't register on the network or anything. NOW i have a SM-N910P board with a custom ROM running MM but unfortunately whenever i try to make a call it freezes the phone and restarts it. Can the original MM ROM be loaded to resolve this issue? How can this be resolved?
Current device:
Samsung Galaxy Note 4
Model: SM-N910P
Baseband version: N910PVPU4DPH4
Build Number: MMB29M.N910PVPU4DPH4
Could someone point me in the right direction to resolve this issue ASAP.

idon-kush said:
Good morning XDA,
Situation: My Galaxy Note 4 (SM-N910A) died. Wouldn't turn on or anything, got a replacement N910A and it wouldn't register on the network or anything. NOW i have a SM-N910P board with a custom ROM running MM but unfortunately whenever i try to make a call it freezes the phone and restarts it. Can the original MM ROM be loaded to resolve this issue? How can this be resolved?
Current device:
Samsung Galaxy Note 4
Model: SM-N910P
Baseband version: N910PVPU4DPH4
Build Number: MMB29M.N910PVPU4DPH4
Could someone point me in the right direction to resolve this issue ASAP.
Click to expand...
Click to collapse
So i came across something very interesting. I was doing a hard reset, got into recovery mode and saw this...
Android Recovery
MMB29M.N910PVPU4DPC1
why is recovery mode saying something dif from whats in the device config re Build/baseband ???!!!???
Still unable to make/receive call.

It could be your phone app. Try setting it as default calling app in settings. If you can't, try another phone app, like the Asus Zen phone app.
My Note 2, running MM had the same issue but I managed to solve that issue my playing around with some 3rd party phone app.

mha93 said:
It could be your phone app. Try setting it as default calling app in settings. If you can't, try another phone app, like the Asus Zen phone app.
My Note 2, running MM had the same issue but I managed to solve that issue my playing around with some 3rd party phone app.
Click to expand...
Click to collapse
Naw i tried many apps before and got ntn, and by ntn i mean the same rebooting issue, it's useless as is rn

Turn network to 2g only....I mean GSM only...

Have you tried setting the phone app as the default app? In settings - app - configure app - default app
I searched around and it seems to be a pretty common issue with cm13. I did both the setting the phone app as the default app and changing around the phone app and it seems to work so far for my phone

I know this is an old thread, but I was recently given a Note 4. I'd like to give it to my son to use, but it's having the same issue. It reboots when it receives or makes a call. It does have an aftermarket battery, do you think that would have anything to do with it?

Maybe it has issues with other apps
On my phone the same thing happens, I realized that being in ultra energy saving mode does not have that problem so I intuit some application installed on my phone is having conflict with the call application, disable a call recording application and I was able to make the call without restarting the phone, this may be the problem even though I have to comment that before I had no problems with the recordings of the calls.