WheelLog Android App

[Seba]

55 minutes ago, GMOne said:

Wheellog has a bug about Ninebot maximum speed. Even though it is 58Km/h (in my case), it shows 50Km/h, and the slider from 50 to maximum always shows 50.

It's actually not a bug  When WheelLog was created, it was rather unusual to have a wheel capable of going at 50 km/h  I'll increase this limit to 70 km/h in next version. This should be enough... at least for some time

[Lefteris]

But the WheelLog can pass more than 50km/h data to the smartwatches that are supported.

[Seba]

1 hour ago, Lefteris said:

But the WheelLog can pass more than 50km/h data to the smartwatches that are supported.

And also displays this speed in details page and says in speech message. The only limit was a slider range, but I already extended its range to 70 km/h.

[GMOne]

On 5/22/2019 at 7:55 PM, Seba said:

It's actually not a bug  When WheelLog was created, it was rather unusual to have a wheel capable of going at 50 km/h  I'll increase this limit to 70 km/h in next version. This should be enough... at least for some time

I thought it was dinamically read from the unicycle. But it isn't. Ok! Let's change the XML.

I noticed that "General settings" becomes "Speed settings" when you enter into the menu. But it isn't only about speed...

Edited May 24, 2019 by GMOne

[Werner]

Hello, 

I've just installed wheel log on my cellphone and also wheel log for tizen on my Samsung S3 but all the informations are just showing 00.

But I'm connected with my Z10.

Had anybody else of you an issue like that?

Edited May 25, 2019 by Werner

[Lefteris]

Check connectivity with your watch.

 

[Planemo]

As Lefteris says - check the watch. I find that sometimes I have to re-start the watch and open the tizen app again.

Wheellog on the phone always connects really quickly to the Z though

 

[Werner]

Thx @Lefterisand @Planemo but I also have only just a list of 00 on my phone.

The app looks like I'm not connected but the shown wheel's mac code is right and every time I try to connect i hear the "connection-sound" of the Z10 and the wheel symbol an the top turns red, but nothing else happens. No data of the wheel are visible. 

Started my cellphone new, no effect. 

Edited May 25, 2019 by Werner

[Planemo]

Sorry Werner, I thought it was just the watch you were having problems with. Tap the wheel icon to turn it white. Then tap the bluetooth icon. The app should start searching and the Z should show in a list. Select the Z and it should hook up. Let us know the result.

Edit: plus you are using an old version of wheelog (you only have 3 tabs available at the bottom instead of 4) so this might be the problem.

Edited May 25, 2019 by Planemo

[Werner]

7 hours ago, Planemo said:

 Tap the wheel icon to turn it white. Then tap the bluetooth icon. The app should start searching and the Z should show in a list. Select the Z and it should hook up. Let us know the result.

Edit: plus you are using an old version.

I did exactly this procedure several times without success. 

Reinstalled the app, restarted all devices. 

Btw: I can find only the version 2.0.19 from 10.20.2018 on Google play and also here

https://m.apkpure.com/wheellog/com.cooper.wheellog#&gid=1&pid=1

[HermanTheGerman]

1 hour ago, Werner said:

 I can find only the version 2.0.19 from 10.20.2018 on Google play and also here

https://m.apkpure.com/wheellog/com.cooper.wheellog#&gid=1&pid=1

That's the reason, why it does not work.

Download 2.0.28 here, and check the page from time to time, because 2.0.30 will come soon, as @Seba wrote:

https://euc.world/getwheellog

Before you install the downloaded apk, you must uninstall the old wheellog, because update does not work.

Edited May 26, 2019 by HermanTheGerman

[travsformation]

@WernerI get it from time to time that my wheel connects but the readings (including battery) are not are all zero. Switching the wheel off and on and restarting the app (I force close it), a few times if necessary, usually does the trick. And once it's connected, it stays connected. That's my experience at least 

[Lefteris]

Maybe you have a Huawei phone?

[Werner]

I got it!

And as I suspected, is was on me:

I had a password in the ninebot app. 

Wheel log could not work with it.

Thx @HermanTheGerman for the link, now I've the newest version!

