Categories
Storage TV

Terratec Cinergy Hybrid XE not working on Synology

Even on the latest 5.1-5021 version of Synology‘s DSM I couldn’t get my Terratec Cinergy Hybrid XE working on my Synology NAS — the corresponding kernel module tm6000 would always generate a general protection fault on my DS414.

Today I upgraded to a DS415+ (with a completely different CPU), and the module still crashes.

So it seems it’s a real bug in the driver, not just a defect on a single platform (which can happen e. g. due to compiler bugs).

Update 2015-06-19:

Unfortunately Synology seem not very interested in this kind of problems. I repeatedly reported this issue, but all they replied is “Thanks for your report, we’re looking into this.” Even in the latest DSM release 5.2 the issue is still present.

Categories
Computers Linux

vzlogger 0.3.9 for Raspbian with microhttpd included

I had a hell of a time compiling vzlogger 0.3.9 for Raspbian with microhttpd included — in the end the resulting binary lacked that functionality.

After a lot of trial-and-error and “forced” the code to be included by hard-coding the following define into as follows:

#define LOCAL_SUPPORT 1
#ifdef LOCAL_SUPPORT
#include "local.h"
#endif /* LOCAL_SUPPORT */

As a convenience to those who want that functionality I’ve attached a ready-made package to this post. Let me know if this helps.

Update 2014-12-28: Version 0.4.0 package with uhttpd support available here.

Update 2015-01-05: Version 0.4.0 package based on Git source with SHA d16c0c4c8d83ab9c13f65eb51d931897e7462bc9 available here.

 

Categories
Cell Phones English

How to install Android 5.0.1 on HTC Desire S

By chance I came across a thread on xda-developers that explains how to install CyanogenMod 12 (cm12) on an HTC Desire S (codename “Saga”). Being a newbie in “hacking” and rooting Android phones I had to read, investigate, and try a lot.

To spare you this effort I’m trying to summarize the steps required below:

  1. Unlock bootloader: To be able to flash a custom bootloader you first need to unlock the bootloader, which is easy since HTC makes this officially available via their web site.
  2. Flash recovery image: I used Team Win Recovery Project 2.8 (or short TWRP 2.8) which I downloaded from a link on this site.
  3. Flash cm12 and Google Apps: Download the latest cm12 image (on 2014-12-05 it was cm-12-20141204-UNOFFICIAL-saga.zip) from this page. Download Google Apps from this page. Put both ZIP files on the micro-SD card.
  4. Reboot to your recovery image by keeping “volume down” key depressed and then switching on the phone. Keep volume key depressed until TWRP splash screen appears. Perform a factory reset. Flash the two ZIP files, add cm12 first, then add Google Apps.
  5. Extract boot.img from cm-12-20141204-UNOFFICIAL-saga.zip and flash that with fastboot. Flash it using these instructions.
  6. Reboot your phone. CyanogenMod splash screen should appear after a while. Your first boot will probably take very long (I think for me it was about 15-20 min). Be patient!

After carefully following all the above instructions I now have the following on my HTC Desire S:

  • Boot rom HBOOT-2.02.0002 in mode S-ON
    bootloader
  • Radio/modem/baseband firmware RADIO-3831.19.00.110 (20.76.30.0835U_3831.19.00.110)
  • TWRP v2.8.0.0
  • Android 5.0.1 in the CyanogenMod flavor, version 12-20141204-UNOFFICIAL-saga. Kernel version is 3.0.101.
    cm-splash
  • Google Apps referred to from this page.

Thanks to everyone on xda-developers for their excellent work and support!

You might encounter the following issues which can be fixed as specified:

  • Touch screen not working properly: You have kind of a “mouse pointer” which you can drag around with your finger on the screen. To “click” something you have to double-tap on the mouse pointer. Fixing this can be accomplished by following this procedure.
  • The home softkey doesn’t work. Fix it by following these steps.

I had success with the following (not meant to be complete, just a couple of things which I consider important or surprising):

  • Sending audio to my Plantronics Blackwire C720 Bluetooth headset works properly, using Google Play Music. This was obviously using the “Media Audio” Bluetooth profile.
  • Skype via the above headset works perfectly well. Sound quality is crystal-clear.
  • Hand-over of a voice call to the above Bluetooth handset and back works perfectly well — maybe even better than on my S4… 🙂
  • Paired my Samsung Galaxy S4 with the HTC Desire S. Successfully sent a contact as VCF file from the S4 to the Desire S. But then process com.android.media crashed.
  • Connect phone to Windows 7 via USB, using MTP protocol. Write speeds to micro-SD card seemed normal.

