Make sensors work #55
Labels
lenok
LG Watch R
Comments
|
@FlorentRevest can you close this, as it is now fixed by @LittleFox94 ? |
|
Only partly resolved, some tests still failing |
|
Which ones? Some sound vague :P |
|
I will add the test output later
Just wanted to quickly answer before it is closed, currently neither watch nor PC available
Am 14. August 2020 13:04:11 MESZ schrieb MagneFire <notifications@github.com>:
…Which ones? Some sound vague :P
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
AsteroidOS/meta-smartwatch#55
--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
|
|
|
Honestly, this looks fine. For reference sake, sturgeon has 8 passed 13 failed. The one thing that is striking is the I think closing this issue would be ok because of this. EDIT: @LittleFox94 Thanks for pointing out :) |
|
One thing to note: we were run sensorapi_test not sensormetadata_test, so the linked code is not the correct one client/clientapitest.cpp:303 is the correct one |
|
What's the state of the heart rate sensor? I tested the newest nightly at the time from 2021-12-05. While this image features the heart rate measurement app, it is just stuck at "Measuring..." with the progress bar going full circle. No heart rate is ever displayed and the sensor at the bottom also does not light up either. However on the install page for lenok it currently says that "Heart Rate" is supported. Has there been a regression in regards to the support of the heart rate sensor or is the state of heart rate measurement support on the web page wrong? Checksums of the image I usedSHA1: SHA512 |
|
I see no obvious change in this repository, so probably some change outside this layer |
|
Did heart rate measurements ever work at some point? |
|
it did, when I originally worked on AsteroidOS/meta-lenok-hybris#10 |
|
Maybe this watch is experiencing the same issue we had for Before going that route though, can you first provide logs? SSH into your watch (https://asteroidos.org/wiki/ssh/) or |
|
mine was running the latest wearos for it before I changed to asteroid |
|
I switched mine over to AsteroidOS right after buying it in 2018 so there's a high chance the WearOS version that was on it before was ancient. Any way, I rebooted the watch, started the "Heart Rate" app, let it run for a few seconds and then closed it. SSH'd into the watch right afterwards and grabbed the logs via Click for Logs |
|
Thanks for that log, it shows quite some helpful information. It might even look like the heart rate sensor is available. It shows that an invalid interval was requested, this might need some further investigation. Can you also send the output of the |
Click for `test_sensors` output |
|
Interesting, it looks like the sensor is available. This: AsteroidOS/sensorfw@ffbadc0 might actually be causing issues for this watch? I'll provide you with a sensorfw.ipk with that patch removed. Will probably have some time to do it tomorrow. Hopefully that changes the behavior. |
|
Before flashing with the nightly I have now I had a nightly running that dates back to May 2020, i.e. before the heart rate stuff was added. So I never experienced a working heart rate sensor so far. |
|
Thanks for waiting. |
|
Aight followed the steps as described in the wiki to install the new version and rebooted the watch. Interestingly the sensor did light up shortly during the boot sequence when the AsteroidOS logo is shown but heart rate measurements still fail as before. Sensor also doesn't light up either while taking the measurement. I added the logs below. Both were done after rebooting watch and starting heart rate measurement app. |
|
Terribly sorry for not getting back to you sooner... Can you send me a dump of your current WearOS installation? I suspect that there's a version mismatch between the expected sensor firmware. Would like to compare versions. |
|
I just tried now on my lenok with dead battery and i could quench a value out of it before it went off. |
|
I retaliated by taking a Christmas break during your response :P Anyway, as for:
I'm not quite sure how to do that. ^^" |
|
(Also maybe someone with the necessary rights could move the recent comment chain around my issue with the heartbeat sensor to a new github issue to not clog up #55 to much :P) |
|
Any news on this issues state? Are @GeckoEidechse problems resolved (somewhere else)? lenok build 19.9.'22
|
|
Mine have been since long time. Only ever flashed nightlies and never encountered not working sensors on lenok. |
Nope, though I haven't attempted flashing back WearOS yet to update my lenok's firmware. |
|
Solved my particular issue in #159 |
|
Guess its time to close both issues then? |
|
No, I think we should update our website. Only after that has been done close the issues. |
Agreed ;) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The connected sensors are described in sensor_def_lenok.conf. However, they are not connected directly to the ARM core, but instead to the Hexagon DSP coprocessor.
The kernel loads the (full of debug printf strings!) firmware to the coprocessor from
/system/vendor/firmware/adsb.*, and then setups several /dev files which are presumably used by the original Android code to interface with the coprocessor using FastRPC.The /dev/adsprpc-smd ioctls are described in the kernel documentation. What is missing is description of the RPC methods provided by the LG code.
These could likely be reverse engineered by statically analyzing the DSP firmware or by stracing ioctl calls in Android.
The text was updated successfully, but these errors were encountered: