Actually, I like the fork. Especially, when it comes to eating certain types of food. :-)
Each virtue and each wisdom needs parading in one’s own time, and must not last forever.
Probably due to lack of customers using Linux (Guess what Mac OSX runs under its hood…), Polar doesn’t offer any piece of explicit Linux software. Obviously commercially motivated and to certain degree understandable.
However, as a 100% Linux machines and FOSS fan, one runs into problems… Luckily, it is possible to get the Flow software to activate and sync the Loop using a VirtualBox with WinXP(32bit). I admit, it’s not 100% free of proprietary software, but I have to use Microsoft PowerPoint now and then because of my project partners, so it doesn’t hurt too much.
After attaching the Loop to the USB port using the cradle, check, if the Loop is seen by your system:
and it will answer with:
Bus 001 Device 005: ID 5986:026a Acer, Inc Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 138a:0017 Validity Sensors, Inc. Bus 001 Device 007: ID 125f:a93a A-DATA Technology Co., Ltd. Bus 001 Device 006: ID 0da4:0008 Polar Electro OY Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
where Polar Electro OY is the device you want to mount in VirtualBox. The key, to get started with a decent Notebook (Thinkpad 440s here) is: Turn off USB 3.0 support in BIOS/UEFI and let VirtualBox automatically attach the device.
Else this horrible error won’t let the VirtualBox recognize the Loop:
To let VirtualBox attach the Loop automatically, add a filter to it:
If the Loop is not seen, check Polar’s manual and search for the error there. Every USB 2.0 port should be able to see it. If it is seen by your OS, install the Flow software on the VirtualBox and hope for the best.
A happy end, looks like this:
The Loop is seen using Bluetooth (4.0) by my Laptop. However, I’m still struggling with connecting that to wine. The Flow-Software installed flawlessly (Thank you QT!) using wine!
Nevertheless, I am a happy user of the Loop right now and am also able to sync via the setup above, as my smartphone is completely incapable of Bluetooth 4.0.
I have to admit, that @PolarGlobal and the customer service do their best, to help, though from their point of view it must have appeared pretty hopeless.
On a short note: I upped design, by brushing the chrome metal parts with sand paper (grit 150) and painted Polar’s “o” and the furrow white:
The Loop after painting the “o” and the furrow white and brushing the metal with sand paper (150 grit). pic.twitter.com/Z8v31PjQDo— ʇɹǝqƃǝᴉs puɐloɹ (@RsCircus) August 8, 2014
Actually, I planned this quite a while. Basically not, because I don’t like the Google eco system. Absolutely contrary. But I want to have control of my property. And, as I have a very very low speced device, I need free RAM!
Here the steps to follow, with the expectation that your phone is:
In my case that’s a CyanogenMod 11 nightly.
Maybe, a bullet point below or above may raise an eyebrow. Thus you have to type in this bullet point together with the name of your phone into your search engine of choice and see how each and every step is done on your specific device.
In the end, however, the interesting proprietary residue from Google, which is built in is Google Analytics. If you have a CyanogenMod You can remove it with freecyngn:
On a side-note: This is just the beginning. Next, I would recommend to:
Basically this piece of prose is expecting, that you are sitting in front of a Linux machine and already have CyanogenMod running on your Huawei Y300/u8833 device and replaced your recovery rom. In my case the recovery rom is TWRP 220.127.116.11. Considering the very first point, you might want to try Ubuntu, which is beginner friendly. Considering the latter, please follow the link given above.
First of all make a backup:
Now we come to the procedure itself. Download Chil360’s kernel adapted for CM11 (as of now) or whatever is the state of the art right now.
Currently Dark Cricket is mainting them here. After download and extraction, cd into the directory where your files are residing. Then fastboot your device, i.e.:
⇒ fastboot devices d2536afb fastboot
As you see, my device is responding with d2536afb fastboot. Everything is set. Now the magic moment.
⇒ fastboot flash boot boot.img sending 'boot' (5544 KB)... OKAY [ 0.522s] writing 'boot'... OKAY [ 1.760s] finished. total time: 2.282s ⇒ fastboot reboot rebooting... finished. total time: 0.001s
Now your device reboots into a faster world. If your device complains like your com.android.phone process stopped working, you flashed the wrong kernel and hopefully made backup. ;-)
Though being far from a perfect solution, I added some flavor to a given soup. If you want to switch between UPPERCASE, lowercase and TitleCase (covering words longer than 3 letters!), add this to your .vimrc:
If you visual-select some text, you can now press ~ to cycle through the cases.
Orig: Automatic Cycling of Uppercase, lowercase and Title Case. 1x~: AUTOMATIC CYCLING OF UPPERCASE, LOWERCASE AND TITLE CASE. 2x~: automatic cycling of uppercase, lowercase and title case. 3x~: Automatic Cycling of Uppercase, Lowercase and Title Case.
This is focusing on Fedora, as atom focuses on Debian. And actually I wanted to provide a manual, because atom’s site seemed so Mac specific. But the setup, following, abstracting the readme with incorporating current issues in the Issue Tracker of github, totally and utterly failed. After one hour of fiddling I gave up, but I started with…
First as root:
sudo yum install libgnome-keyring-devel npm sudo npm config set python /usr/bin/python2 -g
which will install all requirements including node.js. 
Then do the following:
git clone https://github.com/atom/atom cd atom
Comment out argv.push(‘—no-parallel’) in atom/build/node_modules/npm/node_modules/node-gyp/lib/configure.js and create a symlink from /lib/libudev.so.0 to /lib/libudev.so.1 
Though, this is just an editor, be prepared to download a gigantic repository of >200MB. Even the mac-buld features >70MB (2014.05.08) right now.
Still doesn’t work… help?