Database Develop

[Q] All calls only use speaker phone?!

Verizon Moto X
Every time an incoming or outgoing call is made, audio output is only on the speaker. If I hit the button to turn off speaker, it goes back to speaker seconds later. Can anyone help?
EDIT: No ROM, pure stock from Verizon. I reset the device and cleared cache already.

G00gle26 said:
Verizon Moto X
Every time an incoming or outgoing call is made, audio output is only on the speaker. If I hit the button to turn off speaker, it goes back to speaker seconds later. Can anyone help?
Click to expand...
Click to collapse
Are you using a ROM? Xposed? Stock? First off you could try clearing cache and data of the phone app. If you are using a ROM, search the ROM thread. If you are using Xposed, uninstall it and see if the problem goes away. If the problem persists try a factory reset after backing up your data.

PiousInquisitor said:
Are you using a ROM? Xposed? Stock? First off you could try clearing cache and data of the phone app. If you are using a ROM, search the ROM thread. If you are using Xposed, uninstall it and see if the problem goes away. If the problem persists try a factory reset after backing up your data.
Click to expand...
Click to collapse
Sorry I should I specified that info.
No ROM, pure stock from Verizon. I reset the device and cleared cache already.

G00gle26 said:
Sorry I should I specified that info.
No ROM, pure stock from Verizon. I reset the device and cleared cache already.
Click to expand...
Click to collapse
Boot in safe mode: hold volume down at the first splash screen. From a power on. But if you did a data reset then I suspect a hardware failure.
---------- Post added at 06:37 AM ---------- Previous post was at 06:35 AM ----------
Do a RSD restore of the XML/FXZ.

two issues i have dealt with on the same problems across multiple devices. Main two options causing this are:
1. you downloaded some weird app that did some weird stuff with the speaker phone, even uninstalling the app could still be causing the problem. For this issue (if you can think of any apps you downloaded and possibly used for a day or a minute then uninstalled) go download the app again, look for any setting that could have delt with car mode, or plugged in mode, or docking mode, or speakerphone mode, or something similar and disable it, clear data and cache on app, then uninstall and see if it works.
2. you have dust or some debris in the charging port that is causing the phone to think that it is in dock mode where speaker phone automatically turns on. use air blaster or a toothbrush if the dirt is bigger in there.
those are the two main ones i have seen. see if they work it out. one phone that downloaded an app that caused this was an app about speed velocity while travelling, it had some weird settings for some docking thing i think and i had to check an uncheck it before unsinstalling to get the problem fixed

jayboyyyy said:
two issues i have dealt with on the same problems across multiple devices. Main two options causing this are:
1. you downloaded some weird app that did some weird stuff with the speaker phone, even uninstalling the app could still be causing the problem. For this issue (if you can think of any apps you downloaded and possibly used for a day or a minute then uninstalled) go download the app again, look for any setting that could have delt with car mode, or plugged in mode, or docking mode, or speakerphone mode, or something similar and disable it, clear data and cache on app, then uninstall and see if it works.
2. you have dust or some debris in the charging port that is causing the phone to think that it is in dock mode where speaker phone automatically turns on. use air blaster or a toothbrush if the dirt is bigger in there.
those are the two main ones i have seen. see if they work it out. one phone that downloaded an app that caused this was an app about speed velocity while travelling, it had some weird settings for some docking thing i think and i had to check an uncheck it before unsinstalling to get the problem fixed
Click to expand...
Click to collapse
Didn't download any new apps. I won't through them all and the only ones that are related to the speaker or phone calls is:
eCID
AutomateIt
I did what you said on both apps and cleaned the charging port with an air duster, didn't fix it.

G00gle26 said:
Didn't download any new apps. I won't through them all and the only ones that are related to the speaker or phone calls is:
eCID
AutomateIt
I did what you said on both apps and cleaned the charging port with an air duster, didn't fix it.
Click to expand...
Click to collapse
it might not be an app that you would think is related to phone calls. any app that may change its settings if it is in dock mode could cause. such as moto assist. it could also just be a faulty charger port. I haven't seen anyone else say anything about this issue on an x so i would assume it is either HW related and you need to return it or it is app related. even dusting out the port though might not have gotten some gummy stuff out that could be causing it fyi. but these are the first reports that i have seen so thats all that i got.

