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.

sbh54

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..

xperiacompanionfail

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.

emma

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..

« Previous PageNext Page »