The following limitations still exist (or at least these are the ones I noticed so far):

  • Phone is somehow regarded as a tablet by the Android OS.
  • Front camera not working. I thought I had seen it working once, but maybe I’m confused. Anyway, as of now the front camera seems not to be detected/functioning. The back camera is working well with the camera app from the minimal Google Apps package as well as from the official Google Camera you can download from Google Play. Skype and Google Hangouts also work well, apart from the front cam.
  • I replaced some of the apps in the apps dock with apps I installed from Google Play. Some of these apps will disappear after a reboot. When I noticed this and wanted to put them back by opening the apps drawer I observed that Android was currently populating/updating the apps drawer with some still missing apps. But even after it had finished showing all installed apps in the app drawer the apps dock was still missing some apps. So I dragged them back from the drawer onto the dock. Again, after a reboot they will be gone again.
  • Speed of cellular data connections seems slow. Unfortunately I couldn’t verify whether the cellular network settings are ok, since every time I tried to enter one of the corresponding  Settings menu item the process com.android.phone would crash (with the effect that I had to re-enter my SIM PIN and also the screenlock PIN).
    Later I tried it again, and this time it didn’t crash. All the settings were fine, so I wonder whether there is a problem with regards to the modem firmware? (I would like to note that I don’t have a voice SIM in this mobile phone, but just a data-only SIM. Eventually the firmware tries to perform operations that work on voice SIMs and doesn’t properly handle situations where those operations cannot be carried out?!)
  • Update 2014-12-11: Connecting the charger when the phone is powered down will cause it to boot into the TWRP recovery system.
  • Trying to open menu item Wireless & Networks > Cellular networks > Carrier Settings might cause process com.android.media to stop.
  • Ringtone will be quiet on incoming calls.
  • Microphone will be muted (or not properly amplified) when the first outbound(!) call takes place (in non-speakerphone mode). After you have gone on speakerphone and back, the microphone will then be working.
  • Moving apps to the external SD card is unreliable. Often it doesn’t work without any indication as to why. If you then repeat it again it may actually work.
Categories
Computers WTF

USB device draws too much power, PC will shut down

My dad in law recently asked me about a problem he had with his PC since a couple of days. When he switched on the PC he got an error message as follows:

A USB device is drawing too much power, the PC will shut down in 15 seconds.

Which it did. 😉

I asked him: “What did you do?” He: “Nothing.” Me: “Really?! Nothing at all?!” He: “Well, just connected a USB stick to copy over some pictures.” I: “Huh, so nothing… Let’s see…”

First thing I did is disconnect all USB devices (because I thought he might have done something else he couldn’t remember or didn’t want to tell ;-)). The error still prevailed.

So I inspected the front USB ports. And when I saw that I didn’t know whether I should laugh or be angry. He complete destroyed one of the USB sockets, obviously by trying to force in the USB stick the wrong way. The plastic was broken (and removed!!!), and the contacts were smashed against the “cage” of the sockets, obviously causing a shortcut (and thus this “phantom” device drew too much power ;-))

I opened the case to see whether I could disconnect just the single front USB port from the motherboard. But the two ports were connected to the motherboard with a single 10-pin connector block. I could have tried identifying the wires that led to the damaged port, but I was not in the mood for it, so I just used a screwdriver with a small flat blade to “stretch out” the contacts out of the metal cage and make sure that they don’t cause any shortcuts anymore. I then “sealed” the port with sticky tape, so that he wouldn’t use the port anymore.

Afterwards the PC booted up again as usual.

That was a 20 min. measure and cost nothing at all. I bet a computer repair shop would at least have sold him a new motherboard, if not even a new board plus CPU and RAM (since the combo is already 4 years old or something…), plus work of course.

Hope this helps people with similar issues.

Categories
deutsch Networking Routers WTF

Router blockiert SMTP-Server-Port(s)

Vor einige Tagen kontaktierte mich eine Bekannte, deren Domain ich auf meinem Root-Server hoste. Sie sei gerade umgezogen und könne nun plötzlich keine Mails mehr senden, wohl aber abholen. Der Mailclient meldete “Kann den Server nicht kontaktieren”. Und nein, sie habe in ihrem Mailclient definitiv nichts umgestellt. 😉

Da “klingelte” es gleich bei mir. Ich frug sie, ob sie auch einen neuen Router erhalten hätte, was sie bejahte. Meine Vorahnung ging also möglicherweise direkt in die richtige Richtung.

