I was great pleasure to take part in European Canopy Formation [1] at SkyCamp [2] Polska 2017! So many experienced and relaxed people, so much fun, and so much development (I was part of CRW-16-DIAMOND). Thank you!! Hope to see you soon folks! :-)

I am also happy to announce that I had become a website editor and administrator :-)

[1] http://europeancanopyformation.eu/
[2] http://www.skycamp.pl

I am gearing up and starting a new adventure. I have just bought my own PD Lightning 176 canopy dedicated to CRW/CF [1]. Thanks to Simon and the “Lost in Space” crew first jumps were really awsome and safe. Thank you guys! :-)

[1] https://en.wikipedia.org/wiki/Canopy_formation

I just did a self-assembly of JTAGulator. This simple and amazing device indeed works and shortens JTAG pinout search from days to seconds. AMAZING! I have some spare devices to sale cheap in EU, if you want one let me know! :-)

JTAGulator is an open source hardware tool, created by Joe Grand / Grand Idea Studio, that assists in identifying OCD connections from test points, vias, or component pads on a target device. All you need is a target device, bunch of tap wires / cables, USB-Mini cable, and serial terminal to operate JTAGulator.

On-chip debug (OCD) interfaces can provide chip-level control of a target device and are a primary vector used by engineers, researchers, and hackers to extract program code or data, modify memory contents, or affect device operation on-the-fly. Depending on the complexity of the target device, manually locating available OCD connections can be a difficult and time consuming task, sometimes requiring physical destruction or modification of the device.

Sometimes you need to perform a network installation (i.e. when no USB or DVD drive is allowed to boot, but you can boot PXE). In case of FreeBSD you can use DNSMASQ to serve the DHCP that will assign the initial client address and configuration along with PXE boot image served over tFTP. At this point you will have bootloader running, so you can serve filesystem over NFS to obtain working environment and/or the installer..

• Create a directory that will hold the target filesystem over network. In my case that was

  /usr/local/tftp/FreeBSD

• Put OS/Installer files inside above directory

  cd /usr/local/tftp/FreeBSD
  wget http://(..)/file.iso
  7z x file.iso

• Edit /etc/exports to export the filesystem over NFS

  /usr/local/tftp/FreeBSD -ro -alldirs -network 192.168.0.0

• Install the dnsmasq

  pkg install dnsmasq

• Setup the /usr/local/etc/dnsmasq.conf

  enable-tftp
  tftp-root=/usr/local/tftp/FreeBSD
  
  dhcp-range=192.168.0.50,192.168.0.60,255.255.255.0,1h
  dhcp-boot=boot/pxeboot
  dhcp-option=option:router,
  dhcp-option=option:root-path,/usr/local/tftp/FreeBSD
  

• Restart services

  service nfsd onerestart
  service dnsmasq onerestart

• In case you get bootloader running but troubles with NFS make sure that mountd is running. Also you can see who is using the NFS shares with

  showmount -a

PXE Boot always use initial DHCP/tFTP to fetch configuration and bootloader, so the first stage is similar and should work with other Operating Systems and Bootloaders as well, the rest is up to bootloader itself..

It is my great pleasure to inform you folks that, almost after four years, I did a new release of LibSWD-0.7 [1], a low-level embedded systems access open framework. Special thanks goes to Andrew Parlane of Carallon Ltd [2] for his much appreciated contributions! Well now I feel like I need to invent some nice small device based on ARM Cortex-M0 CPU :-)

[1] https://github.com/cederom/LibSWD
[2] http://www.carallon.com/

Each big failure makes me more calm. Strange.
#cogito

If you want to install additional Python [1] modules inside your Blender [2] environment, you can install PIP using this recommended script [3], then use PIP to install all modules that you want. Note Blender’s Python Virtualenv location is /path_to_blender/blender_version/python/bin/python and you need to use this particular interpreter to launch the script.

[1] https://www.python.org/
[2] https://www.blender.org/
[3] https://pip.pypa.io/en/stable/installing/

