Sleep Tracking is weird - Samsung Gear S3

Hi all,
I came from Gear Fit2 to Gear S3. The watch is great but the sleep tracking is weird. My Gear Fit2 used to measure almost accurate where Gear S3 is tracking as bits and pieces. I am using S3 from 22 Nov 2016 and I can see lots of break between sleep where I never wake. The gaps are like 30min to 60 mins.
Gear S3 sleep tracking today.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is the trend of sleep tracking where the solid lines are when I was using my Gear Fit2
Anyone facing similar problem or know any solution, please feel free to comment.
Thanks

Weird, doesn't happen for me. Mine tracks my whole sleep perfectly.

the_scotsman said:
Weird, doesn't happen for me. Mine tracks my whole sleep perfectly.
Click to expand...
Click to collapse
OK. Let me monitor for couple of days and going to call the support if its still a problem.

Wonder if your band is too loose.

kronium said:
Wonder if your band is too loose.
Click to expand...
Click to collapse
As far I know, it is tight enough. I will try one more loop tighter and see today. I have no problem when I was running with it.
Sent from my SGP521 using XDA-Developers mobile app

Same here. I switched from a BT only to an LTE and both watches had the same issue.

HAC5 said:
Same here. I switched from a BT only to an LTE and both watches had the same issue.
Click to expand...
Click to collapse
May be the rising bezel got rotated while we are sleeping. But the interesting thing is, it happens almost same time everyday. I think Samsung needs to fix this by software.
Sent from my SGP521 using XDA-Developers mobile app

kronium said:
Wonder if your band is too loose.
Click to expand...
Click to collapse
Worn it tighter than usual, but still same issue.
Sent from my SGP521 using XDA-Developers mobile app

So when you call it a night and wear the watch, it automatically knows your asleep??? Coming from the original Gear S you would select "Sleep" then it would go into do not disturb mode.

Premier 1k Flyer said:
So when you call it a night and wear the watch, it automatically knows your asleep??? Coming from the original Gear S you would select "Sleep" then it would go into do not disturb mode.
Click to expand...
Click to collapse
S2, Gear Fit2 and S3 - all tracks the sleep automatically. There is no way you can set to sleep mode.

Gotcha.. I'll give it a shot tonight. ?

I've noticed the same thing on my S3. Had it since the 20th and only one night has not been broken up. I also haven't found a way to edit the times to combine them.

jturner02 said:
I've noticed the same thing on my S3. Had it since the 20th and only one night has not been broken up. I also haven't found a way to edit the times to combine them.
Click to expand...
Click to collapse
We shouldn't be editing the sleep data.
Interesting part is, it shows the broken part as Light activity and it's even comes some steps everyday.
Sent from my SGP521 using XDA-Developers mobile app

I've noticed the same problem. The S3 only captures part of my sleep and sends that portion to S-Health. My Fit2 captures the entire night.

I am having the same issue as well. Hopefully this is a software issue that Samsung can fix.

ttown said:
I am having the same issue as well. Hopefully this is a software issue that Samsung can fix.
Click to expand...
Click to collapse
I have chat with the support Australia, the gave a standard suggestions like reset the device, reinstall Gear Manager and pair it again. I will check with them tomorrow and I have to test the sleeping pattern. I told them, I did all they suggested but didn't do any as you all know, it just waste of time and I don't want to lose my data history.

I haven't had it track mine odd at all... I noticed the notification and looked through it, it looks broken up with light activity in a few areas as expected and the times appear to be accurate. I'm using the T-Mobile Gear S3.

I have my gear s3 taken off from wrist and put on table before I go sleep and it does track my sleep for 2 hours, isn't it crazy?

My problem is somehow fixed. I don't which one fixed the issue. I was using Samsung's red band which came free with my frontier. The holes are different than the stock black band. I put the black back. And also I had horrible battery life. So, I rebooted the watch also. From that day, my sleep activity is solid and perfect as usual. I am wearing the band pretty tight, where I got bruised
Sent from my SGP521 using XDA-Developers mobile app

I am having a very similar issue. I always wear my Gear S3 now after switching from Fitbit. Fitbit tracked my sleep almost to the minute, whereas this new and "improved" watch tracks about an hour and a half of my 8 hour sleep. I wish there was a fix for this as I am not accurately measuring how much I am sleeping at night, which is one of the main reasons I wear a smart watch to bed...

