Related
Very similar to comments here, I am having seemingly random crashes on my beloved E980. It was running perfectly fine for many months on CM10.2 + TWRP. The crashes started happening fairly soon after replacing the screen (about same time I flashed to CM11 as well). Two days ago, I used the Hyelton/Madmack .tot method and [successfully] installed two different stock firmware versions with the same results [after maybe a couple hours it will intermittently start crashing again]. I can't seem to ascertain if there are things that provoke it to crash. Sometimes it'll do it after sitting with screen off for some time, but more often it'll happen while under medium to high utilization. There is plenty of free RAM and Flash memory.
Before buying a parts phone from eBay with a broken screen and throwing parts at it I thought I’d first take it apart and see if anything jumps out at me and cross my fingers that it would just work after reassembly; I haven’t done this yet – maybe tonight. I think I've verified that it is a hardware issue at this point, but I was hoping to narrow it down a bit closer – there doesn't seem to be an abundant supply of eBay parts phones right now and I hate guess and buy an unneeded sub-component.
I also thought I’d go ahead and try to capture some log files utilizing methods found here which I have done. Attached is a Logcat file which ran until the phone crashed. I was unable to export a Dmesg log; whether in adb or terminal emulator I get “klogctl: Operation not permitted”. I tried to get a Last_kmsg log but the file is missing after rebooting from crash. I did get exports from error-free reboots before and after the crash which I’ve also attached. I browsed to /cat/proc and sure enough there was no “last_kmsg” subfolder. The phone was sitting with screen off on my desktop for maybe an hour when I heard the USB chime that it disconnected.
Has anyone got some ideas for me to try?
jimmylomax said:
Very similar to comments here, I am having seemingly random crashes on my beloved E980. It was running perfectly fine for many months on CM10.2 + TWRP. The crashes started happening fairly soon after replacing the screen (about same time I flashed to CM11 as well). Two days ago, I used the Hyelton/Madmack .tot method and installed two different stock firmware versions with the same results. I can't seem to ascertain if there are things that provoke it to crash. Sometimes it'll do it after sitting with screen off for some time, but more often it'll happen while under medium to high utilization. There is plenty of free RAM and Flash memory.
Before buying a parts phone from eBay with a broken screen and throwing parts at it I thought I’d first take it apart and see if anything jumps out at me and cross my fingers that it would just work after reassembly; I haven’t done this yet – maybe tonight. I think I've verified that it is a hardware issue at this point, but I was hoping to narrow it down a bit closer – there doesn't seem to be an abundant supply of eBay parts phones right now and I hate guess and buy an unneeded sub-component.
I also thought I’d go ahead and try to capture some log files utilizing methods found here which I have done. Attached is a Logcat file which ran until the phone crashed. I was unable to export a Dmesg log; whether in adb or terminal emulator I get “klogctl: Operation not permitted”. I tried to get a Last_kmsg log but the file is missing after rebooting from crash. I did get exports from error-free reboots before and after the crash which I’ve also attached. I browsed to /cat/proc and sure enough there was no “last_kmsg” subfolder. The phone was sitting with screen off on my desktop for maybe an hour when I heard the USB chime that it disconnected.
Has anyone got some ideas for me to try?
Click to expand...
Click to collapse
so you're saying that when you use hyelton method 2 and flash 20g that it fails while running 20g? try a different usb cable, too. EDIT - also different usb port. also watch for static electricity - I ground myself before touching cpomputer...
KrisM22 said:
so you're saying that when you use hyelton method 2 and flash 20g that it fails while running 20g? try a different usb cable, too. EDIT - also different usb port. also watch for static electricity - I ground myself before touching cpomputer...
Click to expand...
Click to collapse
No, sorry, I maybe glossed over that part. I successfully flashed to the stock firmware just fine. The phone ran well the remainder of the day.
I then rooted it, installed Titanium Backup, and then installed TWRP. I made a couple TWRP backups as I slowly started reinstalling apps with TB and Play store. Similar to the 4 or 5 times I tried re-flashing cyanogenmod, it seems to get worse and worse over time. In the past flashes I have experimented with not using TB and leaving it alone for a day or two with the same result. Since I have TWRP and many backups, I can definitely experiment further trying things.
jimmylomax said:
No, sorry, I maybe glossed over that part. I successfully flashed to the stock firmware just fine. The phone ran well the remainder of the day.
I then rooted it, installed Titanium Backup, and then installed TWRP. I made a couple TWRP backups as I slowly started reinstalling apps with TB and Play store. Similar to the 4 or 5 times I tried re-flashing cyanogenmod, it seems to get worse and worse over time. In the past flashes I have experimented with not using TB and leaving it alone for a day or two with the same result. Since I have TWRP and many backups, I can definitely experiment further trying things.
Click to expand...
Click to collapse
try process w/o twrp, please.
---------- Post added at 02:32 PM ---------- Previous post was at 02:25 PM ----------
also different cable and different usb port.
this is a bummer, man.
KrisM22 said:
try process w/o twrp, please.
---------- Post added at 02:32 PM ---------- Previous post was at 02:25 PM ----------
also different cable and different usb port.
Click to expand...
Click to collapse
Right - I was thinking the same thing. So, early this afternoon I did reflash (with "BIN_LGE980AT-00-V20g-ATT-US-APR-28-2014+0.tot") one more time and did only the following:
Skipped wifi setup, disabled "back up [and restore] data from google account". Rebooted
Went straight to app store and disabled auto download/update
Received notification that Google Play Services needed updating or something - I clicked the notification in order to read entire message and I think it just updated it?
set Hangouts as default messenger. Rebooted once again.
Then, I just tried to heavily use it. I used Maps navigation, took a bunch of rapid fire photos, Gmail, Chrome, etc. It worked great for about 3 hours until I got my first crash while taking some photos and attaching to a few rapid-fire hangouts messages. I removed the external flash card, but left SIM card and rebooted. It crashed one or two more times in the next 5 minutes. Since then it has crashed while using it maybe twice and once or twice while it should have been sleeping.
Any use in trying to capture event logs or should I just go ahead and dig out my phillips 00 screwdriver and tear into it?
I did use a different cable on the same port, but I'm confident my cables and ports are good.
jimmylomax said:
Right - I was thinking the same thing. So, early this afternoon I did reflash (with "BIN_LGE980AT-00-V20g-ATT-US-APR-28-2014+0.tot") one more time and did only the following:
Skipped wifi setup, disabled "back up [and restore] data from google account". Rebooted
Went straight to app store and disabled auto download/update
Received notification that Google Play Services needed updating or something - I clicked the notification in order to read entire message and I think it just updated it?
set Hangouts as default messenger. Rebooted once again.
Then, I just tried to heavily use it. I used Maps navigation, took a bunch of rapid fire photos, Gmail, Chrome, etc. It worked great for about 3 hours until I got my first crash while taking some photos and attaching to a few rapid-fire hangouts messages. I removed the external flash card, but left SIM card and rebooted. It crashed one or two more times in the next 5 minutes. Since then it has crashed while using it maybe twice and once or twice while it should have been sleeping.
Any use in trying to capture event logs or should I just go ahead and dig out my phillips 00 screwdriver and tear into it?
I did use a different cable on the same port, but I'm confident my cables and ports are good.
Click to expand...
Click to collapse
yup, bummer. no twrp and new cable. I'm stumped. a log would mean nothing to me - maybe hyelton.
Wondering if prob happens when it warms up and expansion causes a break in connection. yeah, man the screwdriver. Wish I could be of more help.
Its a long shot, but it could be a faulty battery. Does it crash when the phone is fully charged and plugged into the original 2amp charger? If yes, then its probably not a faulty battery. If no, and it crashes off the charger, especially with a battery <75% then it could be a faulty battery.
Sent from my LG-E980 using XDA Free mobile app
Sprint LG G3, the 990 version. Stock ui.
So yesterday this all started. The touch sensor suddenly stopped registering inputs. From my testing on it (this problem has happened dozens of times since yesterday afternoon) eventually after a few minutes of use the input will just stop working, but the phone functions still work. Videos and games continue to play, phone and video calls still keep running properly, and the home screen clock will keep running while the touch input is disabled. I can volume up and down, but cannot interact with the screen. The power button will not put the screen to sleep.
Eventually the screen will timeout, now I can interact with it again. I hit the power button like normal, and get a vibration, then the screen turns on and I get the dialog box to turn off or restart the phone over my lock screen, as if I long-pressed the power button. I can click away from this and start using the phone again like normal.
But it will happen again. I can get a few minutes of use usually before the touch input disables itself again.
I didn't download anything recently. I did disable notifications for my LINE app yesterday through the app drawer, but after this started I reverted that, just to be sure. Some apps might have auto updated, but this is happening in any app I use.
I have looked around lots of places, but can't find anyone else saying they have this particular problem. Any idea what is going on and how I can troubleshoot this short of trying a factory reset?
superbelt said:
Sprint LG G3, the 990 version. Stock ui.
So yesterday this all started. The touch sensor suddenly stopped registering inputs. From my testing on it (this problem has happened dozens of times since yesterday afternoon) eventually after a few minutes of use the input will just stop working, but the phone functions still work. Videos and games continue to play, phone and video calls still keep running properly, and the home screen clock will keep running while the touch input is disabled. I can volume up and down, but cannot interact with the screen. The power button will not put the screen to sleep.
Eventually the screen will timeout, now I can interact with it again. I hit the power button like normal, and get a vibration, then the screen turns on and I get the dialog box to turn off or restart the phone over my lock screen, as if I long-pressed the power button. I can click away from this and start using the phone again like normal.
But it will happen again. I can get a few minutes of use usually before the touch input disables itself again.
I didn't download anything recently. I did disable notifications for my LINE app yesterday through the app drawer, but after this started I reverted that, just to be sure. Some apps might have auto updated, but this is happening in any app I use.
I have looked around lots of places, but can't find anyone else saying they have this particular problem. Any idea what is going on and how I can troubleshoot this short of trying a factory reset?
Click to expand...
Click to collapse
Boot.into safemode i cant remeber the key sequence google itll disable all 3rd party apps then if it work u know its in a app
---------- Post added at 12:52 AM ---------- Previous post was at 12:50 AM ----------
Further more if it does not help then a factory restore is in the pic. Then of that dont work try restoring stock tot.kdz method and flash tool it is possible for system to corrupt files and reset still not fix.
---------- Post added at 12:53 AM ---------- Previous post was at 12:52 AM ----------
Are u root ed stock rom cm kernals ?
TheMadScientist420 said:
Boot.into safemode i cant remeber the key sequence google itll disable all 3rd party apps then if it work u know its in a app
---------- Post added at 12:52 AM ---------- Previous post was at 12:50 AM ----------
Further more if it does not help then a factory restore is in the pic. Then of that dont work try restoring stock tot.kdz method and flash tool it is possible for system to corrupt files and reset still not fix.
---------- Post added at 12:53 AM ---------- Previous post was at 12:52 AM ----------
Are u root ed stock rom cm kernals ?
Click to expand...
Click to collapse
Hey, thanks for the reply. So I did what you said. I ended up doing a factory restore of my device.
I have had this phone since about a month after it was released two years ago. I rooted way back then, did not install any rom over it yet... and then a few weeks later my kid went and clicked through a software update one day and removed my root, so I just left it go.
Anyway, I did the full factory reset, and started setting my phone up again, and a couple times the problem resurfaced. No apps from the store yet installed, the phone just stopped responding to any touch inputs. I wait for it to go to sleep, and then wake it up to use it again.
This sucks, I guess this is forcing me to upgrade when the G5 releases. But any ideas still? I dread being stuck with the phone being buggy like this for another two months or so. It's not app related, it doesn't SEEM to be hardware based, since everything works perfect up until it just locks up. The problem happens with different batteries I use. There doesn't appear to be any physical damage to the phone at all.
For those who have upgraded already, how did the upgrade process go and how are you liking it so far?
This is a big upgrade and I'm nervous about pulling the trigger until this is vetted out a bit.
Chris
The process went well. I had to play with the display resolution and zoom to get things looking right. I had to re install my theme store theme to get it back. Other than that, it runs great. Only a few apps not compatible with n. But I have like 400 apps. So not bad! Oh yes, I did need a couple of reboots too.
Sweet! Well... having to go five steps back first was a PITA but when finished (and thank God for the Samsung Cloud Backup System - I had just done a backup three days before this project and it saved my arse!) Once I finished the AT&T OTA of QB2, I did a Restore from the Samsung Cloud and the phone looked EXACTLY like it had with Nougat PL4! Desktop, Apps, (most) settings... awesome!
Going good, process went smooth. I'd just say plug up and stay plugged during upgrade
Just did the upgrade. I have to say guys, this was BY FAR the smoothest stock upgrade I've ever experienced from Samsung. They did a nice job on this.
I'm just running into the issue of UI Lag. The update went smooth enough though. I will also say I am having issue with video playback in chrome if I flip to fullscreen then the ability to control the video is gone and i cant minimize it i have to hit the home key to get out of the video.
I just finished installing QB2. Everything works smoothly except one annoying bug. The Activity Zone app launch not in full screen. It's like 70% of the screen. I tried to change the display resolution but the same.
Anyone having the same issue?
snugroho3 said:
I just finished installing QB2. Everything works smoothly except one annoying bug. The Activity Zone app launch not in full screen. It's like 70% of the screen. I tried to change the display resolution but the same.
Anyone having the same issue?
Click to expand...
Click to collapse
No, mine launches full screen!
---------- Post added at 03:46 PM ---------- Previous post was at 03:45 PM ----------
CFoote said:
Just did the upgrade. I have to say guys, this was BY FAR the smoothest stock upgrade I've ever experienced from Samsung. They did a nice job on this.
Click to expand...
Click to collapse
DITTO!
jimd1050 said:
No, mine launches full screen!
---------- Post added at 03:46 PM ---------- Previous post was at 03:45 PM ----------
DITTO!
Click to expand...
Click to collapse
Yes, it launch in full screen but the content of the app is not. Please see attached picture. Do you have the same?
It was full screen in marshmallow
That is quite strange, my Activity Zone is full screen, do you have your Zoom function under "Display" set to small?
Upgrade went smooth , i did it manually and not OTA , all working good with good battery life.
What i did is as follows :
1- Odin the PI2 as a base line
2- Then via recovery from the device I used "update from SD card" and upgraded to PK2
3- Then i did it again via recovery from the device I used "update from SD card" and upgraded to QB2
Download the needed files from the following thread
https://forum.xda-developers.com/s7-active/how-to/s7-active-sm-g891a-ota-updates-firmware-t3540866
I updated to the BQB2 build via OTA about a week after it became available. I'm generally pleased with it, but there are a few things here and there that make me think that perhaps I'm due for a factory reset and start over.
Battery life is slightly down for me, which doesn't match up with reports I'm hearing from others. It's not much lower, but it's noticeable.
UI seems to be slightly more 'laggy'. Reduced the animation scales in the dev options to compensate. Maybe because I was running 'Good Lock' when the update happened?
Seems like wifi connection is not 100% stable. I see the notification bar 'flicker' from time to time, and it keeps re-posting the notification about what network I'm connected to.
Seems to get warmer while charging wirelessly, to the point that it pauses the wireless charging. But, this is in a cradle in my car, with Waze running, and it's warmer than it had been for a few months so not really sure if the update is involved in this or not.
Probably one or two other smaller things that I'm not thinking of at the moment. Obviously they weren't showstoppers, since I can't recall right now.
I like that they included the mobile hotspot toggle again (finally!), but they still don't have a 'mobile data' one. System UI Tuner is still gone, although I've read some people think that's the case with Nougat in general, so not sure.
All that being said, it updated to the BQC2 build today. The wifi thing seems to be resolved, despite this being only a 'security update'. I'll let it shake out for a few days or so and see if I still think it's worthwhile to start all over.
Went smooth for me, took literally less then 2 minutes.
All my apps/settings are working flawlessly and I experienced no issues thus far.
I updated to Nougat since it was released and I can't say I'm happy. Battery looks slightly worse and at least 1 or 2 twice a week my phone slows down getting almost unresponsive. I have to restart it.
That never happened with Marshmallow. I'll try it for one more month and if not I will go back to Marshmallow. Is that still possible?
That is a good question. I know that with small version upgrades the phone keeps the original version stored for a full wipe, but on a big OS upgrade I am not sure. Hopefully someone will know. I want to say yes it can be done.
Im on QD4, loving Noguat at how quick it is. But, i hate how all the menus and settings are all bunched and i have use search to find basic things.
I actually am having some issues with my s7 active I installed the 7.0 update a few months back and never looked back because the 7.0 stock rooms great no issues except recently last week's my phone started rebooting on its own . I though no biggie cause it did every once in a while , but now it has greatly increased . What happen was it froze on Facebook messenger app when I was trying to reply to a message and would not unfreeze so I had too force restart it that is when the problems really begun. The moment I force restarted it and it rebooted and i got into hone screen i keep getting notifications that apps were crashing over and over and the phone decided to restart on its own and keep doing the same thing . So I was like wtf maybe it's a app or something so I decided to do a factory reset and clear cache and rebooted the phone looked like that fixed the problem for a whole 2 minutes then the crashing of apps and random restarts . I was tired so.i was like ok I just turned the phone off and notice that it was kinda warm and decided to go to bed and mess with it tomorrow . So when I woke up I booted the phone up and it was acting normal no crashing or anything no reboots but after 2 hours it randomly started rebooting and sometimes the apps crash bit currently the phone is working but i get random freezes and reboots all day . I have tried searching for a solution but no luck. Some people claim its a app but when I have no apps Installed and it still does it its not a app problem . Some people say it could be the mother board flus faulting out or bad battery can't send it in for repair cause I bought the phone off eBay. Is anyone else having these issues and know of a fix maybe thanks sorry for the long post.
Upgraded to BQB2 a week ago, I am very happy with everything, it's smoother, faster and manages RAM better (well I was Rooted on 6.0.1 so it was laggy) all my apps work perfectly and I've disabled many things with Package Disabler Pro, I've been testing running music, google maps chrome, whatsapp, messenger, face all at the same time, very smooth BUT I must say it does drain battery much faster than before.
Now my phone wont make it through the day, it even drains on standby, I've already flashed 7.0 twice and wiped cache, I'm still, thinking if I will keep this or go back to 6.
Yesterday alone, my battery went from 89% at 1:30am to 52% at 10:30am, only on standby. When I check Battery use my com.android.systemui is the one eating up most of it, I even set my resolution low to HD. If anybody has a solution, any help would surely be appreciated, I don't wanna go back to Marshmellow, but if I must......
Upgraded and everything was fine apparently, then I saw the huge battery drain, tried averything I found and decided to go back to marshmallow.
KGB7 said:
i hate how all the menus and settings are all bunched
Click to expand...
Click to collapse
Can you please provide screen shots?
There are 2 more ups after QD4 (side load), I need to know if I should be prepared to go that far if I proceed with QD4.
Hello.
A couple of days ago when I turned on my phone screen, and a message saying "power off" appeared, and the phone turned off. After that I proceeded to turn on the phone again, and it loaded the OS normally, and then again, the same message appeared and the phone turned off again, and phone never turned on again. By the time that happened the phone had a charge of 92% approximately. I don't know what it could have been, but I'm guessing it is battery-related, so that's why I'm asking if any of you know how to disassembly this phone or at least get to the battery, as I'd like to see if maybe the battery attachment thing got loose or something like that. If anyone knows what could have happened, let me know please.
Nope but why salvage it? Prolly better to sell on ebay as "for parts" at this point.
I can tell you that's just one of the issues our phone Blade V8 pro has. but if you start the rooting process it gets better. What I mean is im about as far as I can be with rooting my phone, without actually completing the task. I don't have a laptop or access to one. So that's the hold up for me. Although I do have everything I need to complete the task already. My List: #1. 7.0 Nugat Update Zip inside my SD Card #2. I have a entire Super User Management products assortment.. Also have apps downloaded that Impose the 7.0 and the 8.1 Updates, so my phone already runs as though I have the updates. But it still shows 6.1 in the Info page.
---------- Post added at 09:57 PM ---------- Previous post was at 09:53 PM ----------
Blackbear.immortal said:
I can tell you that's just one of the issues our phone Blade V8 pro has. but if you start the rooting process it gets better. What I mean is im about as far as I can be with rooting my phone, without actually completing the task. I don't have a laptop or access to one. So that's the hold up for me. Although I do have everything I need to complete the task already. My List: #1. 7.0 Nugat Update Zip inside my SD Card #2. I have a entire Super User Management products assortment.. Also have apps downloaded that Impose the 7.0 and the 8.1 Updates, so my phone already runs as though I have the updates. But it still shows 6.1 in the Info page.
Click to expand...
Click to collapse
MY ZTE BLADE V8 PRO no longer powers off, doesn't force close my apps when it locks, has duel window support, and is Twice or Three times Faster. then when I got it 2 months ago from Best Buy for 199.99 and it was pretty fast then. It's faster then I am already, lol
---------- Post added at 10:18 PM ---------- Previous post was at 09:57 PM ----------
Blackbear.immortal said:
I can tell you that's just one of the issues our phone Blade V8 pro has. but if you start the rooting process it gets better. What I mean is im about as far as I can be with rooting my phone, without actually completing the task. I don't have a laptop or access to one. So that's the hold up for me. Although I do have everything I need to complete the task already. My List: #1. 7.0 Nugat Update Zip inside my SD Card #2. I have a entire Super User Management products assortment.. Also have apps downloaded that Impose the 7.0 and the 8.1 Updates, so my phone already runs as though I have the updates. But it still shows 6.1 in the Info page.
---------- Post added at 09:57 PM ---------- Previous post was at 09:53 PM ----------
MY ZTE BLADE V8 PRO no longer powers off, doesn't force close my apps when it locks, has duel window support, and is Twice or Three times Faster. then when I got it 2 months ago from Best Buy for 199.99 and it was pretty fast then. It's faster then I am already, lol
Click to expand...
Click to collapse
I have this if you can get a file manager to write it on your build properties persist.sys.debug.multi_window=true
just copy and paste it at the very bottom of the document.. I just tried to add screen shots as attachments but wouldn't load them so Ill list the products I use below..
/!\ kShark /!\ has a "Excellent" line of SuperUser products! just search Google Play Store kShark
both FREE and PAID work extreemly well and the Developer answers emails so support is Good.
Also for the most responcive file manager Although Ill Never give up on ES pro.. Maple has File Manager Pro (paid total of 5.99) its Red folder and after u upgrade it has the pirate android on the side also asked if I wanted classic edition gray.. but its the only one I found that will write system files without having root permition, although I never did the root checker and I don't advise you to start that process on any application unless they do it for you. Instantly locks you out of any possible advantage
I noticed a larger than normal defect rate. My phone has a bad fingerprint sensor, and my wife's has a bad mic. My phone broke (i dont like cases) and I tore down the device to swap the mic. Now she can make calls while not on speakerphone. The teardown is not too bad. you start with the back cover. i used a razor blade to get between it and the metal, afterwards i used a guitar pick to pry the rest of it open. it has clips and weak glue. The rest is all screws. so it is pretty straightforward.
https://www.youtube.com/watch?v=xPNkcMUlhEQ
Hello all,
It seems i have a issue with my 6 month old Galaxy Watch 46mm, 1 week after the ONE UI update, all sensors (accelerometer, gyro and HR sensor) stopped working, only the ambient light sensor was working.
So i had no more step counter, turn your wrist to wake the screen (the one i missed the most), HR monitor, nothing.
After couple of restarts, 3 factory resets and waiting for 2 days, all sensors started working again.
Everything was fine for 1 week.
And now since 3 days ago the issue reappeared. no restarts, factory resets, hard restarts helped, till now.
What I noticed is if the Watch is powered OFF and charging the screen rotates accordingly, but if it is powered ON, the screen remains in the same position as it is on your hand, it does not turn 90 degrees.
So for me it seems to be a software/firmware bug.
Does anyone else have this issue?
How did you solve it?
Thanks
Hi,
i have similar problem on my GWA (SM-R500).
Now its four days and many restarts/Factory resets since my sensors died...
I was on Vacation/camping when my last HR reading history shows it happens while sleeping... I've noticed this next day when going for a walk and no notifications go to my watch (i've set to send notifications to watch only when wearing and not using phone). Then noticed that HR sensor is not blinking (set to always on). So i've tried to switch on manual and it starts measuring but in the end shows a "generic" error message (Can't read, try again) - no "dirty sensor" or similar messages... https://www.youtube.com/watch?v=9zo4pOisX_k
Now when i'm at home and searching for help and found this thread. So i've edited my Watchface to test other sensors (accelerometer, gyro) and they dont show any movement either...
I've tried even switch different options in the menus (like detecting workouts, sensors authorisations, etc) what i've found that helped others, but no avail...
According to Galaxy Wearable app i'm runing latest FW
OneUI v1.0
Tizen 4.0.0.3
FW R500XXU1BSD3
a new 15 MB update seems to be comming out,
Samsung’s changelog for the update read:
• Improved system reliability
• Disabled automatic sync of alarm from paired smartphone or watch
• Improved tracking for swim
maybe it will also make our sensors alive again ?
Question is when it will be out in EU
no clue, is it only for US? i am in Europe/Romania also
btw, my sensors started workin for 1 whole day, then went dead again, and now for the last 5 days, they are working 1 hour in 24 hours...which is kind of nice ?? just kidding
It looks like its update only for your (R800) type of watch... My R500 don't have any new update since April...
I'm thinking if there is some way to downgrade Samsung Health because last day it drain my battery in 22 hours, so i think problem is there...
BRazvy said:
a new 15 MB update seems to be comming out,
Samsung’s changelog for the update read:
• Improved system reliability
• Disabled automatic sync of alarm from paired smartphone or watch
• Improved tracking for swim
maybe it will also make our sensors alive again ?
Click to expand...
Click to collapse
Well, it really screwed up the floor count. There's another thread on this here but I normally don't get any counts. Today without climbing any floors at all, I have 173 floors.
I've tried Samsung's CZ Tech support and they responded, that this problem (at least my version) is really caused by last update of SHealth app, they know about it, but sadly there is no way to rollback to previous version, se we must only wait for new update
BRazvy said:
a new 15 MB update seems to be comming out,
Samsung’s changelog for the update read:
• Improved system reliability
• Disabled automatic sync of alarm from paired smartphone or watch
• Improved tracking for swim
maybe it will also make our sensors alive again
Click to expand...
Click to collapse
True that
---------- Post added at 12:45 PM ---------- Previous post was at 12:44 PM ----------
ententeak said:
It looks like its update only for your (R800) type of watch... My R500 don't have any new update since April...
I'm thinking if there is some way to downgrade Samsung Health because last day it drain my battery in 22 hours, so i think problem is there...
Click to expand...
Click to collapse
Yep, my friend has the same problem
whenever i reset my watch to factory settings, the latest samsung health version appears as an update, but i left it with the older version for days, and it still didn't help, are we talking about a much earlyer version?
BRazvy said:
whenever i reset my watch to factory settings, the latest samsung health version appears as an update, but i left it with the older version for days, and it still didn't help, are we talking about a much earlyer version?
Click to expand...
Click to collapse
Thats why i said "At least my version". I have different model (Galaxy Watch Active vs Galaxy Watch 46mm) than you, but similar error...
BTW: today i've wakeup with them "dead" - after 1 day and 10 hours in "battery saver mode" was battery drained from 100% to 0% mostly by SHealth app..
ententeak said:
I've tried Samsung's CZ Tech support and they responded, that this problem (at least my version) is really caused by last update of SHealth app, they know about it, but sadly there is no way to rollback to previous version, se we must only wait for new update
Click to expand...
Click to collapse
ententeak said:
Thats why i said "At least my version". I have different model (Galaxy Watch Active vs Galaxy Watch 46mm) than you, but similar error...
BTW: today i've wakeup with them "dead" - after 1 day and 10 hours in "battery saver mode" was battery drained from 100% to 0% mostly by SHealth app..
Click to expand...
Click to collapse
seems you will get the update also:
https://www.reddit.com/r/GalaxyWatch/comments/cgplgu/new_update_on_my_gwa/
Sadly not yet available in CZ
ententeak said:
Sadly not yet available in CZ
Click to expand...
Click to collapse
got the update 2 days ago, installed it,but nothing changed...
but about 1 week ago, i deleted the Alti-Barometer widget and then uninstalled the Alti-Barometer App thatcomes from the factory, and after several restarts everything started working, except for the floor count, which i can leave without, other sensors still working after 1 week, without any issues
also tested this again after the SW Update from 2 days ago, watch reset, tried to configure Alti Barometer app, sensors crashed, deleted Alti-Barometer app, 5 restarts plus several shutdowns later, everything started working again
so i am 99% happy now, maybe this post will help others
P.S. also with latest Samsung Health App installed, everything besides floor count works fine.
Good to know & glad it's sorted! Cheers
i "forced" that update with changing CSC code from XEZ (CZ) to XAR (US) and get the Tizen 4.0.0.5 update and no luck either... (Changing XAR to XEZ was a little pain in the ass because they use different WiFi bands so i've needed to reconfigure my router to be able to connect to sdb)
and GWA don't have Alti-barometer preinstalled, so i've tried to install it, calibrate (via GPS), tried to measure pressure (no data), tried few restarts with no luck... Now, when Alti-Bar uninstalled, i'm trying more restarts without change...
The sensors are dead even in the service menu (*#0*#)
(BTW: i've got since my last reply 2 days working, one day not and then 5 days in a row when it worked. Then dead again, so i've tried that CSC-updated method...)
Hi all.
I bought a Galaxy Watch 46mm in April 2019 and updated recently :
SM-R800
One UI 1.0
Tizen 4.0.0.4
R800XXU1CSE1
For my part I have the following problem: the number of floors climbed is completely wrong for several weeks now. I do not know if it's from the One UI 1.0 version but when i bought it it worked fine.
So according to you it comes from Samsung Health and not the OS, firmware?
Have you tried to go back on updating the watch by trying to flash it with a previous version?
My watch is still under warranty samsung.
It was sent for repair and they changed the brightness sensor which of course did not change anything !
Attached a screenshot of my watch : you can see 72 floors climbed on the 05/08/2019...
Thank you for your feedback.
I have the sensor issues (HR, lift-to-wake, step count, et al) for almost two months now. countless reboots didn't fix my problem. I then read somewhere that completely switching off the watch, or turning it to 'watch only' mode for 2-3 days fixes the problem. I did just that and voila! Everything works fine. UNTIL, I went to the gym and recorded my workout. I stopped recording my workout and all sensors died again. Followed the process once again, made sure not to record my workout again but it auto detected it this time and died again. I'll turn on my watch again over the weekend to see if the issue auto-fixes again, but I think I have identified atleast one thing that causes this incredibly annoying issue!
EDIT: I've read a lot of people (both on this thread and otherwise) mentioning how the Health app is the culprit. Does anybody have an apk of a previous version to test out this theory?
I give a shot to the "Watch-only mode"... and after few minutes in that mode, turned back on and its working
Edit: it was working for almost same time as it was turned off :/
BTW: I was asking at Samsung's support if there is some way how to rollback (at least like on any android phone - uninstall all updates for default apps) and she say there is no other way than "Factory settings"
If u uninstall Alti Barometer app all works except floor counts. But if u live in building on 4th floor when u go to the apartment gyro sensors goes off and stop working. The same situation is when u go down from 4th floor. Then u must restart GW (on ground or apartment) to start sensors working. Frustrated.