Python 3.6.0 NumPy and SciPy from MacPorts crash on import bug [1].
[1] https://trac.macports.org/ticket/53453

Google have implemented my idea to make Google Books TTS work like an audio player – it can now work in background and being controlled with bluetooth headset – so I can play, pause and rewind paragraphs of the book read by speech synthesizer just as it was music. This is soo fantastic!!

I have been proposing this solution to Amazon to implement in Kindle for Android, but for years they did not listen. I have switched to Kindle application after Amazon bricked my Kindle3 3G reader with a software update (and all other devices worldwide). Now I just wait until Google Books allow to import my Kindle library, and I will never go back to Kindle. Greedy loses twice.

I have recently started the OrangeADE project [1], that is Orange Autonomous Device Evaluation, an online platform to evaluate security level of network equipment and verify against known vulnerabilities. OrangeADE is released as Open-Source under the “new” 3-Clause BSD license. Enjoy the work in progress! :-)

[1] https://github.com/CeDeROM/OrangeADE

You just need to see this awsome Mars Curiosity [1] simuluator [2] made by NASAJPL [3] with Blender3D [4] Blend4Web [5] HTML5 [6] WebGL [7] Free and Open-Source Software :-)

[1] https://www.nasa.gov/mission_pages/msl
[2] https://eyes.nasa.gov/curiosity
[3] http://www.jpl.nasa.gov
[4] https://www.blender.org
[5] https://www.blend4web.com
[6] https://www.w3.org/TR/html5
[7] https://www.khronos.org/webgl

Blender 3D can work with DualShock4 Playstation4 wireless controller over Bluetooth [1].

[1] http://www.blendswap.com/blends/view/78315

Use advanced features of your Synaptics Trackpad on a laptop running FreeBSD [1] with:

• set in /boot/loader.conf:

  hw.psm.synaptics_support="1"

• set in /etc/rc.conf:

  moused_enable="YES"

• set in /etc/X11/xorg.conf:

  Section "InputDevice"
      Identifier      "Mouse0"
      Driver          "mouse"
      Option          "Protocol"      "auto"
      Option          "Device"        "/dev/sysmouse"
      Option          "ZAxisMapping"  "4 5 6 7"
  EndSection

If you want to have “MacBook” like two-finger scrolling along with other parameters you can set in /etc/sysctl.conf:

hw.psm.synaptics.min_pressure=16
hw.psm.synaptics.max_pressure=220
hw.psm.synaptics.max_width=10

hw.psm.synaptics.vscroll_hor_area=1300
hw.psm.synaptics.vscroll_ver_area=-600
hw.psm.synaptics.vscroll_min_delta=50
hw.psm.synaptics.vscroll_div_min=100
hw.psm.synaptics.vscroll_div_max=150

hw.psm.synaptics.weight_current=3
hw.psm.synaptics.weight_previous=6
hw.psm.synaptics.weight_previous_na=20
hw.psm.synaptics.weight_len_squared=2000

hw.psm.synaptics.div_min=9
hw.psm.synaptics.div_max=17
hw.psm.synaptics.div_max_na=30
hw.psm.synaptics.div_len=100

hw.psm.synaptics.margin_top=200
hw.psm.synaptics.margin_right=200
hw.psm.synaptics.margin_bottom=200
hw.psm.synaptics.margin_left=200

hw.psm.synaptics.window_min=4
hw.psm.synaptics.window_max=10
hw.psm.synaptics.multiplicator=10000

[1] https://wiki.freebsd.org/SynapticsTouchpad

If you want to use NTFS volumes on FreeBSD [1], you need to use FUSE infrastructure andNTFS-3G [2] port. Syntax of fstab is a bit differen in this case:

/dev/ntfs_partition /mnt/ntfs_mounpoint fuse rw,locale=pl_PL.UTF8,mountprog=/usr/local/bin/ntfs-3g 0 0

Also remember to put fuse_load=”YES” in /boot/loader.conf and install the sysutils/fusefs-ntfs port. Do not use hibernated volumes.

