I can scan for devices, but when I click on one to try and pair, I just see the message: "An app is needed to use this device."
I debloated a bit including various google/samsung stuff, but pretty much stuck to the safe lists. Hoping that someone might know of a fix. I've tried the obvious (resetting app preferences, restarting, etc.).
ughlife said:
I can scan for devices, but when I click on one to try and pair, I just see the message: "An app is needed to use this device."
I debloated a bit including various google/samsung stuff, but pretty much stuck to the safe lists. Hoping that someone might know of a fix. I've tried the obvious (resetting app preferences, restarting, etc.).
Click to expand...
Click to collapse
I get that error when the device I am pairing isn't in pairing mode. My Jabra earbuds.
Related
Hi!
Somethig strange just happend... Grab my Samsung Galaxy Tab and noticed, that wifi was off... so i turned it on... it said scanning... and after 5 or 8 seconds wifi turned off by itself... tried again... turned off again...
so...
rebooting - no help...
what's going on??? help?
--------------
ok, factory reset helped.... but i'm still wondering.... was it a virus... does anyone know sth about it??
The word "virus" isn't really applicable to Android devices. If used in VERY broad terms it almost applies, but even then it's a stretch.
There are programs that do malicious things out there, and the best thing you can do to avoid that is check the permissions on everything you download.
I doubt it would have been a virus. There are a lot of other explanations. But, for peace of mind, search the market for AVG and download the free version. Personally, I think it is more often than not a source of false positives, but as I said, it can provide some peace of mind as well
Seamus1 said:
There are a lot of other explanations.
Click to expand...
Click to collapse
Like...? Give me some ideas, please.
Well, I will say from the outset that I am not an expert at the technical details when it comes to such things. I would imagine that there was either some kind of corruption with the configuration files, or possibly with the OS itself. I have seen certain devices that occasionally reboot when power to WiFi is toggled on, for example. As to what caused it, there are really far too many possibilities to be able to say. I think that it would be difficult to get a virus from any of the app markets, most questionable stuff gets flagged. And of course you have the ability to see what these apps have access to. So perhaps it was an app that you allow network access to that screwed up the configuration through an error. Installing stuff that is non-market and of questionable repute could very well get you something malicious though.
Anyway, my original suggestion was going to be to try wiping all of the associated configurations and clearing the cache. But, you had already posted that you had it sorted out, so I didn't bother.
I am sure there are more informed people who could shed more precise light on the matter, these were just my ideas.
This does "just happen" sometimes. Usually, forgetting the connection information and re-entering it does the trick. If that doesn't then a hard reset (as you've already discovered) is the next best thing.
The technical term for what happened is "glitch".
Hey all, so I recently spent some time learning up on these awesome forums, and at least for getting started I decided to just modify stock 2.2, I have just really wanted to be able to play games using my ps3 controller on my nook so I thought the easiest path was to root using the Universal Rev3, and the Unknown Apps, at least to get me started. I have a bluetooth keyboard I also use with this setup for school. Okay so that's the upfront details.
My issue is that, while my bluetooth is connecting fine with everything before I run sixaxis, and my controller works (yay, i got what i wanted!) while I'm running the program, it's when I stop sixaxis and it restores my bluetooth (or says it does... or gets stuck and never says it does) my bluetooth simply can't be switched back on until after I reboot... I've completely stopped and disabled and cleared the cache on the sixaxis app... and nothing, still won't turn back on. Now this is a cadillac issue, my controller works, my keyboard works, but I just have to reset. The problem is that I know it shouldn't be this way and if it has to be, I'll survive, but if not I'd love a way to make it work right, or at the very least see if there's an option to... "respring" (I know that's an iphone thing I just didn't know if there was a faster equivalent to a reboot without having to completely turn it off and back on)?
Anyone else had this problem? Any thoughts? Any options? Thanks for your time and information, have a great day!
"t's when I stop sixaxis and it restores my bluetooth (or says it does... or gets stuck and never says it does) my bluetooth simply can't be switched back on until after I reboot..."
Obviously, its at the fault of the app, because otherwise (sixaxis not installed/used) bluetooth would function properly and no restart would be required.
Therefore, sixaxis is not ending support of the controller properly, re-enabling bluetooth support, or whatever its trying to do for the device, android version, or whatever its problem is in code.
Probably good to let the app's dev know about it and find out if they say anything.
Since root access is required, it definitely requires some deeper access to android (the deeper the more problems are likely to occur). Some code doesn't even work for all devices and they could have gone that route with their app knowingly - whether it was a necessary side effect due to the type of app they created or specifically because of a workaround of what google allows devs to do with android.
Either way it is often an app with problems as reviews show.
sandsofmyst said:
"t's when I stop sixaxis and it restores my bluetooth (or says it does... or gets stuck and never says it does) my bluetooth simply can't be switched back on until after I reboot..."
Obviously, its at the fault of the app, because otherwise (sixaxis not installed/used) bluetooth would function properly and no restart would be required.
Therefore, sixaxis is not ending support of the controller properly, re-enabling bluetooth support, or whatever its trying to do for the device, android version, or whatever its problem is in code.
Probably good to let the app's dev know about it and find out if they say anything.
Since root access is required, it definitely requires some deeper access to android (the deeper the more problems are likely to occur). Some code doesn't even work for all devices and they could have gone that route with their app knowingly - whether it was a necessary side effect due to the type of app they created or specifically because of a workaround of what google allows devs to do with android.
Either way it is often an app with problems as reviews show.
Click to expand...
Click to collapse
Hey thanks a ton for the information. I had started to suspect that but since I'm a noob here I thought it was best to ask. Will contact the developer. But hey for now if all I have to do is a reset after a gaming session to make all things right, it's not so bad. Thanks again!
EDIT: Okay, so after doing some fiddling with my own Nook HD+ it looks like the Nook itself has trouble shutting down bluetooth! When I go into my battery use bluetooth is staying on permanently after initially turning it on. The time continues to run no matter what I do or shutdown with Android Task Manger. And it appears I'm not the only one. http://bookclubs.barnesandnoble.com...Bluetooth-won-t-turn-off-Nook-HD/td-p/1462091
Also since mine is rooted and has unknown sources installed I felt like I needed a control group. So I borrowed my wifes Nook HD+ which is completely stock, no mods at all... and it does the exact same thing... This is mind boggling. Could a few people turn their bluetooth on long enough to register in their battery monitor, then turn it off, and tell me if their time is still running for the bluetooth? It would really help me identify whether this a software problem with Nook software, or it's a hardware issue that they had amongst several models and they shipped with bad parts, etc. Thanks!
gregorcarbine said:
Could a few people turn their bluetooth on long enough to register in their battery monitor, then turn it off, and tell me if their time is still running for the bluetooth? It would really help me identify whether this a software problem with Nook software, or it's a hardware issue that they had amongst several models and they shipped with bad parts, etc. Thanks!
Click to expand...
Click to collapse
It could also be this or similar: https://code.google.com/p/android/issues/detail?id=69135
Quote, "Problem: When turning off the Jawbone, it causes the Bluetooth(BT) to misbehave and not turn off nor function."
...Though that's for android 4.4.2 and nook 2.2 is android 2.2... wow that's old... that could of course be it as well - if the problem is with android, it could have been fixed in a later android version.
In the end, it doesn't appear to have to do with the device itself, but perhaps with that android version's bluetooth package or an installed app. And which android version (if any) would work for you idk. I remember people saying cm and sixaxis didn't work with bluetooth on the nook in the past, so if that's still the case, don't know that either.
I'm not sure how far back many apps are going today with android versions but something like: https://play.google.com/store/apps/details?id=org.myklos.btautoconnect&hl=en
could possibly do something(?). But, I'm just reaching there for anything in the you never know category.
But hopefully that gives a better picture as to what it could be. Sorry, I can't give an actual [working] solution, though for all I know I gave a path to the only solution.
So I got a new toy. A Samsung Gear Live. I've had it for a week and so far really like it. The biggest issue I seem to be having is the companion apps. I don't know why, but they refuse to work. Everytime I try to use one I get an error message to the tune of, " not connected to a device with this application" or "lost connection to phone". This is clearly untrue. I can see that I'm still connected and even the device itself acknowledges it. I just can't figure it out.
I have attempted a power cycle, using the restart function, a hard reboot, even reseting it back to factory. I rebooted my phone, Uninstalled and reinstalled the apps on the phone, and still no luck. I'm at a loss. Anyone who knows what to do on this front would be very welcome.
What are companion apps?
Sent from my SM-N910T3 using XDA-Developers mobile app
Companion apps, are the apps that are activated on your smart watch. Like the dominoes easy order app, or a bank app that let's you check your balances without pulling out your phone.
I did find my problem however. It seems that my gear live was shipped with a dev kit. I had to completely reflash it to stock software to get it to run correctly.
How did you figure out it was a dev kit? Im having similar problems. Thanks.
Fixed the problem resetting the watch and reinstalling the Android wear app. However now in the storange manager its showing three of several apps. How to fix please?
You can find if it has a Dev kit under the settings. Under build I believe. It should be a set of numbers with "dev" somewhere in it. If that's there, it's gonna hold up your regular use of the watch. It caused the apps not to work right or not to show up, etc. I'll see if I can find the link I used before for how I reset the watch to stock firmware.
I have been going through and optimizing my T813 by disabling stuff that doesn't need to be running, firewalling off anything that does need network access, etc. However, I've run into a couple odd issues.
The first is DRParser.apk (DRparser Mode). It is marked as safe to disable on the Galaxy S6/S7, and I have. Or at least I tried. Even when it is frozen, it is somehow getting started because it is banging at the firewall like nuts. I have AFWall+ setup to show toasts from the logger, and it is constantly showing DRparser Mode has been denied access to a half dozen IP addresses. I double checked, and yes, it really is disabled in Titanium Backup. There is some serious WTH going on here, as it persists after a reboot. I have used TiBu to successfully freeze other services, so I'm not sure what is so special about this one.
The other weird one is mDNS, which I believe is part of the "find stuff nearby" functionality. I don't actually have a problem with it, but I can't find a specific service to enable in the firewall. I'm guessing it's bundled with something else, but I'm not sure what. It's also getting flag by AFWall, but not nearly as often.
The last one is the game optimizer service. I'm not sure why it is trying to access the network, but it is. I'm tempted to freeze it, but I'm not sure what it actually does.
Anyone have any ideas on these?
jshamlet said:
I have been going through and optimizing my T813 by disabling stuff that doesn't need to be running, firewalling off anything that does need network access, etc. However, I've run into a couple odd issues.
The first is DRParser.apk (DRparser Mode). It is marked as safe to disable on the Galaxy S6/S7, and I have. Or at least I tried. Even when it is frozen, it is somehow getting started because it is banging at the firewall like nuts. I have AFWall+ setup to show toasts from the logger, and it is constantly showing DRparser Mode has been denied access to a half dozen IP addresses. I double checked, and yes, it really is disabled in Titanium Backup. There is some serious WTH going on here, as it persists after a reboot. I have used TiBu to successfully freeze other services, so I'm not sure what is so special about this one.
The other weird one is mDNS, which I believe is part of the "find stuff nearby" functionality. I don't actually have a problem with it, but I can't find a specific service to enable in the firewall. I'm guessing it's bundled with something else, but I'm not sure what. It's also getting flag by AFWall, but not nearly as often.
The last one is the game optimizer service. I'm not sure why it is trying to access the network, but it is. I'm tempted to freeze it, but I'm not sure what it actually does.
Anyone have any ideas on these?
Click to expand...
Click to collapse
I can't even find anything via google that even explains what this apk does. But I did find that the app associated with it is com.sec.android.app.parser. You might want to look for that in /Setup/apps. Once you open apps, you might have to click the settings and choose "show system" for it to appear in the list. I'm running the RR ROM on my T810 and that app isn't installed with the Pico gapps, so I can't test it.
edit: After a little more research, it appears that the apps function is to decode "special codes" that you dial on your phone. Without it, you won't be able to dial those codes. But I have no idea why that would require access through your firewall. But it would explain why it isn't found on my T810, which doesn't have a cellphone function.
This is on a T813, which also has no LTE functionality. I'm guessing Samsung puts a largely "standard" image on these devices, as it also has the Phone services as well. (from poking around, this thing feels a bit like a gigantic Galaxy S6). However, it's a moot issue, as it is lumped under a bunch of other stuff, at least a couple of which do require network access. So, whatever it is, I have to let it through. :|
I did, however, come across some info on the mDNS issue:
https://forum.xda-developers.com/showpost.php?p=63977673&postcount=2742
Apparently that is a strange AFWall+ issue, and there is a custom script to resolve the issue.
jshamlet said:
This is on a T813, which also has no LTE functionality. I'm guessing Samsung puts a largely "standard" image on these devices, as it also has the Phone services as well. (from poking around, this thing feels a bit like a gigantic Galaxy S6). However, it's a moot issue, as it is lumped under a bunch of other stuff, at least a couple of which do require network access. So, whatever it is, I have to let it through. :|
I did, however, come across some info on the mDNS issue:
https://forum.xda-developers.com/showpost.php?p=63977673&postcount=2742
Apparently that is a strange AFWall+ issue, and there is a custom script to resolve the issue.
Click to expand...
Click to collapse
It may be "lumped with other stuff" but I would think that "the stuff" would all be phone related and therefore removable. It isn't there in the custom ROMS. Did you look for the app I listed in your app settings?
Yes, it's there. DRParser.apk in /system/app. I can, if I need to, delete it now that I have a full system backup on the SD card - which I suppose is the next step. I usually disable services rather than deleting them, though.
jshamlet said:
Yes, it's there. DRParser.apk in /system/app. I can, if I need to, delete it now that I have a full system backup on the SD card - which I suppose is the next step. I usually disable services rather than deleting them, though.
Click to expand...
Click to collapse
Renaming or deleting the apk is an option, but I was talking about disabling com.sec.android.app.parser in the app settings.
Like so many others, I keep experiencing countless issues with AA informing me that it doesn't know how to send a text, that it's still learning of that it needs to gather more information. I'm on a Samsung S10 5G in a Kia Soul. First I tried a new cable. No help. I tried clearing the phone's cache. No help. Have tried multiple messaging apps. No help. (Currently using Pulse). Any other suggestions greatly appreciated.
How rubbish Rodney?
I don't understand your question. Its lack of consistency in doing things like simple sending/reading of SMS messages makes even the iPhone solution much more usable.
He is saying AA is crap and he is looking for a suitable working alternative.
I'm afraid I don't know how to do that. But I'm still learning *grin*
That's just it, I don't know. Are we stuck with it? Is there any app that can unify multiple apps and put them on the car's screen? I don't think so. I can't believe I'm saying this, but Apple's implementation of something is better than Google's.
In my truck not only does the factory head unit ask to read calls and text via Bluetooth but also via android auto. It could be possible that the two techs are competing and causing errors. One thing that may revel clue to or two is to park and open Matt log with your phone plugged in as you normally do and have someone send you texts and look for any errors.
mine420 said:
In my truck not only does the factory head unit ask to read calls and text via Bluetooth but also via android auto. It could be possible that the two techs are competing and causing errors. One thing that may revel clue to or two is to park and open Matt log with your phone plugged in as you normally do and have someone send you texts and look for any errors.
Click to expand...
Click to collapse
Thanks! One question: What's Matt log? AA has also started saying something along the lines of, "Sure, but first let me get some more information" - around this point the voice generally fades out and I can't here anything else, but sometimes it also continues with - "select the prompt on your device" but there's never a prompt.
With my car it only works via the steering wheel controls when the phone is connected via the USB cable. I might have to see how it works with just OK Google.
I thought this one was fixed... but every time I've tried to send a text lately "OK Google text X person" ti gives me let me gather some more information... then nothing. Am I doing something wrong, or is texting through assistant on AA broken?
Note10.1Dude said:
I thought this one was fixed... but every time I've tried to send a text lately "OK Google text X person" ti gives me let me gather some more information... then nothing. Am I doing something wrong, or is texting through assistant on AA broken?
Click to expand...
Click to collapse
mines gone back their doing this after the update about 2wks ago.
https://myaccount.google.com/devicecontacts
You should activate this option