Related

Heating & charge loosing problem

Hello everyone.
Since last Friday, 26 February, the phone heats up even when surfing the Internet. charge loss is 25-30% per hour. Problems appear only on Friday. All was well for two months of using.
Has anyone experienced this problems?
Z5 Dual E6683
Battery usage
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Kellis said:
Battery usage
View attachment 3664383View attachment 3664384View attachment 3664385
Click to expand...
Click to collapse
i can say that my z5 is also overheating alot even if i just install some apps or just browsing on net...if i run a game after 5 or 10 mins it starts to lag (every game) i wonder how it will it work on hot summer days LOL it looks like im turning back the phone.
Kellis said:
Battery usage
View attachment 3664383View attachment 3664384View attachment 3664385
Click to expand...
Click to collapse
I have this exact same problem, I'm wondering whether it's a software issue
I have same problem too. Any fix?
egemaster said:
I have same problem too. Any fix?
Click to expand...
Click to collapse
I'm hoping it's just a software bug, since multiple users have this issue, it just randomly started right? Also can you connect it to a PC?
a00r said:
I'm hoping it's just a software bug, since multiple users have this issue, it just randomly started right? Also can you connect it to a PC?
Click to expand...
Click to collapse
i can connect it pc.
My z5 usable only 10 hours n its temp like hell. Im using it when its inside fridge.
egemaster said:
I have same problem too. Any fix?
Click to expand...
Click to collapse
a00r said:
I'm hoping it's just a software bug, since multiple users have this issue, it just randomly started right? Also can you connect it to a PC?
Click to expand...
Click to collapse
I turned off the GPS sensor. Phone has become heated less, but still heats up stronger than two weeks ago.
Phone discharges still a bit fast.
​
I have exactly the same problem for last 2-3 weeks.
Tried flash roms for different regions, and all the same.
Phone battery lasts for about 10 hours.
Hope that will be sorted out by Sony soon, because phone is not for daily use like that!
toncheee said:
I have exactly the same problem for last 2-3 weeks.
Tried flash roms for different regions, and all the same.
Phone battery lasts for about 10 hours.
Hope that will be sorted out by Sony soon, because phone is not for daily use like that!
Click to expand...
Click to collapse
yes, it seems other people are having this problem as well, so after 3-4 months the sony xperia z5 battery dies for some people hmm, anyways I am in the process of getting it RMA or repaired by sony, but contacted the seller, waiting on their response
I have the same issue, it started after two programs installed, com.facebook.appmanager and com.facebook.system. I don't have a facebook account and I removed the facebook app but these apps are nonremovable, I disabled them in app manager but the battery drain and heat is still there. I don't know if it's related.
Factory reset isnt helps too
Unfortunatelly nothing helps. I sent mine to local Sony service. Will report back what they did.
Kellis said:
Factory reset isnt helps too
Click to expand...
Click to collapse
I was wrong. reset to factory settings has helped me . after that I had not been updated through playmarket or sony update.

New phone. But it keeps crashing?