[1] https://www.freebsd.org
[2] https://www.freshports.org/sysutils/fusefs-ntfs

If you happen to get a nice laptop with a powerful graphics card, such as polish HYPERBOOK SL502VR [1], it is highly probable that you will use UEFI boot mode. In that case you need to use SCFB [2] driver instead of VESA. Use the xf86-video-scfb package to get Xorg running.

Hybrid Graphics at first used MUX device that did a LCD connect to a selected video card on boot. Nowadays both cards use common Video Framebuffer [3] to draw over a screen. The simple video card (Intel in my case) is always active, while the more powerful and power consuming video card is started on-demand (nVidia in my case). This however requires a dedicated DMA BUF implementation, which is not yet available on FreeBSD, so none of the cards can see any monitor connected, resulting in “No Screens Found Error” from Xorg.

I have already reported a bug/feature request to nVidia. Also developers of FreeBSD are working on the Hybrid Graphics implementation.

[1] http://sklep.hyperbook.pl/hyperbook-sl502-vr-p651rp6g-gtx-1060-p-25965.html
[2] https://wiki.freebsd.org/Graphics/SCFB
[3] https://en.wikipedia.org/wiki/Framebuffer

I am really unhappy that Google’s Android 7 started living with its own life against its user will. Android 7 will turn on and off Bluetooth connectivity on its own and scan the area itself, even that you turn off the Bluetooth device by hand. It looks that you have no control over your own phone anymore! Shame on you Google! Really poor design idea :-(

Update: I have reported this issue to Google Security Team, they got interested, so this does not seem to be a “standard feature”.. maybe a phone design flaw or firmware/microcode bug..

Google Chromecast is a device that allows you to stream audio-video content over WiFi network from Application to a HDMI enabled display. This works really nice when you want to watch Netflix or show some movies from your mobile device on large screen TV/Projector.

Recently, Google released a new line of Chromecast devices that support audio only and higher resolution displays, renaming Chromecast to Google Home. This rebrand also replaced mobile application for devices management. New application forces user to have working internet connection, use localization, and sign with google account in order to work. There is no way to roll back to old application. Not really cool.

I have found and reported one nasty bug in this new Google Home application (version 1.19.29), that prevents you from discovering and setting up old Chromecast devices after Factory Defaults Reset or WiFi password change (so it can connect to your WiFi again). I only have old device so I am not sure how this affects new devices. You will not be able to discover your Chromecast device over WiFi when Localization Services are disabled and according permission was not granted!! In order to connect to your Chromecast:

• Reinstall or clear application data/cache.
• In startup configuration wizard you must grant access to localization services. If you do not enable localization and allow it to work granting permissions, you will not find your Chromecast later on.
• Search now for a Chromecast device still in setup wizard, you will find it, only if you did previous step correctly.
• Note that when you find a device that way, you can skip sign in with google account.
• If you do not grant localization permissions you will not be able to detect your chromecast device anymore.

I hope this has nothing to do with killing old line of devices with a software update. I also hope Google will fix this issue in next releases and they really don’t force users to give up so many personal information (why do they need GPS/Bluetooth running for a simple WiFi connection otherwise)..

Created a FreeBSD Port for Google Protobuf version 3.1.0 :-)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214957

Starting up the Configuration Reference Manual for Ultimaker CURA 3D printing Open-Source software :-)

https://github.com/Ultimaker/Cura/wiki/Cura-Configuration-Reference-Manual

Why only NEXUS devices are sensible choice for Advanced Android Users and Developers? Because NEXUS device vendors provide source code and device drivers.

This makes is possible to re-compile and re-create any customization of the Android by advanced users and developers. The most popular among them is CyanogenMod based on AOSP (Android Open Source Project).

Why is such customization really necessary? Because Vendors does not keep up with the Android development, their releases are flawed, contains unwanted modifications, quite often development is abandoned just after product release.

I know that Drivers Development is time and money consuming task for Vendors. Still, providing source code for device drivers would make it possible to run alternative and/or customized OS, also prolong device life for second-hand users in poor countries. Vendor sells the device anyway and Users can make fixes and customization. Why this Win-Win scheme is so hard to achieve in reality? Is really enforcing sales with mass garbage so important?

