Develop Bugs

[Q] Galaxy Gear doesn't unlock Note 4 -- help asked

Summary: I've got the original Galaxy Gear, and also a Note 4 international (in The Netherlands). The Gear is not rooted. The Note 4 is rooted, but only for Titanium Backup purposes. I've got everything connected and set up and all works properly, except automatic unlocking!
Set-up: I set up my phone to work without locking. Rebooted the phone and the gear. Then I set up automatic unlocking when the gear is near, in the gear manager. It asks me a pattern (twice) and a PIN (twice) and the switch gets "on".
Problem: From now on my phone is always locked, and always asking for a pattern. This is different from my same set-up with an S5, where the phone neatly only requires a swipe when near with my gear (no rhyme intended) and only asks for a pattern when the gear is off or away.
I tried:Reinstalling Gear Manager from scratch. Resetting Gear to factory settings. Clearing all data from Gear software from Titanium. Clearing/deleting all connections in BlueTooth. Reinstalling/geconfiguring Gear Manager, connection, Gear, phone. Disabling all locking on phone. Rebooting both phone and Gear between each step mentoined. Searched the internet/forums for suggestions, nothing found (most people experience the Note NOT locking íf they have any problems at all). Saw somewhere people in forums mentioning needing to put the phone on top of the watch touching it (some proximity issue): I tried that touching it EVERYWHERE on the phone, but this also did nothing. Nothing of this worked, all resulting to the same problem.
Not tried: Complete reflash to factory of phone........not wanting to do that.
Question: Are there any people here with similar issues and maybe (hopefully!) suggestions to fix it? It's really annoying to have to unlock my phone all the time!

Hi,
I'm also having the same problem! Still looking for a fix as well....
mvdhnl said:
Summary: I've got the original Galaxy Gear, and also a Note 4 international (in The Netherlands). The Gear is not rooted. The Note 4 is rooted, but only for Titanium Backup purposes. I've got everything connected and set up and all works properly, except automatic unlocking!
Set-up: I set up my phone to work without locking. Rebooted the phone and the gear. Then I set up automatic unlocking when the gear is near, in the gear manager. It asks me a pattern (twice) and a PIN (twice) and the switch gets "on".
Problem: From now on my phone is always locked, and always asking for a pattern. This is different from my same set-up with an S5, where the phone neatly only requires a swipe when near with my gear (no rhyme intended) and only asks for a pattern when the gear is off or away.
I tried:Reinstalling Gear Manager from scratch. Resetting Gear to factory settings. Clearing all data from Gear software from Titanium. Clearing/deleting all connections in BlueTooth. Reinstalling/geconfiguring Gear Manager, connection, Gear, phone. Disabling all locking on phone. Rebooting both phone and Gear between each step mentoined. Searched the internet/forums for suggestions, nothing found (most people experience the Note NOT locking íf they have any problems at all). Saw somewhere people in forums mentioning needing to put the phone on top of the watch touching it (some proximity issue): I tried that touching it EVERYWHERE on the phone, but this also did nothing. Nothing of this worked, all resulting to the same problem.
Not tried: Complete reflash to factory of phone........not wanting to do that.
Question: Are there any people here with similar issues and maybe (hopefully!) suggestions to fix it? It's really annoying to have to unlock my phone all the time!
Click to expand...
Click to collapse

sib0rg said:
Hi,
I'm also having the same problem! Still looking for a fix as well....
Click to expand...
Click to collapse
Mee three

Which version of the os are you running on the gear? The original or the new tizen version? That might be the issue of you didn't upgrade the watch to the new version that the gear 2 is using.