jayboyyyy said:
it might not be an app that you would think is related to phone calls. any app that may change its settings if it is in dock mode could cause. such as moto assist. it could also just be a faulty charger port. I haven't seen anyone else say anything about this issue on an x so i would assume it is either HW related and you need to return it or it is app related. even dusting out the port though might not have gotten some gummy stuff out that could be causing it fyi. but these are the first reports that i have seen so thats all that i got.
Click to expand...
Click to collapse
First thing I did was I cleared out Moto Assist and turned off it's features. Thank you for trying though.

G00gle26 said:
First thing I did was I cleared out Moto Assist and turned off it's features. Thank you for trying though.
Click to expand...
Click to collapse
If you are willing to try, attempt to flash the FULL SBF for your carrier (the same version you are currently on) using RSD Lite or manual method (instructions in the General sub-forum, "Return to 100% Stock" thread).
You see, using an SBF to return to stock can actually repair a corrupted or damaged filesystem because it *replaces* the partitions. A "factory restore" cannot. It only erases userdata and cache.
It will erase everything, so copy anything important (pictures etc.) to your PC before doing this. It is your best hope of recovering. If this does not fix it, it is almost certainly a hardware issue.
Good Luck :good:

If after a full reflash this still occurs, I'd think it's a hardware related issue that you'll have to RMA your phone for or have swapped by Verizon. Personally, I hate Verizon refurbs as they use a cheaper 3rd party to "fix" phones (they usually make them worse). The 4.4.4 image doesn't wipe data, and when manually flashing, you can exclude the erase userdata command. For manual flashing, use mfastboot and follow the flashing order and commands in the XML. RSD will do it automatically.
Some people have also had no front or rear camera access too, and that's hardware related (usually a ribbon cable connection or defective sensor).

Jason.DROID said:
If after a full reflash this still occurs, I'd think it's a hardware related issue that you'll have to RMA your phone for or have swapped by Verizon. Personally, I hate Verizon refurbs as they use a cheaper 3rd party to "fix" phones (they usually make them worse). The 4.4.4 image doesn't wipe data, and when manually flashing, you can exclude the erase userdata command. For manual flashing, use mfastboot and follow the flashing order and commands in the XML. RSD will do it automatically.
Some people have also had no front or rear camera access too, and that's hardware related (usually a ribbon cable connection or defective sensor).
Click to expand...
Click to collapse
The new 4.4.4 "image" -does- erase data. The original leaked FXZ posted by @SamuriHL didn't include the erase userdata command, but the new leaked FXZ does include it. SamuriHL only hosted the first leak temporarily until the new was posted to the droid-developers website.
The actual "images" inside both leaks are 100% identical though. The only difference is the new one contains the erase userdata command, and (I think) the "<step operation="getvar" var="max-download-size" />" command as well. Before anyone asks, NO you don't need to use the new one if you already used the original one. Other than the stated commands, they are completely identical.
I'm only putting this out there so someone doesn't flash the new one thinking their data will be saved -- it will not. That is, of course, unless you use SamuriHL's excellent tools made for this purpose....they allow you to preserve your userdata.
:good:

Jason.DROID said:
If after a full reflash this still occurs, I'd think it's a hardware related issue that you'll have to RMA your phone for or have swapped by Verizon. Personally, I hate Verizon refurbs as they use a cheaper 3rd party to "fix" phones they usually make them worse!
Click to expand...
Click to collapse
I always thought so. I got my first Official Moto refurbished phone when Moto sent me a Maxx for my X. Totally different packaging.
---------- Post added at 08:31 AM ---------- Previous post was at 08:14 AM ----------
Oh, & the Maxx is flawless!

I solved it! I isolated the problem to the app AutomateIt. There was a rule that was enabled by default when the app installed that turned the speaker on when away from the ear but the second rule to turn it off when it goes back next to your ear never triggered. So it's not a hardware issue thank GD. Case closed folks, thanks for all your help and the tip for safe mode. :good:

Smart Lock Settings Disappeared?

