Hi all,
I got my tab for a little while now, i rooted it but that is pretty much the only change i made.
I got a new phone; the xperia pro but with no data plan since i already pay for my tab.
I heard that its possible to turn the tab into a hotspot so my phone could connect to the internet whenever i want as long as the tab is nearby.
I've looked on the market but didnt find the best app to do it so am asking you guys to give me THE best app for this.
Thank you for your help
Btw, if some of you wonder whats the meaning of my name, its actually a "play on word" here u get the 3 diff meaning it can have
NainConpetant
(stupid farting midget)
(competent midget)
(incompetent)
FIXED, got it to work, it was easy, in wi-fi settings i found how to do it.
I would erase the thread, but i cant
Please someone help!
I've tried a couple of ROMs on my Galaxy S3 i9300, and the one I took a shine to was the Foxhound 1.4.
Love everything about it but I cant seem to get the Allshare Cast function to work.
I have the dongle, and the phone connects, but after a few seconds it disconnects again.
This happens on every ROM i try.
Does anybody know how to fix this?
Before I rooted my phone and it was completely stock, I did not have the Allshare Cast function in settings.
This has arrived after an update from Samsung, but since I'm on root and custom ROM i never got this update.
May this be why it dont work?
My girlfriend has stock unrooted S3 and the Allshare Cast works perfectly.
Wonder if I have to unroot my phone, update it from Samsung, then do it all over again...?!
Hope someone can help me.. Drives me insane
Hi,
in our warehouse I use the Galaxy Wifi 4.0 with a Motorola RS507 bluetoothscanner for orderpicking.
I have 10 of them all working without any problem. Now I needed 10 more, but the 4.0 is replaced by the 4.2. So I bought them instead.
But I cannot get the scanners working with this device.
If I want to connect the scanner I get the message:
Confirm passkey is xxxxxx to pair with RS507 1234
I can press "Accept" or "Decline"
When I press "Accept", it says "paired" but I cannot use the device.Also the device give no confirmation sound that it is connected.
On all the other devices (Wifi 4.0, Galaxy S, Lenovo A1 Tablet) I get the message:
Confirm password to pair with "RS507 1234"
Then I only have to press Accept and the device is paired and working.
Does anyone have a similar problem with another bluetooth device and knows a solution how I can connect the scanner?
If it will not work I have to look around for the old Galaxy Wifi 4.0.
Thanks for your help.
kiteman76 said:
Hi,
in our warehouse I use the Galaxy Wifi 4.0 with a Motorola RS507 bluetoothscanner for orderpicking.
I have 10 of them all working without any problem. Now I needed 10 more, but the 4.0 is replaced by the 4.2. So I bought them instead.
But I cannot get the scanners working with this device.
If I want to connect the scanner I get the message:
Confirm passkey is xxxxxx to pair with RS507 1234
I can press "Accept" or "Decline"
When I press "Accept", it says "paired" but I cannot use the device.Also the device give no confirmation sound that it is connected.
On all the other devices (Wifi 4.0, Galaxy S, Lenovo A1 Tablet) I get the message:
Confirm password to pair with "RS507 1234"
Then I only have to press Accept and the device is paired and working.
Does anyone have a similar problem with another bluetooth device and knows a solution how I can connect the scanner?
If it will not work I have to look around for the old Galaxy Wifi 4.0.
Thanks for your help.
Click to expand...
Click to collapse
Try enabling CONFIG_BT_HID in your kernel. I say this since the scanner's datasheet has blutooth HID listed, the 4.2 kernel doesn't have it enabled, and my 4.0 *does* have it enabled. In the 4.0 it's configured as a module, but you could try getting away with linking it directly in your kernel just in case the 4.2's init scripts/ueventd doesn't load it.
If you need help doing this let me know in a PM.
jlyo said:
Try enabling CONFIG_BT_HID in your kernel. I say this since the scanner's datasheet has blutooth HID listed, the 4.2 kernel doesn't have it enabled, and my 4.0 *does* have it enabled. In the 4.0 it's configured as a module, but you could try getting away with linking it directly in your kernel just in case the 4.2's init scripts/ueventd doesn't load it.
If you need help doing this let me know in a PM.
Click to expand...
Click to collapse
Thanks for your help. But I configured the scanner to use SPP an not the HID profile. Is SPP also disabled ?
It is not that important for me anymore.I bought 15 new 4.0 devices. But as a sport I want to get it working on de the 4.2
Can I ask?
kiteman76 said:
Thanks for your help. But I configured the scanner to use SPP an not the HID profile. Is SPP also disabled ?
It is not that important for me anymore.I bought 15 new 4.0 devices. But as a sport I want to get it working on de the 4.2
Click to expand...
Click to collapse
Hi, We are trying to do pretty much the same thing pairing RS507 to Galaxy Player. Can I ask where you found or can you describe the procedure for pairing.
Thanks!
eikaun said:
Hi, We are trying to do pretty much the same thing pairing RS507 to Galaxy Player. Can I ask where you found or can you describe the procedure for pairing.
Thanks!
Click to expand...
Click to collapse
What version of the Galaxy Player do you have? I only succeeded in connecting it to the 4.0 and the 5.0. If you need more help, let me know.
Yes I need help
kiteman76 said:
What version of the Galaxy Player do you have? I only succeeded in connecting it to the 4.0 and the 5.0. If you need more help, let me know.
Click to expand...
Click to collapse
To answer your question 4.0. Yes I need help I am flying by the seat of my pants on this. If you can help with a start to finish explanation including any software you downloaded I would very much appreciate it. Like I say I really need some help - so thanks
RS507 and Android Phone
eikaun said:
To answer your question 4.0. Yes I need help I am flying by the seat of my pants on this. If you can help with a start to finish explanation including any software you downloaded I would very much appreciate it. Like I say I really need some help - so thanks
Click to expand...
Click to collapse
Hi,
I've tried connecting Android to various other BT scanners before (using the SPP) and have not had problems. But I'm struggling on the RS unit.
What I normally do is on other scanners is turn pairing on for the scanner, connect and pair to the unit from the phone. Then start my application on the phone, which initiates the connection to the scanner and connects. Then I can read from the scanner and all works well.
On the RS this seems different, as you don't seem to put the RS in pair mode and connect to it. instead the process seems to be to scan a barcode on/for the device (with MAC id?) and the RS connects?
Either way, I have not managed to get this to work.
Can someone provide me with the correct process to connect the RS to an android device in SPP mode?
Any help or working code example would be much appreciated!
so i hate this and its annoying, when i get a text the screen turns on, i had that problem on my galaxy s3 and was looking around and found a file to flash from the sprint glaxy s3 fourms so i flashed it on my verizon galaxy s3 and i was able to disable the screen on notification , i was thinking about trying that on my verizon note 2 but decided not to , figured i go here and ask if anyone knows how to disable it or know of any hack with out using a third party app please and thank you!
I already used my gear s for months successfully with my note 4. Always worked OK, also remote connection through WiFi or 3g went without hiccups. Yesterday I bought an edge+, I reset my gear to defaults and installed and ran gear manager. Pairing was OK. All seemed good, only the moment Bluetooth connection is lost the gear switches to WiFi and almost immediately says it cannot set up remote connection. Also on 3g is not working. I ticked the remote connection checkbox in gear manager settings but doesn't work. Already three times reset the gear and setup again, completely removed all gear manager components, no luck so far. Working seamless on Bluetooth, not through remote connection.
Any body with s6 edge+ experience the same?
I have the same issue with my S6 edge+.
I also used the gear S with note 4 without remote connection issues.
I passed by Galaxy S6 Edge to Galaxy S6 Edge+ and I do not work more calls and notifications remotely with Gear S .
Before when I walk away from the range of the bluetooth with the Galaxy S6 Edge could perfectly to have call forwarding and notifications, now with Galaxy S6 Edge+ I get the message that you can not make the call diversion etc etc. connect to Bluetooth.
You have done the same experience?
You know the reasons and solutions?
Thanks for the reply
( * Please forgive Google Translate for the bad translation)
ddborello said:
I passed by Galaxy S6 Edge to Galaxy S6 Edge+ and I do not work more calls and notifications remotely with Gear S .
Before when I walk away from the range of the bluetooth with the Galaxy S6 Edge could perfectly to have call forwarding and notifications, now with Galaxy S6 Edge+ I get the message that you can not make the call diversion etc etc. connect to Bluetooth.
You have done the same experience?
You know the reasons and solutions?
Thanks for the reply
( * Please forgive Google Translate for the bad translation)
Click to expand...
Click to collapse
I have the same issues. I reported them to Samsung. I suggest everybody does the same. So maybe Samsung wakes up and fixes this problem. I suspect it has something to do with gear manager. I noticed that the preinstalled version on the s6 edge plus is older then the one you find in the Samsung store. But I cannot update to this version....
Not dependent on the software version. My S6 Edge+ version is the same that is on the Galaxy Apps (v.2.2.15070942)
ddborello said:
Not dependent on the software version. My S6 Edge+ version is the same that is on the Galaxy Apps (v.2.2.15070942)
Click to expand...
Click to collapse
You're right. Same version here. I was wrong because in my galaxy store the date next to the version number seems to be today's date. When I looked yesterday it was 9 Sept. That way it looked like it's was released today.
+1, same here
I also updated my S6 edge to the plus version. Everything worked fine with S6 edge but now I can't connect remotely (wifi or 3G). BT connection is OK.
I have reported this to Samsung and they promised to be in touch. Nothing yet thought...
6sto said:
I also updated my S6 edge to the plus version. Everything worked fine with S6 edge but now I can't connect remotely (wifi or 3G). BT connection is OK.
I have reported this to Samsung and they promised to be in touch. Nothing yet thought...
Click to expand...
Click to collapse
I thought i read somewhere that there was an update for gear manager. Can you check the samsung store to see if there actually is? Maybe it fixes the remote connection problem. I cant check for myself because i had to send my edge+ for repairs (i'm the guy who's back cover shattered)
Let me know please.... And if not succesful keep reporting to samsung... I'll do the same
Sent from my SGP512 using XDA Premium HD app
For me no update available..
Build date is 14.9 but its the same version number (2.2.15070942)
It still doesn't work
Last V.2.2.15070942 ..... remote transfer does not work!
We must insist to request a final settlement with the Service Samsung People.
Same here...note 4 worked perfectly. I swiched 2 days ago to S6 Edge plus and only Bluetooth connection works. Remote conection fails. Tried 3 resets/ uninstals but still nothing
Just reconnected to note 4 and remote connection works flawlessly... Back to the edge and the same problem... Come on Samsung!!!!!
Sent from my iPad using Tapatalk
I was having this issue at first but I got it to work, and now it's fine everytime.
Make sure the watch is on, and connected via Bluetooth. Then in the Gear S app, select "remote connect" so that it turns the option on. Then go to "auto call forwarding" and turn that on.
Then walk away until the Bluetooth disconnects. It will appear that remote connection is not working. Then walk back to your phone until Bluetooth reconnects. Then turn off remote connect (without turning off auto-call forward). Then turn remote connect back on. Then go to auto call forward and turn it on again. Viola, works.
ingenious247 said:
I was having this issue at first but I got it to work, and now it's fine everytime.
Make sure the watch is on, and connected via Bluetooth. Then in the Gear S app, select "remote connect" so that it turns the option on. Then go to "auto call forwarding" and turn that on.
Then walk away until the Bluetooth disconnects. It will appear that remote connection is not working. Then walk back to your phone until Bluetooth reconnects. Then turn off remote connect (without turning off auto-call forward). Then turn remote connect back on. Then go to auto call forward and turn it on again. Viola, works.
Click to expand...
Click to collapse
You have edge+ ? Cant try myself for the moment, maybe somebody can confirm? Tnx for the tip...
Sent from my SGP512 using XDA Premium HD app
Yes Edge+
Sent from my SM-G928T using Tapatalk
I use Multi Sim on the gear S so i tried it with the Multi Sim option. Doesn't work for me.
Anyone succeed with this method? I tried it a few times but with no luck.
ingenious247 said:
I was having this issue at first but I got it to work, and now it's fine everytime.
Make sure the watch is on, and connected via Bluetooth. Then in the Gear S app, select "remote connect" so that it turns the option on. Then go to "auto call forwarding" and turn that on.
Then walk away until the Bluetooth disconnects. It will appear that remote connection is not working. Then walk back to your phone until Bluetooth reconnects. Then turn off remote connect (without turning off auto-call forward). Then turn remote connect back on. Then go to auto call forward and turn it on again. Viola, works.
Click to expand...
Click to collapse
Hi there,
Having the same issues as everyone else here. I am connected to a Note 5 , with the gear manager pre installed. everything works fine except for the remote connection, I just get an error message "failed to enable remote connection" .
I was going to try this fix you suggested, however on my version of gear manager I do not even have the option of auto call forwarding, so I cant try your fix.
I have also tried connecting to a friends S5 and the remote connection worked fine.... this is very disappointing from Samsung to have this major function not working properly for so long.
I hope they provide an update / fix soon.
Regards
Brian
---------- Post added at 03:21 PM ---------- Previous post was at 03:18 PM ----------
glenner05 said:
I have the same issues. I reported them to Samsung. I suggest everybody does the same. So maybe Samsung wakes up and fixes this problem. I suspect it has something to do with gear manager. I noticed that the preinstalled version on the s6 edge plus is older then the one you find in the Samsung store. But I cannot update to this version....
Click to expand...
Click to collapse
Can you provide a link to the where to report to Samsung please and Thanks
So the problem is with the note 5 as well....it must be the version of gear manager cause its a different version than my note 4 which it works perfectly on for the past 9 months. I love my gears s. So i hope Samsung fix this problem!!!!
Sent from my iPad using Tapatalk
cydiamante said:
So the problem is with the note 5 as well....it must be the version of gear manager cause its a different version than my note 4 which it works perfectly on for the past 9 months. I love my gears s. So i hope Samsung fix this problem!!!!
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
I just spent some time with a "Samsung Expert" in online chat discussing the issue , they said this has not yet been reported to them, so I hope everyone who is posting here will start reporting it to Samsung.
They have now arranged to call me on Wednesday and remotely take control of my phone to see if they can find or resolve the issue , so I will wait and see what they come up with, in the mean time I hope everyone will start contacting Samsung.
I will post back again after my call with them on Wednesday.
Regards