Was meine Vorahnung war? Nun, wenn plötzlich nach Verwendung eines neuen Routers das Versenden von Mails nicht mehr möglich ist, das Abholen aber sehr wohl noch, dann liegt der Verdacht nahe dass der Router diese Verbindungen blockt. Allerdings war mir zunächst nicht klar wieso der Router dies tun könnte.

Bevor ich weitere Untersuchungen durchführte stellte ich zunächst einmal sicher, dass mein Exim-SMTP-Server auch tatsächlich ordnungsgemäß funktioniert. Danach verschaffte ich mir Remote-Zugriff auf ihren PC mit Hilfe des kostenlosen und sehr empfehlenswerten TeamViewer.

Zum Test der Verbindung wollte ich “händisch” per Telnet eine Verbindung zu meinem SMTP-Server herstellen. Der Telnet-Client war noch nicht installiert, so dass ich ihn erst nachinstallieren musste. Dann führte ich in einem Command Prompt folgenden Befehl aus:

telnet <Mailserver-Hostname> 587

Es gab eine Fehlermeldung der Art “Connection timed out.”

Das war für mich der Beweis, dass meine Theorie richtig war. Ich verschaffte mir also per Webbrowser Zugang zur Administrationsoberfläche des (Telekom-) Routers und fand dort auf Anhieb einen Bereich, in dem ausgehende Mailserver eingetragen werden können. Die Mailserver der großen Mailprovider waren dort bereits eingetragen. Ich fügte also meinen Mailserver hinzu, und unmittelbar nach Anwenden der geänderten Konfiguration konnte die Verbindung zu meinem Mailserver wieder hergestellt werden.

Warum aber sperrt der Router unbekannte SMTP-Server? Als ich die Liste mit explizit konfigurierbaren Mailserver sah, war es mir auf Anhieb klar, obwohl ich sowas bisher nicht gesehen hatte. Der Router versucht Spambots daran zu hindern, von infizierten Rechnern aus Mail zu versenden.

An sich ja keine schlechte Idee, aber warum wird der Besitzer nicht deutlich (z. B. durch einen roten Einleger im Karton) darauf hingewiesen, dass diese Sicherheitsfunktion standardmäßig aktiv ist und welche Wirkung sie hat? Ist das womöglich auch ein Versuch, kleine Provider zu sabotieren?!

Wie auch immer, der “Einsatz” dauerte etwa eine Viertelstunde, danach war meine Bekannte wieder glücklich. Vielleicht hilft dieser Artikel ja dem einen oder anderen, ein vergleichbares Problem zu lösen. Über Feedback würde ich mich freuen.

Categories
Development WTF

Order in Google Play before Unix Epoch ;-)

Just noticed something funny: There’s a purchase in the “My Orders” list that supposedly happened before Unix Epoch:

Screenshot from Google Play showing one specific order -- with a date of December 31, 1969
Screenshot from Google Play showing one specific order — with a date of
December 31, 1969

Maybe for some reason they don’t have the order date, and therefore set the date to “-1” (so a second before Unix Epoch, which is 1970-01-01)… Just guessing…

Anyway, I thought it’s funny enough to share it with you…

Categories
Storage TV

MSI Mega Sky 580 DVB-T Stick Support dropped by Synology

MSI Mega Sky 580 DVB-T stick users beware:

With DSM 5.0-4493 Update 4 for my DS414 Synology suddenly deliberately disabled support for my MSI Mega Sky 580 DVB-T stick.

I did not immediately notice this, since Synology do not warn you that you device has been disabled. So I missed a couple of programmes I wanted to record for my kid — thank you so much, Synology! 🙁

I downgraded to DSM 5.0-4493 and then installed Update 3 again, and my stick is still working.

Let’s see how Synology react to my complaint. If they will not enable my stick again I will complain to Amazon where I bought the device from — let’s see how they will respond…

Categories
Computers Storage

Synology’s speed lie

Since a while I own a new Synology NAS, a DiskStation DS414. Synology advertizes this model with speeds of

Over 207.07MB/s Reading, 135.63MB/s Writing

However I never came even close to those speeds in my daily use of the DiskStation, so I tried to set up an ideal scenario in which I would get the fastest speed the NAS could deliver.

I did so by using a very fast client (a MacBook Pro Retina with a 2.5 GHz Core i7 CPU and SSD drive), and connected that directly “back-to-back” (i. e. without any network device in-between that could potentially slow the network traffic down) to one of the networking ports of the NAS.