Hi all,
So I got a Samsung galaxy s7 from o2 yesterday. It's less than 24 hours old, and it seems to run quite hot!
Sometimes it'll be next to me, I'll pick it up, send a few texts and browse the internet and I can feel warmth/heat coming from just near to the camera.
It's also frozen on three occasions where I've been on chrome. The screen and all buttons become completely unresponsive, and even holding the power button down doesn't do anything, for a while at least.
I've read on Google factory resetting can help, but surely that shouldn't apply considering this was fresh as of yesterday? I'm pretty sure my phone shouldn't be crashing and being unresponsive so quickly into its life.
Question is, is this a fault? Or software?
It can sometimes, I would recommend resetting it, giving it some time and if needed taking it back for replacement
sstanton86 said:
Hi all,
So I got a Samsung galaxy s7 from o2 yesterday. It's less than 24 hours old, and it seems to run quite hot!
Sometimes it'll be next to me, I'll pick it up, send a few texts and browse the internet and I can feel warmth/heat coming from just near to the camera.
It's also frozen on three occasions where I've been on chrome. The screen and all buttons become completely unresponsive, and even holding the power button down doesn't do anything, for a while at least.
I've read on Google factory resetting can help, but surely that shouldn't apply considering this was fresh as of yesterday? I'm pretty sure my phone shouldn't be crashing and being unresponsive so quickly into its life.
Question is, is this a fault? Or software?
Click to expand...
Click to collapse
Hi. I went through the same issue a few weeks back. Mine was a unlocked uk model brand new.
I did everything from factory resetting, to installing firmware from scratch and nothing helped.
Ultimately for me I believe it was a hardware issue and ended up returning for a full refund.
Also for me I was getting a lot of random reboots.
My model was manufactured in march.
Used the phone info app on Google play to check.
Could you check to see when yours was made.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Phone : Samsung s7 G930F
Android: MM 6.0.1
hyperthrust said:
Hi. I went through the same issue a few weeks back. Mine was a unlocked uk model brand new.
I did everything from factory resetting, to installing firmware from scratch and nothing helped.
Ultimately for me I believe it was a hardware issue and ended up returning for a full refund.
Also for me I was getting a lot of random reboots.
My model was manufactured in march.
Used the phone info app on Google play to check.
Could you check to see when yours was made. View attachment 3851130
Phone : Samsung s7 G930F
Android: MM 6.0.1
Click to expand...
Click to collapse
Hi mate thanks for replying.
Mine was made in April according to that app.
I think I fixed the issue, and it was to do with 'Mediaserver' being the number one thing using my battery up. So I reset the phone, cleared the cache etc and it seems to work fine now with no crashes. It's a shame because the average user would just buy the phone and not even think about doing what I did.
My phone still gets warm though. Did you find that? And if applicable does your new s7 gets warm too?
sstanton86 said:
Hi mate thanks for replying.
Mine was made in April according to that app.
I think I fixed the issue, and it was to do with 'Mediaserver' being the number one thing using my battery up. So I reset the phone, cleared the cache etc and it seems to work fine now with no crashes. It's a shame because the average user would just buy the phone and not even think about doing what I did.
My phone still gets warm though. Did you find that? And if applicable does your new s7 gets warm too?
Click to expand...
Click to collapse
Mine gets warm too, so I downloaded GSam to monitor the temperature. After monitoring the temperature for a while I realized that my nexus 5 runs hotter but I don't notice it cause it's made out of plastic instead of metal/glass.
hyperthrust said:
Hi. I went through the same issue a few weeks back. Mine was a unlocked uk model brand new.
I did everything from factory resetting, to installing firmware from scratch and nothing helped.
Ultimately for me I believe it was a hardware issue and ended up returning for a full refund.
Also for me I was getting a lot of random reboots.
My model was manufactured in march.
Used the phone info app on Google play to check.
Could you check to see when yours was made. View attachment 3851130
Phone : Samsung s7 G930F
Android: MM 6.0.1
Click to expand...
Click to collapse
Yours is rooted? Why is Knox flipped?
Yes, it is or was. I was having the problems before rooting and after rooting.
Made no difference at all.
Mine was just defective. No software updates made a difference.
Phone : Samsung s7 G930F
Android: MM 6.0.1
I went into o2 store earlier today explained the problem, and because i was in my 14 day period i got it replaced no questions asked. So far even though this phone was manufactured a month prior to the one i returned (March), it seems fine and was only warm downloading the latest updates. Hopefully im on to a winner here!
Hey,
I have the same problem!
I have tried many things but not rooted my phone or did any modificiation.
I found out that I got these problems because of my Spotify App and I am sure the actual version of Spotify causes a big problem deep in the system of the S7.
Have you an idea how I could prove that?
I removed my Spotify App for 2 weeks and had not even one problem. Since I reinstalled Spotify, I get all those issues again
sstanton86 said:
I went into o2 store earlier today explained the problem, and because i was in my 14 day period i got it replaced no questions asked. So far even though this phone was manufactured a month prior to the one i returned (March), it seems fine and was only warm downloading the latest updates. Hopefully im on to a winner here!
Click to expand...
Click to collapse
So the new one doesn't get slightly warm after browsing for more than 20 minutes?
Are you using a case?
Travis Bickle said:
So the new one doesn't get slightly warm after browsing for more than 20 minutes?
Are you using a case?
Click to expand...
Click to collapse
Slightly warm. Was during downloads etc but not anything abnormal or to worry about. The other handset was clearly faulty.
No case either for now.

Share your uptime records!