anyone find a solution yet? I am running the stock android on the gear (don't want to update to tizen - as I like my side loaded apps)
those with the tizen update installed is the auto unlock working for you?
I have also noticed the e-mail notifications are not coming to the gear from the Note 4 either. With my Note II everything worked/works great (running android 4.4.2). The Note 4 running 4.4.4 doesn't , so it's not a problem with the gear.
thanks,
Kit

[Q] Is there a way to pair Galaxy Gear S to a Galaxy Tab S 8.4 LTE (SM-T705)?

Hi,
I dont know if anyone has an answer to my question but I am just curios if there a method in doing this
"Is there a way to pair Galaxy Gear S to a Galaxy Tab S 8.4 LTE (SM-T705)?"
Coz to my surprise that here in Singapore I tried to pair demo Galaxy Gear S from retail store or even Samsung Store and it would not detect the Gear S on my Tab S 8.4 using the Gear App that I got from the Samsung Store.
They also said that the Gear S is not compatible with any newer tablets (Tab S) that Samsung has even the tablet has LTE and can make outbound and received inbound calls.
Anyone out their either ROOT method or NOT please do let me know coz it would be a waste that Gear S wont be able to pair to a Tab S 8.4 LTE (SM-T705) with phone capability.

Edit:
The only way that I was able to pair my Tab S with my Gear S was to first setup the Gear S on a Note 2, then
I did a titanium backup of Gear Manager and restored that on my Tab S.
I was then able to connect them after wiping the Gear S first. It took a little trial and error and a few restores but it worked.
All of the default Gear Apps work.
The Gear Store is empty but I am hoping a build prop edit will fix that.
Otherwise the Tab S said it was not a supported device.
Sent from my SM-T705 using Tapatalk

kable said:
Edit:
The only way that I was able to pair my Tab S with my Gear S was to first setup the Gear S on a Note 2, then
I did a titanium backup of Gear Manager and restored that on my Tab S.
I was then able to connect them after wiping the Gear S first. It took a little trial and error and a few restores but it worked.
All of the default Gear Apps work.
The Gear Store is empty but I am hoping a build prop edit will fix that.
Otherwise the Tab S said it was not a supported device.
Sent from my SM-T705 using Tapatalk
Click to expand...
Click to collapse
Damn, I have the same issue. And I just sold my Note 4. waiting on delivery for the note 4 duos.

I realize this is an older thread but I picked up the International Tab S this week and wanted to post the process it took for me to get this working with my Gear S.
So, to start off, I have all functions working except the built-in SMS feature. I can use any other message app and get notifications but I am still trying to figure out what it will take to have the built-in SMS on the Gear S synchronize with the Tab S. I think it may require the SMS app from a supported device so that is where I am going next with this.
To get the Gear Manager itself to find the Gear S required Root access and editing the build.prop file. In this file there are two things you must change:
1) [ro.product.model=] should be changed from SM-T705 to SM-N910A (or any Gear S supported model)
2) [ro.build.characteristics] should be changed from tablet to phone. This has to be changed back after completely pairing for the first time, otherwise Settings will force close every time you try to open it.
At this point I have all the apps I need and all functionality except the SMS issue mentioned above and the forwarding feature was not working. After much troubleshooting I discovered that I could not even forward from the settings menu directly. After a lengthy chat with AT&T, and having them reapply my IMEI from my Note 4 to the account, it is now working as expected.
I am very happy with this tablet, even though I do not currently have LTE capability. Being able to combine my tablet and phone is incredible and thanks to the Gear S it is feasible. I guess to each their own but it works great for me. I am hoping that at some point we can figure out a way to add the US LTE bands to this device but it is not that big of a deal for me. Everything I have tried to stream and access has been flawless so far. I hope this post is helpful to others trying to get the Gear S working with the Tab S.
**** Update ***** I just realized that I can send SMS from the Gear S and it goes out like it game from my Tab S phone number as it should. So it appears that it is only coming back from the Tab S that is not working properly at the moment.

[Q] Hello, just a couple questions.

Hello, i've just got a couple questions about Android itself and a device I recently bought.
Today I got a Samsung Galaxy Tab S 10.5 for the sole purpose of using it for study, I also bought a case/keyboard it. I also have a Samsung Galaxy S4 LTE-A. I'm wondering if there's a way for the two devices to "talk" together at all. I am also wondering on the tablet how to get rid of the "Quick Connect" option which is next to "S Finder" in the pull down menu from the top of the screen. I'm still somewhat new to Android, so any general tips would be great too. I've removed some bloatware from both of my android devices themselves, such as all of the Samsung pre-installed software.
Also any recommended apps too would be great and also some tips on how to use my tablet and get the most out of it. I've been a desktop computer person my whole life and I've built a few too, I just felt like a new change and I want to make the most out of it. I apologise if this is the wrong area to post in, it's just I have no idea where to ask for help.
Thanks.

