Search results for:

@Gordon. The Custom font converter is great but it means you have to create seperate functions for each size of the font. I am wondering if there could be the possbility of selecting a replacement Vector font from font.google.com ? What I have in mind would be the ability of the user to add a module (or code) created by a converter tool that would allow a user to have an alternative Vector font. Then in settings the user could select a setting 'Custom Vector Font' rather than the system Vector font.

I played around with Gadgetbridge and managed to get missed calls notified on my bangle 1.
Had zero success with Bangle 2. Gadgetbridge would not reliably install on Bangle 2.
The App Loader would say it had installed and then there would be no settings menu for it.
I did install the files manually but still could not get a connection.
Using the latest Gadgetbridge Android app from F-Droid, found the App hangs an aweful lot.
Noticed comments about not selecting pair.

The Gagetbridge on B2 seems a bit flakly at the moment.

Moving the arrow into the same line with the menu title

I've not really figured out what this arrow does :(

Issue with larger font is the line length.

Options are
1) narrower spidery font - not a fan, they log butt ugly
2) when the line is selected the TEXT could be aligned to the end of the line showing the other half
3) When line is selected it could auto scroll as in ticker tape.
4) The lines just become menu headings and the selection of the setting itself is done in sub menu's.

My preference would be 4 as it is visually consistent.

I'm not sure I would like the concept of a very long press it would quickly get confused with a long press.

I think on a Bangle 2 I would say long press should be reset as per BTN3.
But single press when in showMenu could be back as that would be very helpful.

Here's where I got to with a quick hack.
Using setFont("Vector",20) and fontheight=20 (Bottom screenshot)

This shows that you can get 6 lines on a full screen with a font height of 20 and its much more readable.

However this is not allowing for the setting of the value eg Show/Hide, On/Off. But that could be in a standard submenu rather than trying to show it on the same line. Other watch menus take that approach.

I also tried Lato20 (Middle screenshot)
and Inconsolata20 (Top screenshot) from fonts.google.com
I think I like Lato20 the best.

// save E_showMenu_Q3.js as hackmenu.js and change fontsize to 20 and setFont("Vector",20)
var hackmenu = eval(require("Storage").read("hackmenu.js"));

var m = {
  "" : { "title" : "Settings" },
  "Make Connectable" : function() { LED1.set(); },
  "App/Widget Settings" : function() { LED1.reset(); },
  "BLE" : function() { LED1.set(); },
  "Debug Info" : function() { LED1.reset(); },
  "Beep" : function() { LED1.set(); },
  "Vibration" : function() { LED1.reset(); },
  "Quiet Mode" : function() { LED1.reset(); },
  "Locale" : function() { LED1.reset(); },
  "Exit" : function() { }, // nothing for now
};

hackmenu(m);

there is no such swipe up and down.

Sorry I mean't on a Bangle 2 this is supprted. I can drag my finger down the screen and the selection changes as I swipe it downwards. Same in the up direction.

swipe left as back
swipe right as select

Yeah - I like that idea.

We already have swipe up, swipe down to move the selection so I would not want to change
that to touch left and right. In general I feel quite nervous about having to touch something as it can easily go wrong and feels awkward to do.

I'd like to see the Back option awlays being the first option as when you return from a lower grouping it is always the first option that is selected.

Thanks - good to know.

Is it possible to hack the font in ShowMenu to support some experimentation ?

Nice - whats that clock called Gordon ? Looks very funky.

Been messing about with custom fonts and themes and how they work across a Bangle 1 and Bangle 2. New clock app called Pastel on its way soon. Supports Bangle 1 and Bangle 2 Light and Dark themes and has a settings menu so you can chose from 5 different custom fonts.

>g.theme.fg
Uncaught ReferenceError: "fg" is not defined
 at line 1 col 9
g.theme.fg
        ^
>
>g.theme
={ fg: 0, bg: 7, fg2: 1, bg2: 3,
  fgH: 0, bgH: 3, dark: false }
>
>g.theme.bg
=7
>g.theme.fg
Uncaught ReferenceError: "fg" is not defined
 at line 1 col 9
g.theme.fg
        ^
>g.theme.fg2
=1
>g.theme.fgH
Uncaught ReferenceError: "fgH" is not defined
 at line 1 col 9
g.theme.fgH
        ^
>g.theme.bgH
=3
>

Thanks - I can confirm I can use the TAP mechanism and it works well.
My only issue is reading the text, even with reading glasses the contrast and size is hard to read.
I have started a new thread for a separate discussion.

Starting a new thread from a discussion around the thickness of the menu item lists in the Bangle 2.
They are possibly a bit thin and hard to use.

If find the text too tiny to read, even with my reading glasses on.
Navigation works well using swipe up / down and you can select an option that is highlighted just by tapping the sceen somewhere else. So my main complaint is not being able to read the text.

