Related
So I keep setting my watch notifications to "all", but after the screen turns off and I go back to the notification settings, it always goes back to " none".
The android wear version is 5.0.2
Maybe it's just a bug, but if someone could tell me how to fix this that would be great.
Thanks!
I think "theater mode" is on? Please check!
Verstuurd vanaf mijn Nexus 9 met Tapatalk
giancarlo_f said:
I think "theater mode" is on? Please check!
Verstuurd vanaf mijn Nexus 9 met Tapatalk
Click to expand...
Click to collapse
Nope.. I just turned "theater mode" on and then went back into the notification setting and it was set to "all".
I noticed that the problem I'm having is not constant. Like now it's working fine but earlier today and even before that it was having this issue.
Anything else you think it could be?
Thanks.
Same problem here.
---------- Post added at 07:57 PM ---------- Previous post was at 07:40 PM ----------
I seemed to get it working.
Went to settings-Device-Sounds and Notifications-Application Notifications. Then I selected "Android Wear" and turned on "Priority"
Hope it sticks.
@Malaysk Sorry to ping you on here mate but really need some help.
I flashed my Eonon GA5151F Mazda 3 android headunit with the Malaysk ROM and its all installed correctly.
The only issue I'm having now is the GPS isn't locking on. It can find sats in the sky (up to 12) then drops down to 1 for a few seconds then back up but never comes up that it has fixed / locked on.
Any suggestions I would be truly greatful!
Some specs just in case:
Screen res: 800X480
RK3188
I have the exact same problem with my kld unit - MCU 2.30
The Malaysk rom refuses to lock satellites
I then installed the latest stock KLD rom - and it also fails to lock them. I wonder is this related to the the latest we android core - rather than malaysk's specific rom?
Sent from my Nexus 10 using Tapatalk
Did yours lock on before you flashed the rom?
Mine worked fine and only changed the ROM so can only assume it's the ROM version perhaps.
Have you tried an older Rom version at all?
I had the same with my KGL - went back to the latest KGL rom and its been fine for about three months now.
It was locking fine before the update. I've gone back to the older factory firmware now and it's still not locking picked up loads of satellites but they all stay red
Sent from my Nexus 10 using Tapatalk
---------- Post added at 07:55 PM ---------- Previous post was at 07:23 PM ----------
Ok - went back to a much earlier stock rom now (22052015) and after 30 mins driving it finally locked. Hopefully it stays!
Update : no joy - today it's refusing to lock satellites again. Anyone have any idea why?
Sent from my Nexus 10 using Tapatalk
Ok well this is weird. I installed the APK that comes with the Malaysk ROM called "GPS Test" and my GPS is now locking on and working.
In frustration, I pulled out the unit - disconnected the GPS antenna - and reconnected. Everything now works. Go figure. Must have worked loose
Sent from my Nexus 10 using Tapatalk
Make sure to set the timezone correctly as well, I think this makes a difference.
Just installed a new 11-c0255 into my car. When I attempt to set up bluetooth I can find my phone no problem but when they try attempt connect you can see the bluetooth icon appear for a split second on the car screen, and the bluetooth buttons become colored. Then it all goes back to grey. A few second later it happens again(both the bluetooth icon and the colored buttons) then back grey.
I have tried on with both mine and my girlfriends phone and it does the same with both.
Also the weather app is always blank, even if i manually add a city it remains blank.
Any ideas?
Interesting enough my friends Iphone and his girlfriends stock HTC both connect fine. Could be a bluetooth issue with the CM13 me and my g/f are running.
Confirmed an issue with the CM13 rom we are using.
Still dont know why I have the blank weather app.
Finally! I thought i was the only one. CM13 in my Oneplus One does the same thing. I go back to 12.1 (5.1.1) and all is fine.
EDIT: Mine is a Pumpkin C0250
I have a OnePlus One and have been having TERRIBLE problems with Bluetooth not always connecting. I haven't suspected the phone because my Bluetooth OBD dongle also can't connect when it happens... but it may be possible something the phone is doing is crashing the bluetooth stack on the radio. Guess I'll switch back to the old Nexus 5 for a test run... *sighhhh*... Changing SIMs is a pain because I have a pretty hefty case on the OnePlus One.
EDIT: Oh, I see you were on CM13. I'm still on CM12.1 YOG4PAS3JL. Still, worth a shot.
singlecell83 said:
Also the weather app is always blank, even if i manually add a city it remains blank.
Any ideas?
Click to expand...
Click to collapse
Start here: http://forum.xda-developers.com/android-auto/mtcb-android-head-units-qa/weather-widget-t3305168
Hello. I have this problem too. My phone is a oneplus one. When i was on cm12.1 I had no problems at all. Now I'm on cm13 and i have exactly the same issue as you... Connects and disconnects two times, just for a moment and then keeps disconnected...
Bluetooth media works fine...
Anybody know any fix?
Thnx!
Enviado desde mi A0001 mediante Tapatalk
---------- Post added at 09:14 PM ---------- Previous post was at 09:13 PM ----------
itzal77 said:
Hello. I have this problem too. My phone is a oneplus one. When i was on cm12.1 I had no problems at all. Now I'm on cm13 and i have exactly the same issue as you... Connects and disconnects two times, just for a moment and then keeps disconnected...
Bluetooth media works fine...
Anybody know any fix?
Thnx!
Enviado desde mi A0001 mediante Tapatalk
Click to expand...
Click to collapse
Enviado desde mi A0001 mediante Tapatalk
singlecell83 said:
Also the weather app is always blank, even if i manually add a city it remains blank.
Any ideas?
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showpost.php?p=65228919&postcount=1353
With this version my weather app start working.
My volume wheel only works for the first 15 minutes or so then and then it stops working until I reboot the unit.
Any idea ? Software or hardware fix ?
A few have the same issues. Myself included. For me it was software related. Out of interest what navigation do you use.
Sent from my SM-G920F using Tapatalk
I agree, since a software reboot fixes it I'm guessing it a software. Did you find a fix ?
I'm using Waze
Waze was my culprit. Try an alternative as an experiment.
Sent from my SM-G920F using Tapatalk
Unfortunately, Waze is the reason why I bought the head unit. Although I'll try to see if that's the problem and if so ask Waze if they can fix it
Thanks
Some others have went back to an older version of Waze. The last one before the change in material design.
Some others with same problem have discounted Waze so it's a bit of a lottery.
Sent from my SM-G920F using Tapatalk
Just noticed I have the same problem as well (volume knob stops working after a few minutes, reboot fixes it for a bit, repeat). I don't know when it started as I've always just used the steering wheel controls for volume.
Kicker is that I don't use Waze nor have it installed.
Using latest (Apr 23 2016 RK3066 800x400, latest JY MCU) Malaysk ROM, basic JY headunit.
@gk66 - since you last wrote your post, have you had the problem occur again despite using the older version of Waze?
I don't use an older version. Ditched Waze completely. Use Google maps. Problem hasn't resurfaced yet.
Sent from my SM-G920F using Tapatalk
gk66 said:
I don't use an older version. Ditched Waze completely. Use Google maps. Problem hasn't resurfaced yet.
Click to expand...
Click to collapse
Ah, I should learn to read. Thanks for the info though!
I haven't done extensive testing but Waze seems to be the culprit in my case too.
Muting waze also works. I've set it to "alert only" and it's much better but still stops from time to time.
When Waze talks it lower or mute media volume, my guess is that Waze does it wrong or uses an old API, I've had problem even on my phone where media volume would stay low or stop altogether.
I'll make a bug report and hopefully they can fix it
Caddish said:
I haven't done extensive testing but Waze seems to be the culprit in my case too.
Muting waze also works. I've set it to "alert only" and it's much better but still stops from time to time.
When Waze talks it lower or mute media volume, my guess is that Waze does it wrong or uses an old API, I've had problem even on my phone where media volume would stay low or stop altogether.
I'll make a bug report and hopefully they can fix it
Click to expand...
Click to collapse
Thanks for that. Glad you've found the culprit.
Sent from my SM-G920F using Tapatalk
Waze is not the only cause, also this happens with pc radio with the latest malaysk firmware for rk3188
Nobody said it was the only culprit. Why not start a thread to identify all the culprits
Sent from my SM-G920F using Tapatalk
I'm having the same issue. Radio works fine until I launch waze, within ten minutes the knobs don't work anymore.
Since everybody is having sporadic issues, I'm actually testing out if the audio mixing you can set in Settings->GPS has anything to do with it. I always had it set to mixing, and I now put it to switch. Tomorrow I'll know more after a round trip to work.
No waze here, yet I have the same issue. Happens out of the blue, even when just running the original radio apk and no navigation at all. The SWC keeps working. Functionality returns after a reboot or a jump to the hardware settings. As the SWC always functions I don't mind TOO much but it a bit sloppy.
Tried changing the GPS settings today. Whatever I did, nothing helped, not even putting a random app that doesn't produce sound as my navigation app.
Which MCU do you all have? Mine is JY/Joyous...
Waze is not the culprit, it just happens more often when using it. Bluetooth calls (interrupting your current audio) often break it. Other apps switching audio break it too.
It is most likely some bug in the firmware related to switching the audio input.
There is no solution found yet.
---------- Post added at 11:12 PM ---------- Previous post was at 11:09 PM ----------
SilverViper2k said:
Since everybody is having sporadic issues, I'm actually testing out if the audio mixing you can set in Settings->GPS has anything to do with it. I always had it set to mixing, and I now put it to switch. Tomorrow I'll know more after a round trip to work.
Click to expand...
Click to collapse
Mine is set to Mixing 5. I haven't tried to switch yet.
---------- Post added at 11:14 PM ---------- Previous post was at 11:12 PM ----------
SilverViper2k said:
Which MCU do you all have? Mine is JY/Joyous...
Click to expand...
Click to collapse
KLD2, RK3188 SD. Came with KLD2 v2.77 firmware, now running v2.81. Both have the issue. I haven't tried flashing older firmware
I tried using tomtom as my main GPS application, same issue, so it's definitely not Waze specific. Friday I'll drive without using any GPS app and see if it still fails.
Next time as soon as I notice it failed, I'll check system log for any errors or exceptions, perhaps something stands out.
I do know that the turning of the knobs is logged in the log even after they failed and don't change volume. One of the xposed modules that shows the buttons pressed and such does not recognize turning of the knobs after they have failed...
SilverViper2k said:
I do know that the turning of the knobs is logged in the log even after they failed and don't change volume. One of the xposed modules that shows the buttons pressed and such does not recognize turning of the knobs after they have failed...
Click to expand...
Click to collapse
Hmmm. The system log still gets the volume knobs turning but not the app? That could mean the firmware is ok and the bug is somewhere in the Android audio?
shtirlitz111 said:
Hmmm. The system log still gets the volume knobs turning but not the app? That could mean the firmware is ok and the bug is somewhere in the Android audio?
Click to expand...
Click to collapse
Yeah that's why I started playing around the GPS settings...
Any idea which app/service is responsible for handling the volume knobs?
Anyone face the same issue? I manually updated the patch via side loading and sometimes the double tap won't wotk.
angka8 said:
Anyone face the same issue? I manually updated the patch via side loading and sometimes the double tap won't wotk.
Click to expand...
Click to collapse
I found it wasn't great in the dark, I assume it uses the light sensor to determine if in pocket etc
Sent from my Google Pixel XL using XDA Labs
I have noticed the same thing. It isn't 100% consistent.
FWIW: Mine seems to be very consistent if I triple tap. Perhaps the first tap wakes it up if it's in a deep sleep?
Hopefully fixed in the December update.
JAYNO20 said:
Hopefully fixed in the December update.
Click to expand...
Click to collapse
No change for me.
cam30era said:
No change for me.
Click to expand...
Click to collapse
Has been working consistently for me so far. Will post back if that changes.
---------- Post added at 03:07 PM ---------- Previous post was at 02:26 PM ----------
OK, still not working consistently. I don't get what's happening to make it randomly not work. When it doesn't work, it doesn't matter how many times I tap it does NOTHING. Then if I unlock it with my fingerprint and shut it off again it immediately lights up the ambient display like I just tapped on it again.
JAYNO20 said:
OK, still not working consistently. I don't get what's happening to make it randomly not work. When it doesn't work, it doesn't matter how many times I tap it does NOTHING. Then if I unlock it with my fingerprint and shut it off again it immediately lights up the ambient display like I just tapped on it again.
Click to expand...
Click to collapse
I can't tell you the "why". But I can tell you that mine does work consistently if I tap it 3 times. Something's different in our devices, or our setup....
Edit: not 5 minutes after posting this, my XL started randomly not responding to dttw.
cam30era said:
I can't tell you the "why". But I can tell you that mine does work consistently if I tap it 3 times. Something's different in our devices, or our setup....
Edit: not 5 minutes after posting this, my XL started randomly not responding to dttw.
Click to expand...
Click to collapse
Makes no sense. I'm glad we are seeing the same issues though, at least it's consistent there
I'm having the same exact issues. Tap not working consistently and sometimes the lift doesn't work either. Hmm.
It's worth noting I had the same issues with the Elemental kernel before this ddtw option was available. The ddtw option was just as inconsistent for me.
Neither working at all for me.
Update: Seems to be working fine now.
if you have a screen protector that might cause the issue
if it still doesnt work without screen protector reflash the factory image
The update seems to fix the issue.
Update: the issue still there. But much less frequent
The is double tap to wake? Is this with a custom kernel? Otherwise I didn't know this was an option. How do you activate that feature?
I have noticed that is works better if the screen is locked. So if your phone doesn't lock for 5 or so minutes, it may not work until after that time. Try to set your phone to "Power button instantly locks" and then try it. Mine was not working at all, but when I locked the device sooner, it started to work consistantly. Might not help you, but fixed it for me.
Works fine for me, do you have a tap on?
---------- Post added at 09:42 AM ---------- Previous post was at 09:42 AM ----------
GCbard said:
The is double tap to wake? Is this with a custom kernel? Otherwise I didn't know this was an option. How do you activate that feature?
Click to expand...
Click to collapse
It's an option with the newer OTA.
clockcycle said:
Works fine for me, do you have a tap on?
---------- Post added at 09:42 AM ---------- Previous post was at 09:42 AM ----------
It's an option with the newer OTA.
Click to expand...
Click to collapse
Where is this option located? I'm on the November update. Is this with the December update?
GCbard said:
Where is this option located? I'm on the November update. Is this with the December update?
Click to expand...
Click to collapse
December OTA. Same location as other Moves/ gestures.
FWIW: what I've noticed is that if my phone is sitting on something, DTTW works 100% of the time. If I have it in my hand, it's very sporadic.