I'm currently on v0.4 of Naven's Atrix port and can't seem to get Bluetooth to fire up. I don't remember having this problem with older versions of this ROM.
Using both the widget control and the prompt in Settings, Bluetooth tries to turn on and ultimately, fails.
I found these potential fixes doing my due diligence:
1. Uncheck Compatibility Mode in SpareParts
2. Download and run Bluetooth Fix Repair
3. Open Bluetooth Share in Settings>Applications and wipe data/cache
4. Wipe cache and dalvik in Tenfar's System Recovery and reboot
5. Move bluetooth apps back to internal memory
Thus far, nothing has worked.
Any ideas?
Pj
Phoenix, AZ
I'm doing follow-up to my original post, in the event someone ends up experiencing similar issues and searches for a solution.
It's definitely an app or process conflict of some sort. I downloaded a market app, Bluetooth Wall, which has the ability to scan apps and identify those with bluetooth access capabilities.
Unfortunately, I don't have the patience to uninstall all of these apps one-by-one, so I discovered another workaround.
After a reboot, as soon as the home launcher is loaded, I push the Bluetooth toggle to get bluetooth going. This has worked every time, thus far. Unfortunately, if I deactivate Bluetooth at any time afterwards, I cannot reactivate it without a reboot.
According to the battery usage monitor, an unused bluetooth connection (not actively discoverable) is responsible for about 2-3% of total battery life. And with Bluetooth Wall running, my phone should be safe in this state.
Hopefully, I'll get to the heart of this problem after a little more work ...
Pj
Phoenix, AZ
BT works great with the new 234 sbf.
Unfortunately i don't have Atrix so I can't try and see what happens.
I am the developer of Bluetooth Fix Repair, and I'm always looking to support more devices, so I need to ask you: What did my app say? Unsupported Device, or "Fix Applied, good luck!"
Thanks
Phk
Phk,
Thanks for tracking my post down ...
If I recall correctly, Bluetooth Fix Repair ran successfully.
The problem with my X2, though, seems to be an app conflict -- even though I recently flashed to a new build - 2.3.4. from 2.3.3. - the conflict persists.
Pj
Phoenix, AZ
Related
I have been a lurker here for a long time. But have needed to register in order to figure out if I have run into a bug...or if I did something wrong.
I registered just now...so I am not allowed to post this in the Dev sections...so please forgive me for putting this in the General Section.
I am not new to rooting or loading roms on android phones. So I don't think this is a result of a mistake or issue with either of those processes.
I have noticed that since loading DasBAMF 1.2 (first version I loaded...so can't speak to earlier versions), my bluetooth voice no longer syncs voice with my car. What is weird is the media sync is working fine...but it just cannot connect to the phone for calls.
BTW...It did work when I was using stock OS.
Thanks,
bump....anyone?
did you try wiping ?
oh yes....
Full wipe-> Install DasBAMF1.0-Logged into Google->let sit for 45 mins->checked all contacts settings and what not to make sure everything was settled->recovery-> no wipe->install DasBAMF 1.2->install apps only via TiBackup->used for 2 days->recovery->no wipe->install DasBAMF 1.3
BTW...had the same issue with 1.2 (but that might have been obvious).
Thanks for the response.
Have you wiped since you installed 1.3? I have had similar problems as you, with other devices, and this one, and usually after several attempts I can remove the device from the BT pair window and repair.
I would try the latter first, then do a cache wipe, dalvic wipe and a factory reset and check.
No issues with BT connectivity in my car or my headset. Version 1.3 actually connects faster than the other ones did for me (including ROMs on my Droid 1). I haven't tested it yet but I will with my next ROM but historically my connections have come back using TiBu so I'll be testing that later.
My TB was working with my car radio and syncing via bluetooth. After performing the "1 click" root, having issues with bluetooth and car. Not sure whats up, still have stock ROM. I see others are having this issue even without root.
I just replied in http://forum.xda-developers.com/showthread.php?t=1018438
for pairing issues with a car, but along the same lines I was able to successfully make a call with no voice/pairing issues running Das BAMF 1.3. I haven't tried the media sync, so I cannot attest for that.
Never got this solved for DasBAMF.
Wiped and restored the virgin OS that only had root and nothing else, then installed 1.2, 1.3, and 1.3.2 ... Bluetooth would not work for voice.
So wiped and installed Liquid ThunderSense...and I am back in business. weird....but hey...at least I am good to go now.
Hope I'm not duplicating anything, but there seems to be a lot of BT related questions and none answered in one unified place. Also I think the BT Dev thread should be left to the devs (to keep it easier for them to work on things, rather than help us mere mortals ).
This applies to CM7 (latest nightlies, Tablet Tweak RCs) ONLY (as far as I know).
So, if bluetooth does not turn on, there a few things that you can try.
Do a HARD reset (that is, hold down the power button until the NookColor turns off, then start it back up.
Fix Permissions in ClockworkRecovery:
Boot into CWR (w/SD, load it in. With CWR installed on eMMC, go to ROM Manager > Reboot into Recovery. Alternatively, hold down the power plus "N" button for ~8 seconds (from a shutdown NookColor).
Try both!
An interesting thing to note is some users (myself included) can only start up bluetooth within a pretty short window of time after the NC has booted up. Not sure why timing is important, but could be a factor for those who cannot start up BT after some given time of operation.
I found this tip that may work after a fresh (read: wipe system/data) install, but may also work after flashing a nightly over a nightly.
If you're ready to turn on Bluetooth, there's a trick. If you don't do this, Bluetooth will just refuse to turn on / be enabled.
Turn off wifi (Settings > Wireless & Networks > Wi-Fi)
Reboot
Turn on Bluetooth (Settings > Wireless & Networks > Bluetooth)
Turn on wifi
It seems a bit odd, but that's what you have to do. From then on out it'll work fine.
Click to expand...
Click to collapse
Credit here (step 2)
For a list and description of devices that work with the NC, check this out:
Known functional Bluetooth devices
For tethering data via BT, try android-wifi-tether. While it can be used to create an access point on your phone via wifi, you can also opt to use BT to create the tether. This works well in conjunction with TetherGPS which I use to provide GPS info to the NC from my G1 while using CoPilot Live to show navigation (I don't have data on the G1).
If you have the BT enable problem try this kernel and let me know if it changes anything:
http://forum.xda-developers.com/showpost.php?p=12683824&postcount=1754
dalingrin said:
If you have the BT enable problem try this kernel and let me know if it changes anything:
http://forum.xda-developers.com/showpost.php?p=12683824&postcount=1754
Click to expand...
Click to collapse
Tried that previously and it did not work for me.
In other words, it works as with all the kernels I've tried (your OC'd and stock kernel): it will start up if I start is quickly, but otherwise not.
ace7196 said:
Tried that previously and it did not work for me.
In other words, it works as with all the kernels I've tried (your OC'd and stock kernel): it will start up if I start is quickly, but otherwise not.
Click to expand...
Click to collapse
me too. I went back to 4/4 since them. If I leave BT on all the time, it is on when I boot, but if I turn off BT and reboot, it won't come on without a hardboot (holding down power.)
Fix permissions is NOT needed, just a hard boot.
dalingrin said:
If you have the BT enable problem try this kernel and let me know if it changes anything:
http://forum.xda-developers.com/showpost.php?p=12683824&postcount=1754
Click to expand...
Click to collapse
For the last few days Ive been trying to get BT working w/ my car stereo, using phiremod 5.3
I have no problems enabling Bluetooth (first time I had to reboot a few times and fix permissions)
With it flat against the stereo, I'm 'paired but not connected' and getting it to actually connect usually takes 4 - 5 tries.
After its connected- when I try to play any kind of music, it gets stuck every few seconds- and stays stuck for more than a few seconds (like 10) and plays again.
I just downloaded this kernel, (wiped caches, fixed permissions again) and it connected on the second time, and only got 'stuck' once for maybe 2 seconds, and played the rest of the song with no problems.
Seems like it changed something on my end...
Just figured I'd mentioned it.
(I can go back to the other kernel, or a different version of cm7, and see if I get the same connecting/ stuttering problem, if you thing it would help)
Btw- thanks so much for sharing all of your hard work!
breebauer said:
After its connected- when I try to play any kind of music, it gets stuck every few seconds- and stays stuck for more than a few seconds (like 10) and plays again.
I just downloaded this kernel, (wiped caches, fixed permissions again) and it connected on the second time, and only got 'stuck' once for maybe 2 seconds, and played the rest of the song with no problems.!
Click to expand...
Click to collapse
I dont' know if anyone who's building from source wants to take a look at this patch committed 3 days ago on the omapzoom tree to frameworks/base, but it seems to address a bluetooth corruption problem.
Can anyone who's using the copilot app tell me exactly how to get it set up? I can get the GPS signal to the nook but then I get an error about an invalid imei number.
Sent from my NookColor using Tapatalk
Calla969 said:
Can anyone who's using the copilot app tell me exactly how to get it set up? I can get the GPS signal to the nook but then I get an error about an invalid imei number.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Check out this posting:
http://forum.xda-developers.com/showthread.php?t=1024963
I believe you also need the Bluetooth GPS Provider app from the market.
Calla969 said:
Can anyone who's using the copilot app tell me exactly how to get it set up? I can get the GPS signal to the nook but then I get an error about an invalid imei number.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Never had an issue with the IMEI number, but here's how I got it setup.
Start with the TetherGPS app running server on the phone and client on the NC, as well as tether-wifi from google running on the phone, then connect to the AP on the NC
Next, open/install the app. It should read the GPS data from the phone
Now, switch back to a wireless connection with internet access, download the voice, then enter the serial/etc...
Finally, load the app back up after all the registration stuff 'n things, and use the "internet" connection from the phone to grab the GPS info.
Copied and edited from cm7 user thread.
I have xoom bluetooth keyboard with disconnect issues. Would the special kernel help with this?
From the accessories thread. "I found a work-around. Download the app Bluetooth Keyboard JP, change the settings in settings > Language and Keyboard to that app, then connect the keyboard." Anybody else try this or others? Blue Input is another one. I know of one more but can remember its name.
I'm running Phiremod v5.3 cm7 from emmc and cm7 nightlies from sd card. I usually have a data sd card but can switch it out. I have updated the cm7 sd card before. Not sure which nightly and OC I used last. Could use ClockWorksMod to flash this kernel to Phiremod v5.3. Could replace the kernel, uImage, on the SD card. Usually there are different kernels for emmc and sd card.
Another issue: When I have the keyboard active and playing flash files from the internet, it seems to buffer more. If I move the keyboard out of range or use settings to disconnect the keyboard, the buffering is less and the flash files play better. I have cyfi bluetooth external speakers. When I use them I get the same buffering issue, so I just use an external player through the headphone jack instead.
ace7196 said:
Never had an issue with the IMEI number, but here's how I got it setup.
Start with the TetherGPS app running server on the phone and client on the NC, as well as tether-wifi from google running on the phone, then connect to the AP on the NC
Next, open/install the app. It should read the GPS data from the phone
Now, switch back to a wireless connection with internet access, download the voice, then enter the serial/etc...
Finally, load the app back up after all the registration stuff 'n things, and use the "internet" connection from the phone to grab the GPS info.
Click to expand...
Click to collapse
Question: will 'Wireless Tethering' work in place of 'tether-wifi'? Or does it -have- to be 'tether-wifi'? Thanks!
any software will work that tethers.:-D
ace7196 said:
Never had an issue with the IMEI number, but here's how I got it setup.
Start with the TetherGPS app running server on the phone and client on the NC, as well as tether-wifi from google running on the phone, then connect to the AP on the NC
Next, open/install the app. It should read the GPS data from the phone
Now, switch back to a wireless connection with internet access, download the voice, then enter the serial/etc...
Finally, load the app back up after all the registration stuff 'n things, and use the "internet" connection from the phone to grab the GPS info.
Click to expand...
Click to collapse
Apparently the latest version of Copilot has introduced this error. I have spoken with tech support regarding the issue and they told me that they are aware of the problem and will release an update early next week that will fix the problem. Apparently if you have version 8.2.504 it works, but the new version breaks it. The dev won't send me a copy of the old version, so I guess I'll just have to wait and hope.
lschroeder said:
Copied and edited from cm7 user thread.
I have xoom bluetooth keyboard with disconnect issues. Would the special kernel help with this?
From the accessories thread. "I found a work-around. Download the app Bluetooth Keyboard JP, change the settings in settings > Language and Keyboard to that app, then connect the keyboard." Anybody else try this or others? Blue Input is another one. I know of one more but can remember its name.
Another issue: When I have the keyboard active and playing flash files from the internet, it seems to buffer more. If I move the keyboard out of range or use settings to disconnect the keyboard, the buffering is less and the flash files play better. I have cyfi bluetooth external speakers. When I use them I get the same buffering issue, so I just use an external player through the headphone jack instead.
Click to expand...
Click to collapse
I don't know if that is a solution, but the problem appears to be a conflict between wifi and bluetooth. Turn off wifi and most of your keyboard problems will go away.
Also there is an app on the market called "Null Keyboard" Which simply turns on a keyboard device that disables everything keyboard related. It doesn't disable bluetooth input, but it gets rid of the long-press pop ups and is suppose to solve other issues as well (including the software keyboard popping up every time you want to type.)
I haven't had time to install it, but it's purchased.
Does anyone know where (on the Nook) the BT chip/antenna is located?
It might help to know, since the range is so limited...
breebauer said:
Does anyone know where (on the Nook) the BT chip/antenna is located?
It might help to know, since the range is so limited...
Click to expand...
Click to collapse
http://www.zdnet.com/photos/nookcolor-teardown/487636?seq=62&tag=content;photo-frame#photo-frame
So across the bottom and up the right side as you hold it portrait.
khaytsus said:
http://www.zdnet.com/photos/nookcolor-teardown/487636?seq=62&tag=content;photo-frame#photo-frame
So across the bottom and up the right side as you hold it portrait.
Click to expand...
Click to collapse
Thanks! That makes a big difference...
(For some reason, I was thinking it was on the upper left corner- not sure why)
chisleu said:
I don't know if that is a solution, but the problem appears to be a conflict between wifi and bluetooth. Turn off wifi and most of your keyboard problems will go away.
Also there is an app on the market called "Null Keyboard" Which simply turns on a keyboard device that disables everything keyboard related. It doesn't disable bluetooth input, but it gets rid of the long-press pop ups and is suppose to solve other issues as well (including the software keyboard popping up every time you want to type.)
I haven't had time to install it, but it's purchased.
Click to expand...
Click to collapse
I was just using google voice to text from several feet back. In fact it was hard to read the small print from that distance. I did not realized that keyboards have a larger range then headsets.
Testing Bluetooth Keyboard JP now. Force closes, so just switched to swift keyboard I downloaded from amazon app store for free. To get out swift keyboard and get a null keyboard, I hit the back key on the xoom keyboard, then the virtual swift keyboard no longer shows up.
@chisleu do you have a link or instruction to modify bluetooth keyboards so that keys can have their mappings corrected. Xoom has some correct and some wrong or disabled under CM7.
Couldn't get BT to work at all however powering down while the wifi is off, and turning the bluetooth on before the wifi made it works on the first try. Was streaming Slacker to my stereo in a matter of minutes. Wifi doesn't seem to interfere with the BT audio stream at all, audio sounded crisp and perfect. Range however was still limited to a foot or so.
Hoping there is a possible hardware mod that can hook up an antenna to the BT chip. I'd be in heaven if I had full BT functionality on this beast.
FYI, Although I don't have any RF experience I'm still an electrical engineer so if anyone can toss me a bone on the PCB layout or pinouts of the nook I might be able to try stuff to boost the range.
What is the feasibility of adding dial-up networking client support to CM7? Some folks are able to tether their NC to their phone using an ad hoc wifi network, and others have had success via a Bluetooth personal area network (PAN) using the "pand" utility. Unfortunately, I have a Blackberry phone, and it does not support the PAN profile. It does, however, support dial-up networking (DUN) over Bluetooth (confirmed with a Windows laptop).
According to https://sites.google.com/a/android.com/opensource/projects/bluetooth-faq, "dund" is the client utility that is needed to establish a dial-up connection from Android to another device. When I run this command on the NC, it says "dund: not found". I'm not a developer and don't know how much effort would be involved in adding this functionality to the build. Is it just a matter of including the binaries, or is there additional development work involved?
Thanks in advance..
Has anyone noticed the following ?
a) Turning on / off bluetooth affects the WiFi connection including sometimes disconnecting the WiFi (when BT is being turned off i.e.).
I use BT to connect with the gtab to my samsung and transfer files etc. When o go to disconnect, the wifi connection has also dissapeared.
b) As a side issue, the Market app kept force closing when launching it, when i changed to went to a different location and it connected up with the WiFi connection there. The Market app was active at first location before i left. Haven't had a chance to reproduce and check the exact scenarios yet.
Have stock Froyo (3389) with Enhancement 3.1.4b (Market app).
i suggest going to custom rom.
i had dropping wifi issues and those fc issues but it was due to a poorly made rom brillant corners and since theres no support i gave up on it
other froyo roms like beastly worked great. didnt drop conenctions
cahuja said:
Has anyone noticed the following ?
a) Turning on / off bluetooth affects the WiFi connection including sometimes disconnecting the WiFi (when BT is being turned off i.e.).
I use BT to connect with the gtab to my samsung and transfer files etc. When o go to disconnect, the wifi connection has also dissapeared.
b) As a side issue, the Market app kept force closing when launching it, when i changed to went to a different location and it connected up with the WiFi connection there. The Market app was active at first location before i left. Haven't had a chance to reproduce and check the exact scenarios yet.
Have stock Froyo (3389) with Enhancement 3.1.4b (Market app).
Click to expand...
Click to collapse
Just curious as to where you got stock 3389 from? It wasn't even released as an OTA update as far as I know. if you prefer stock, then 3588 or 4349 are the most used versions. Have you made any other mods yet? CWM, market fix, etc? If not, then using stock recovery, you can flash either of the stock roms. See Goodintentions "Gtablet for dummies" page for links to the images, and instructions on how to flash using stock recovery.
I, too, have the same problem. On my first mod TnT Harmony 1.2 and now with Caulkin's G-Tab 1.1 I have a problem with bluetooth causing interference with wifi. I am using the BlutO keyboard along with "Bluetooth Easy Connect" in order to get it to actually connect. However, on both mod's the effect is the same, as soon as I turn off the bluetooth my wifi stays connected. I really like Caulkin's G-Tab it is amazingly fast and would prefer to stay there but would move to another one if a different mod would solve this problem. Any suggestions?
Oops must have been typing the rdp port too many times that day. Sorry its 3588.
Sent from my SGH-T959 using XDA App
I didnt want to take a chance with any particular complete rom replacement, thats why used the 'enhancement' pack which basically provided the speedup with market and still the std tnt ui.
Followup, yesterday I had to rebuild the 'bricked' gtab which was suffered from fc's just as I started to give demos :-((
So mucho thanks to the viewsonic for dummies site for collecting all the info in such an easy to read format
I did code red procedure and did the bocksize change which I had not had to do first time. Noticed a speed up in the stock (quadrant - 1743) just by doing a wipe and change of blocksize. Then adding enhancement pak took it to 2400.
Happy now. Tab is going to the field in uk, and hopefully will live thru next 3 wks without incidence.
Problem with bluetooth and wifi still exists. Basically turning on bluetooth and connecting will stall the wifi - it looks like it is still connected but open the settings panel and it will update to show 'disconnected' then touching the button will turn off wifi, then touching it again starts it connecting again and then its fine. A pain when you are trying to hookup bluetooth gps and use maps app.
Sent from my SGH-T959 using XDA App
Hi Friends,
Few days a go as I was watching youtube videos for around 45 minutes continuously through the youtube app. The streaming suddenly paused and never continued from that point. I tried other videos but it kept on buffering (the circle kept on spining and nothing happened, as noticed on the leds of wifi router it seemed youtube app is not using the net but when i search for more videos the thumbnail do showup normally).
To over come this issue i tried reflashing. This happened when i was on the new HyperDroid_v4.0 with Pongster's MattedBlack v4.0 Surgeons which is amazing for battery saving.
I then tried reflashing HyperDroid_v4.0 again after formatting /cache /system /data /sdcard /emmc which wiped everything, but still no avail.
Then i again tried reflashing DarkyROM2 XXKH3 BASE (2.3.4) formatting everything but still no luck at all.
I even tried these flashing after Factory data reset selecting Format USB storage as well .
When i do the flashing everything else seems to be working fine as usual except the youtube playback and android market doesn't download, like i said for the youtube app, everything like searching the apps, browsing through apps details works fine except it doesn't download at all. It shows as if it's downloading but it stays as is forever.
Very sorry if same question was posted before this as i couldn't find like it.
I have been trying to fix this for 2 days in a row but still no luck.
Has anyone come across this same issue.
Please help.
Thank you very much in advance..
Update:The problem was finally solved after again formatting /cache /system /data /sdcard /emmc and flashed stock ROM though Odin and then I installed DarkyROM tool and then flashed DarkyROM2_KI3_Base ROM.
I will soon jump to HyperDroid_v4.0 with Pongster's MattedBlack v4.0 Surgeons again as it has superb battery life.
I will be updating you guys if the same problem persist.
Thank you all
Hello everyone!
Although I am not using GS2 (I have a Galaxy Note), I chose to post here because I didn't want to create a new post and I believe this is not a device-specific issue (see below for why).
I have the exact same problem as OP (as far as I can see). When I got my note less than a week ago, everything was working great. Then, last Friday I noticed that I cannot download anything from the market. After choosing to download something (both paid or free), after clicking "accept & download" at the permission screen, the screen goes back to app screen and market shows the app as "downloading..." with working, yet empty, progress bar. Everything else using the internet works fine - browsing from different browsers, notifications, email etc. I even tried installing an alternative market app, and it would download/install apps no problem. Also, downloading straight .apk files works as well. Later that evening I also noticed youtube app doesn't work - just the "loading" circle keeps running, until it times out. Browsing/searching market/youtube works without a problem. I am using the stock ROM and it isn't even rooted. Later, following some suggestions from google searches on the problem, it turns out that downloads work when I disable network and let it use mobile internet. I also later found out that it works on other wifi networks, just not my home wifi (which used to work perfectly, with no configuration changes to the router).
Next day I also found out that my girlfriend's android (LG Optimus Me P350) has the same exact problem, therefor it is not a phone model specific problem.
Here is what I tried so far:
Factory reset - left me with no apps and no way to re-download them. The market download did work ONCE after the reset, but that was to download the update to the market itself, nothing else;
Clearing Download Manager data - worked for ONE download. At first it worked for one download every time, meaning, after clearing download manager data, I was able to download one app, after that it would go back to the problem. I could then clear data again, and it would again download one app. After about 5 apps downloaded this way, this solution won't work at all anymore;
Force closing/clearing data of market, gmail, talk (in combination with above step) - didn't work;
Signing out/in to gmail and/or talk - didn't work;
Changing google account in market - didn't work;
Stopping/starting download countless times - didn't work;
Switching wifi on/off - only starts downloading briefly when phone switches to 3G while wifi is off. As soon as it gets wifi connection back, the download stalls at the position it was until I switch wifi off again (so it can continue to use 3G);
Switching phone to airplane mode, off/on, then disabling airplane mode - didn't work;
Changing phone's DNS records with an app to OpenDNS - didn't work;
Updating router firmware - didn't work;
Resetting router firmware - didn't work;
Setting port triggering on router for port 5228 - didn't work;
Port forwarding to Note IP for same port - didn't work;
Disabling router firewall - didn't work;
My router is Linksys E1000.
I think that is all I tried. I have been trying to find a solution for the whole weekend, and nothing as far. Searching google makes me believe that many people have had the same problem. I have found many solutions, which don't work, or only work once. This problem is really, really irritating. Also, I have found out that for many people the problem seems to randomly disappear without doing anything after some time (days to months), sometimes coming back and sometimes not. I experienced this myself when after going to sleep, I was able to download one app in the morning with no tried "fixes" at that time. This also makes me believe that there are many "fake" solutions, which did work for some people, but not for others - quite possibly, while these people were "solving" the problem, it actually solved itself, yet because the person did something, he/she believes that was the solution. A notable example of this could be "google account 24-hour reset" where users experiencing the problem are suggested to log out of their google accounts everywhere and not use the account for anything for 24 hours. Seeing as this is possibly a problem somehow connected to another device, not just the phone itself, I did consider flashing DD-WRT on my router, but I wouldn't really want do do that since my router is not that powerful and with all the DD-WRT features my broadband speed gets capped at about 65Mbit/s. Still a lot, but I have a great internet connection and am able to get real speeds of about 90Mbit/s with stock router firmware.
If anyone has any ideas, please share Thank you in advance!
Just a quick reply - I contacted my apartment building network tech, and he said that they didn't do anything regarding the internet that day, but they did however do something to offer TV service to residents (edit: The TV network shares the same hardware as internet's). He said that it shouldn't have changed anything regarding internet, but he would look into it. A few hours later everything is working.
Of course, it could be one of those cases where the problem disappears with no apparent reason, but I guess they did something to fix it. So, if you are experiencing the same problem (market downloads not working and youtube app not playing videos), and you have tried everything else (preferably confirmed the problem persists on someone elses phone), I would suggest you start going up the chain to whoever is managing your network (after yourself). If at all possible, try getting wifi access through someone else who is using the same ISP/network - if the problem persists even when connected to another AP/Router, it's pretty sure the ISP or network is to blame.
Hope this helps someone, since I wasted a few days on this
Hi all. Not sure if this is a general Android problem or a Samsung issue but posting here to see if anyone else is having this issue. Upon using the Hey Google voice command, the green light in the corner indicating the mic is in use turns on, but nothing pops up and no Google Assistant is visible. If I tap on the green light it tells me Google is using the mic (obviously), so I go into the mic permissions from there and toogle off and then on the Google Assistant mic permissions. I can then use the voice command and Google Assistant will come up as usual. This then repeats many times per day.
Is anyone else having similar issues? I have tried all fixes I've seen online and nothing helps.
If the Google command is not working despite the microphone light being on, there could be a few possible reasons. Here are some troubleshooting steps you can try:
Check your internet connection: Ensure that you have a stable internet connection. Voice commands require an active internet connection to function properly.
Restart your device: Sometimes, a simple restart can resolve temporary issues. Try restarting your device and see if the Google command starts working again.
Clear cache and data: Go to the settings of the Google app or your web browser and clear the cache and data. This can help resolve any temporary glitches that might be causing the issue.
Check microphone settings: Make sure that the microphone is enabled and properly configured on your device. You can do this by going to the settings and checking the microphone settings.
Update Google app or browser: Ensure that you have the latest version of the Google app or web browser installed. Updates often contain bug fixes and improvements that can address issues with voice commands.
If none of these steps resolve the problem, it may be a more complex issue that requires further troubleshooting or assistance from technical support.
Arun.k2742 said:
If the Google command is not working despite the microphone light being on, there could be a few possible reasons. Here are some troubleshooting steps you can try:
Check your internet connection: Ensure that you have a stable internet connection. Voice commands require an active internet connection to function properly.
Restart your device: Sometimes, a simple restart can resolve temporary issues. Try restarting your device and see if the Google command starts working again.
Clear cache and data: Go to the settings of the Google app or your web browser and clear the cache and data. This can help resolve any temporary glitches that might be causing the issue.
Check microphone settings: Make sure that the microphone is enabled and properly configured on your device. You can do this by going to the settings and checking the microphone settings.
Update Google app or browser: Ensure that you have the latest version of the Google app or web browser installed. Updates often contain bug fixes and improvements that can address issues with voice commands.
If none of these steps resolve the problem, it may be a more complex issue that requires further troubleshooting or assistance from technical support.
Click to expand...
Click to collapse
Unfortunately I did all of that besides clear the Google app completely because that is a nightmare...but if it keeps happening I may have to. All of the normal stuff I've tried.
So I did clear Google app data and it's still happening as of tonight. I'm on a locked S23 ultra in the US directly from Samsung so I don't know how something like could break this badly without being rooted or something.
I've had this happen to me. I am rooted and on dr.ketan ROM.
After wiping data and setting up Google app again it starts working, but stops again the next day.
I have 2 same phones that are basically mirrors as far as setup and this was only happening to one of them.
After many attempts including clearing data and setting up Google app again it always stopped working on the next day.
Eventually I restored TWRP back up which is from before the problem occurred. Now it is working again.
This is why I would never use a phone without root or TWRP.
Had this problem too until yesterday, it was just an issue with the specific app Version of Google.
Newest Update fixed it
Arun.k2742 said:
If the Google command is not working despite the microphone light being on, there could be a few possible reasons. Here are some troubleshooting steps you can try:
Check your internet connection: Ensure that you have a stable internet connection. Voice commands require an active internet connection to function properly.
Restart your device: Sometimes, a simple restart can resolve temporary issues. Try restarting your device and see if the Google command starts working again.
Clear cache and data: Go to the settings of the Google app or your web browser and clear the cache and data. This can help resolve any temporary glitches that might be causing the issue.
Check microphone settings: Make sure that the microphone is enabled and properly configured on your device. You can do this by going to the settings and checking the microphone settings.
Update Google app or browser: Ensure that you have the latest version of the Google app or web browser installed. Updates often contain bug fixes and improvements that can address issues with voice commands.
If none of these steps resolve the problem, it may be a more complex issue that requires further troubleshooting or assistance from technical support.
Click to expand...
Click to collapse
Bro..are/were you part of Google tech support? Your trouble shooting steps uncannily resembles the same steps that Google tech support would normally advice!
So this is still happening, even after all updates, many clearing cache and data, many restarts of the phone. It will work initially, and then the next time I need it the mic light will come on and google assistant doesn't pop up. Anyone else perhaps have had this happen?
xgerryx said:
So this is still happening, even after all updates, many clearing cache and data, many restarts of the phone. It will work initially, and then the next time I need it the mic light will come on and google assistant doesn't pop up. Anyone else perhaps have had this happen?
Click to expand...
Click to collapse
This happened again to me yesterday. I went to app info, cleared cache and force stopped Google app, then without opening the app said "hey Google" and it started working again. It still works today. Hopefully it will stay that way.
xgerryx said:
So this is still happening, even after all updates, many clearing cache and data, many restarts of the phone. It will work initially, and then the next time I need it the mic light will come on and google assistant doesn't pop up. Anyone else perhaps have had this happen?
Click to expand...
Click to collapse
I have a sort of similar issue where randomly google assistant will just stop waking up to the hey google command. I have found in my case if you go into default apps then switch the default assistant to a different option and then set it back to Google it resolves my issue for a while. May not work in your case but worth a try.
tiho5 said:
This happened again to me yesterday. I went to app info, cleared cache and force stopped Google app, then without opening the app said "hey Google" and it started working again. It still works today. Hopefully it will stay that way.
Click to expand...
Click to collapse
Yea this does work temporarily. I tried it again just now and it happened exactly the way I described before. Just the mic light, nothing popped up, tap the mic light, mic being used by Google. Just a total disaster at this point. I can only hope that the June update (if we ever get one) somehow fixes this.
znel52 said:
I have a sort of similar issue where randomly google assistant will just stop waking up to the hey google command. I have found in my case if you go into default apps then switch the default assistant to a different option and then set it back to Google it resolves my issue for a while. May not work in your case but worth a try.
Click to expand...
Click to collapse
Setting the default app to something else for assistant and then putting it back to Google had no effect for me. Still wasn't working until I cleared cache and force stopped Google.