Personally I never change Make Connectable and find it really annoying that I keep hitting it when trying to exit Settings. The top option definietly needs to be BACK for a quick exit when you return from a lower level menu. Be interesting to see what others think.

I wondering if we could have a tidy up of the settings App.
Here is my proposal for regrouping related settings.

Also I propose that BACK is the first option of every sub menu.
This way it makes it much easier to go BACK BACK BACK BACK and exit settings with the minimum of button pushes and navigating up and down.

BACK

• App / Widget
  BACK
  etc
  etc
  
• Communications
  BACK
  Make Connectable Y/N
  BLE
  Programmable
  HID
  Passkey Beta
  Whitelist
  
• Notifications
  BACK
  Debug Info
  Beep
  Vibration
  Quiet Mode
  
• System
  BACK
  Locale
  Default Clock
  LCD
  Theme
  Reset Settings
  Turn Off
  BACK
  

Add layout.rerender - so you set modified:true

This will still require the developer to keep a prevVal to compare against.
I'd much rather the layout manger figured out when an item had been changed / not changed.
It would make the apps much easier to write.
Also on the B2 I have noticed you dont get flicker so you can code as if its not a problem.
On the B1 you either have to use buffered screen writing (uses CPU) and memory or minimise flicker by shadow variables for the previous value to compare against.

You just drag your finger up and down to scroll the selected item, and tap to select.

Yes, done the scrolling bit but assumed that the tap had to be on the actual menu item. Its pretty nerve racking when you want to select VIEW and the option below it is ERASE or DELETE though.

realistically you'd only be able to have maybe 3 menu items on a screen

Currently there are 8 lines of menu items but they are hard to see and select.
Could the thickness be configurable ? And the text adjust to the thickness ?
EG select 6,5,4 menu items per scoll window ?
The TEXT is so small that you need a magnifying glass to read the text sometimes.
I would not mind scrolling a bit to get to the option I wanted and the list was easier to READ.
It feels very awkward at the moment.
I think this is general problem with Smart UI design.
The AmizFit watches tend to go for 4 lines in a list , scrollable / readable.

I guess this discussion belongs in a seperate thread.

Was there any more information?
Do you know wich app was installing at the time?

You could try installing the apps one by one.

but this is all looking really promising now!

I think we have reached the point now where we have a credible - but not perfect step counter.
Its 98-100 accurate for walking. Not so great in other non stepping scenarios.
But its acceptable when sleeping, not counting at all when sitting typing, watching TV etc.

Improving it further would require a much more complex algorithm, but we now have a good baseline if someone facies taking it to the next level. Be really interesting to see what others think when 2v11 gets released - assume that is sometime away as you have only just released 2v10 ?

Just tried accelog. Problem solved.

It is just about usable on a B2 through the touch screen.

The problem is that the font for the list menu's is so small you need pin point precision with your finger poking to invoke the right option. I think we need at least double the font height for the list menu's. The problem will then be the horizontal space to get the TEXT in. So maybe the list needs to be spread out a bit so that the available touch area to select the option is a bit larger. I guess these will all be discussed over the coming weeks as we gather experience of the B2.

Yes that works.
But what I am doing is

• writing test on my Chromebook storage.
  
• Clicking the FileSystem icon in the IDE
  
• Selecting upload file.
  
• Navigate to the file on the hard disk, select the file
  
• Change the name to test
  
• Upload it to the Bangle
  
• Then open the IDE FileSytem to browse the files.
  
• Look at the file 'test' and all it has in it is 'require("Font7x11Numeric7Seg"); '
  
  

Now if I attempt to run that file from the Run option it causes the exception.

I tend not to use the RHS of the IDE as its faff to save my work to disk all the time as it can only download to code.js. So tend to edit in Emacs and then load the changed file through the IDE.

I did see this loading and hanging behaviour when I tried to install the 7x11Segment font file - for a test app.

Last night I uploaded the boot loader and got a hang but recovered after deleting the 7x11Segment.
The s7clk work fine on both bangles.

Getting early test results now against the 2.10.27 firmware that has the full implementation of the step counter in it. Also using the upated widpedom.

SLEEP Amiz 8, 2.10.27 89

• DRIVE Amiz 3, 2.10.27 136
  
• WALK Amiz 3070, 2.10.27 3046 (99.1%) accurate on the walk
  
  

Added logs for the the DRIVE and WALK and into the test harness.
The results validate the test harness and point to the differences with the javascript version.

X_STEPS = 6, RAW_THRESHOLD = 14
File, Expected, Simulated, Diff, (Orignal)
HughB-walk-a3070-b3046.csv, 3070, 3013, -57, (1909)
HughB-drive-a3-b136.csv, 3, 124, 121, (535)

If you look at the walk results, the simulated value of 3013 its actually only 33 steps off the value
measured on the physical device. This gives a lot more confidence in the test harness, and suggests caution with the javascript version in future.

Going to leave everyone in peace for a bit as on holiday next week :)