The NAS contains three hard drives, a Western Digital WD30EURS (3 TB, max. speed according to benchmarking >130 MByte/s both reading and writing), a Seagate ST32000542AS (2 TB, max. speed at least 109 MByte/s), and a Western Digital WD40EFRX (4 TB, max. speed 146 MByte/s), in a SHR compound (technically a form of RAID5, so due to the striping involved speed should increase compared to a single drive configuration).

I then copied about 25 GB of large files (movies) between the Mac and the NAS.

The fastest speeds I could get was a meager 79.5 MByte/s on reads, and 39.4 MByte/s on writes. That was extremely disappointing, but it confirmed my subjective feeling that the NAS is slow.

To confirm the read data rates I executed the following command directly on the NAS, to have a means of a “plausibility check:”

nas1> hdparm -t /dev/sda /dev/sdb /dev/sdc

/dev/sda:
 Timing buffered disk reads: 328 MB in  3.01 seconds = 109.09 MB/sec

/dev/sdb:
 Timing buffered disk reads: 332 MB in  3.00 seconds = 110.66 MB/sec

/dev/sdc:
 Timing buffered disk reads: 392 MB in  3.00 seconds = 130.66 MB/sec

This shows that the NAS is capable of reading at a higher speed than it could deliver to the client via the network — possibly an issue with the CPU being too weak to deliver the full speed Synology promise?

Anyway, I find these disappointing results inacceptable, and it makes Synology’s statement a “lie.” Also, I found severe instability and defects with respect to the VideoStation package and recording from a DVB-T stick. Plus the massive issues Synology have with the power-saving “Hibernation” feature that never worked for me (neither on this box, nor on its predecessor DS212+.) And I’m not alone, a lot of people have the same issue, but Synology seem unable to solve it.

Considering the high price of the NAS (almost 400 EUR!), my strong opinion is that the device simply is not worth its money. It would have been better to buy a HP ProLiant MicroServer and get more power for less money. 🙁

Categories
Mac

Mac SSD speeds

There have been some complaints recently about speeds of SSD drives built into Mac computers, mostly MacBook Pro and Air. Supposedly current models are much slower than earlier models, sometimes as slow as only 50% of the transfer rates.

As I was curious I benchmarked mine. I used Blackmagic Disk Speed Test which is available for free from Apple’s App Store.

I got 416 MByte/s for writing, and 474 MByte/s for reading for my 512 MB SSD drive, which I consider pretty fast:

 

Blackmagic Disk Speed Test results

I have a MacBook Pro Retina, 15-inch, Early 2013 with 2.4 GHz Intel Core i7. My SSD is a APPLE SSD SD512E Media which is obviously made by SanDisk.

What about yours? Please comment here in my blog, giving your machine and SSD details.

Categories
Computers Mac

“SSD-Lotterie” mit Apple

Ein Artikel bei heise online hat mich gerade nachdenklich gemacht: Dort wird berichtet dass SSDs unterschiedlicher Zulieferer teilweise dramatisch unterschiedliche Geschwindigkeiten aufweisen was dazu führen kann, dass ein aktuelles Modell des MacBook Air nur halb so hohe Transferraten erreicht wie ein Vorjahresmodell. Und das ist nicht das einzige Beispiel dieser Art, es gibt noch mehr.

Ich frage mich was “den typischen Mac-Käufer” dazu bewegt, diese Politik von Apple zu akzeptieren. Ist es schlicht Unwissenheit — was noch irgendwo “verzeihlich” wäre — oder ist es blinde Folgsamkeit, Hauptsache man besitzt das geliebte “Statussymbol”?

Zugegeben, die Formulierung ist ein bischen provokativ. Ich selbst besitze drei MacBook Pros, würde mich aber dennoch durchaus als sehr kritischen Apple-User bezeichnen. Nach zwei iPhones habe ich beispielweise Apple den Rücken gekehrt und bin “ins Android-Lager gewechselt”, weil die Plattform für mich einfach “offener” ist und mir mehr Möglichkeiten bietet.

Wie seht Ihr das? Sollte man Apple nicht durchaus mal spüren lassen dass man sich als Verbraucher nicht gerne auf den Arm nehmen lässt? Gibt es überhaupt eine Möglichkeit dazu? Oder kommt man in bestimmten Situationen bzw. Konstellationen nicht darum herum, “in den sauren Apfel (Apple?) zu beißen” und trotzdem zu kaufen? ;-)

Eure Meinung interessiert mich sehr — hier habt Ihr ein Forum. :-)