Hello.
I've had the Galaxy S5 for a while now (5 years), and while it is not my main device at this stage, I still keep it around as a backup phone.
On Pie-based ROMs and earlier, the heart-rate monitor worked just fine, on Samsung Health it just required to download a little apk and it would function with no issues, and 3rd-party apps like Cardiograph would be able to use it with no issues.
However, it seems that in Android 10 and 11, the HRM can't be accessed at all. It is detected, Samsung Health shows the option, but the sensor just doesn't do anything. And in 3rd-party apps, it isn't even an option I can use. I only can use the flashlight and camera combo, which I really don't want to use.
Does anyone know why it doesn't work? Is it something to do with how 10 and up work? And can something be done about? Or will I have to remain on Pie?
Related
I'm trying to track down some wlan_rx_wake issue.
My understanding is that what is supposed to happen is that multicast is normally enabled when a device is awake, or perhaps with the screen on, but when the screen blanks, or more likely the system suspends, the broadcom chip is set to ignore multicast
This allows the device to sleep peacefully without being woken up by local lan broadcast traffic.
Does anyone know if the stock samsung 4.3 kernel (J9/VIA) does this?
How about alternative kernels/roms - do any explicitly enable or disable this?
It may also be an app that has the multicast lock... but I've disabled all apps I can with this permission leaving just stock samsung apps that can't be disabled. I can't root as I need sky go. I'm reluctant to replace with non standard rom due to knox, but will consider it (I've replaced firmware many times on other devices inc. s3)
The reason I ask is on my local lan I was seeing my S4 (and note 10.1) have this wakelock active for far too long. I've now removed most broadcasts from the network (most were netbios related!) and this wakelock is well under control now (6 minutes out of 1:16 isn't bad). However I have the same issue in the office where I can't fix the lan....
One way or the other I have a suspicion this is an oversigh in samsung's 4.3 rom.
I should say broadcast more generally....
So far the only mentions I can find are
- This modified 4.3 google edition kernel http://forum.xda-developers.com/showthread.php?t=2342298&highlight=multicast+suspend
More battery life tests and use of Better battery stats etc, along with network traces rather convinces me this is an increasing problem. At home I have some control over my network. at a place of work, less so.
Public wifi access points are usually ok as inter-device broadcasts are blocked. But home with uPNP, lots of devices doing arp requests etc is nearly impossible to manage - though I did cut mine down by about half. I'm looking at whether ddwrt could help with some filtering in a seperate wireless AP just for the phone/tablet!
The only real fix is for the device to implement filtering, which from the kernel source it looks as if it might but the only way to try for sure is either to root (breaking sky go) or do a custom rom (breaking KNOX, and possibly sky go). I wish I knew if there's some app/config causing my broadcast filter not to be active, or if it's a samsung kernel build choice.
I've continued to see this across my S4 (4.3) and Note 10.1 (4.1) running official samsung roms. It's been frustrating as it equates to sigificant power drain.
My sons' nexus 5 / 10 does not show this issue.
A few days ago I decided to flash a port of OmniROM 4.4.2 onto my note 10.1 . Same network, same apps - the problem has basically gone. There is still some wifi wake time but nothing like the amount previously.
My guess is the omnirom/aosp kernel is correctly filtering broadcasts, or just maybe it's because it's missing some samsung bloatware.
Possible fixes on the S4 are more awkward
- Any rooting, flashing a non-official rom etc will result in a KNOX 0x1 flag. Not really an issue to me, but annoying
- Whilst I *love* Omnirom on the tablet it may not be stable enough for phone use yet
- The samsung S4 camera is very good. Much better than alternatives
My current thought therefore is to
- hold out for samsung s4 build to see if the issue is addressed
- If not try rooting and disabling all samsung bloat, and try alternative kernels (if any) on the TW rom
- if all else fails consider OmniRom or CM11 , or Samsung's GE rom (by this point KNOX will be tripped anyway)
ANy thoughts?
Anyone else seeing this issue?
Any kernel devs care to comment?
So another check. Phone sat idle for an hour, of which 47 minutes was awake.
Apps did account for around 13 minutes of this - the big proportion being skype which I just installed earlier today. What a surprise. That's getting deinstalled (again), but most of the rest was just wlan_rx_wake ie the device being woken up to deal with packets. If asleep that should be minimal, as it is when running 4.4 on the tablet, yet it isn't - clearly samsung are not implementing the broadcast/multicast filter on sleep. AARGGH
I'm slightly bemused I see so few people mentioning this. Is it that they don't look? Don't care? Or is it just me......
I'd be tempted to do a complete reinstall... it would be a lot easier if I could easily backup (titanium backup or CWM backup) yet do either and I trickt the KNOX switch. thanks Samsung. Not. It's not a big deal as everthing is cloudified, but it would cost me a few hours getting things setup again, even things like the desktop layout ...
So is anyone using an S4 on 4.3 and NOT seeing this issue when on wifi (with multiple devices around) ? If so, just perhaps I'll try a factory reset, but I already did that coming from 4.2 anyway. Or perhaps you are using a custom rom/kernel and not seeing this or noticed it improved?
See also http://forum.xda-developers.com/showthread.php?t=2133176&page=3
Still on stock rom, and still puzzling this.
Most samsung value add that can be disabled in a stock, unrooted rom, is.
Yet a wireless network packet trace (run on an attached PC) shows a significant amount of activity - not being *received* by the phone, but actually being sent
Packets like this show up around every second! Hardly surprising the device is kept awake a lot
24631 888.950873000 android-295fdb686877cc14.home 239.255.255.250 SSDP 167 M-SEARCH * HTTP/1.1
M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
MAN: "ssdp:discover"
MX: 1
ST: urn:dial-multiscreen-org:service:dial:1
In fact in 10 minutes idle this was pretty much the only traffic to or from the phone!
This looks very chromecast-ish -- which I don't have. presumably it's something screen share related from samsung -- even though no devices are connected/setup to cast screen
This must also be from a non-disable-able app - but I'm unsure how to categorically pin it down without root access
I've actually been here before on my note 10.1 - where my resolution was to switch to omnirom. That's less easy on the S4 due to knox concerns, and camera & other more esoteric features (spen is fine with omnirom on the note 10.1!)
Went through trying to kill processes/tasks that I could (I'm not root) and nothing stopped these SSDP broadcasts.
Checked settings - no changes made any difference.
Played with adb shell, dumpsys, logcat & finally ddms - but no jobs.
Wish I could find out the process that is initiating these packets!
An update.......
I decided to try one more time with the stock 4.3 BTU rom and did a full factory reset
WIth no google or samsung account, and no apps I had no wlan_rx_lock
I then configured google accounts (inc. gmail etc) with sync and added only minimal apps (zedge, chrome, mysms, kii keyboard)
still no wakelock issue
This would suggest it's app related, though by not configuring my samsung account (I don't need to) that could affect the way the bloatware works too.
Quite happy now! Wish I could take a "snapshot" backup. Of course that would need a custom recovery and break the KNOX flag. Oh samsung. that's annoying.
The plan is to leave it like this until after work, then to add tweetings & spotify. I'm going to slowly add apps back so hopefully help in identifying when (if at all) the problem reduces. Of course there could be a latent affect which would just be painful.
Annoying too I wasn't able to find the cause with adb, better battery stats, dumpsys etc without doing it the basic way.
planetf1 said:
An update.......
I decided to try one more time with the stock 4.3 BTU rom and did a full factory reset
WIth no google or samsung account, and no apps I had no wlan_rx_lock
I then configured google accounts (inc. gmail etc) with sync and added only minimal apps (zedge, chrome, mysms, kii keyboard)
still no wakelock issue
This would suggest it's app related, though by not configuring my samsung account (I don't need to) that could affect the way the bloatware works too.
Quite happy now! Wish I could take a "snapshot" backup. Of course that would need a custom recovery and break the KNOX flag. Oh samsung. that's annoying.
The plan is to leave it like this until after work, then to add tweetings & spotify. I'm going to slowly add apps back so hopefully help in identifying when (if at all) the problem reduces. Of course there could be a latent affect which would just be painful.
Annoying too I wasn't able to find the cause with adb, better battery stats, dumpsys etc without doing it the basic way.
Click to expand...
Click to collapse
Awe I was reading your monologue breathlessly while hoping for a solution. I've been at work 8 hours, and I have 4h 43m of awake time. All of it minus 10 mins was due wlan_wake
I'm on omega with ktoonz
Hi all,
Currently looking for an upgrade from my Moto G and have a specific list of requirements (long-ish battery life, cheap-ish, ideally fast charging, ideally ANT+, ideally waterproof, accurate GPS for tracking runs) which the S5 seems to meet well. Only thing I dont think I could live with is TouchWiz (and the assosciated lag I would expect it would bring with it).
My question: how is CM running on these devices with regards stability and force closes etc. Can live with a small dip in camera quality and having never had a fingerprint scanner I wont miss it but really need a rock solid, stable device. Is there a better alternative out there (am also closely considering the Zuk - but not waterproof and possibly patchy GPS - and the Moto X Play - slightly more expensive and reports of lag)?
I'm currently running CM13 on my KLTE, and it honestly seems fine.
Battery life is just under 4hrs SOT.
It charges pretty fast IMO (About an hour and a little bit with a constant 1800mA @ 4.5V)
Though was I've read in a quick Google search is that CM doesn't support ANT+ ever since the s4 branch.
Never had issues when the phone's been blessed with water, Its a pretty tight seal all around.
GPS is accurate. I usually get a fix within the first ten seconds. Mind you I use GPS Status to download AGPS info to help.
I rarely get force closes but there are the occasional soft reboots with the phone, which seems to put it in a boot-loop when it does. But that could be my configuration of Xposed and other modifications that do that.
i dont like the in-use battery life at all, deep sleep life is insanely improved on CM13 i assume due to doze, you can buy third party extra large batteries that are also a replacement for the back cover
cm-12.1-20151226-NIGHTLY-klte = quite stable, think i had only a couple minor bugs, no crashes, my baseband is a little old, i tried some gps app from fdroid during a walk & it was as if the calibration kept changing... i passed the same spot more than once, it would be too far north one time then too far southeast another time & so on, but maybe it was storing literal data points (some other apps, especially map apps i would assume they might auto align themselves to roads), crashed the camera when using opencamera too fast or switching between it & stock camera, opencamera couldnt do 60 or 120fps videos even though the option was set
cm-13.0-20160116-NIGHTLY-klte = turning flashlight off kills camera (& the flashlight tile) until reboot, i was going through menus fast or something, the status bar crashed & then soft reboot was frozen on the loading face icon, i was hoping snapdragoncamera was enabled cuz i see it in changelogs, but i still see stock camera unfortunately...
charging is quite fast, from 0 to ~80% at least (this is normal for about every device anyway)
i havent tried any other versions yet, i dont have gapps, only been web browsing in lightning browser (from fdroid), trying kernel adiutor, notepad, little bit of camera, i dont have a SIM card yet, hope it works fine...
i believe i saw a modified TW rom that keeps the TW framework, but visually tries to be AOSP, the purpose of course is to be able to use the samsung camera & some of the other proprietary apps/features
My build is a KLTEusc smg900r4, with cm13, on first boot I had issues with the access points to the mobile network, but after I input one access point it found the rest on its own, only other issue is when sending long text messages it doesn't go through from some reason, overall very proud of it, much better than touchwiz
Hi everyone ! Just wonder to know if anybody succeeded to use DJI Phantom 3 standard or other model with OnePlus 5 ? I have horrible lags on video preview of the aircraft that make impossible using the phone to control it... I've been trying for the past week, flashing different kernels, using different apps and was not able to make it working... Anyone that might have a fix ? ??
Due to his specs the OnePlus 5 should works perfectly... I can even make it working on my old Samsung Galaxy S5 and it runs smoothly...
I assume you have all power-saving features turned OFF
I assume you have the "developer options" for your graphics / animations on the phone left at stock settings.
Does the OSD (on screen display) for your battery life, altitude and those things update in real time smoothly while the FPV is lagging?
If so, then it is more like a Wi-Fi communication issue over that specific port. Ensure you have no security/ antiviral apps running that would be scanning these types of ports (or doing any type of deep-packet-inspection).
So I have my phone rooted, mainly use it for music and video chatting with my fiancée (away at school). I currently have the latest LOS and Gamma Kernels installed. No BusyBox or anything like that. Just Magisk with V4A and the debloat module to get rid some of the baked-in apps that I use alternatives for.
I seem to run into this issue on a pretty regular basis. I'm noticing that it tends to happen most when the phone dies, but many of the features become unresponsive. The fingerprint scanner stops working, WiFi stops working and becomes unselectable, mobile data disables itself, the navigation bar becomes mostly unresponsive and does nothing when you tap the home or task manager button. The phone basically becomes pretty unusable.
I'm wondering if maybe this is something that I'm doing, or if it's maybe a bug within the LOS software? Is there any known fix for this? Am I maybe doing something wrong when flashing the ROMs and kernels?
Often times, maybe once every 3-5 weeks, I have to wipe the phone and re-flash everything, which is getting pretty annoying at this point since I often lose data on some of my apps, pictures that hadn't been able to back-up via Google Photos, etc.
When I upgraded my 6t to Android 11 my banking apps are saying that my phone is rooted when it's not. So I had to downgrade.
Anyone else have that problem or any ideas ?
Thanks
Not sure why that happened except the apps weren't compatible with 11. No shock there.
On both my N10+'s I could "upgrade" to 11.
I remain on 9 and 10 because 11 would trash them in my opinion. Scope storage and forced encryption are fully active on 11*. Did you notice the permission popups on 11?
If there are features that 11 offers you just gots to have, go for it and take the usability hits. The one you described likely has a workaround or the cause will be corrected with an update in either the app or firmware. Many of 11's worst flaws though like scoped storage will remain and be in 12 as well.
*scoped storage doesn't seem to be fully active on N10+ that's running on it. That may be partially a Samsung mod or simply because I'm using older app versions. Both devices run nearly identical with no major usability issues in 10 that I've seen other than killing Karma Firewall's logging feature and 2 overlay apps rendered non-functional. My old WPS office app is fully functional as are photo galleries.
blackhawk said:
Not sure why that happened except the apps weren't compatible with 11. No shock there.
On both my N10+'s I could "upgrade" to 11.
I remain on 9 and 10 because 11 would trash them in my opinion. Scope storage and forced encryption are fully active on 11*. Did you notice the permission popups on 11?
If there are features that 11 offers you just gots to have, go for it and take the usability hits. The one you described likely has a workaround or the cause will be corrected with an update in either the app or firmware. Many of 11's worst flaws though like scoped storage will remain and be in 12 as well.
*scoped storage doesn't seem to be fully active on N10+ that's running on it. That may be partially a Samsung mod or simply because I'm using older app versions. Both devices run nearly identical with no major usability issues in 10 that I've seen other than killing Karma Firewall's logging feature and 2 overlay apps rendered non-functional. My old WPS office app is fully functional as are photo galleries.
Click to expand...
Click to collapse
Thanks for the reply. I think I may have seen popups but can't remember. I downgraded back to 10.3.12 and everything is back to normal. There is now an update to the android 11 to 11.11 and I'm not sure if I wan to take the chance again. It's too much work to revert back.
I contacted oneplus but they were not much help. Just said to send in some logs.
Also I should have pointed out that my phone is the t-mobile converted to international. Maybe android 11 is picking up on that ?
I would leave it on 10, it's a better OS in my opinion.
I had this problem due to a automatic google app restore on my 6t.
The phone was not rooted but got the superSU installed (not working but it was there).
This was the reason on my phone why banking apps didn't work.