Bump

Enable 'Nearby devices' under connections in settings.

ashyx said:
Enable 'Nearby devices' under connections in settings.
Click to expand...
Click to collapse
Okay, thanks! Any other tips?

User feedback on Official Cyanogenmod 13 for N5100

Hello guys,
Was wondering if people running the new official CM builds could give the rest of the community some overall impressions about the ROM. Specifically, what's working and what isn't, the issues they've faced so far and suitability as a daily driver. In the dev thread the only thing specified as not working is making calls.
The Dev thread is obviously not appropriate for this discussion and I'm eager to migrate from stock to AOSP since the device has long been abandoned by Samsung.

Well having an ATT Note 8.0 myself... as a 2nd unit to my 2 Note 8.0 devices running 4.4.2 amd 4.2.2. I chose to keep 4.2.1 on the ATT Note 8.0, due to it being locked and somewhat the step child here. Hopefully you have the Rogers (Canadian) version of my ATT Note 8.0. There are threads on Rogers Note 8.0 to assist you in recovering your device. If you have an ATT Note 8.0, your only hope is to have ATT send it in for exchange repair.
I am surprised you paid for a used item that did not work from a pawn shop. You may not get your money back, as some shops do not have a return policy.

gooberdude said:
Well having an ATT Note 8.0 myself... as a 2nd unit to my 2 Note 8.0 devices running 4.4.2 amd 4.2.2. I chose to keep 4.2.1 on the ATT Note 8.0, due to it being locked and somewhat the step child here. Hopefully you have the Rogers (Canadian) version of my ATT Note 8.0. There are threads on Rogers Note 8.0 to assist you in recovering your device. If you have an ATT Note 8.0, your only hope is to have ATT send it in for exchange repair.
I am surprised you paid for a used item that did not work from a pawn shop. You may not get your money back, as some shops do not have a return policy.
Click to expand...
Click to collapse
I'm not sure you're responding to the correct thread.

Anyone? Is there a chance the voice calls will work in the future or is it a dead end? Also how well do the cameras work (front and rear)?

Random video issues exist. Colored diagonal lines when using Netflix, Google video, etc. Also glitches sometimes when using various OS functions.

There are two of us with N5110s that have no gps output. Since I use mine for marine charts and the other is used for aviation charts it is more than an inconvenience. Sad to say that the other person (very competent, and specifically something of an expert on GPS) tried to file a bug report about it and was refused!?! Very strange.
What makes this particularly annoying is that the CM12.1 nightlies, very stable for a very long time, were converted to CM13 nightlies without any warning. Imagine my surprise when my occasional update resulted in CM13 booting (with problems) and required a wiping of /data to make it stable. Either a huge warning or a separate line of nightlies would seem appropriate.
Edit: I am also experiencing the occasional video flashing, but it doesn't get in the way of usability.
I am a big fan of CM but it does look like CM13 is still having teething problems.
Greg

The screen flicker issue is still there. Until they do not solve that issue, I cannot comfortably use CM13 on my N5100. I have to stay with CM12.1, and periodically test the nightly releases of CM13, until that bug is completely solved.
Everything else, seems to work fine.

sorry an unrelated question.
is there any cm 12.1 that works fine on n5100 which has fix calling bug.thanks

The flashing issue is supposed to be fixed in today's (4 May 16) nightly. Trying it now...
GPS still does not function.
Greg

