So, I could not find the answer to this, when is it exactly the doze mode activated (becoming active).
All articles only mention, after some time when the device is stationary (no movement).
How long is that some time?
After some read, found this article:
https://newcircle.com/s/post/1739/2015/06/12/diving-into-android-m-doze
And here is the source code of the DeviceIdleController:
http://tools.oesf.biz/android-MNC/xref/com/android/server/DeviceIdleController.java
It looks like, the doze mode will be activated after 1 hour (2 times 30 minutes).
But again, I am not Java developer, probably there are much more detail in the process.
What if the device is moved? Will the doze mode "cancelled"?
Well, it would be nice if custom ROM developer could add some customization in this, like shorten the activation time. Or even better, after the doze mode activated, it will stay active even if the device is moved (inside pocket), until the user do something (e.g. waking up, pressing button).
We need a developer to perform doze!!!!!
Enviado desde mi Nexus 6 mediante Tapatalk
I had these exact same questions. How long does it take to enter doze and how much does it take to wake from doze? Like if I bump my phone on desk is it going to hop out of doze mode? Would be cool to alter the time limits. Glad someone is looking into this!
And what parameters are measured for "stationary"? If the GPS is involved then truckers, EMTs, highway patrols and there like will never hit doze.
Sent from my Nexus 6 using Tapatalk
Hoyt Thompson said:
And what parameters are measured for "stationary"? If the GPS is involved then truckers, EMTs, highway patrols and there like will never hit doze.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I would really hope Google would have considered that when making doze.
Sent from my Nexus 6
Mr Patchy Patch said:
I would really hope Google would have considered that when making doze.
Sent from my Nexus 6
Click to expand...
Click to collapse
I am sure they did but it would be easier for the devs to tweak it or us to use it to its potential if a more descriptive instruction is given rather than "stationary"
inquiring minds want to know and searches are turning up few results
Hoyt Thompson said:
And what parameters are measured for "stationary"? If the GPS is involved then truckers, EMTs, highway patrols and there like will never hit doze.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
If I am not mistaken, the doze will detect "significant motion" for that stationary checking.
Code:
void startMonitoringSignificantMotion() {
if (mSigMotionSensor != null && !mSigMotionActive) {
mSensorManager.requestTriggerSensor(mSigMotionListener, mSigMotionSensor);
mSigMotionActive = true;
}
}
void stopMonitoringSignificantMotion() {
if (mSigMotionActive) {
mSensorManager.cancelTriggerSensor(mSigMotionListener, mSigMotionSensor);
mSigMotionActive = false;
}
}
However, how much significant? That's up to the manufacturer implementation. At least this is not defined in the software. That's what I understood. This is an explanation I found:
http://stackoverflow.com/questions/...-of-type-significant-motion-sensor-in-android
But again, I am not Android developer.
I guess, to know about that significant motion, you can install this app (FREE) and then test with some motions
https://play.google.com/store/apps/details?id=com.axelk.sensorapp
From the app description:
Android Sensors is an very useful and simple application.
With Sensor Test for Android on your device you can view and read ALL AVAILABLE android-sensors. (similar to Sensor Box for Android or Phone Tester)
Additionally, you'll receive via the info button other useful information such as the sensor works and what it does.
I'd appreciate a good rating and a +1 (Google+)!
Sensor Test for Android is tested on different devices and versions.
I was not able to test all 8000 different types of Android devices, it´s possible that on some devices appear errors.
Affected people with a not working Sensor-Test-App should reboot and run it again.
Sensor Test for Android is still under construction!
If you have any troubles with your device, please send me an e-mail with the problem (Device-type, Android version, screenshot) before submitting a bad rating.
[email protected]
List of available sensors: (not all sensors will be present in your device)
- ACCELEROMETER
- MAGNETIC FIELD
- ORIENTATION
- GYROSCOPE
- LIGHT
- PRESSURE
- TEMPERATURE
- PROXIMITY
- GRAVITY
- LINEAR ACCELERATION
- ROTATION VECTOR
- RELATIVE HUMIDITY
- AMBIENT TEMPERATURE
- MAGNETIC FIELD UNCALIBRATED
- GAME ROTATION VECTOR
- GYROSCOPE UNCALIBRATED
- SIGNIFICANT MOTION
- STEP DETECTOR
- STEP COUNTER
- GEOMAGNETIC ROTATION VECTOR
- HEART RATE
About me:
Sensor Test for Android is my technicians work I programmed in the summer holidays of my training as a technician (electrical engineering).
Before starting programming, I knew just how to spell JAVA.
I only had contact with LabView, a "painting by numbers" for programmers. For this application a documentation will be created, with which following students can easily incorporated into the Java programming language.
I'd appreciate a good rating and a +1 (Google+)!
Downloaded the sensor app @gogol seems a good amount of movement is needed for significant motion be counted(walking a few steps). Gonna do some more testing... Thanks for the info!
anthonyg45157 said:
Downloaded the sensor app @gogol seems a good amount of movement is needed for significant motion be counted(walking a few steps). Gonna do some more testing... Thanks for the info!
Click to expand...
Click to collapse
Good to know!
I am wondering if putting the phone inside our pocket would trigger significant motion. Otherwise, we need to put it lay down stationary on the table
Thanks for the experiment.
This is interesting, "Agressive Doze" mode from Greenify!
http://forum.xda-developers.com/apps/greenify/aggressive-doze-experimental-feature-t3223731
This isn't based on anything code related but Pebble users are reporting that on marshmallow their pebble's lose connection to the phone app almost 15 minutes on the dot after the phone screen turning off so that's my guess
Seriously 1 hour for doze mode to be activated? Sounds flawed. I'm still hesitating whether to buy Nexus 6...
How is the experiment goes?
Related
I have started working on an app for Windows Mobile 6 phones w/ GPS to do run/walk/bike tracking like the Nike+. Here is a little Video of the app in action:
http://www.youtube.com/watch?v=bIqKHCb21cg&feature=channel_page
Version 0.6.5 9s attached
- Smartphone detection is in
- Run Form updated to be smartphone happy, view log is next.
Version 0.6.4 is attached
- Calories burnt calc!!!! (put your weight in...lbs for now...kg coming )
Version 0.6.3 is attached
- 1 Mile/KM kills the app bug fixed!
Version 0.6.2 is attached
- I am not dead! I promise
- This is mostly a maintence update. All the tracking code has been pulled from the views and put off in modules (as it should have been from the get go) so I can get a Smartphone version working soon.
Version 0.6.1 is attached
- Audio updates - new sounds for mile/km passed and distance goal hit
- Audio updates - updates to how the power management is dealt with for audio, still not perfect, but better
- Center button (on your direction pad) now turns the display off and on and also it stops the phone from sleeping when you use that display off method. This is great for phones that get a bit wierd on their GPS in unattended mode.
Version 0.6 is attached
- New internal tracking code to improve performance and make new feature additions easier (this was more about me than you )
- First audible notices. Each mile/km and distance goal hit. It is just a tone right now, but I will record and add voiced stuff tonight.
- New Settings tab for audible notices
- Smartphone users can atleast start the app and track a run now! (still no settings or view log...that is coming)
Version 0.5.9 is attached
- Fix the View/Save log bug (I hope)...you might have to delete your Run Log (yeah for Alpha testing!)
- New way to calculate speed that is more accurate for me. This might depend on what GPS chip your phone uses...try both and see which you like more (change in the Settings Screen)
Version 0.5.8 is attached
- AppToDate bug fix
- Start of true metric support
- little bug fixes
Version 0.5.7 is attached
- I think the String->Date bug is fixed, please let me know!
- Added an "Action" menu under the left soft key for start/stop/save (silly non-touch screen phone users!)
Version 0.5.6 is attached
- EMAIL A RUN!
(that is a horrible name for the feature right now....since it just gives you a link to share...)
http://www.trackmyrun.mobi/viewrun.php?run_id=18&auth_code=5qii4mfy
Version 0.5.5 is attached
- Settings screen is up and working
- Goal progress is based on settings now (not just 3.1 all the time)
- All based on miles still, KM is coming soon fear not!
- Few more bug fixes and exception catches
Version 0.5.3 is attached
- GPS unattended mode updates
- Few bug fixes
- Ignore Calories/Pace, those spots are place holders/debugging right now...they will work in a later release
Version 0.5.1 is attached
- GPS stays up in unattended mode now (screen off by time out or hitting the power button)
- Few little bug fixes
Version 0.5 is attached
- KML support is all in now
- Go to view a lot (has to be a new one) and select View in Google Maps
- Change the line in the KML file to be green since that yellow was hard to see
Version 0.4 is attached.
- Fixed a few of the stupid SubString() bugs
- Added Experimental KML support! (start a run, do some stuff, then go to options->experimental->Build KML). It will put test.kml in your devices root folder
- Working on new speed tracking code, it is far more accurate...but not done yet (so ignore that it has like 900 #'s after the decimal point)
- Ignore what it says for calories burnt...that isn't what you think it is
ENJOY!
Version 0.3 is attached.
Looks good! I would definatly use this app!
Looks impressive. The auditory upgrade feature would be cool to add.
There are similar Apps. One in particular is also cool is:
GPS Cycle Computer v2
http://forum.xda-developers.com/showthread.php?t=424423
How would this calculate calories burned if your activity differs?
i.e. Rollerblading vs. Running vs Cycling, etc.
or is it simply based on time and distance to give a general calculation?
Nice looking app, I will definitely be keeping an eye out for this one. Keep up the good work.
Does this track coordinates? Or does it track via something else? Cause then I'm thinking that you need an active data connection for this to work :|
Kraize said:
Does this track coordinates? Or does it track via something else? Cause then I'm thinking that you need an active data connection for this to work :|
Click to expand...
Click to collapse
It tracks coordinates, so no data plan is needed at all for this. Just a working GPS. Now, I plan in the future to have online features for showing your routes on google maps and storing run data online, ect...but that is in the future...
band27 said:
Looks impressive. The auditory upgrade feature would be cool to add.
How would this calculate calories burned if your activity differs?
i.e. Rollerblading vs. Running vs Cycling, etc.
or is it simply based on time and distance to give a general calculation?
Click to expand...
Click to collapse
There are some standard formulats that are based on weight, time of exercise and how vigorous the activity is. For walk, jog, run that is easy (since I now your MPH's). For biking, roller blading, ect that gets tougher.
This is looking awesome. Could really do with an App like this. Keep it up and hope your "about a week" estimate is correct for a first beta.
A question though; I have a Touch HD. Has the interface been written to be able to cope with a WVGA resolution?
dom_mitchell1 said:
This is looking awesome. Could really do with an App like this. Keep it up and hope your "about a week" estimate is correct for a first beta.
A question though; I have a Touch HD. Has the interface been written to be able to cope with a WVGA resolution?
Click to expand...
Click to collapse
I have only tested it on a VGA display (my Touch Diamond). I have played with it in the QVGA emulator and the Square VGA emulator. The layout is far from final (I am not happy with it at all right now), so that is in flux a lot.
Go ahead and try the current version if you like:
http://grebowiec.net/trackmyrun.zip
Please be aware this is a VERY alpha version. There are known bugs that throw exceptions that I don't catch...so be nice
If you do however have any failures or success, please let me know.
gweedo767 said:
Go ahead and try the current version if you like:
http://grebowiec.net/trackmyrun.zip
Please be aware this is a VERY alpha version. There are known bugs that throw exceptions that I don't catch...so be nice
If you do however have any failures or success, please let me know.
Click to expand...
Click to collapse
Thanks a lot! I'll give it a go once I get home and give you some feedback!
AppToDate Support
Could you possibly think about having this AppToDate Support. Since this is in the early stages of development, it would be great to run AppToDate to get the current version. Thanks.
Couldn't wait until I got home so just loaded it up here. Everything seems good until I tried to View Log when it crashes out on me.Unfortunately I don't have NETCFv35.Messages.EN.wm.cab installed installed so cannot view details.
Also +1 for Apptodate support!
dom_mitchell1 said:
Couldn't wait until I got home so just loaded it up here. Everything seems good until I tried to View Log when it crashes out on me.Unfortunately I don't have NETCFv35.Messages.EN.wm.cab installed installed so cannot view details.
Also +1 for Apptodate support!
Click to expand...
Click to collapse
Did you start and then stop a run? The log file isn't created until you do atleast one and I bet it is dying trying to read the log file (which doesn't exist yet for you if you didn't do a start/stop)
I will do some reading on AppToDate in a bit, see what all it takes to integrate it.
gweedo767 said:
I will do some reading on AppToDate in a bit, see what all it takes to integrate it.
Click to expand...
Click to collapse
That would be very much appreciated. It just makes things a lot easier.
gweedo767 said:
Did you start and then stop a run? The log file isn't created until you do atleast one and I bet it is dying trying to read the log file (which doesn't exist yet for you if you didn't do a start/stop)
Click to expand...
Click to collapse
Yeah I had done and paced about abit; notched up 0.003 miles. Stopped the run successfully and then tried to view the log.
I've just jogged home from a friend's house (1.237 miles). This time when I stopped the run it crashed. No error code or anything; just said I had to quit and restart.
Sorry that's probably not much good for bug finding!
dom_mitchell1 said:
Yeah I had done and paced about abit; notched up 0.003 miles. Stopped the run successfully and then tried to view the log.
I've just jogged home from a friend's house (1.237 miles). This time when I stopped the run it crashed. No error code or anything; just said I had to quit and restart.
Sorry that's probably not much good for bug finding!
Click to expand...
Click to collapse
Did it do fine during the whole run though?
gweedo767 said:
Did it do fine during the whole run though?
Click to expand...
Click to collapse
Yeah no problems there. Slight lag on speed changes but I guess that's to be expected/part of the suposed and much debated GPS lag on the HD!
No complaints about performance at all.
I'm really liking the look of the App, certianly looks good so far; will be awesome if/when audio feedback can be given.
Something that would be good is if you could make the data from the logs uploadable to a PC to plot onto a graph (via Excel).
Like I said, great work so far! Loving this, who needs Nike/Apple!
dom_mitchell1 said:
Yeah no problems there. Slight lag on speed changes but I guess that's to be expected/part of the suposed and much debated GPS lag on the HD!
No complaints about performance at all.
I'm really liking the look of the App, certianly looks good so far; will be awesome if/when audio feedback can be given.
Something that would be good is if you could make the data from the logs uploadable to a PC to plot onto a graph (via Excel).
Like I said, great work so far! Loving this, who needs Nike/Apple!
Click to expand...
Click to collapse
The lag might be that I only update the display every 5 seconds (that is for all data). I think I might update the speed in real time (there is a call back function I can attach to for that). I do have plans for graphing/tracking/mapping in the future via an upload to a website feature...but that is a bit down the road I want to get all the stand alone client features working correctly first!
Please let us know when you have completed a final version. this program will be very useful. I know its still in the early stages hopefully you will be able to find the bugs and get them fixed, so we can download complete version.
Since I'm not allowed to post in the dev forum, I'll just leave this here:
The light sensor code on the HTC vision is out of date. It can only return 10 light levels, which range from 0..1024. I've been told this is apparently a Froyo standard and that modern phones return from 0..10240.
github dot com/CyanogenMod/android_device_htc_vision/blob/gingerbread/libsensors/LightSensor.cpp
wtf, can't even link to things as a new user?!?
On line 143, you can see the 10 constants that the light sensor code picks between. They are supposed to be in "Lux", but can anyone with a photography rig confirm this? Looking at this chart,
engineeringtoolbox dot com/light-level-rooms-d_708.html
1024 lux is an overcast day. If that's the maximum it can report, that seems like a particularly ****ty light sensor.
Is the hardware that bad, or is the Cyanogenmod code not taking full advantage?
Once we can figure out what the light sensor readings should be, I'll submit a patch to fix the default Automatic Brightness settings (which right now are totally out of sync with the hardware light levels). See line 40 here.
github dot com/CyanogenMod/android_device_htc_vision/blob/gingerbread/overlay/frameworks/base/core/res/res/values/config.xml
Anyhow, only 9 more posts to go before I can participate in the CM9 dev thread
Definitely submit a CM bug report explaining this. Then when you can post links, post a link to the issue thread and everyone will happily plus 1 it.
Hardware is not that bad - this is a CM problem. I've patched mine so it works properly, also, don't use CM. My recommendation.
Thanks for the encouragement. I've filed a bug here. My etiquette may or may not get a warm reception there, so +1s would be appreciated.
code.google [dot] com/p/cyanogenmod/issues/detail?id=4796
I agree with the comment, you should submit it as a patch on gerrit cm review
code.google.com/p/cyanogenmod/issues/detail?id=4796
Alright, installing git now, let's see if I can use it properly.
I might just submit the easy update to the default config.xml AutoBrightness values. My C++ is pretty crap and I doubt I can tell what's going on with the light sensor code.
That seems like an ugly kludge, but it is an open source project after all...
ERROR - JOKES NOT ALLOWED AS NEW USER
What a pain to sync the entire CM source with my crappy internet connection... the 'repo' script recommended in the Gerrit howto hangs overnight.
Code:
repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
repo sync -j16
Killing and restarting the script seems to start again from scratch, so I'm making no forward progress.
I wonder if there's a way to submit patches to gerrit by way of github or some other remote git hosting service?
While setting up git / repo to submit a change to Gerrit, I learned two things - the G2 / Desire Z has a Capella Microsystems CM3602 Light sensor, and the reason the lux values are screwed up - cyanogen did it!
https://github.com/CyanogenMod/andr...mmit/2b53447ec6b2a3fd3e299428d359b3603db19025
Why, I don't understand. The change reason is "Match lightsensor values to kernel". Anyone know more?
Nice, I saw your gerrit submission here http://review.cyanogenmod.com/#change,12845
I hope it gets some good feedback!
Thanks c00ller, I wish I could have added some explanation to the change submission. It would make it a lot easier for a reviewer to figure out what's going on. The real fix would be to change the Vision's lightsensors values to the standard 10..10240 . But without knowing why cyanogenmod reverted them to 1..1024, there's a lot of potential confusion.
The reason for the change is, like the commit message says:
"Match lightsensor values to kernel"
If you look at the kernel source,
Code:
github.com/CyanogenMod/htc-kernel-msm7x30/blob/android-msm-2.6.35/arch/arm/mach-msm/board-vision.c#L317
you can see that these are exactly those levels:
Code:
static struct microp_function_config microp_lightsensor_function = {
.name = "light_sensor",
.category = MICROP_FUNCTION_LSENSOR,
.levels = { 0x1, 0x3, 0x5, 0x13, 0x1A, 0x45, 0xDB, 0x135, 0x1F2, 0x3FF },
.channel = 3,
.int_pin = 1 << 9,
.golden_adc = 0xC0,
.ls_power = capella_cm3602_power,
};
He probably just forgot to adjust the sensor <-> display level mappings in the config.xml (which is what you did in your patch):
Code:
review.cyanogenmod.com/#change,12845
I tried it and it works fine, and I gave it +1
Aha, thanks for the explanation m0viefreak!
I still don't understand exactly where in the code the hardware sensor outputs should be translated into engineering "lux" units. Libsensors seems like the right place to me (naiive non-programmer).
I'd like to advocate for migrating to the gingerbread light sensor standard, since some cyanogenmod auto brightness functionality assumes its 1..10240 lux light sensor range. For example, the "reset threshold".
Is the kernel code using the obsolete 1..1024 range for reverse-compatibility with froyo?
Thanks for bringing this up. I was actually just wondering if the kb backlight issue on Vision keeps coming up because of incorrect light sensor range.
..although this would seem to suggest that the backlight would be on all the time, rather than never on...anyway
I was going to talk to somebody about this but didn't know who to tell about this issue. The brightness can be right at times but the brightness can be changing every few seconds.
Sent from my HTC Vision using xda premium
Any update on the submitted Gerrit change?
Sent from my HTC Vision using Tapatalk 2 Beta-5
azrash said:
Any update on the submitted Gerrit change?
Sent from my HTC Vision using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
Was wondering the same thing.
Same here.
Would anyone be willing to file a glitch/issue in the CM7 github for me?
Any news on this one?
When the light sensor can work properly, than battery life would also get a boost.
Can someone maybe post a link to a (flashable)file to get the right readings from the light sensor? Or tell me if there's a editable file on the system partition I can manually edit?
{
"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"
}
Hello everyone, since I received my Nexus 5 I have been working on an app that uses the low powered step counter API new in KitKat.
How this is different from most other pedometer apps is that with the hardware step sensor, this app uses almost no additional battery so you can keep it running all day. In my testing I noticed no difference in battery life between a day with Pedometer running and a day without it.
From the Google Play description:
Features:
- Set your goal! It is recommended that you take 10000 steps a day. This app allows you to set a goal that's right for you, and displays your current progress.
- Track your progress! This app will keep track of how much and how far you walked, all day, every day. History is presented neatly, both in a list and a graph for easy viewing.
- Colorful themes: choose one of 5 themes that fill your display with color, or go with the standard holo light or dark. With 7 themes in total, there's one for everyone!
- Low powered: Unlike other pedometer apps, this one will not affect your battery life at all.
- Achievements and leaderboards: sign in with your Google+ account to unlock achievements and compete with your friends in leaderboards!
- Both single-day and multi-day achievements are available
- [Pro only] Walk info: see how far you've walked today. Calorie counter coming soon.
Click to expand...
Click to collapse
Often times I'm too lazy to carry my Fitbit with me, especially since having it sync to my phone drains battery. With my phone being the pedometer I feel that I've been motivated to be more active.
There is also a pro version you can buy if you'd like to support me. This pro version currently adds a distance counter, so you can see how far you've walked all day. I plan on adding more pro-only features in the future, such as a calorie counter and maybe a widget. But don't worry, the free version will still be perfectly capable of serving as your daily pedometer. If a feature is extremely popular within the pro version I'll consider adding it to the free version as well.
Downloads: Free version, Pro version ($2.99)
I have used only three permissions. One is start on boot. This is used to start counting as soon as you start the device. The other two are write (and therefore read) external storage. This is used solely for the purpose of exporting logs to assist with debugging if the need arises. Don't worry, your data is safe, and this app will not be sending away any of your information.
If you have any questions of suggestions feel free to contact me, I try to respond within the same day.
* * * * * * * * * * *
Changelog
Mar. 27, 2014: v1.2.0
- Added long awaited history feature!
- Multi-day achievements for Google Play Games!
- Another attempt to fix inaccurate step count
- Added option to display imperial units (pro only)
- More UI optimizations and bug fixes for better use experience
- Preparation for new feature: activities!
Jan. 4, 2014: v1.1.2
- UI optimizations
Jan. 2, 2014: v1.1, v1.1.1
- Added Google Play Games (achievements and leaderboards)
- Low priority persistent notification
- Walk info screen [Pro]
- Bug fixes
Dec. 25, 2013: v1.0
- initial release
Gonna give this a go for the next few days. Thanks!
Ok just downloaded it. We will see how it compares to my fitbit one for a week
Sent from my Nexus 5 using XDA Premium 4 mobile app
I'm working on a rather big update, includes more Fitbit-like features such as history and activities. The basic features is about done, gonna make it look nice now and test it some more. Might upload a beta apk and post the Google Play beta link here for anyone interested in testing. I'm hoping to officially release the update in a week or so, so stayed tuned!
Have you thought about partnering with a rewards company or something? Would be interesting if you could get coupons or discounts from achieving the 10,000 steps or so.
Love it!
ickboblikescheese said:
I'm working on a rather big update, includes more Fitbit-like features such as history and activities. The basic features is about done, gonna make it look nice now and test it some more. Might upload a beta apk and post the Google Play beta link here for anyone interested in testing. I'm hoping to officially release the update in a week or so, so stayed tuned!
Click to expand...
Click to collapse
Hi. I just got my Nexus 5 yesterday. Your app was one of the first I downloaded as I had an S4 and was looking for a low battery pedometer like the S-Health app. Yours looks great, and is pretty accurate (and NO battery drain!). One issue, I had to reboot the phone and when it started again it only showed about half of my steps??... I would love to beta test the app for you. Keep up the good work. (I also would love to have history and be able to see previous days step counts, etc.)
One of my biggest gripes is when driving, all pedometer apps keep counting. There is usually a pause feature or something similar, but it would be ideal if it could detect if you are driving or not. If this is not easily achievable, is there an intent or something else I can use with Tasker to control this app?
Thanks, and it looks really promising!
Sent from my Nexus 5 using Tapatalk
Touchless Control
Good App! thank you for building something like this. I love the statement:
Low powered: Unlike other pedometer apps, this one will not affect your battery life at all.
If its not too much, can you also look into building an app for the always listening/touchless control feature that uses the low powered core? We have another thread with a bounty on this feature.
Har5h
fiftyclick said:
One of my biggest gripes is when driving, all pedometer apps keep counting. There is usually a pause feature or something similar, but it would be ideal if it could detect if you are driving or not. If this is not easily achievable, is there an intent or something else I can use with Tasker to control this app?
Thanks, and it looks really promising!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Detecting if you are driving or not would require GPS or some form of location service, which negates the advantages of using a low powered sensor. In the current version (1.1.2) there is a pause button, but as I'm removing that in 1.2.0 for something else, you could use Tasker to force stop the app to stop counting, and use Tasker to launch the app/quickly go home to start the counting service again.
hrm5023 said:
Good App! thank you for building something like this. I love the statement:
Low powered: Unlike other pedometer apps, this one will not affect your battery life at all.
If its not too much, can you also look into building an app for the always listening/touchless control feature that uses the low powered core? We have another thread with a bounty on this feature.
Har5h
Click to expand...
Click to collapse
Sorry, but I don't know a thing about using hardware specific features. I'm actually quite new to programming, this project is the first big thing I made.
Sent from my Nexus 5
fiftyclick said:
One of my biggest gripes is when driving, all pedometer apps keep counting. There is usually a pause feature or something similar, but it would be ideal if it could detect if you are driving or not. If this is not easily achievable, is there an intent or something else I can use with Tasker to control this app?
Thanks, and it looks really promising!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I don't think it kept counting when I was driving the other day. If it did it didn't count a lot.
Accuracy
Hey, has anybody made a accuracy test?
Thanks
Any plans to have this push results to something like FitBit or MyFitnessPal?
As for the driving thing, could you add an option for bluetooth device connected?
Example Interface:
Do not count steps if the following device is connected: (check boxes)
- Car Radio
- Headphones
- Phone Radio
- BlueTooth Headset
Do not count steps if plugged into a power source: (pull down)
USB
AC
Any
Disabled
In this way, you could set the device not to count steps if you are in your car (connected to your car radio via blutooth or maybe plugged into a power source).
I would think the power draw of these options would be in line with your design goal of keeping it to a minimum.
I have not used the app very long (pro version), does it keep track of history? An example would be a daily summary of steps/distance.
In this way, manually importing the information into other fitness trackers is easier.
Thank you for your consideration!
maddbomber83 said:
Any plans to have this push results to something like FitBit or MyFitnessPal?
As for the driving thing, could you add an option for bluetooth device connected?
Example Interface:
Do not count steps if the following device is connected: (check boxes)
- Car Radio
- Headphones
- Phone Radio
- BlueTooth Headset
Do not count steps if plugged into a power source: (pull down)
USB
AC
Any
Disabled
In this way, you could set the device not to count steps if you are in your car (connected to your car radio via blutooth or maybe plugged into a power source).
I would think the power draw of these options would be in line with your design goal of keeping it to a minimum.
I have not used the app very long (pro version), does it keep track of history? An example would be a daily summary of steps/distance.
In this way, manually importing the information into other fitness trackers is easier.
Thank you for your consideration!
Click to expand...
Click to collapse
What you say about charging and Bluetooth connected should be simple enough to add, I'll see if I can add it. History is also coming in the next version, here's a sneak peek at what I have so far
Of course, your full history will also be viewable and can be exported as CSV, although that part isn't quite done yet.
Sent from my Nexus 5
ickboblikescheese said:
What you say about charging and Bluetooth connected should be simple enough to add, I'll see if I can add it. History is also coming in the next version, here's a sneak peek at what I have so far
View attachment 2536576
Of course, your full history will also be viewable and can be exported as CSV, although that part isn't quite done yet.
Sent from my Nexus 5
Click to expand...
Click to collapse
Thanks for such a simple app. It worked fine for the first day. However, it's not working now. I have restarted phone, still same result. After first day in the night, i press pause button. Next day i pressed play, but it's not counting steps. Do you have any update coming out soon?
It works, and the UI is "clean" and easy, but the count is not perfetc... can't it be optimized?
matteventu said:
It works, and the UI is "clean" and easy, but the count is not perfetc... can't it be optimized?
Click to expand...
Click to collapse
It's difficult to differential a person physically shaking the phone versus actual walking. The fitbit series face the same problem as well
Sent from my Nexus 5 using Tapatalk
id4398 said:
Thanks for such a simple app. It worked fine for the first day. However, it's not working now. I have restarted phone, still same result. After first day in the night, i press pause button. Next day i pressed play, but it's not counting steps. Do you have any update coming out soon?
Click to expand...
Click to collapse
Try force stopping it, clearing data, rebooting, then launch it again and press start. It worked fine for me, not sure why that happened. But yes, I do have an update coming out soon, although I've been very busy lately and haven't had time to work on it.
matteventu said:
It works, and the UI is "clean" and easy, but the count is not perfetc... can't it be optimized?
Click to expand...
Click to collapse
Fixes to step count will be in next release, but not sure when that will be because as I said, very busy. Hopefully I can get it out before I leave for a band trip early February.
detdett said:
It's difficult to differential a person physically shaking the phone versus actual walking. The fitbit series face the same problem as well
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Do you mean it will also count shakes? That's normal, as how it counts by detecting the accelerate/decelerate patterns of walking. It just happens that you can replicate it by shaking. And that's not really a problem of the app specifically, I'm just catching events from when the sensor thinks it detects a step and then displaying that.
Couldnt make it work.. Will try again later tho..
Sent from my Nexus 5 using XDA Premium 4 mobile app
Same issues with the app picking up steps while driving as others have experienced. 20mile drive this morning, over 3000 steps.
Perhaps a simple logic could be if phone is charging then stop counting.
Other than that app seems pretty good, simple.
does it count miles/km , calories burned etc?
Introduction
Here is my contribution to this awesome device and community. This is a compass app. Once opened, it displays a full screen compass on the EPD, along with some useful sensor data, such as acceleration, pitch, roll, heading, brightness and battery details. It also has a helpful "bubble", which means it can be used to measure how level a surface is. Check the attachments for screenshots.
The application has been optimized to use minimal amount of power, and all the sensor data has been flipped accordingly to work as the device is upside down. Also, only one permission: access to backscreen. The app has been tested on the latest Lollipop. I don't know if it works on the older KitKat.
Download
You can download the application here: https://www.androidfilehost.com/?fid=24052804347773513
Installation
To install it, you must first enable unkown sources from your settings - security, then download the apk to your device and finally open it using a file manager. The application is launched from the back screen via it's own widget, which you need to add to some small slot from Yotahub.
Future plans
I might add coordinates and altitude in the future, but that will increase the battery use slightly because it requires GPS. Maybe I'll put it behind a setting or something. Feedback is always welcome!
Nice and good working!!
Very good - HeinMueck
My congratulations, very nice app for Yota.
Clipman said:
Introduction
Here is my contribution to this awesome device and community. This is a compass app. Once opened, it displays a full screen compass on the EPD, along with some useful sensor data, such as acceleration, pitch, roll, heading, brightness and battery details. It also has a helpful "bubble", which means it can be used to measure how level a surface is. Check the attachments for screenshots.
The application has been optimized to use minimal amount of power, and all the sensor data has been flipped accordingly to work as the device is upside down. Also, only one permission: access to backscreen. The app has been tested on the latest Lollipop. I don't know if it works on the older KitKat.
Download
You can download the application here: https://www.androidfilehost.com/?fid=24052804347773513
Installation
To install it, you must first enable unkown sources from your settings - security, then download the apk to your device and finally open it using a file manager. The application is launched from the back screen via it's own widget, which you need to add to some small slot from Yotahub.
Future plans
I might add coordinates and altitude in the future, but that will increase the battery use slightly because it requires GPS. Maybe I'll put it behind a setting or something. Feedback is always welcome!
Click to expand...
Click to collapse
Hi there, it was a damn good work of you. Thanks heaps. I downloaded this Apk on my YD201 Chinese origined mobile (with default Kitkat Rom) and cannot find the compass app anywhere. Can you tell me how to access it ?
app not installed
App does not install on the latest android marshmellow which undoubtedly every yotaphone2 user will want to be on
Hey Hey,
here is the new version of my heart rate app for the D5. Features are:
- Always On heart rate monitoring
- defining intervals and duration of heart rate monitoring
- turn heart rate sensor on/off
- show the sensor data on your watchface
- log Sensor data
- log Accelerometer data
- chart Sensor data
Here is the link:
1.5 beta: https://mega.nz/#!2tFhWBqC!FcmKdUblrOQiLDd-WRNmBOzhEZqWAEk6mp05Qulvy6s
SensorLib for D5:
https://github.com/fisch92/SensorLib
Old Versions:
1.4: https://mega.nz/#!e5FRFAgZ!3glFDXdyZrQrKtbh22h7qHTYJ3c-AeAg0osSLlapilY
Knowing Bug:
- Create the chart is a little bit slow
Next version:
- classify with the accelerometer data your activity
- do some stuff at custom activities (gesture detection)
I need your help:
- First of all I improved the hr measure or I hope it. Can you share your experience with me, because there are some other measure methods which supported by the hr sensor and I haven't other devices to test the accuracy
- Second I add accelerometer measurement. I want to classify your activity like google fit and also I want to detect custom gesture with this but I fear that this drains the battery too much. Tell it me if you notice this, please
Also I want to develop a library to make the usage of sensors easy for other Developers
fisch92 said:
Hey Hey,
here is my first Test with the heart rate sensor. Features are:
- Always On heart rate monitoring
- defining intervals and duration of heart rate monitoring
- turn heart rate sensor on/off
- read the sensordata from your watchface
Here is the link:
https://mega.nz/#!yxUgybBI!gzSeRBMUf1V10T_ilJ5TcvJ76qrClxieOGQdKBIQWVo
Knowing Bug:
- I think the app should build the mean of the heartrate over time to improve the current value. Actually it's a little bit volatile.
- Heart rate monitoring stops when display goes off
- Turn On/Off option is not working.
Next version:
- fix the Bugs
- log the Data into a Database on your Device
- chart Data
- will come soon
Click to expand...
Click to collapse
thanks for the thread, i downloaded the app to my pc and then copied it to Download folder on the watch and from the watch i tried to install it by opening it but it did'nt let me, since it is an apk file i did'nt extract it on my pc. i will download it again and see what will happpen. geat job hope others will follow you especially in the metter of better notification app that will include a way to answer calls from it.
Hey Hey,
here is the new version of my heart rate app for the D5. Features are:
- Always On heart rate monitoring
- defining intervals and duration of heart rate monitoring
- turn heart rate sensor on/off
- read the sensordata from your watchface
- log Sensordata
- chart Sensordata
Here is the link:
https://mega.nz/#!O9EWnRTQ!EgFhxvpK2TVSOmETOjBuuz9eUO-Q95zr7UtMvG8sfe8
Old Version:
https://mega.nz/#!yxUgybBI!gzSeRBMUf1V10T_ilJ5TcvJ76qrClxieOGQdKBIQWVo
Knowing Bug:
- Create the chart is a little bit slow
Next version:
- try to enrich heart rate Data (yesterday I ride my bike and I ride on a hill I needed no sensor to know that my heart rate is pretty high. So I looked at my app, it shows a hr of 54 I try the system app ... same result)
- add compass
Also I want to develop a library to make the usage of sensors easy for other Developers
Will this work with the X5?
caltomoto said:
Will this work with the X5?
Click to expand...
Click to collapse
I don't know, but I think it should work. You can try it and tell us your results
fisch92 said:
try to enrich heart rate Data (yesterday I ride my bike and I ride on a hill I needed no sensor to know that my heart rate is pretty high. So I looked at my app, it shows a hr of 54 I try the system app ... same result)
Click to expand...
Click to collapse
On my K8 R, D5 and X5, the HR is within 10-20 of actual. Sounds like you might have a sensor issue or there's a bug in the firmware. What are your results using different firmware?
Lokifish Marz said:
On my K8 R, D5 and X5, the HR is within 10-20 of actual. Sounds like you might have a sensor issue or there's a bug in the firmware. What are your results using different firmware?
Click to expand...
Click to collapse
Oh ok, I use Imperium W812a ROM v1.2.0. Also my Docking Station has a pulse of 72 actually :silly: maybe its a sensor issue
I make some little Bugfixes:
https://mega.nz/#!rtMhUSLD!pwiwKxbeOTcqA9tpazhDPwoKNlLkMpdpH2ZfeHS109w
fisch92 said:
I make some little Bugfixes:
https://mega.nz/#!rtMhUSLD!pwiwKxbeOTcqA9tpazhDPwoKNlLkMpdpH2ZfeHS109w
Click to expand...
Click to collapse
works great thanks.
fisch92 said:
I make some little Bugfixes:
Click to expand...
Click to collapse
In this latest version, display remains continuously on and if I remove it from Recent apps display turns off but then HR does not work.
Any luck getting it to run as a background service or getting the stock app to run in the background? Here's the thought, background service + "On Wake" trigger = HR updating on faces when you rotate your wrist to check the time. I haven't had my coffee yet so this thought is less detailed than usual..
the app does'nt drain the battery that much but the reading are off, i do'nt get a reading over 100 when i workout but i wonder if because of the HR itself and not the app, can someone with x5 or k9\k8 check? thanks
Lokifish Marz said:
Any luck getting it to run as a background service or getting the stock app to run in the background? Here's the thought, background service + "On Wake" trigger = HR updating on faces when you rotate your wrist to check the time. I haven't had my coffee yet so this thought is less detailed than usual..
Click to expand...
Click to collapse
I will fix it in next version
soniasophie9697 said:
the app does'nt drain the battery that much but the reading are off, i do'nt get a reading over 100 when i workout but i wonder if because of the HR itself and not the app, can someone with x5 or k9\k8 check? thanks
Click to expand...
Click to collapse
sounds like my problem the only moment my watch shows me a HR over 100 was before my bachelor exam but when I do sport the messure is always between 50-70. But this isn't because of my app or is it? Did you get the same values with the systemapp? Or maybe the ROM thich one does you have?
I was getting 40-50BPM resting rate from the app, which would be fine if I were an 18yo triathlete vs a 40-something stay at home dad after a double espresso.
fisch92 said:
sounds like my problem the only moment my watch shows me a HR over 100 was before my bachelor exam but when I do sport the messure is always between 50-70. But this isn't because of my app or is it? Did you get the same values with the systemapp? Or maybe the ROM thich one does you have?
Click to expand...
Click to collapse
wait...does it not also for workout? when i do my running? i had problems with the HR build in before it never showed me the right results after a workout, i thought it because just on light was green and it should be two but many said that it is the same on their watch with BT chest belt i do'nt have this problem.
Sorry, but these indications HR D5 for nothing suited.
Now, I ran on the treadmill. According to the indications (sensors in the handles) was 108-110. I checked the hand artery and was about 100. And our d5 65-71. Terribly underestimates. I think I will buy a normal sensor on a belt, because this is not what to trust. They made the sensor as a gadget rather than something useful.
A mistake of 5-15 would be ok, but so it's more like an oracle do you think it's a sorftware issue or a hardware issue. Had somebody here better experience with the hardware sensor? Maybe on other devices or other firmware or in special situation?
Actually the measure of my app is quite simple. It do the measure like the engineermode app and my app calc the mean over time and throw bad measure (hr of 0) away. But actually I don't know how the measure calculates the hr of the sensor data. Maybe this is improveable
I have tested not on your application. I did the measurement on the system application D5. But it probably would still be the same sensor error.
New Version is here:
https://mega.nz/#!e5FRFAgZ!3glFDXdyZrQrKtbh22h7qHTYJ3c-AeAg0osSLlapilY
What is new:
- remove WakeLock (Screen of Watch don't turn on by each messure)
- remove always on feature (if someone is worry about this, let me know )
For Developers:
https://github.com/fisch92/SensorLib
I build a library that make the usage of the hr sensor as easy as I can
The other sensors will be added later.