Another HALL OF SHAME entry goes to Google for missing reliable Voice Dial functionality. It is over 5 years of bleeding edge development of Android, thousands of people in the most powerful IT corporation on this planet, most advanced Text-To-Speech and Speech-To-Text engines available, and still, no reliable Voice Dial function. People that use phone to work simply need a Bluetooth or Wired Headset that is able to correctly dial a designated phone number they want to make a call. These are daily work basics. Learn from Apple iPhone. Until these basic functionalities are provided first I see no reason to introduce thousands of not-yet-working or never-working-will-one-day-fix stuff that only create false image of endless possibilities, potentially, but not at all functional in the real world scenarios..

I have Accessibility, Text-To-Speech, Voice-Input, OK-Google, Google Search, Handsfree, Voice Dialer, Google Voice Typing, Offline Speech Recognition, Bluetooth and Wired Headset Support. Still, it is impossible to dial a phone number via Headset that would not involve touching the phone. Really sad :-(

Update: After several days of struggle (using unsupported flashing tool and ripping the firmware from an official software that declined to work) I have managed to run Android 6.0 (7.0 is already out) on my mobile. Here Google seems to have replaced “Voice Dial” application with “Google Search” and now you can ask Google to dial a number for you. Well, it only works when you are online, and now Google knows exactly what you do all the time. What a breakthrough! ;-)

I have recently bought Xperia M5 mobile phone (400EUR) and SBH54 bluetooth headset (100EUR) both from Sony. W was previously happily using cheaper Xperia Z1 Compact mobile phone (250EUR) and Motorola HT820 bluetooth headset (30EUR). I DID NOT EXPECT TO GET SUCH A CRAP FROM SONY!

Xperia M5 D6503 has several issues that makes it a phone for a child, at most, including Bluetooth Headset problems that makes it impossible to talk, UTB OTG problems, no MHL support (HDMI-over-USB), no Cardboard VR support, no Repair from Xperia Companion for unlocked devices, and many more. This is NOT a phone for a developer not even to the working person, just a crappy toy. I consider ALL XPERIA “M” SERIES AS JUNK! The only sensible well designed both hardware and software seems to be “Z” series, maybe “X”, DO NOT WASTE TIME AND MONEY ON XPERIA “M” SERIES.

SBH54 Bluetooth Headset looks really promising “wearable assistant”, but at the moment it cannot really work well with one device, not to mention offered multipoint (only two peers at most!!!) connection that worked well in older devices. For instance I had no problem with 10 year old Motorola to listen MP3 from a computer and have a phone ready to talk in the same time which is not possible with SBH54. I only get frustrated with this crap, and other users as well complain on your official forum. This device is still a pure chaos and works unpredictably. Cannot really perform its basic function “headset” with Xperia M5. Android application does not work as Service and disappears when you need it most. You need to pair it again with the same devices after poweroff. Headphones sound it very good but they break apart. Its not really useful nor reliable in any way at the moment. Hope it gets a firmware update soon and I could take it out from the trash.

This is really sad because hardware looks very well for both devices. In theory parameters and functions look fine as well. However, Software/Firmware makes it useless buggy annoying junk. Shame on you Sony for releasing such a buggy junk! I am happily placing Sony, XperiaM5 and SBH54 into HALL OF SHAME, with no respect to those two unfortunate failures. Time-To-Market is not worth the Respect and Customers that you loose.

World is now at point now where companies release happily a new product that is still at early prototype stage and don’t even give a shit about that.. people loose time and money for this crap..

Note: After all struggle and years of play with Android I consider only NEXUS to be sensible and reasonable choice to work with. Sorry.

Sony Xperia phones are my favorite. Very good and durable electronics, amazing photo camera, nice utilities on top of standard Google Android OS. I have also always respected Xperia for allowing users to unlock their phones for Open-Source Firmware Customization on this amazing hardware..