How stable is your Moto X Pure Edition? What's the greatest length of time that you've kept your device going without restarting or running the battery to shutdown?
Share your best records and the story behind them!
I just reached mine last night (see attached picture). That equals out to just over 35 days. The reason for the eventual reboot was because I triggered some kind of weird glitch that made everything on the screen go all washed-out. No matter what I did, nothing short of rebooting the device would make it go away, so I had to give up my streak.
This would be a good thread. Mine usually runs fine till 6-7 days then I could notice stuttering or frame drops which gets solved with a reboot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I basically never reboot my moto, timer resets only when my battery reaches 0% which is rare ocasion.
iks8 said:
I basically never reboot my moto, timer resets only when my battery reaches 0% which is rare ocasion.
Click to expand...
Click to collapse
You definitely rarely reboot.
I have never tried to see how long I could let it go. I reboot once a week just to avoid issues.
Any other records? Why do people reboot their MXPE?
It looks like that 75 day figure is the record so far.
aybarrap1 said:
You definitely rarely reboot.
I have never tried to see how long I could let it go. I reboot once a week just to avoid issues.
Click to expand...
Click to collapse
Interesting. What kind of issues do you try to avoid? I'd also be curious to know the main reasons why people reboot. Whether it's the screen glitch, a catastrophic software malfunction, the installation of an Xposed Framework module, or even just because the battery ran down, I would love to hear what "broke" your records as well.
I reboot as many apps get buggy the longer they are up.
Bill720 said:
It looks like that 75 day figure is the record so far.
Interesting. What kind of issues do you try to avoid? I'd also be curious to know the main reasons why people reboot. Whether it's the screen glitch, a catastrophic software malfunction, the installation of an Xposed Framework module, or even just because the battery ran down, I would love to hear what "broke" your records as well.
Click to expand...
Click to collapse
I'm just trying to avoid issues in general. I've been doing this from before my Pure days. I've had a few instances of problems with network connectivity after 3 to 5 days off usage on this device with the only way to fix it is by rebooting. This just reinforced my weekly habit.
I hope that the uptime improves for you
aybarrap1 said:
I'm just trying to avoid issues in general. I've been doing this from before my Pure days. I've had a few instances of problems with network connectivity after 3 to 5 days off usage on this device with the only way to fix it is by rebooting. This just reinforced my weekly habit.
Click to expand...
Click to collapse
I used to have to reboot rather frequently with the Galaxy Note 2 as well. For some reason, the auto-rotation system would completely stop working within 2-4 days of having used the dialer app. It was weird because, when this happened, the tilt sensor would behave weirdly in applications that made use of it and auto-rotation would only work in the dialer (and a couple of other apps). Even stranger was the fact that it would magically start working again as soon as "auto brightness" was enabled (but fail as soon as this feature was turned back off). It was a known issue with that particular rom, but went on to ultimately never be solved. If it wasn't for that one pesky problem, I could've probably hit a month (or more) of uptime on that phone too.
At any rate, I hope you get the network connectivity issue resolved. You might've seen the long thread on the issue that I posted a few months back, and I never did get to the bottom of it. Hard reset was the only cure. Thankfully, the bug hasn't come back, even though my setup is pretty much the same as it was before.
Endurance record!
Hit another high score! Only reason I shut it down was to replace the battery. Works out to a little more than 50 days.
People have been really *****y about the delayed software release, but I'm glad that they took their time and allowed us to not only achieve this kind of stability, but also multi-window and night mode. The Moto X Pure Edition truly is the ideal smartphone. :good:
Bill720 said:
How stable is your Moto X Pure Edition? What's the greatest length of time that you've kept your device going without restarting or running the battery to shutdown?
Share your best records and the story behind them!
I just reached mine last night (see attached picture). That equals out to just over 35 days. The reason for the eventual reboot was because I triggered some kind of weird glitch that made everything on the screen go all washed-out. No matter what I did, nothing short of rebooting the device would make it go away, so I had to give up my streak.
Click to expand...
Click to collapse
My X Pure has that same weird visual glitch every once and a while also. Not sure what it is.
parker.stephens said:
My X Pure has that same weird visual glitch every once and a while also. Not sure what it is.
Click to expand...
Click to collapse
This is common bug, my moto x style also has it from time to time
Unusual, but sometimes repeatable
parker.stephens said:
My X Pure has that same weird visual glitch every once and a while also. Not sure what it is.
Click to expand...
Click to collapse
iks8 said:
This is common bug, my moto x style also has it from time to time
Click to expand...
Click to collapse
Yeah, it's definitely difficult to pin down. I've only seen it 2-3 times in almost a year and a half of ownership, so it's hardly a serious enough issue to raise a fuss about.
My new record. Unfortunately I had to reboot because my localization services stopped working ;\
excellent uptime
iks8 said:
View attachment 4552105
My new record. Unfortunately I had to reboot because my localization services stopped working ;\
Click to expand...
Click to collapse
Solid run! That's somewhere short of 3 months, which is very impressive, especially when you consider that some people don't even keep their phones that long .
Good share.
Bill720 said:
Solid run! That's somewhere short of 3 months, which is very impressive, especially when you consider that some people don't even keep their phones that long .
Good share.
Click to expand...
Click to collapse
when I rebooted I realised that I forgot my pin code and I've locked my sim card XD I'm not recommending such a long runs if you have short memory xd. Btw phone was running perfectly fine without any slowdows.