Thx to all for your effort. 

Edited May 26, 2019 by Werner

[Lefteris]

OK that was something so we should add that to the list of non working connections cause of the password.

Is there any chance to get password working for Z series wheels?

maybe @MRN76

can help?

[toggeli]

On 5/26/2019 at 11:31 PM, Lefteris said:

OK that was something so we should add that to the list of non working connections cause of the password.

Is there any chance to get password working for Z series wheels?

maybe @MRN76

can help?

Which wheellog version do you use? I have a ninebot one S2 and passwords work fine with 2.0.28 and 2.0.29 at least (I think the protocol should be the same for all ninebot wheels)

[Werner]

I've now version 2.0.28 and you're right:

It worked well with my ninebot One S2 but not with my Z10 until I tried it without the password.

[Seba]

2 hours ago, Werner said:

I've now version 2.0.28 and you're right:

It worked well with my ninebot One S2 but not with my Z10 until I tried it without the password.

One S2 and Z10 uses different protocols and this is why password-protected Z10 won't communicate with WheelLog.

[Lefteris]

Is there anything to probe so it can help you get the Z10 working with password?

[Seba]

I've prepared "beta" version of upcoming 2.0.30 release of WheelLog. As there are many changes and new features, I release this "beta" for those of you that want to be the first testing new features and provide feedback that will help me to remove any issues and bugs. As this is "beta" version, please keep in mind that new features are not translated yet from English. It is also possible that this version will have some flaws that will negatively impact your user experience. So if you are happy with 2.0.28 and don't wanna be a "guinea pig", plesae stay with 2.0.28 and wait for final release. But if you decide to use this beta, please let me know about your experiences. If you don't notice any problems, also let me know about it.

And once again - this is not final release! This is only a development, "beta" version intended for testing. It may contain bugs, be unstable etc. 

 

Download link: 

• https://euc.world/downloads/wheellog-eucworld-2.0.30beta1.apk

Some of features added:

1. Speed and distance correction. You can now apply corrections to wheel speed and distance values. It's especially useful for KS-18L/XL owners, as these wheels have tendency to inflate readouts by about 20%. So if you want to have wheel readouts as precise as possible, you can make corrections. Usually, both correction should be the same as speed is just distance in time. But there is a warning - use this option wisely. It will affect all wheel speed and distance readouts, but won't scale alarm speed values. So if you have set speed alarm (I mean WheelLog alarms, not wheel beeps) to 30 km/h and then set speed correction to -18% (typical correction for KS-18L/XL), this will cause alarms to be triggered on corrected speed. As it will drop to 25 km/h, speed alarm won't be triggered. So if you want to get real speed, when applying corrections change speed alerts accordingly. It's also a good idea to left speed correction untouched (at 0%) and apply only distance correction (-18% for KS-18L/XL). In this way speed will be consistent over WheelLog and KS app, but distance will be corrected to reflect real distance. Personally, I got used to inflated speed readouts and left it as is, but find correction of distance very useful.
2. Disable voice messages when Bluetooth audio is not connected. I use voice messages everytime I ride, as they keep me informed on speed, distance, battery etc., but most important thing is that I always get instant speed alert when I go above my preset limit. But when I finish my ride, first thing I do is to turn BT headset off. Previously this caused all the messages to be played over phone speaker, so anyone near me would hear it. Now when I switch off my BT headset, voice messages are muted. Speed/temperature/current alerts are not affected. Also quiet periodic beep on wheel connection problem will be still active.
3. Disable BT & GPS status voice messages. It's rather self explanatory. If you experience frequent wheel reconnection, you may be bothered by constant "Wheel connection lost" / "Connected" messages. You can disable them. This setting doesn't disable quiet periodic beep on wheel connection problem that will be still active.
4. Notification when app update is available. I notice that there are users still using some old versions. This may cause some issues that may become serious over time, as I constantly change and expand euc.world API. This should help all users to be consent about new versions available.
5. Periodic messages using tour data when wheel data unavailable. If you have tour started and there is no wheel connection active, you'll still get periodic messages about your ride progress. In this case speed and distance will be GPS-based and the message will be preceded by high-pitched info beep tone instead of usual, low-pitched info tone. This will let you easily distinct between wheel-based and GPS-based messages. This is an option for all of you using WheelLog with unsupported wheel, but will also help to keep track of tour progress even if  wheel is disconnected for any reason.
6. Improved euc.world experience. There are many individual changes here, so I won't go into details. You can for example choose to automatically start tour on wheel connection and finish tour on wheel disconnection after preset delay. Changed buttons orientation helps to use device both in landscape or portrait orientation. Added icons notifying about problems with network and GPS and when image upload is active. Etc. etc.

Known bugs and limitations:

1. New features are currently in English only.
2. Changing settings during ride may reset ride time, distance etc. I discovered this issue today, so I don't know the cause yet and I'll be looking for it. Probably this issue existed in all previous versions, but left unnoticed.

There are also many other features, changes and improvements. This includes user interface, extended speedometer range, better Rockwheel compatibility, relaxed BT connection state criteria that should prevent constant reconnection in some cases etc. When I'll publish final 2.0.30, I'll also post a video with detailed explanation of all the new features of WheelLog. It's easier to show than write about

[Unventor]

Hi @Seba, is it possible to have Wheelog connected to the wheel and have voice readout to eg a BT comm unit connected to the phone running Wheelog?

I can't seem to get it to work. 

[Lefteris]

37 minutes ago, Unventor said:

Hi @Seba, is it possible to have Wheelog connected to the wheel and have voice readout to eg a BT comm unit connected to the phone running Wheelog?

I can't seem to get it to work. 

I was about to test this out today cause I also use a left earpiece for comms

[Seba]

47 minutes ago, Unventor said:

Hi @Seba, is it possible to have Wheelog connected to the wheel and have voice readout to eg a BT comm unit connected to the phone running Wheelog?

I can't seem to get it to work. 

Hmm, this should be possible as this is one of the main scenarios - WheelLog connected via Bluetooth Low Energy to the wheel and at the same time all voice messages going to Bluetooth audio. Both BLE and BT audio works independently and simultaneously. However your BT headset needs to support A2DP profile. I'm not sure (didn't tested) if BT device that only supports BT headset profile (HSP) will work. Probably not. But most BT comm devices supports both headset profile and A2DP audio profile. Maybe this is only a matter of some settings or something? When you enter Bluetooth settings for paired BT devices in Android settings, there should be a checkbox with "Multimedia audio" or similar for your BT comm.

Would you give me information about make and type of your BT comm?

[Lefteris]

On the Z10 when i ride alone at the beach roads i tent to play music thru the media connection (a2dp) to the wheel, there are 2 kinds one for the app and one for media playback and/or calls (non usable)

If i use the voices thru bluetooth i hear them thru the Z10 speakers, it lowers down the music that is currently playing, says the phrases and then restore the volume level of the music i was playing.

It would be great in a scenario like mine that i play music in the Z10 but forward calls from the bluetooth headset, i choose media audio to the Z10 and calls to the headset, when i receive a call the music stops on the wheel but i can talk using my left headset earpiece. After i'm finished and the call ends, music resumes automatically!

I'm hoping to get the notifications on the headset as per calls connection instead on the wheel as media connection. 

But this scenario is only doable if the owner has a phone that supports dual bluetooth devices connection, like me on the samsung s7 edge, that can separate media audio from phone calls audio.

[Seba]

7 minutes ago, Lefteris said:

It would be great in a scenario like mine that i play music in the Z10 but forward calls from the bluetooth headset, i choose media audio to the Z10 and calls to the headset, when i receive a call the music stops on the wheel but i can talk using my left headset earpiece. After i'm finished and the call ends, music resumes automatically!

In general, I don't use my wheel as a BT speakers. Instead I use Sena 10S helmet communication set, that works exactly as you describe. When I play tunes from Spotify, its volume is lowered during voice message then restores to normal. But when I answer the call, both music and voice messages are muted during entire call. Previously I used Aftershokz Trekz Titanium and it worked the same way.