Unfortunately, Sony seems to have this habit to make a bad decisions, so amazing hardware is not always followed with a good software. This is why Open-Source Customization is so important. I have already found several nice devices with a really bad firmware. What is more, this corruption seems to spread, and Sony blocks factory firmware restore for an unlocked devices with their official Xperia Companion utility. This means unlocking a device does not only Voids a Warranty, but also silently makes it Impossible to Go Back to a Stock Firmware! This is really bad idea.

Luckily smart people tends to predict and help each other out. Developer team of Sony Mobile released EMMA utility (nice name by the way) that allows you to re-flash mobile that is unlocked in case something goes wrong or you simply want to get back to a stock firmware.

Open-Source Firmware Customization will become a standard, even for large enterprises, with mutual benefit to their customers, because looking at the big picture we are part of the same eco(no)system..

It was fun to take part in NXP Technology Days 2016. Last year fusion of Freescale into NXP looks good, lots of useful solutions and possibilities gathered in one place. Very interesting On-Chip Security Mechanisms for Embedded Systems and Open-Source implementations for i.MX6 CPU family. Let’s hope that (probably upcoming) fusion of NXP into Qualcomm will not affect Open-Source Community in a bad way..

My request for base DHCP Client options parsing was partially implemented.

If you happen to work on OSX with MacPorts and GPGTools using SmartCard for SSH then installing OpenSC (0.16.0 in my case) will break your smart card access for GPG/SSH. If you remove OpenSC with an uninstall utility things get back to normal.

It is my pleasure to be part of organizing committee and scientific board of this cyclic international conference on Telemedicine and eHealth arranged by Polish Telemedicine and eHealth Society. You can click image below to see the full conference program.

Today is my last day with HBO in Poland. I could not even imagine how bad can commercial mobile application be until I found HBO GO PL Android. This is such FAIL that I am not going to pay anymore for this crap. I have waited over a year for things to get better. I bet most of the 5 star ratings are fake. You don’t give a shit about user feedback, so users will to the same with you. Goodbye HBO..

On the other hand Netflix has just entered Polish VoD market with a far better application. They responded to my feedback in less than minute and implemented suggested (localization) changes in two days. Now that is good cooperation! Learn from that!

I have just found and reported bug in credit card related form/script in popular Polish trading platform Allegro. This was just a minor compatibility issue.. ;-)

I have just reported several issues and ideas related with this nice Google Hangouts Android application:

• The name Hangouts is not popular and hard to remember. Abandoning “Google Chat” or “Google Talk” was a bad idea. People tend to remember short names and popular words such as “Skype” or “Viber”. This may be funny but people really cannot remember “Hangouts” well.
• Receiving calls is misleading. There are several different ways to answer an incoming call in Hangouts. Most common way is to press a button and then drag it onto an icon that is not visible until you press a button. Another way is top view pop-up which could have color buttons in addition to small icons. Older people have problem with this. Average non-geek user simply needs Green Answer and Red Reject button.
• Hangouts would be simpler to use and more popular if it worked just as an ordinary Phone Call application. Non-geek users have this habit already on how to use Phone Call application, that Hangouts should leverage.
• Hangouts voice/video call should be available directly from a Contact Book if gmail address is present. Just as phone call.
• There are Android devices that offer hardware phone buttons (such as LG Wine Smart). Green Connect and Red Disconnect buttons should be also available to perform actions in Hangouts.

These simple ideas arised from observing older people trying to use Hangouts to videocall their family members..

It is possible to connect a game controller to Android based device and use it as input for your application [1].

[1] https://developer.android.com/training/game-controllers/index.html

Most modern Android based devices support USB OTG function [1]. USB is a Host centric bus that means there is only one Host device and many different Devices can be connected to it. Using inexpensive USB-OTG cable it is possible to swich smarphone USB port from Device to Host, and connect external devices, if chipset and OS build allows this. Google provides detailed information on how to code USB Host [2] in your application.

[1] http://www.usb.org/developers/onthego/
[2] https://developer.android.com/guide/topics/connectivity/usb/host.html