Samsung released a Marshmallow (Android 6.0/M update to the Gear app, the Gear Plugin, and the Samsung Accessory Service apps on October 12. They then released updates again on October 15 and 16.
None of these three updates allow the S2 to stay connected via Bluetooth to your Marshmallow phone. Phone will connect once, and then fail to reconnect UNLESS you do a "Light" or "Factory" reset. Of course you lose some or all of your data and settings. And then if your S2 goes out of range of Phone, reset time again.
Just wanting folks to be aware. Suggest you leave a comment in Google Play for all three apps, but who knows if Samsung even reads those comments. At this point I don't even know if the people at Samsung who need to know about this, are even aware of issue.
I hope this is fixed soon... I left negative feedback until it is resolved.
I replied to you on the other thread, did you make sure permissions were set for both Manager and Plug In apps?
I learned awhile back ago, first to update is the first to find the new problems. Automatic updates and being the first to download is COOL, but not always functional.
15 days, and still not working on Android 6.0 Marshmallow phones. Apparently if you are on Marshmallow, and hadn't already installed the Gear app from the Play Store, you're now seeing "your device is not compatible" and you can't install it.
A user on Android Central with a Nexus 6 on Marshmallow is reporting that there is a firmware update under About Gear in the Gear app that has fixed the Bluetooth connection issue. I don't have my S2 with me at the moment, so anyone with a Marshmallow phone should check for the Firmware. Please let us know if you're successful in repeatedly reconnecting without having to do a reset every time you go out of range. Thanks!
I can confirm that I have repeatedly been able reconnect my S2 to my Nexus 5 on Marshmallow after I installed the S2 firmware update that was available in the USA in the Gear app under the About Gear settings. I went from firmware version R720XXU2AOIL to R720XXU2AOJ3. I found that even after installing the firmware, I had to do one Light Reset on the S2 before the S2 would reconnect.
So far so good. Have intentionally gone out of range 6 times and reconnected all 6 times. Will report back if situation changes.
FitzAusTex said:
I can confirm that I have repeatedly been able reconnect my S2 to my Nexus 5 on Marshmallow after I installed the S2 firmware update that was available in the USA in the Gear app under the About Gear settings. I went from firmware version R720XXU2AOIL to R720XXU2AOJ3. I found that even after installing the firmware, I had to do one Light Reset on the S2 before the S2 would reconnect.
So far so good. Have intentionally gone out of range 6 times and reconnected all 6 times. Will report back if situation changes.
Click to expand...
Click to collapse
I literally sold my S2 Classic recently because of this issue. It's really fixed now? I need to learn to exercise patience.
Yeah, been working all day, so I'm optimistic that it's fixed.
I'm about to upgrade my phone to Marshmallow. Did this issue get fixed? Can the Gear S2 connect with Marshmallow phones?
I'm on a Note 5 with Marshmallow and have had no problems with connectivity to my Gear S2.
Thank you! I updated my phone to Marshmallow too and it's working fine since yesterday.
Ive got a htc one A9 running marshmallow 6.0.1 does anyone knows if is 100% compatible with the gear s2 i hear people telling me it is but at what end? Do all functions work with non samsung devices? I use a lot of gmail and whatsapp and i hope to reply via the gear s2 so just wondering. Thanks to anyone that helps
Related
I don't know how many of you have the Gear 2 along with a ton of apps/games (600+) on your Note 3, but any time I select "notifications" from within the Gear Manager with the Gear 2 it instantly freezes/crashes...giving me an error of "Unfortunately, Gear 2 plugin has stopped."
So I get NO notifications on the Gear 2 like I do on my Gear 1. After speaking with Samsung tech support 3 times it has been confirmed that this seems to basically be a memory issue (which I actually experienced with the Gear 1 as well until a Gear Manager update came out that helped).
In addition to the new gear being Tizen based and not having Android apps like Watch Styler (which causes me to lose over 100+ Gear 1 watch faces), I have also been extremely frustrated with the way the devices connect to your phone. Once connecting the Gear 2, going back to re-connect the Gear 1 is a true pain in the ass! The Gear Manager will constantly have to restore/re-install it's software every time you go back and forth between the two devices. When the Gear 1 finally does re-connects, which has sometimes taken over an hour to do, you'll not only find your watch battery drained but also some of your settings in the GM have been lost for your Gear 1. It's almost like Sammy didn't expect any of the Gear 1 owner to buy the Gear 2 so they hardly tested the two of them working well together.
So in short, with no notifications, no Watch Styler faces, no more camera shortcuts, no more hourly chimes, connection issues, and the WatchOn app that claims not to work with my Comcast cable box (when the same app works perfectly on my Note 3 and Note 10.1 with all my Comcast boxes) says to me that this $300 paperweight might be returned to the store soon for a full refund!
Buyers beware!...
P.S. - If anyone has a fix for the "crashing notifications" problem please let me know (and I've repeatedly tried clearing cache & data for GM with no luck). If nothing else, I need that at least to be working or this device is pretty much useless to me. Thanks.
When was the release date? 7 days ago...
What exactly did you expect? Give developers a little bit more time lol
There are also availability problems
I have absolutely no problems connecting the gear to my note 2 and everything works fine
For your Note 3 problem
Try this:
tizenexperts.com/2014/04/hack-unofficial-fix-samsung-galaxy-note-3-not-working-with-samsung-gear-2-neo
Helga Pataki said:
When was the release date? 7 days ago...
What exactly did you expect? Give developers a little bit more time lol
There are also availability problems
I have absolutely no problems connecting the gear to my note 2 and everything works fine
For your Note 3 problem
Try this:
tizenexperts.com/2014/04/hack-unofficial-fix-samsung-galaxy-note-3-not-working-with-samsung-gear-2-neo
Click to expand...
Click to collapse
I know this device was just recently released, however, I currently have 8 Android devices (5 of them Samsung) and I am very used to new tech ALWAYS having a bug or 2 when released. But not being able to properly connect a device "that has to be connected to even boot up initially" or not getting any notifications/communications at all on a smart watch is really unacceptable IMO because this is part of the watch's main functionality! If it doesn't connect or communicate messages at launch then how useful is it at $300. Having been a beta tester years ago, this product just doesn't seem to be very well tested to have such major problems right out of the box.
I've heard that an update might have been released today. I'm hoping that this info is true and that it addresses at least these major issues. I can then wait for the other fixes to come down the line later. By the way, thanks for the link! It doesn't really fix my problem with re-connecting the Gear 1 from the Gear 2 or the notifications issue, but interesting nonetheless.
I have the exact same problem ! The only way I got it to work was factory reset of note 3 then install Gear Manager and setup your notifications. But after a while the problem returns.
I'm hoping Samsung can fix this. I thought it may have been issue with the Omega ROM I installed on Note3 but it appears to be a prob on any ROM.
Sent from my SM-N9005 using xda app-developers app
Gear 2 notifications stops working after while
mcse17 said:
I have the exact same problem ! The only way I got it to work was factory reset of note 3 then install Gear Manager and setup your notifications. But after a while the problem returns.
I'm hoping Samsung can fix this. I thought it may have been issue with the Omega ROM I installed on Note3 but it appears to be a prob on any ROM.
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
I am facing same problem. I restarted. did factory reset. and restarted many times. It starts working and then after a while stops working and no notifications on my Gear 2. I miss Gear 1 never had problem with Gear 1 but this Gear 2. How to contact Samsung to resolve this problem.
All,
The 5 September update of Gear Manager caused my watch to continuously disconnect from my Note 3.
The only thing I could do was factory reset the Gear 2 and reconnect. However, restoring the backup failed as the progress indicator remained at 100% and never continued. The last resort was a full wipe and start from scratch reinstalling all the apps.
Gear Manager settings show that an old backup is still present but it is greyed out.
Anyone else had this problem?
Sent from my SM-N9005 using XDA Free mobile app
gschot said:
All,
The 5 September update of Gear Manager caused my watch to continuously disconnect from my Note 3.
The only thing I could do was factory reset the Gear 2 and reconnect. However, restoring the backup failed as the progress indicator remained at 100% and never continued. The last resort was a full wipe and start from scratch reinstalling all the apps.
Gear Manager settings show that an old backup is still present but it is greyed out.
Anyone else had this problem?
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
I'm runing tizen mod 3.0 and my galaxy s4 running hyperdrive RLS 18.1. I am having the same issues but cannot figure out of its eithe rof my roms on the phone or watch. i did notice that this disconnect issue did not occur when I had the stock factory image on my gear 2. I thought it might be the roms. But now that you mention it, it may be the latest update with gear manager.
I'm hoping some savy developer or someone with more expertise on the issue can shed some light on this issue.
RJV3 said:
I'm runing tizen mod 3.0 and my galaxy s4 running hyperdrive RLS 18.1. I am having the same issues but cannot figure out of its eithe rof my roms on the phone or watch. i did notice that this disconnect issue did not occur when I had the stock factory image on my gear 2. I thought it might be the roms. But now that you mention it, it may be the latest update with gear manager.
I'm hoping some savy developer or someone with more expertise on the issue can shed some light on this issue.
Click to expand...
Click to collapse
There is an update that was released today as well, and of 9 reviews 7 of them state that it breaks the gear 2. But hey, they added support for the Gear S....
anmghstnet said:
There is an update that was released today as well, and of 9 reviews 7 of them state that it breaks the gear 2. But hey, they added support for the Gear S....
Click to expand...
Click to collapse
Thanks for the heads up. I was able to pull the old gear Manager apk file and did 4 factory resets on my watch and my phone to get the thing up and running again. Can't believe samsung would update the gear Manager and not do extensive testing if people are already complaining of it breaking gear 2 connection. [emoji19]
RJV3 said:
Thanks for the heads up. I was able to pull the old gear Manager apk file and did 4 factory resets on my watch and my phone to get the thing up and running again. Can't believe samsung would update the gear Manager and not do extensive testing if people are already complaining of it breaking gear 2 connection. [emoji19]
Click to expand...
Click to collapse
Any chance you could post the old gear manager apk?
I have TizenMod 3.0 and Saproviders stops, I can't get notifications on the gear anymore... Samsung is really making me lose patience :/
Edit : all due to today's upgrade.
Same here. Anyone else know if we can deactivate the automatic updating? I did my bi-weekly CWM backup just last night (lucky!) so I have no problem restoring but as soon as I reboot the damn thing automatically updates! I want to pull the sim out, do a restore, deactivate the auto-update function and just leave it as it is until there is a fix. I would try restoring from Titanium but there are like 9 additional apps that it either installs or updates after the new Gear Manager installs!
This may be late for some of you but this is how I get around the problems...
1) Before you update the gear manager app, make a backup of the gear manager apps with titanium backup. (all the apps associated with gear manager will have the same gear logo)
2) Then open the app and update the software
3) Once complete, confirm that your Gear watch is connecting and receiving notifications. (The easiest way to do that is send yourself a text message)
4) If your watch is not working correctly or not connecting to the phone, then go back into titanium backup and restore the Gear Manager app back to the backup you made in step 1.
5) Repeat steps 2 and 3 until it works.
I personally had to do this twice before it connected and I received notifications. For future updates this is the only way I would do it because it is such a glitchy application and I'm tired of factory resetting my Gear and re-installing everything multiple times.
I hope this helps someone!
Strangely enough this update worked fine for me. It was the previous update that messed all up here..
Sent from my SM-N9005 using XDA Free mobile app
gschot said:
Strangely enough this update worked fine for me. It was the previous update that messed all up here..
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
Was your watch rooted or modded?
Not this time. Reverted back to stock just to be sure after the problems of the previous update. Just had it rooted then though.
Sent from my SM-N9005 using XDA Free mobile app
gschot said:
Not this time. Reverted back to stock just to be sure after the problems of the previous update. Just had it rooted then though.
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
So you used ODIN to revert to stock, rooted by normal means and then updated the Gear Manager and it worked fine afterwards?
I flashed stock with Odin and left it that way after the problems with the previous gear manager update. Before that I just ran stock rooted, no custom rom. The only reason I rooted was to remove the camera sound, but I don't use the camera that much on the gear.
Sent from my SM-N9005 using XDA Free mobile app
gschot said:
I flashed stock with Odin and left it that way after the problems with the previous gear manager update. Before that I just ran stock rooted, no custom rom. The only reason I rooted was to remove the camera sound, but I don't use the camera that much on the gear.
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
I'm thinking that this new Gear Manager update checks the watch for root access and won't let it connect. That's just my first impression anyway.
I removed root from my watch but kept TizenMod, re-paired the watch and it connected without a hitch.
I don't think root is the problem because most of the comments are negative and I doubt most people have their Gear rooted. I think it's a software issue because even before root was available there were plenty of people having issues with connecting and the software has not improved much since then.
alienmanam said:
I don't think root is the problem because most of the comments are negative and I doubt most people have their Gear rooted. I think it's a software issue because even before root was available there were plenty of people having issues with connecting and the software has not improved much since then.
Click to expand...
Click to collapse
When was the last time you made a positive comment for something like that on Play Store?
Still... you might be right. All I know is that as soon as I un-rooted it cleared right up. Could be coincidence though.
Gear manager update
Binary100100 said:
When was the last time you made a positive comment for something like that on Play Store?
Still... you might be right. All I know is that as soon as I un-rooted it cleared right up. Could be coincidence though.
Click to expand...
Click to collapse
I installed the new Gear Manager update yesterday and I thought all was ok. Its only when I came to load "Fitness with Gear" I noticed it won't sync anymore. Tried everything to get it to come back but its a no go. anyone any idea's on this or having the same problem?
Rich
xtermin8 said:
I installed the new Gear Manager update yesterday and I thought all was ok. Its only when I came to load "Fitness with Gear" I noticed it won't sync anymore. Tried everything to get it to come back but its a no go. anyone any idea's on this or having the same problem?
Rich
Click to expand...
Click to collapse
Hmm.
Perhaps it could be related to Fitness with Gear because I have it installed as well.
Binary100100 said:
When was the last time you made a positive comment for something like that on Play Store?
Still... you might be right. All I know is that as soon as I un-rooted it cleared right up. Could be coincidence though.
Click to expand...
Click to collapse
If it's an app I really like and support then I'll make a positive comment but I do also make negative comments as well. Root may cause some issues but before I had root I still had trouble with the app and had to factory reset multiple times just to get it to connect. I'm rooted and it still took me 2 times of trying to update to get it to work correctly. I think overall, Samsung did not spend enough time developing before releasing the Gear and Gear Manager. They're too busy pushing out a new phone every year and a new watch every 6 months.
alienmanam said:
If it's an app I really like and support then I'll make a positive comment but I do also make negative comments as well. Root may cause some issues but before I had root I still had trouble with the app and had to factory reset multiple times just to get it to connect. I'm rooted and it still took me 2 times of trying to update to get it to work correctly. I think overall, Samsung did not spend enough time developing before releasing the Gear and Gear Manager. They're too busy pushing out a new phone every year and a new watch every 6 months.
Click to expand...
Click to collapse
Agreed. This is definitely a poor job on Samsung. They did this **** just before the release of the Gear S? What a way to win hearts and minds. Think Apple will have these issues? I mean damn... the developers on this forum don't even have fails this big! When they notice that something that they developed doesn't work as expected they pull the link, fix the problem, TEST IT and then release it almost immediately. This is neglect.
Ever since updating to 5.1.1 via OTA update on my AT&T Galaxy Note Edge SM-N915A, I have had numerous issues. The phone lags/freezes often at best, but also crashes and reboots randomly. Worse yet, it has gotten into a boot loop a few times. I have factory reset and cache-wiped numerous times and even flashed a clean 5.1.1 via odin and still have the same issues. Apparently 5.0.1 or 4.4.4 cannot be flashed via Odin once 5.1.1 is installed and I can confirm this is true as I have tried.
Is anyone else having these issues? I have seen similar reports from the Note 4 forums but they seem to be getting new firmware updates to fix the issues. My firmware is N915AUCU2COI2 and is the latest available for the SM-N915A as far as I can determine.
try to flash kernel find on xda.
sagelwwa said:
Ever since updating to 5.1.1 via OTA update on my AT&T Galaxy Note Edge SM-N915A, I have had numerous issues. The phone lags/freezes often at best, but also crashes and reboots randomly. Worse yet, it has gotten into a boot loop a few times. I have factory reset and cache-wiped numerous times and even flashed a clean 5.1.1 via odin and still have the same issues. Apparently 5.0.1 or 4.4.4 cannot be flashed via Odin once 5.1.1 is installed and I can confirm this is true as I have tried.
Is anyone else having these issues? I have seen similar reports from the Note 4 forums but they seem to be getting new firmware updates to fix the issues. My firmware is N915AUCU2COI2 and is the latest available for the SM-N915A as far as I can determine.
Click to expand...
Click to collapse
Hi. Regards. also I have the same problem. Now 5.0.1 and 5.1.1, the phone note n915a edge is frizz me and every time I restarted. I'm going through the same thing you and if you've not been able to find solution that can share. thanks
mtayabkk said:
try to flash kernel find on xda.
Click to expand...
Click to collapse
Wouldn't that require ROOT access? The AT&T variant has a locked bootloader, so no root.
sagelwwa said:
Ever since updating to 5.1.1 via OTA update on my AT&T Galaxy Note Edge SM-N915A, I have had numerous issues. The phone lags/freezes often at best, but also crashes and reboots randomly. Worse yet, it has gotten into a boot loop a few times. I have factory reset and cache-wiped numerous times and even flashed a clean 5.1.1 via odin and still have the same issues. Apparently 5.0.1 or 4.4.4 cannot be flashed via Odin once 5.1.1 is installed and I can confirm this is true as I have tried.
Is anyone else having these issues? I have seen similar reports from the Note 4 forums but they seem to be getting new firmware updates to fix the issues. My firmware is N915AUCU2COI2 and is the latest available for the SM-N915A as far as I can determine.
Click to expand...
Click to collapse
I've been experiencing the same issues since 12/19/15. I too have the N915A... and it has worked just fine up until that day. I noticed while I was out xmas shopping that it was rebooting a number of times while i stood in line waiting to check out of the store. I did not want to be that guy in line pulling apart an electronic device so i waited until I got to the car. Pulled the battery, she was a hot mess, then once it was cool I re inserted and powered the phone back up only to find it to be really laggy, a number a apps were crashing on without me touching them, random reboots, need to pop the battery, SD, and SIM to restart the phone without it getting hungup on the boot routine.
I recently used ODIN to load 'stock" 5.1.1. firmware but no luck. Not entirely sure that its N915A firmware, found it from other threads on the forum. Before knowing we could not go back to previous version, I took a whack at going back to those as well. So far I've reset the phone probably 7 or 8 times with a fresh OTA firmware install and only installing a few apps like Facebook, RSA VPN client and Team Viewer to keep variables minimal.
Ever since xmas day i stopped trying and been trolling the web for support only to here that the N915A has no root yet and other unavailable mods thus far . I have not tried to do anything else yet from a programming standpoint. I put the phone into developer mode, toggled some settings for the CPU and GPU in there so that they ran independently.Setup to be notified when an app crashed in the background. Downloaded Nova Launcher to avoid TouchWiz as I've heard that can be buggy with 5.1.1. So far the phone has been working somewhat normal. No random restarts, however if I restart it myself i may need to remove the battery for a minute to get it going again. The battery seems to be draining faster than it should, least of my worries for now. If i just let the phone do its things without trying to be a few thoughts ahead of it, it seems to process just fine.
Oddly its improving, I'm not sure why. Also, not pleased with it either but its better than having a brick atm. Intend to keep trolling the webs for more solutions until a root is dev'd and nursing this thing until it either hits the bucket again or for some weird reason gets better on its own....
Lil Grim said:
I've been experiencing the same issues since 12/19/15. I too have the N915A... and it has worked just fine up until that day. I noticed while I was out xmas shopping that it was rebooting a number of times while i stood in line waiting to check out of the store. I did not want to be that guy in line pulling apart an electronic device so i waited until I got to the car. Pulled the battery, she was a hot mess, then once it was cool I re inserted and powered the phone back up only to find it to be really laggy, a number a apps were crashing on without me touching them, random reboots, need to pop the battery, SD, and SIM to restart the phone without it getting hungup on the boot routine.
I recently used ODIN to load 'stock" 5.1.1. firmware but no luck. Not entirely sure that its N915A firmware, found it from other threads on the forum. Before knowing we could not go back to previous version, I took a whack at going back to those as well. So far I've reset the phone probably 7 or 8 times with a fresh OTA firmware install and only installing a few apps like Facebook, RSA VPN client and Team Viewer to keep variables minimal.
Ever since xmas day i stopped trying and been trolling the web for support only to here that the N915A has no root yet and other unavailable mods thus far . I have not tried to do anything else yet from a programming standpoint. I put the phone into developer mode, toggled some settings for the CPU and GPU in there so that they ran independently.Setup to be notified when an app crashed in the background. Downloaded Nova Launcher to avoid TouchWiz as I've heard that can be buggy with 5.1.1. So far the phone has been working somewhat normal. No random restarts, however if I restart it myself i may need to remove the battery for a minute to get it going again. The battery seems to be draining faster than it should, least of my worries for now. If i just let the phone do its things without trying to be a few thoughts ahead of it, it seems to process just fine.
Oddly its improving, I'm not sure why. Also, not pleased with it either but its better than having a brick atm. Intend to keep trolling the webs for more solutions until a root is dev'd and nursing this thing until it either hits the bucket again or for some weird reason gets better on its own....
Click to expand...
Click to collapse
I've heard it's a problem of upgrading to lollipop. this model has errors. hopefully at & t throw a actulizacion soon to correct these improvements
ltindi32 said:
I've heard it's a problem of upgrading to lollipop. this model has errors. hopefully at & t throw a actulizacion soon to correct these improvements
Click to expand...
Click to collapse
So that's it then? Is there really no way whatsoever to go back to 5.0.1 or even 4.4.4 kitkat from 5.1.1? I've been trying to do it for a while now but I'm new to this Odin downgrading thing.
sagelwwa said:
Ever since updating to 5.1.1 via OTA update on my AT&T Galaxy Note Edge SM-N915A, I have had numerous issues. The phone lags/freezes often at best, but also crashes and reboots randomly. Worse yet, it has gotten into a boot loop a few times. I have factory reset and cache-wiped numerous times and even flashed a clean 5.1.1 via odin and still have the same issues. Apparently 5.0.1 or 4.4.4 cannot be flashed via Odin once 5.1.1 is installed and I can confirm this is true as I have tried.
Is anyone else having these issues? I have seen similar reports from the Note 4 forums but they seem to be getting new firmware updates to fix the issues. My firmware is N915AUCU2COI2 and is the latest available for the SM-N915A as far as I can determine.
Click to expand...
Click to collapse
I also have the AT&T Galaxy Note Edge SM-N915A. Ever since I updated via OVA this June 2016 it has been freezing/rebooting on its own/crashing apps. I have found 3 SM-N915A roms but cannot revert back to these previous builds. I have tried KEIS3 via Samsung to reflash firmware but it wont recognize my device name. After 2 weeks of crashing the phone is now a joke, when it once was king. It was such an awesome phone when it was released. Now I must lay it down to sleep. I guess I will get the Note 7 Edge which should be released this August.
I just wanted to express my frustration over ATT Branded Phone and will not be buying their branded phones anymore. I will be buying international versions or unlocked phones since ATT screwed me on this one.
harondaddy said:
I also have the AT&T Galaxy Note Edge SM-N915A. Ever since I updated via OVA this June 2016 it has been freezing/rebooting on its own/crashing apps. I have found 3 SM-N915A roms but cannot revert back to these previous builds. I have tried KEIS3 via Samsung to reflash firmware but it wont recognize my device name. After 2 weeks of crashing the phone is now a joke, when it once was king. It was such an awesome phone when it was released. Now I must lay it down to sleep. I guess I will get the Note 7 Edge which should be released this August.
I just wanted to express my frustration over ATT Branded Phone and will not be buying their branded phones anymore. I will be buying international versions or unlocked phones since ATT screwed me on this one.
Click to expand...
Click to collapse
I ended up being only days left in warranty and getting a replacement. Then a few months later I switched to T-Mobile and got the SM-N915T. So far so good and just OTA updated to Android 6.0. Only negative is T-Mobile's coverage in my area is poor, but WiFi calling, unlimited data (speed limited), and unlimited Binge On media streaming at full speed are great positives. T-Mobile Tuesdays is pretty cool too I must admit :good:
Same problem on SM-N915F even persisting after the new 6.0.1 update
Me too, my note edge N915G get restart constantly after ota update to 6.1 i try to flash with odin but always fail..
I've updated my (Canadian) Gear S2 Classic's OS a few times in the past without incident, but this time the update appears to have left it in a reboot loop. I get the power-on splash screen and a quick vibration every 4 seconds. I can interrupt it by holding down the power button, then tapping it when "Rebooting..." appears, but the only options in the reboot menu are Continue (no change), Download (stayed stuck there for a few hours, no change) or Power Off. There is no Recovery or Wireless Download option. I installed the new version of the Gear software on my Samsung Note 3 before starting, but it obviously won't connect now. Help!
Boot Loop after attempted 61Mb update
Same issue with mine. Yesterday I downloaded this 61Mb update, then I was opted to upload it onto my Gear S2. When the progress bar on my cellphone indicated that upload has finished I tapped the update icon and went to the kitchen to pour me some coffee. When I got back to the device I noticed the blinking boot screen. When the boot loop started annoying me and I figured out that the update eventually failed I long pressed the switch off button and realized that the reset option is missing. Only continue, download and shut down.
I took my Gear to service only to find out that they are devoid of the flashing device, whereas the available usb craddle is only for charging.
It's happened to me also
I have gear s2 Classic and after update it crashes like what other described ??
Has anyone found a fix for this? Just had to update my Gear S2 as well and same thing now, not booting or getting past the boot, holding power and trying different things, but not working. WTF????
Tekkie3 said:
I've updated my (Canadian) Gear S2 Classic's OS a few times in the past without incident, but this time the update appears to have left it in a reboot loop. I get the power-on splash screen and a quick vibration every 4 seconds. I can interrupt it by holding down the power button, then tapping it when "Rebooting..." appears, but the only options in the reboot menu are Continue (no change), Download (stayed stuck there for a few hours, no change) or Power Off. There is no Recovery or Wireless Download option. I installed the new version of the Gear software on my Samsung Note 3 before starting, but it obviously won't connect now. Help!
Click to expand...
Click to collapse
Today I face same problem as you, I got 61M update and after that it stock in boot loop. also in boot menu I only have 3 options that you mention and no recovery menu!!
please some one help
Same thing happened to me, i live in the UK but watch is US version and Samsung UK don't want anything to do with it.
Sixty8guns said:
Same thing happened to me, i live in the UK but watch is US version and Samsung UK don't want anything to do with it.
Click to expand...
Click to collapse
I am getting a deja vu. seems to be a samsung glitch. I upgraded my S2 as you guys did and it got stuck in a reboot loop. The same thing happened with my earlier smart wacth, the 'Gear Fit'. After some time a new firmware was distributed and solved the issue. I wonder how this can be performed on these watches because I only have a charge cradle. Is the download via wireless access? Time will tell.
[email protected] said:
I am getting a deja vu. seems to be a samsung glitch. I upgraded my S2 as you guys did and it got stuck in a reboot loop. The same thing happened with my earlier smart wacth, the 'Gear Fit'. After some time a new firmware was distributed and solved the issue. I wonder how this can be performed on these watches because I only have a charge cradle. Is the download via wireless access? Time will tell.
Click to expand...
Click to collapse
It updates wirelessly, through the gear app. I'm thinking that's where the problem is coming from
I'm in the UK and got the 61mb update today, it's downloaded to my s2 classic but I'm nervous of installing after what you guys have gone through.
has anyone successfully applied this update to their classic?
Sent from my SM-G935F using Tapatalk
took the plunge and update went OK...notifications wouldn't sync till I cleared cache in gear manager app on phone.
Sent from my SM-G935F using Tapatalk
What firmware version are you on now? I did a gear software check and it says I am all up to date with PC5
Update: Just wanted to share a quick update. I logged onto the Samsung app today and finally got the update. One interesting thing was that when I first checked it said what it has been saying, that I am up to date, but then I unchecked the 'automatically check for updates' box and manually checked for an update again. This time it showed there was an update available. Not sure if that box has anything to do with it or just a coincidence but maybe worth a shot to anyone else having the problem.
I have the same issue. I have the Bluetooth only version but don't have a Samsung phone. Would be nice to know why some are getting updates and others are not.
Has anyone found a solution to the bootloop problem yet.
New update bricked my device too. Exactly as the OP described.
Add me as another with a rebooting gear s2.
Exactly same issue as described by op
Anyone found a fix for this yet? Samsung support so far pathetic, have tried several branches, still one or two left to try...
Hi guys! I'm from Malaysia. Just updated to this package, 61MB. I'm on boot loop. Pressed Power button continuously, got to "rebooting...", but never to recovery options,.... It just keeps boot looping...
Any advice? Thanks!
Follow-up: I'm back from vacation and now have time to deal with this. I purchased the watch online through bestbuy.ca, but the retail stores want nothing to do with warranty repairs unless you purchased their in-house Geek Squad plan. I therefore had to go to the Samsung Canada support website, where I struck up a text chat with a representative and have arranged to send the watch to them for repair/replacement. On the upside, they sent me a prepaid FedEx shipping label, so at least that's free. I'll post more as it proceeds. An interesting footnote, as soon as I mentioned that this seems to be a known issue in discussion forums, I was immediately copy-and-pasted this boilerplate: "Samsung does not have control over information provided in third-party websites/ forums. We cannot assure the information provided in those websites is correct. The information posted on forums cannot always be validated, we observe that many similar described issues are posted as a unique issue, but when assessed the actual causes of these instances often differ. Content posted on third party web-sites are always subject to opinion."
Tekkie3 said:
Follow-up: I'm back from vacation and now have time to deal with this. I purchased the watch online through bestbuy.ca, but the retail stores want nothing to do with warranty repairs unless you purchased their in-house Geek Squad plan. I therefore had to go to the Samsung Canada support website, where I struck up a text chat with a representative and have arranged to send the watch to them for repair/replacement. On the upside, they sent me a prepaid FedEx shipping label, so at least that's free. I'll post more as it proceeds. An interesting footnote, as soon as I mentioned that this seems to be a known issue in discussion forums, I was immediately copy-and-pasted this boilerplate: "Samsung does not have control over information provided in third-party websites/ forums. We cannot assure the information provided in those websites is correct. The information posted on forums cannot always be validated, we observe that many similar described issues are posted as a unique issue, but when assessed the actual causes of these instances often differ. Content posted on third party web-sites are always subject to opinion."
Click to expand...
Click to collapse
I've had very good service from Samsung Canada. It's never taken more than a couple days at the shop. The original Galaxy S with failed update and Gear Fit which wouldn't charge after a month.
Sent from my SM-T710 using Tapatalk
My install consistently fails at 15%. Took it to service center, they flashed newest firmware on my phone and tried it again but again fails. Has anyone successfully installed this 61mb update?
I updated my Pixel 2 to Android P DP, and at first my Gear S2 sport would work normally, but eventually I noticed it was constantly in standalone mode. I decided to check the Gear app and BOOM, it broke. At that point I thought I just had to hard reset my watch, but that did not solve. Every time I try to pair the Gear app breaks, of if I go to the bluetooth menu and try to pair from there it says that it couldn't pair because of an incorrect pin or passkey.
Anyone is facing the same issue or have a solution for this?
Thanks.
Same issue
It's not any help, but I've also experienced the same problem with my Gear S2 and Pixel 2 XL. I was hoping that DP4 would fix this but it's obviously the Samsung Gear app that's the issue. Samsung hasn't updated the app since November, 2017.
charleswlee said:
It's not any help, but I've also experienced the same problem with my Gear S2 and Pixel 2 XL. I was hoping that DP4 would fix this but it's obviously the Samsung Gear app that's the issue. Samsung hasn't updated the app since November, 2017.
Click to expand...
Click to collapse
Umm I get updates for the gear app all the time pretty sure I do at least
I just checked, the app itself was last updated forever ago, but the Gear S Plugin(which I believe is the one that matters) was updated in May this year. Hopefully after Android P is released they'll fix it. But this type of situation makes me want to avoid Samsung products.