I am running an XZ1 Compact US version stock and locked bootloader. I am on the 47.1.A.12.205 firmware and when I go to smart Lock in settings it is blank. Has anyone else had this issue?
Trying to upload screenshots but cannot currently.

Milly7 said:
I am running an XZ1 Compact US version stock and locked bootloader. I am on the 47.1.A.12.205 firmware and when I go to smart Lock in settings it is blank. Has anyone else had this issue?
Trying to upload screenshots but cannot currently.
Click to expand...
Click to collapse
Apparently the smartlock feature has been fixed in the latest firmware update.
But if you want to see the page before you update, open settings\lock screen & security, scroll to the bottom and disable smart lock (google) under trust agents, reboot the phone, go back to trust agents, enable smart lock (google), now go back to the smart lock settings and they will be visable.

Latest firmware has not fixed the issue, at least not for me. Smart lock settings still are blank after every reboot. I still have to use the trust agent trick and reboot again.

htc 10, 7.1.2 LOS ROM, same issue here.
after trying everything mentioned, nothing worked.
so I downloaded a newer google play services via apkmirror
it actually froze the device when trying to enter smart lock... thus I went to apps and uninstalled back to the previous version.
bingo bango we have smart lock settings.
worth a try, you lose no data, and is quicker than clearing cache

andybones said:
htc 10, 7.1.2 LOS ROM, same issue here.
after trying everything mentioned, nothing worked.
so I downloaded a newer google play services via apkmirror
it actually froze the device when trying to enter smart lock... thus I went to apps and uninstalled back to the previous version.
bingo bango we have smart lock settings.
worth a try, you lose no data, and is quicker than clearing cache
Click to expand...
Click to collapse
U should wait and see if it lasts...
We already know how to make it appear again. The problem is that after a few days, it goes back empty again.

Dany XP said:
U should wait and see if it lasts...
We already know how to make it appear again. The problem is that after a few days, it goes back empty again.
Click to expand...
Click to collapse
I've been checking it multiple times, I'll report in a few days. This was just something that worked for me and shared. :good:
. Also different phones, but where's the harm in trying to help?

andybones said:
I've been checking it multiple times, I'll report in a few days. This was just something that worked for me and shared. :good:
. Also different phones, but where's the harm in trying to help?
Click to expand...
Click to collapse
Updates?

Dany XP said:
Updates?
Click to expand...
Click to collapse
Smart lock is broken. It holds 'trusted devices' for a couple of days, sometimes only hours. It then resets itself and goes back to a blank page. Google don't seem to be interested in fixing it and although Sony keep up with the security updates, it's not covered by that. Don't hold your breath fir a fix anytime soon.

Didgesteve said:
Smart lock is broken. It holds 'trusted devices' for a couple of days, sometimes only hours. It then resets itself and goes back to a blank page. Google don't seem to be interested in fixing it and although Sony keep up with the security updates, it's not covered by that. Don't hold your breath fir a fix anytime soon.
Click to expand...
Click to collapse
I was asking to andybones, he was trying a new Google play services, as u can read above...

Dany XP said:
I was asking to andybones, he was trying a new Google play services, as u can read above...
Click to expand...
Click to collapse
As I said, I wouldn't hold your breath. The official Google forum still has no fix.