Battery overheat while charging since Tizen 3.0.0.1

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I saw some reports on Facebook, people are experiencing "overheating" while charging, and then it stops charging while it's not fully charged yet!
I'd the same experience, just after updating my Gear S3 Frontier to Tizen 3.0.0.1: I saw the LED on my charging-dock "Orange blinking", and my device was around 80%!
My watch was also extremely hot on the back...
More people experience this, since the latest update?
I was just thinking that my watch was charging hotter.
It also overheated the other night
Edit: just did it again. It was in power saving mode on charger
Turn the watch off and then try to charge it.
Sent from my MHA-L29 using XDA Labs
similar issue on mine, no idea how to fix
If this happens more then 1 time...
Maybe for tests usefull:
Factory Reset...
Then start WITHOUT init via Samsung Gear/Phone...
By this Trick:
https://www.youtube.com/watch?v=2bVpAItyzWE
Maybe this is Software failure... or really Hardware problem like dead Battery or Charger or...
Maybe wrong measurement...
Example.
Look at this Picture in this post:
https://forum.xda-developers.com/showpost.php?p=74599116&postcount=19
First I thought this is only my half dead damaged SM-R760...
But I saw something like this also on other Videos/Pictures...
I know my CPU is not 40000 C hot...
Funny, because Samsung seems to know such phenomen... Because they removed temp check in CQK3 Download wireless...
Only as info.
Best Regards
henklbr said:
I saw some reports on Facebook, people are experiencing "overheating" while charging, and then it stops charging while it's not fully charged yet!...
Click to expand...
Click to collapse
Yip...same here...device was working fine and charging just fine on 2.3.2.4 Tizen version but 2 days into the Tizen 3.0 and suddenly I'm having the exact same issue...Am trying all sorts of fixes at the moment but none seems to be working just yet...
Same Issue at 46%
henklbr said:
I saw some reports on Facebook, people are experiencing "overheating" while charging, and then it stops charging while it's not fully charged yet!
I'd the same experience, just after updating my Gear S3 Frontier to Tizen 3.0.0.1: I saw the LED on my charging-dock "Orange blinking", and my device was around 80%!
My watch was also extremely hot on the back...
More people experience this, since the latest update?
Click to expand...
Click to collapse
I'm experiencing the same issue. Hope they fix it soon.
dianawallface said:
I'm experiencing the same issue. Hope they fix it soon.
Click to expand...
Click to collapse
Guys just downgrade till they fix this with another update...
Early days but have just factory reset and no warmth whatsoever in my Gear S3
just stared getting this issue today, installed Tizen 3 weeks ago, i'm using after market charger at work though, what about everyone else?
My gear S3 is dead becoz of this. Always overheated since day 1 updated to Tizen 3 & my gear S3 is running hot. I think this is why it's dead. Damn Samsung. People fixed things but you broke things.
Now have to send back to service center for warranty claims.
Us classic on latest tizen 3. I got a pair of aftermarket chargers from Amazon and they overheated the watch (already on 3). I paid up for a factory charger and all is good. Honestly, I never searched to see if it was a software issue.
Found this:
https://us.community.samsung.com/t5...ing-charge-after-Tizen-3-0/td-p/223727/page/5
But seems also in older Firmware happened:
https://forum.xda-developers.com/gear-s3/help/gear-s3-constantly-overheating-t3535057
Something like this could be really deadly for PCB/PBA... :crying:
I bought such "final result" second hand... :crying:
After Battery replacement also no life sign... not powers on anymore...
So I can not repair my SM-R770...
IMHO pre owner used Original Charger and no Tizen 3... but something "burned"/damaged... Hardware...
I saw few days ago Ebay offer... from SM-R760...
Seller told about battery replacement without luck...
So I think something similar happened...
Other hint:
https://www.iotgadgets.com/2017/02/...rs-with-your-gear-s3-it-could-fry-your-watch/
It seems not only wrong Charger could create problem...
It seems also with Original equipment... S3 with S3 Charger... possible...
Best Regards
Mine is doing this now too after the tizen 3 update. Original charger too. Good job Sammy!
Mine did the same thing. Never happen before. I just turned the watch off and let it go. Now I have to say this only happen once. I know leave the watch on.. nothing happens.
Hmmm...
Seems nearly all Versions affected...
LTE also...
https://us.community.samsung.com/t5...board-id/wearabletech/thread-id/18270/page/12
I would use for instance SDB Tool... and Log files... if possible.
In theory also other ways possible with Filemanger to copy Log from Gear S3...
Code for Log...
Code:
*#9900#
Code:
Run LOG_DUMP
Maybe more infos possible if Debug Mode setting ON...
Best Regards
I've got the Gear S3 frontier from T-Mobile and I'm having a similar problem with mine after time on the charger the base starts flashing red.. No idea if anything pops up on the screen or not I'm normally not in the room or I'm sleep when it's on the charger.
This started after the tizen 3.0 update.. I contacted Samsung now they want me to send in my watch and be without it for almost 2 weeks. This is crazy to say the least.
1.
Since weeks nobody share CQL1 Firmware fir ODIN... so we could compare CQK3 and CQL1...
I mean SM-R760 or SM-R770...
2.
Because in my experiments... I have now LDU Firmware on my SM-R760...
I can not charge to 100% ...
But I remember this is normal... as Live Demo Units in Store not charge fully...
I am using only part of Firmware... rootfs.img
For fully 100 % charge... I am using Download Wireless Mode...
Maybe if somebody would/could upload CQL1 Firmware for study...
Maybe we could identify where Samsung do funny changes in rootfs.img...
I will upload filelist... form FOTA package... CQK3toCQL1...
Here are also tiny changes to Kernel visible..
Best Regards
My interim solution for Samsung Gear S3 Overheating
Hi,
I had the same overheating issue too.
But I am using an interim solution personally to get my Gear S3 Frontier to full charge.
When I want to charge my Gear S3 Frontier, I turned my Gear S3 to airplane mode.
In 3 occassions, I can get to 100% charge without getting the overheating notification.
However, in one occassion, when it gets to 100%, the overheating notification does pop up.
Note: I am still observing this method. Would be glad to hear from you if this method works, assuming you choose to use this.
My explanation:
If you are charging your Gear S3 while you are moving around, your Gear S3 is continuously scanning for your phone, and also receiving signal via GPS, Bluetooth & WiFi. So it is still doing a lot of work in the background.
Why airplane mode:
Turns off all tranceiving & receiving of signals. Minimize the stress to the Gear S3.
Logically, when you are charging your Gear S3, you will not be using it, right? So, no harm turning to Airplane mode temporarily. A bit troublesome, but for me, it solves the problem of not getting to 100% charge.
On the other hand, I do believe the overheating notification serves as a signal to the Gear S3, to stop the charging process due to whatever reasons. It might be a safety feature.
Just my personal opinion.
Thanks.
From, Ronald
alexhee said:
My gear S3 is dead becoz of this. Always overheated since day 1 updated to Tizen 3 & my gear S3 is running hot. I think this is why it's dead. Damn Samsung. People fixed things but you broke things.
Now have to send back to service center for warranty claims.
Click to expand...
Click to collapse
Just sent my back 2 weeks ago and got it back within a week's time. No longer overheating and batter life is much better than before. It's been 5 days since I got the watch back. It's been 12hours with 70% battery life after off the charger since 4am.

