I've tried everything. Ever since Google play services updated along with the AA app the app closes, and when I plug it in to my head unit I get a notification saying Google play services has stopped.
Anyone experience this? I'm on Marshmallow with Google Play Services 8.7.xx
colbyrainey said:
Samsung Galaxy Note 4 (Rooted, CM13)
Click to expand...
Click to collapse
Try with another smartphone, your CM13 might not be yet compatible with AA.
Marshmallow CyanogenMod might have some problems in the connectivity (ex. Bluetooth), CM12 might work...
themissionimpossible said:
Try with another smartphone, your CM13 might not be yet compatible with AA.
Marshmallow CyanogenMod might have some problems in the connectivity (ex. Bluetooth), CM12 might work...
Click to expand...
Click to collapse
Thanks for the advice, but it's been working on my phone with CM13 for 3+ months before the latest round of updates.
colbyrainey said:
it's been working on my phone with CM13 for 3+ months before the latest round of updates.
Click to expand...
Click to collapse
See here and the comments:
https://www.youtube.com/watch?v=xnQco_j2-HI
Thanks. That's not quite the issue I'm having, though. The comments didn't seem to be much help, though.
Sent from my SM-N910V using XDA-Developers mobile app
colbyrainey said:
Thanks. That's not quite the issue I'm having, though. The comments didn't seem to be much help, though.
Sent from my SM-N910V using XDA-Developers mobile app
Click to expand...
Click to collapse
It must've been something in the latest build from my developer; I reverted back to a previous build and it is working again. Thanks for your help!
Related
Pebble finally released its official 2.0 update to Android and I did a quick review on what to expect! Check it out!
http://goo.gl/xRQUeM
Updated around 130pm EST. No issues as of yet.
Sent from my LG-V500 using Tapatalk
Shawheim said:
Updated around 130pm EST. No issues as of yet.
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
When i click on notifications in the settings or development options, the app crashes. Does anyone else have this problem or know a fix?
I'm on 2.0.12
Are you on the official update or were you using the beta first?
Sent from my LG-V500 using Tapatalk
The official
Sent from my Nexus 5 using xda app-developers app
Can't help, I'm using Notifications Center. But mine is not failing. I went from b11 to official through Google Playstore.
Yeah Idk. Uninstall and reinstall. That's the only suggestion I have.
Sent from my SM-N900P using Tapatalk
How are people finding it?
I went from Beta 10 (bought my watch the day it came out)
-it was crap, buggy, slow, the app store made my phone hot and chewed the battery.
to Beta 7 (the release prior to "app store")
-no app store. instant responses. worked pretty well
to Beta 11
-still a bit slow, but the Pebble app behaved and battery use was okay. App store worked better (could scroll back and forth between watch faces)
to Official
-barely tested before an update came out
to Official.. (update 1?)
-is okay.. not as fast as Beta 7 still.
-Phone has started crashing.
-Powered off at 3am the other day (GSAM graph and Sleep as Android had data until then)
-Froze on the app store this morning. Then crashed.
..not sure whether I'll try uninstalling everything or perhaps flashing a new ROM.
Incidentally, I have a mate who won't move off of Beta 7
Official got an update today. Working very well so far
I changed my rom and it seemed to have fixed the problem I was having earlier.
Sent from my Nexus 5 using xda app-developers app
After I received my Pebble, the firmware was updated to the latest version 2. I had been using with my Note 3 on stock KitKat and found that almost half the time, it will lose the bluetooth connection. Has anyone using Note 3 encounter this issue?
Today I got very frustrated with it and tried factory reset of the Pebble but still has same issue. I even tried Pebblebits but the issue remains.
I tried to flash the beta 9, 10, and 11 but didn't manage to flash. Is there anyway to go back to the last most updated version 1 firmware? The only reason I want to do that is to find out if my issue is Pebble or rom very issue.
Sent from my Nexus 7 using Tapatalk
V2.0.2 firmware updated on my Pebble. Hopefully the bluetooth issue I had will be resolved.
Edit:
Did factory reset on my Pebble a few times but still cannot solve the problem.
Next, suspected that Notification Center seems to cause the BT disconnection, so I removed it. Tried other free notification apps but still had problem with BT disconnection.
Decided to purchase YaNC PRO and unfortunately still had BT disconnection.
The last straw was to reboot my Note 3.
Looks like the BT disconnection is gone. Notifications are also coming in now. Hopefully this situation continues.
Edit:
It's slightly improved but at times, I still face BT disconnections, ie notifications not sending to my Pebble even when the notification bar shows the Pebble is connected.
Of anyone has any suggestions, please share with me. Thank you.
Sent from my Nexus 7 using Tapatalk
I have a disconnection too. But this is a data type connection. If I have weather on the watch it wont update, when I do a manual update on the watch it says disconnected. The way to get it back is to reboot the phone, or go to the support tab, have it check for a update, and let it force close, then its OK for a while. I'm currently use Kitkat (Custom ROM),unfortunately I had to remove weather from my watch.
Sent from my Next7P12-8G using xda app-developers app
anybody have a hard time accessing the app store and the watchface stores?
superbonto said:
anybody have a hard time accessing the app store and the watchface stores?
Click to expand...
Click to collapse
Yeah, I can't access it, either from the app or the site. Seems to be down at the moment.
Sent from my Nexus 5 using XDA Premium 4 mobile app
tkgod said:
Yeah, I can't access it, either from the app or the site. Seems to be down at the moment.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks dude!
I was worried because I just bought this Pebble and I thought mine was a faulty unit.
I"m using Pebble with my Galaxy S3 (rooted stock ROM) and I had several times problem with random disconnection and reconnection of BT connection with Pebbles.
Always solved by default reset of Pebble + removing / installation of Pebble application.
Hope that it will help sb who have same problem...
Looks like the latest Google Search update is testing always listening (lock screen, apps) for OK Google Hotword detection. Only for "certain accounts" at the moment though.
with Search 3.5 installed, certain Google accounts are now able to use “OK Google” Hotword detection in any screen, including the lock screen and third-party apps. Unfortunately, this feature is only available on a few accounts at the moment, but hopefully the rollout continues quickly.
Click to expand...
Click to collapse
http://www.xda-developers.com/andro...and-android-tv-remote-released-to-play-store/
This has been a highly requested feature since the launch of the N5. Anyone have one of these mythical accounts?
Link to force the functionality:
emoibm said:
Check this out : https://plus.google.com/105167476097349888456/posts/46A68S7Dytb
Click to expand...
Click to collapse
New possible work around:
OuncE718 said:
Type in " OK Google Everywhere" in the search app and then go to settings and you will now see the option.
http://www.androidpolice.com/2014/07/03/still-dont-have-ok-google-everywhere-try-this-simple-trick/
Click to expand...
Click to collapse
Can you just install the APKs in order to get the updates without having to wait for our turn? Even on a Rom?
Thanks in advance
Nope
Sent from my Nexus 5 using Tapatalk
I tried with the APK but didn't work for me and others. Someone said we got to wait.
Sent from my Nexus 5 using XDA Free mobile app
NinoDolce1 said:
I tried with the APK but didn't work for me and others. Someone said we got to wait.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I guess your account isn't one of the few.
Do you guys think it is just random accounts, or would these account holders know ahead of time that they have these special permissions? I'm assuming it's for accounts which signed up for some beta testing.
You are right. It might be for early beta testers.
Sent from my Nexus 5 using XDA Free mobile app
Started working for me as soon as I installed the apk. Haven't done anything special as such to get it. You can get the hotword detection working from settings. Basically, it works exactly like a moto x except it doesn't work when the phone is both not being charged and also the screen is off. Waiting for custom hotwords now, "OK Google" seems kinda lame.
I read that it's being released in waves to different users and you also have to be on the latest Google play services 5.* But it is being rolled out in a back end search update in waves, few reports of users already having it.
Sent from my Nexus 5 using XDA Free mobile app
simonarturo said:
Can you just install the APKs in order to get the updates without having to wait for our turn? Even on a Rom?
Thanks in advance
Click to expand...
Click to collapse
Usually you are able to, except for this particular app now. So I'm sad.
I have it, lol.
Check this out : https://plus.google.com/105167476097349888456/posts/46A68S7Dytb
emoibm said:
Check this out : https://plus.google.com/105167476097349888456/posts/46A68S7Dytb
Click to expand...
Click to collapse
Confirmed working. Thanks for posting!
Sent from my Nexus 5 using XDA Free mobile app
This update only seems to be working on my S5 and not N5
emoibm said:
Check this out : https://plus.google.com/105167476097349888456/posts/46A68S7Dytb
Click to expand...
Click to collapse
Nice! Thanks for sharing. I'm gonna edit OP with your link.
emoibm said:
Check this out : https://plus.google.com/105167476097349888456/posts/46A68S7Dytb
Click to expand...
Click to collapse
WIll this work with italian language? Thanks...
I guess my account is part of "the few"??? I went to Google Settings -> Voice -> "OK Google" Detection and saw a few extra options including detect anywhere. Ticked those options and worked great even on Nova Launcher with Nova's native OK Google feature DISABLED.
I was watching an Android wear video on YouTube on my phone and with this turned on when the person in the video said "OK google" my phone heard it and tried to search.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Confirming this works on my N5 with L. Thanks for the second link with instructions.
Anthonok said:
I was watching an Android wear video on YouTube on my phone and with this turned on when the person in the video said "OK google" my phone heard it and tried to search.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Haha it's the "XBOX ON" issue all over again. I think maybe it should stop listening when the speaker is outputting sound since they're right next to each other.
Here's the link for the apk http://www.androidfilehost.com/?w=f...1c8ecbba2b5ce81b6d0337194d149d219daab5a3b7513
Works great for me. Woohoo!
Hello, I'm having a bug on my newly flashed CyanogenMod 12 on my nexus 6, I found a bug where the settings crash whenever I try to activate a new keyboard, if anyone has this bug as well please let me know so I know its a CyanogenMod based bug and not a mistake in flashing, I have the newest nightly, Jan 18
Joshua.n said:
Hello, I'm having a bug on my newly flashed CyanogenMod 12 on my nexus 6, I found a bug where the settings crash whenever I try to activate a new keyboard, if anyone has this bug as well please let me know so I know its a CyanogenMod based bug and not a mistake in flashing, I have the newest nightly, Jan 18
Click to expand...
Click to collapse
I have the same problem on my Nexus 7 (2012) with the latest version of CM12 nightly (01/18/2015). I'm unable to use Swiftkey and have FC with settings.
Yay, okay thank you very much
Joshua.n said:
Hello, I'm having a bug on my newly flashed CyanogenMod 12 on my nexus 6, I found a bug where the settings crash whenever I try to activate a new keyboard, if anyone has this bug as well please let me know so I know its a CyanogenMod based bug and not a mistake in flashing, I have the newest nightly, Jan 18
Click to expand...
Click to collapse
Speaking of bugs, I am having trouble sending or receiving MMS using the CM12 nightlies messaging app. I had to switch to Textra and that works. I can't figure out why and neither could AT&T. Any ideas?
Sent from my Nexus 6 using XDA Free mobile app
Joshua.n said:
Hello, I'm having a bug on my newly flashed CyanogenMod 12 on my nexus 6, I found a bug where the settings crash whenever I try to activate a new keyboard, if anyone has this bug as well please let me know so I know its a CyanogenMod based bug and not a mistake in flashing, I have the newest nightly, Jan 18
Click to expand...
Click to collapse
This fixes it
http://review.cyanogenmod.org/#/c/85829/
fredgarvin5 said:
Speaking of bugs, I am having trouble sending or receiving MMS using the CM12 nightlies messaging app. I had to switch to Textra and that works. I can't figure out why and neither could AT&T. Any ideas?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Its working for me, on the texting app, sorry not sure why it isn't for you
apascual89 said:
This fixes it
http://review.cyanogenmod.org/#/c/85829/
Click to expand...
Click to collapse
Thank you for this but im a bit of a novice when it comes to these things can you please explain what to do, sorry for the inconvenience
Joshua.n said:
Thank you for this but im a bit of a novice when it comes to these things can you please explain what to do, sorry for the inconvenience
Click to expand...
Click to collapse
Oh sorry I should've explained better. That is the fix, but unless you build your own, there's not much to do but just wait for that to get merged. Once it does get merged it'll be fixed in the next nightly after that. If you Co. 0ile your own builds you can cherry pick that into packages/apps/Settings before building.
apascual89 said:
Oh sorry I should've explained better. That is the fix, but unless you build your own, there's not much to do but just wait for that to get merged. Once it does get merged it'll be fixed in the next nightly after that. If you Co. 0ile your own builds you can cherry pick that into packages/apps/Settings before building.
Click to expand...
Click to collapse
Oh ok, i guess ill just have to wait then, thank you though
I had the same problem. Tried the fix and it didnt work. Went back stock which is okay but isnt cm12
I really want to install CM12 but I guess I'll have to wait until they iron out the bugs. I am also wondering if any of you guys who installed CM12 can receive calls while the phone's headphone jack is connected to car AUX cables. I can't hear a thing what the other side was saying, but they can hear me fine. Thanks in advance. I experience this same exact bug on stock.
Did you get a different cable and try?
fredgarvin5 said:
Speaking of bugs, I am having trouble sending or receiving MMS using the CM12 nightlies messaging app. I had to switch to Textra and that works. I can't figure out why and neither could AT&T. Any ideas?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Try deleting the unused apn settings. Leave only the one you're using a nd delete the rest
apascual89 said:
Try deleting the unused apn settings. Leave only the one you're using a nd delete the rest
Click to expand...
Click to collapse
By golly that worked! How did you know that?
Sent from my Nexus 6 using XDA Free mobile app
fredgarvin5 said:
By golly that worked! How did you know that?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
LOL I went through the same. Can't remember who recommended it. It was in the Slim ROMs thread.
apascual89 said:
LOL I went through the same. Can't remember who recommended it. It was in the Slim ROMs thread.
Click to expand...
Click to collapse
Thanks!
Sent from my Nexus 6 using XDA Free mobile app
Led
Anyone know why there is an led for charging when phone is off but not while phone is on? Any issues with 21s build?
Joshua.j.phillips1 said:
Anyone know why there is an led for charging when phone is off but not while phone is on? Any issues with 21s build?
Click to expand...
Click to collapse
Where is that option for led?
Sent from my Nexus 6 using XDA Free mobile app
fredgarvin5 said:
Where is that option for led?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
No option. Turn phone off and use plug charging. For some reason, if you use the qi charger, it automatically reboots phone. If phone is off, and plugged in, led turns on. Turn on phone, led disappeared. On Nexus 6, unlocked, 21st build.
There are options now.
Sent from my Nexus 6 using XDA Free mobile app
I'm wanting to index some common issues and solutions (If any) for PA's 1st version for the N6. This is N6 only! not Oneplus, 6P, ect
Keep a clean format with your posts
---------
Description of issue, how to repeat.
Solution
log-cat link (if you have one)
---------
I'll try to update this as they are posted.
Only one I have seen myself is the security settings
Bug- Settings crashing when trying to configure pin, pattern, password
solution- none
Log- none, will be fixed next release according to PA Team
Remember do not use Open Gaaps. PA team has had some issues. Also not recommended to use full package...(I'm running Nano myself)
Can't even pass bootup screen.
Sent from my Nexus 6 using XDA-Developers mobile app
usmanhaider101 said:
Can't even pass bootup screen.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Full wipe and reflash. What GApps are you using?
usmanhaider101 said:
Can't even pass bootup screen.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Use banks gapps. Worked great for me. Actually running pa right now.
Sent from my Nexus 6 using Tapatalk
I have just downloaded the latest version of gapps(stock) and I'm running PA Nexus 6. Whenever I get a call or place a call the active call screen does not show up. So without my smart watch I have no idea who is calling. Has anybody else ran into this error?
Bluetooth/android wear worked fine, however when I paired the phone to my car the bluetooth share process started crashing constantly.
I switched to purenexus after two days but here's what I noticed:
-I was using the elementalX kernel
-random reboots when listening to google play music
-icon theming only worked once while using google now launcher (applied one pack and then couldn't change that pack)
No logcats, sorry. I might try going back after the next substantial update and keep the stock kernel that comes with it.
Sent from my Nexus 6 using Tapatalk
jnyce87 said:
I have just downloaded the latest version of gapps(stock) and I'm running PA Nexus 6. Whenever I get a call or place a call the active call screen does not show up. So without my smart watch I have no idea who is calling. Has anybody else ran into this error?
Click to expand...
Click to collapse
Same here! Went to DP4
Sent from my SM-T330NU using Tapatalk
dpalmer76 said:
Same here! Went to DP4
Click to expand...
Click to collapse
Yea apparently there's a known issue with stock open gapps. But since I switched, I've had no issues what's so ever. I have to say this is the smoothest my nexus has ran in some time. Just patiently waiting for the next update when they fix the lockscreen pin fc.
Finally, I succeeded at installing closed framework on my customized stock Samsung ROM (meaning, stock without bloatware). Thanks to the Wanam guys, BTW, whom, unlike the actual xposed programmers, cared about making a flashable zip that actually works for us, Samsung users.
So I am finally able to try having push notifications still working, even if greenify is active, and other cool stuff. Even, yes, the Google Assistant.
The problem is: it keeps going back to the "get started" screen every time I say "OK Google", forcing the voice model retraining. This is annoying. Is there a fix?
It's a known issue, it happens on most devices (except some lucky users). I'm sure a fix is on his way
Sent from my Samsung SM-G920F using XDA Labs
Thanks.
I have the same problem ?
Prince Cooky said:
I have the same problem ?
Click to expand...
Click to collapse
Look before posting:
BaTarrY said:
It's a known issue, it happens on most devices (except some lucky users). I'm sure a fix is on his way
Click to expand...
Click to collapse
Sent from my Samsung SM-G920F using XDA Labs
Just reporting: the newest Google App update (6.8) fixed the issue.