Dany XP said:
Updates?
Click to expand...
Click to collapse
Hey, sorry for not posting sooner, totally forgot.
I hadn't been checking it, but I only use the on body detection. Is the issue that it is blank AND the services stop working, or is it the blank page problem only?
Onbody detection has been working for me since last posting but as mentioned, forgot to keep checking for blank page. Right now I checked and it isn't blank, however, I do flash gapps relatively often to update the apps. I last did this 2 days ago and I'm thinking that is why it isn't blank right now, but I do feel this is a Google issue as it's on multiple devices and my "method" was just another temp. way around the issue.
I will keep checking daily and post again, (I'll try not to forget again) but I do feel it will be blank soon. I wish we could find a permanent solution, but seems that is on Google.
Didn't mean to stir anything up in the thread here, I was just posting what my phone behavior was.
I'll turn on trusted places and see if that continues to work like Onbody has.

I've been checking multiple times a day since my last posting.
So far it hasn't disappeared, but maybe it has something to do with rebooting?
Clearly I don't reboot often. :laugh:

Well... At least Android Pie fixed this issue... It was about time.

S10 Camera Failed with a Twist

Hey all, searched the forum but 0 results for "Camera Failed"
So about a month ago I went swimming in the community pool with my S10. I went swimming and water park with my S8 and S9 never any issues. This time maybe I stayed in too long, haha.
So the next morning I did notice moisture on the front and rear cameras! Doh! Fired up the camera only to get "camera failed". No biggie, I have premium protection with TMo which does cover this ($99 deductible). I went to make a claim and there was an issue with the warranty not being added on my account, but TMo takes care of it's customers and added it for me and started to process the claim. A few days later the moisture disappeared, and then a few days after that the camera was resurrected!
My replacement didn't show up so when I logged in the rep said for whatever reason it didn't go through, but we were able to cancel the claim. Back in business!
Fast forward to 2 days ago when TMo pushed an update to the phone. I updated with the latest software and immediately noticed I'm back to "Camera failed". I have tried the basics like clearing cache, clearing app cache, booting into recovery to clear the cache, and in safe mode. Still no go.
The kicker is (and this was also apparent during the first failure) the camera app shows failed, and all apps that use the camera also throw an error about accessing the camera EXCEPT the Poshmark fashion marketplace app. It access the camera no issues, front and back! I also uninstalled Poshmark, cleared cache, and rebooted without success.
So I was wondering if anyone had any ideas before I try a factory reset because it takes a while to restore a lot of my settings and customization. And if that doesn't work I'll wait a few days and see if it comes back to life like last time and if it doesn't, file a warranty claim.
Thanks

I think I'd still do a reset and try the camera without restoring anything. If it fails then, you've already done the reset for the return. If it works still don't restore anything, live with it a few hours and keep trying different settings with both front and rear cameras. If you can't make it break, then do your restore. I know a restore is tough to do sometimes, but I hate those nagging problems you can't put a finger on.

Tel864 said:
I think I'd still do a reset and try the camera without restoring anything. If it fails then, you've already done the reset for the return. If it works still don't restore anything, live with it a few hours and keep trying different settings with both front and rear cameras. If you can't make it break, then do your restore. I know a restore is tough to do sometimes, but I hate those nagging problems you can't put a finger on.
Click to expand...
Click to collapse
Yeah I know there isn't a lot of options left at this point. But it's weird that the poshmark app has no problems accessing the camera when everything else does, and that after the TMO update it killed my camera again.
Thank you

Similar problem
Nurmi_CEO said:
Yeah I know there isn't a lot of options left at this point. But it's weird that the poshmark app has no problems accessing the camera when everything else does, and that after the TMO update it killed my camera again.
Thank you
Click to expand...
Click to collapse
Well I had the same problem on my s10, however it was being used in heavy rains and the next morning there was moisture in both the front &back cameras.
However it was still taking pictures (full of blur), no it wasn't showing any camera failed error. I took it to the service centre where they had the phone disassembled and heated up the camera module. The phone is working fine ever since, I recently got the June update (India) and my phone's camera is still working properly. Do try a factory reset and let me know as we whatever happens

Nurmi_CEO said:
Yeah I know there isn't a lot of options left at this point. But it's weird that the poshmark app has no problems accessing the camera when everything else does, and that after the TMO update it killed my camera again.
Thank you
Click to expand...
Click to collapse
T-Mobile should push another update with camera night mode, QR code and so on. At least we(people in US) are waiting for it! See if the upcoming update fixes the issue. Don't you use Samsung back up? It is built-in to your phone. I always use it and it saved placement of your home screen shortcuts, settings(most of them), your apps and other stuff.

pma1504 said:
Well I had the same problem on my s10, however it was being used in heavy rains and the next morning there was moisture in both the front &back cameras.
However it was still taking pictures (full of blur), no it wasn't showing any camera failed error. I took it to the service centre where they had the phone disassembled and heated up the camera module. The phone is working fine ever since, I recently got the June update (India) and my phone's camera is still working properly. Do try a factory reset and let me know as we whatever happens
Click to expand...
Click to collapse
I will and see what happens. Thanks!

Charkatak said:
T-Mobile should push another update with camera night mode, QR code and so on. At least we(people in US) are waiting for it! See if the upcoming update fixes the issue. Don't you use Samsung back up? It is built-in to your phone. I always use it and it saved placement of your home screen shortcuts, settings(most of them), your apps and other stuff.
Click to expand...
Click to collapse
Ok I will do a factory reset and see what happens and checkout Samsung backup. Thanks

pma1504 said:
Well I had the same problem on my s10, however it was being used in heavy rains and the next morning there was moisture in both the front &back cameras.
However it was still taking pictures (full of blur), no it wasn't showing any camera failed error. I took it to the service centre where they had the phone disassembled and heated up the camera module. The phone is working fine ever since, I recently got the June update (India) and my phone's camera is still working properly. Do try a factory reset and let me know as we whatever happens
Click to expand...
Click to collapse
No go on the reset. Same thing. Camera failed on every app except Poshmark.
I'm going to ride it out this week and if it's still dead by Sunday I'll file an insurance claim

I'm hoping it does start working, now even I'm worried about updates breaking my camera (I got no insurance on this). Still I don't understand why the camera failed popup came on your device in the first place ( even if it had moisture) because even I had gotten the camera full of fog however it was still working properly (I took it to the service centre In a day though). I'm attaching the most recent update that I received, this water damage thingy actually happened on the 12th of June

Hello, i had the Same issue after the May Update. I tried evertyhing Clearing Cache Reset Phone....
I went to an samsung store they changed my front camera as warrenty case so i paid nothing. Till today no problems, camera works fine again.

Nurmi_CEO said:
No go on the reset. Same thing. Camera failed on every app except Poshmark.
I'm going to ride it out this week and if it's still dead by Sunday I'll file an insurance claim
Click to expand...
Click to collapse
I have trouble wrapping my head around it working with Poshmark only. Outside of reflashing the rom I can't see anything else to try, yet it does point to a software and not a hardware problem.

Tel864 said:
I have trouble wrapping my head around it working with Poshmark only. Outside of reflashing the rom I can't see anything else to try, yet it does point to a software and not a hardware problem.
Click to expand...
Click to collapse
When I did a reset on the phone, I held the volume up + bixby to boot into the bootloader and selected "wipe data/factory reset".
It's been a while since I have been rooting and modding my phones since the S8 and up Snapdragons were non rootable for the longest time. Would it be a "cleaner fresher reset" if I used Odin to flash the stock firmware? Is Odin still a thing anymore with the newest Galaxies?

Nurmi_CEO said:
When I did a reset on the phone, I held the volume up + bixby to boot into the bootloader and selected "wipe data/factory reset".
It's been a while since I have been rooting and modding my phones since the S8 and up Snapdragons were non rootable for the longest time. Would it be a "cleaner fresher reset" if I used Odin to flash the stock firmware? Is Odin still a thing anymore with the newest Galaxies?
Click to expand...
Click to collapse
Yeah you're right Odin still works with modern Samsung phones (it did with my old j7 prime-exynos android 8.1). You can try reflashing the stock firmware and maybe downgrading it if that's possible. Honestly Samsung devices have become a disappointment now to me

Issues with Fingerprint Sensor

Hi guys, I've got a Verizon N960U I've been using, and the fingerprint sensor hasn't been working for the last month or so. When I attempted to use it, it would show the message "An error has occurred with the fingerprint sensor. If this message appears repeatedly, restart your device". Initially I saw suggestions of clearing the fingerprint cache, but the fingerprint app wasn't showing up in the app list after selecting the option to show system apps. initially I thought i was just tired and had missed it, so I ordered a new sensor and installed it. No change. Tried to open the *#0*# menu to do some diagnostics, but that didn't open either, although later I found out that was due to Verizon disabling it on their FW. Today I decided wifi calling wasn't that important to me, and flashed the N960U1 XAA firmware to the phone (after a factory reset) in hopes of either returning the fingerprint app to the list, getting the *#0*# menu back, or both. I have gotten neither.
Most of the threads I've seen regarding the fingerprint issues usually end with "take it to Samsung and let them fix it", but that isn't an option for me, as I got the phone secondhand, with no warranty and a cracked screen, which I had to replace. I really don't wanna put that much more money into the phone, but I'm running out of ideas. Anybody know of something I haven't tried yet?

I have a question, was the fingerprint sensor working after you had your screen repaired?

DJSmoove said:
I have a question, was the fingerprint sensor working after you had your screen repaired?
Click to expand...
Click to collapse
Yup, working pretty well too, fairly responsive. If I had to guess, I think it was a recent update that killed it. I'd also been having issues with the camera, but a cache clear would fix that, for a while at least. Clearing the cache helped the fingerprint reader once, but the fix didn't help for long.

Try manually reinstalling the OS back onto you device using Odin. Could be that some of the files had gotten corrupted during the installation process of the update.

iceepyon said:
Try manually reinstalling the OS back onto you device using Odin. Could be that some of the files had gotten corrupted during the installation process of the update.
Click to expand...
Click to collapse
I've just tried that again, no dice. Mebbe I need a sanity check. My order of operations has been factory reset from settings page, boot to recovery, reset once more just for fun, reboot to bootloader, and then flash via odin the latest XAA image I get from Frija, which would be this: SM-N960U1_1_20191025150053_qp9lx74x57_fac.zip.enc4. Wait for it to start up and check. Am I missing a step here?

I would take your device to a Samsung Service Centre or the repair shop, where you got your device fixed and let them take a look at it. Could be that the fingerprint scanner is damaged.

Possible Solution?
So I think I fixed it. Doing a standard Odin flash didn't work, but I did a flash with the re-partition option using the pit file extracted from the latest firmware, and it seems to be working now. I'll update if anything changes.

Update, the fingerprint sensor stopped working again. It was nice while it lasted. Anyone else got an idea of why the cache/filesystem could be getting corrupt over time?

trk14 said:
Update, the fingerprint sensor stopped working again. It was nice while it lasted. Anyone else got an idea of why the cache/filesystem could be getting corrupt over time?
Click to expand...
Click to collapse
Seems like the storage on your device is starting to fail and needs to be replaced. I would take your device to a Samsung Service Centre and get it inspected by a technician. If that is the case and you aren't insured or your device's warranty has expired. Then I would recommend that you get a new device. As it is cheaper than getting the storage on your device replaced.

Having a hell of a time fixing this &$¥€©% thing

A few days ago, some of my lights, plugged into smart outlets, stopped responding. I couldn't get them to turn off or on via my phone or my Hub.
I tried clearing my app data. No go.
So then I got the bright idea to delete my home entirely. Didn't work, either. Then I realized they had another app of their own I had forgotten I had installed, so I went into that, removed all three, and set them up again. So now those work.
But the one "smart" bulb I have installed, can't be re-added, and I can't seem to add my Hub 2 to the speaker group (my gen1 Hub and Home mini show up, though). The bulb is one of those "C by GE" ones, and I tried resetting it by following the video tutorial. Neither "wax on/wax off" method worked (basically entails turning it off and on repeatedly, counting up to 8 seconds each time). I dunno if it's on an older firmware, or a 2.8+ one, but I didn't get the "3 blinks" reaction it was supposed to elicit, either way.
So, the short of it is, even with the C by GE app, I can no longer control that light bulb or even add it. The Home app, when I choose to add a light bulb, just kicks me back to the main dashboard with all the controls. Even after clearing the app data and storage. And no matter how many times I create and delete a speaker group, I can't add my gen2 Hub to it. It doesn't show as up there, but I can otherwise control it. Wtf.
Any ideas?

Try clearing the system cache.
Try a network reset.
Check settings and permissions of all associated apks. Clear data of the same.
Is all needed hardware enabled and working?
Any new apps, firmware, updates of any kind?
Set updated apps back to factory loads.
Changes you made?
Goggle search for similar reported problems in same make and expand the search if nothing is found.
Play with it... probably something simple*.
*once you find it

Yup, tried all those options and more.

GuyInDogSuit said:
Yup, tried all those options and more.
Click to expand...
Click to collapse
Something changed.
Forgive my ignorance as I like my devices dumb as rain stupid but how are you communicating with them, blue tooth?
I don't reccomend a factory reset as the issue would likely reoccur if you don't find the root cause even if it fixed it initially.
A factory reset would help to determine if a hardware failure had occurred though.

I don't know what changed, as I hadn't added anything to this setup.

GuyInDogSuit said:
I don't know what changed, as I hadn't added anything to this setup.
Click to expand...
Click to collapse
Auto updates, destroyer of worlds...
Perhaps something in the environment has changed ie RF interference.

blackhawk said:
Auto updates, destroyer of worlds...
Perhaps something in the environment has changed ie RF interference.
Click to expand...
Click to collapse
Huh.... No idea, really.

GuyInDogSuit said:
Huh.... No idea, really.
Click to expand...
Click to collapse
Well something changed, either settings, software, firmware or hardware.
Were any apps uninstalled recently?
It's rare on Android but uninstalls can changed buried normally untouchable settings and cause hell.
Most times the operator is the prime suspect... as I've found from experience

blackhawk said:
Well something changed, either settings, software, firmware or hardware.
Were any apps uninstalled recently?
It's rare on Android but uninstalls can changed buried normally untouchable settings and cause hell.
Most times the operator is the prime suspect... as I've found from experience
Click to expand...
Click to collapse
On my phone? How would that affect a smart home hub?

GuyInDogSuit said:
On my phone? How would that affect a smart home hub?
Click to expand...
Click to collapse
You never did say how they link up?
If the hub has internet access that opens a new can of worms. Malware is omnipresent at this point with technology.

blackhawk said:
You never did say how they link up?
If the hub has internet access that opens a new can of worms. Malware is omnipresent at this point with technology.
Click to expand...
Click to collapse
They're all connected to my Nest Hub.

GuyInDogSuit said:
They're all connected to my Nest Hub.
Click to expand...
Click to collapse
Never was even aware of that... so the issue may be on the hub side.
Have/can you do a network reset on the hub?
Sometimes, surprisingly, Google will support their products free of charge. Worth a shot.
I can now see why you're learning new curse words

blackhawk said:
Never was even aware of that... so the issue may be on the hub side.
Have/can you do a network reset on the hub?
Sometimes, surprisingly, Google will support their products free of charge. Worth a shot.
I can now see why you're learning new curse words
Click to expand...
Click to collapse
I had considered contacting Google but I thought I'd ask here first since it's visible to more people who might have knowledge about it. /shrug
I'll try the reset option.
Any ideas about that bulb? Or do you think the network reset could help with this?

GuyInDogSuit said:
I'll try the reset option.
Any ideas about that bulb? Or do you think the network reset could help with this?
Click to expand...
Click to collapse
A network reset is easy and pretty painless.
Try pulling the power and battery to force it to reset.
A factory reset is the last resort. If it had any major firmware updates this becomes more likely to fix the issue.
I couldn't find any option to clear the system cache like on most Androids

blackhawk said:
A network reset is easy and pretty painless.
Try pulling the power and battery to force it to reset.
A factory reset is the last resort. If it had any major firmware updates this becomes more likely to fix the issue.
I couldn't find any option to clear the system cache like on most Androids
Click to expand...
Click to collapse
This has... a battery??

GuyInDogSuit said:
This has... a battery??
Click to expand...
Click to collapse
I think so but it's just what I saw online.
It may not be easily accessible if so it's not a good option.
A Google search for this issue might net you a solution. Probably more common than you think.

I got the three Google devices added to a speaker group finally, somehow.
The light bulb, though, just ain't showing up. It's no longer kicking me out from the light adding process, though. It just isn't detecting it.

GuyInDogSuit said:
I got the three Google devices added to a speaker group finally, somehow.
The light bulb, though, just ain't showing up. It's no longer kicking me out from the light adding process, though. It just isn't detecting it.
Click to expand...
Click to collapse
Lol, sort of funny... I hope the light bulb lights up for you soon
Try a reboot. Cycle the slave device by disconnecting it from the power perhaps?

blackhawk said:
Lol, sort of funny... I hope the light bulb lights up for you soon
Try a reboot. Cycle the slave device by disconnecting it from the power perhaps?
Click to expand...
Click to collapse
Forgot to update on this.
I did get the GE bulb working. I attempted the factory reset thing again, and seems the third time was the charm. Might have helped that I unplugged the light fixture for a few minutes first.