CarinaPDX said:
The flashing issue is supposed to be fixed in today's (4 May 16) nightly. Trying it now...
GPS still does not function.
Greg
Click to expand...
Click to collapse
Yes, you are right. The flicker issue is solved in nightly release from May 4, 2016.
I have installed it, and make a backup of both, CM 12.1 and CM 13, to be protected if,
for some reason, something wrong will happen.
A workaround to easily change the USB mode from default, that is charging, to MTP data transfer,
will be usefull when connecting the phone to PC. It is very annoying to go every time to
Settings => Developer Options => Select USB Configuration, and choose the desired mode,
or select mode from drop down menu when you are notified for new USB connection presence.
There are third party applications on Google Play, like "USB for Marshmallow",
but it will be better if a solution to problem will be implemented directly in CM13,
that will set default mode to MTP data transfer.

I've tried Unofficial CM13 on my GT-N5100 3G/WIFI developed by RGIB.
SIM card not detected. Screen flicking. Camera failed.

parsa.io said:
I've tried Unofficial CM13 on my GT-N5100 3G/WIFI developed by RGIB.
SIM card not detected. Screen flicking. Camera failed.
Click to expand...
Click to collapse
have you followed Rgib's instructions on the first post of cm13?

Volte
Add volte support for oneplus one for the next official update

Because of the security policy, Samsung Health Monitor App can't be opened on a rooted device. Device has never been rooted.

My Sprint Samsung Galaxy Note10 Plus can't use the Health Monitor App that is connected to my Samsung Galaxy Active 2 watch. It claims my phone is rooted. I have not rooted a phone since my Samsung Galaxy S4. I have however, been downloading / transferring my info from phone to phone whenever I upgrade. Is it possible their is some error related to my old data? Is it possible my phone could have been rooted without my knowledge? I would like to use this app. I am a bit more concerned with my phone returning an it is rooted error. Anyone have any advice on this? I am running Android 12 with One UI version 4.1. Thanks in advance for any assistance.

Don't use SmartSwitch...
Was it running ok on 11?
12 is a mess.
I'm still and will stay running on Android 9 and 10. Security has not been an issue with only slight user modifications like disabling wifi.

It was not running on 11 either. Don't know why it says that. I have had an S6 Edge, S8 Plus, and now the Note 10 Plus. I have not done anything remotely close to rooting, flashing, or anything else since my S4. I have health issues and so I would really like the convenience of the Health Monitor App. All other features Knox should not allow to work if it was truly tripped work. So, I'm at a loss. Thanks for your reply.

crucian4 said:
It was not running on 11 either. Don't know why it says that. I have had an S6 Edge, S8 Plus, and now the Note 10 Plus. I have not done anything remotely close to rooting, flashing, or anything else since my S4. I have health issues and so I would really like the convenience of the Health Monitor App. All other features Knox should not allow to work if it was truly tripped work. So, I'm at a loss. Thanks for your reply.
Click to expand...
Click to collapse
It's sounds like a solvable issue if the knox efuse isn't tripped.
Make sure the Wearables apps have all their many permissions or it will puke on you.
Any Samsung apps disabled? Dependencies...
Clearing app data or reinstalling maybe. Clear system cache.
Call Samsung tech support, occasionally they do have solutions.

crucian4 said:
My Sprint Samsung Galaxy Note10 Plus can't use the Health Monitor App that is connected to my Samsung Galaxy Active 2 watch. It claims my phone is rooted. I have not rooted a phone since my Samsung Galaxy S4. I have however, been downloading / transferring my info from phone to phone whenever I upgrade. Is it possible their is some error related to my old data? Is it possible my phone could have been rooted without my knowledge? I would like to use this app. I am a bit more concerned with my phone returning an it is rooted error. Anyone have any advice on this? I am running Android 12 with One UI version 4.1. Thanks in advance for any assistance.
Click to expand...
Click to collapse
Try this as a workaround......weird your device thinks its rooted, or once was rooted.
[RESTRICTIONS-REMOVED] Samsung Health Monitor - WearOS - 1.1.3.002 - Root, Age, Country & Device Restriction Removed - 23rd May 2023
Hello Everyone, I hope you all are fine... ~~~ WearOS WATCHES ONLY ~~~ ~~~ FEATURES, BUGS & FUTURE WORKS~~~ FEATURES: Works on Samsung Watch4 and Watch5 (as mentioned Samsung WearOS Watches), Multilanguage, no root detection, no country...
forum.xda-developers.com