Question Camera Error/Failed

Hello!
Anyone else having this kind of problem? Here is an intermittent error, sometimes it appears when trying to take a picture, sometimes when recording. I've done everything on the internet to solve this problem, but nothing solves. Apparently it resolves for a while but ends up coming back.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try clearing system cache.
Clearing cam data.
Disable global power management... destroyer of worlds.
May be a 3rd party app causing this.
When it happens immediately go to Device Care>memory and see what apps just loaded on the top of the list of cache apps. Many times this can lead you to the culprit.
if you haven't yet, reproduce the issue then submit error report to samsung members app > get help > error report.
also, I suggest you try booting to SafeMode and see if the issue reproduces. You noted that it was somewhat random, but give it a few tries and see if it reproduces. If it doesn't the there is a chance that it's caused by 3rd party app.
Lastly, could you share the phone's model number, software version running, and the camera app's version
I am experiencing the same exact issue. It's not consistent which is really annoying. Hard reset helped a little bit. Cleared data and cache and that didn't help. Factory reset didn't help me either. SM-S908U SP1A.210812.016.S908USQU1AVC8 Camera version 12.0.01.50
b00st4ddicted said:
I am experiencing the same exact issue. It's not consistent which is really annoying. Hard reset helped a little bit. Cleared data and cache and that didn't help. Factory reset didn't help me either. SM-S908U SP1A.210812.016.S908USQU1AVC8 Camera version 12.0.01.50
Click to expand...
Click to collapse
Return it if you can. It could be a hardware issue.
Eramix3 said:
Hello!
Anyone else having this kind of problem? Here is an intermittent error, sometimes it appears when trying to take a picture, sometimes when recording. I've done everything on the internet to solve this problem, but nothing solves. Apparently it resolves for a while but ends up coming back.
Click to expand...
Click to collapse
I actually had this issue about 2 weeks ago on my Verizon S22 Ultra. About 2 weeks ago in the morning, I grabbed my phone to take some pics. I had been walking with it in my pocket for a bit. When I pulled it out, I noticed my phone was a bit hot, I tried taking a few photos of something and I was in direct sunlight and that error popped up. I closed the app, tried again and got the same pop up, I was holding the phone in landscape mode as well when this kept happening in direct sunlight that was behind me.
A few hours later I was taking pics and it worked fine and has been taking pics ever since without issue. Not sure why it happened but it hasn't happened since the 2 times it popped up about 2 weeks ago.
Justinphxaz said:
I actually had this issue about 2 weeks ago on my Verizon S22 Ultra. About 2 weeks ago in the morning, I grabbed my phone to take some pics. I had been walking with it in my pocket for a bit. When I pulled it out, I noticed my phone was a bit hot, I tried taking a few photos of something and I was in direct sunlight and that error popped up. I closed the app, tried again and got the same pop up, I was holding the phone in landscape mode as well when this kept happening in direct sunlight that was behind me.
A few hours later I was taking pics and it worked fine and has been taking pics ever since without issue. Not sure why it happened but it hasn't happened since the 2 times it popped up about 2 weeks ago.
Click to expand...
Click to collapse
Exactly same issue here
b00st4ddicted said:
I am experiencing the same exact issue. It's not consistent which is really annoying. Hard reset helped a little bit. Cleared data and cache and that didn't help. Factory reset didn't help me either. SM-S908U SP1A.210812.016.S908USQU1AVC8 Camera version 12.0.01.50
Click to expand...
Click to collapse
you are fully updated and even the app is up to date... hence it implies that it's not really a software issue... or even if it is, it's specific to your device or handful of people.
I would assume hardware issue and visit authorized repair center (you can also report the issue to samsung just to cover all grounds and receive confirmation that it's not a software issue).
I have a US Snapdragon 512GB version and been having the same issue since 2 months. It's very annoying. I had few software updates in this period and hoped that it would fix it but no luck.
I don't know if it's a hardware of software issue at this point. I took it to couple of service centers they don't have the parts in stock to replace camera module
It does sound like it is a hardware problem. You may have to either do a warranty replacement, or send it to Samsung for repairs.
In either case, it won't be an immediate fix.
krishkanth787 said:
I have a US Snapdragon 512GB version and been having the same issue since 2 months. It's very annoying. I had few software updates in this period and hoped that it would fix it but no luck.
I don't know if it's a hardware of software issue at this point. I took it to couple of service centers they don't have the parts in stock to replace camera module
Click to expand...
Click to collapse
oh snap~ repair centers are running out of parts now???? could it be the supply shortage hitting the repair businesses too

Categories

Resources