Tag Archives: bug

[Ableton] Repairing Defective ALS Files Manually

abletonlogoneu2

 

What happened?

  • many avoidable (stupid) situations arise from hectic rush: we for instance accidentally deleted an ableton set (.ALS file extension) from a local NAS server
  • without going too deep into detail: since we don’t have a RAID based NAS we could recover (some parts of) the desired .als file by putting the NAS’ drive into an old PC and restored the found data with UFS/XFS-Explorer (absolute recommendation) to an external USB drive
  • after loading the recovered ALS file, we encountered the corrupt file error from Ableton

bildschirmfoto-2014-01-01-um-3-59-16-pm

The following article is written by a Mac user, but many (if not all) things should most likely be able to be applied to Windows aswell. Continue reading

[Muzaq] Workaround for Audacity Crashing

Abstract

At least on a Mac Audacity seems to have issues when it comes to using third party plugins (i.e. AU or VSTs). To pinpoint which type of plugin is responsible for poor Audacity to crash, you can do the following.

I. Locate Audacity Config File

On a Crapple Mac the audacity.cfg file should be located here:
/Users/<your-username>/Library/Application Support/audacity

Continue reading

[iOS] Finding Information About Crashed Apps

Crashes and system freezes have become an exception nowadays. However, they still do occur. Here we show you two ways of accessing detailed log information on your iOS devices.

1. Finding Logs inside of iOS

This approach does not require a jailbreak. Inside the filesystem you may find logs here:

  • Settings
    » General
    » About
    » Diagnostics and Usage
    » Diagnostics and Usage Data
    » LatestCrash.plist

To make things easy you can just select the whole text and copy it to an email. Et voilà: developers will love you for having helped them…

Continue reading

[Win] Oracle VirtualBox: Workaround For Initialization Issue Pt. II

Find our previously released workaround for initialization issues here.

CPU VT-X/AMD-V Issue

After configuring a dual core virtual machine and trying to start you may encounter a message box indicating:

  • Hyper-V launch failed; Either VMX not present or not enabled in BIOS.
  • Hyper-V launch failed; at least one of the processors in the system does not appear to provide a virtualization platform supported by Hyper-V.

This issue may occur no matter which host operating system you’re using. The reason for this might be:

  • you’re not using a CPU that supports hardware virtualization
  • your BIOS does not support hardware virtualization properly
  • hardware virtualization is disabled in your BIOS settings (check it!)
  • there is a bug in your current BIOS version
  • the trusted execution flag prevents booting properly

Known Workarounds

Try these settings in your BIOS:

  • Enable Execute Disable bit (depending on the motherboard manufacturer this can be called: XD-Bit, EDB, NX-Bit, AMD EVP)
  • Enable Virtualization bit (depending on the mobo manuf. this can be called: VT, IVT, AMD-V)
  • Enable VT for Direct I/O Access (depending on the mobo manuf. this can be called: VT-d based I/O)
  • Disable Trusted Execution Technology (depending on the mobo manuf. this can be called: Intel TXT, TET)

Of course, upgrading your BIOS to the latest version can also be of help, but flashing the BIOS is always a little risky.

Final Words

As we’re currently using VirtualBox only on the Windows XP platform we categorized this article under Win, anyway it is very likely that the same issue also occurs under Linux or Mac OS, as VirtualBox on all platforms derives from the same source code.

The above settings apply for example for installing MacOS SnowLeopard in a VM under Windows 7 on Gigabyte EP35-DS3 or Dell Optiplex 745/755.

[Pre] WebOS Vulnerable To Several Attacks

Researchers from Intrepidus Group said in an advisory published on Friday last week that Palm’s WebOS operating system is subject to web application vulnerabilities.

These bugs can all be traced back to that fact that WebOS is essentially a web browser and the applications are written in JavaScript and HTML.

The bugs and vulnerabilites released are for WebOS 1.3.5. Palm has fixed all of them in WebOS 1.4. Anyway the Intrepidus Group said there are still undisclosed bugs in WebOS 1.4.

Via Intrepidus Group

[Games] A Pseudonym for Bugs = Monopoly City Streets

Monopoly – a game that almost everybody knows – has been revived and redesigned for the virtual sphere as “Monopoly City Streets” (MCS). As many other news services have already written thousands of pages about it, we’re not gonna repeat it here. To summarize: it seems this game is fun for many millions around the globe.

Sadly although the makers have already taken actions against issues and problems by upgrading hardware and by resetting the whole game to enable everybody to start anew, there are aswell technical as social issues unsolved all over.

I for example have today bought an 8 million street and built some little houses on it. See here how you can become the leader of the game with an 8 million street. And no, I was not cheating. I enjoyed playing with real competition until this happened:

So how often does this happen? I wrote an error report, but how many other people do that? The most logical consequence would have been to sell the street immediately to get the cash transferred for real…

[MacOS] Is EFI-X illegally using 3rd Party Program Code?

About a year ago a company called ASEM released a device called EFI-X. This device has been claimed to be capable of booting several Microsoft Windows versions and Mac OS X Leopard.

Legal concerns

From the beginning there were question regarding the legal status of the device. But ASEM claimed the device is legal, although it circumvents Apple’s binary protection using Apple’s copyrighted secret operating system keys (OSK1 and OSK2).

Technical issues

Anyway EFI-X devices had some issues. Many forums reported about problems with Bonjour and sharing in general. In the meantime articles from the official EFI-X support forums have been suddenly disappeared. Customers reporting issues or solutions and workaround to severe bugs have been banned from EFI-X support forums – our own help article to recover almost lost data was removed aswell and one of our members has been officially banned from their forums (the reason was this article in october 2008).

Examining EFI-X in deep

Now some frustrated customers who are on the other hand technologically very familiar have examined the EFI-X device in deep. One of the main points AsereBln found: in contrast to what EFI-X is stating: “Our approach is entirely different, (..) all our code and development is our own only” – they seem to be using program code that has been developed by the OSX86 community though. They seem to be using “Disabler.kext“. Moreover another user (RezRov) found out the EFI-X Windows update software seems to be violating the LGPL as it incorporates a modified USB device library (libusb-win32).

Use of possibly unlicensed 3rd party program code, possibly illegal use of Apple security keys, and customer support below grade for a 170€ (250US$) commercial product that seems to be the summary about a year after product launch.

Lessons learnt

We suppose end users should be aware of this possible hassle. Only an original Apple Mac is really hassle free and 100% compatible to a Mac. But if you are technologically interested and have the time and motivation search the OSX86 communities for setups. The OSX86 forums are full of knowledge and willing to help. But remember a PC won’t ever be 100% compatible to a real Mac.

[Pre] Merry Me again: Update Reunites Palm Pre with iTunes

The “little Palm Apple battle” goes into its next round. A week ago Apple released iTunes 8.2.1. This update blocked Palm Pre users from synchronizing music and movies with iTunes. We reported about this update and the technical implications of the sync feature here.

Palm has now released a firmware update (webOS 1.1.0) for the Palm Pre. According to Palm’s blog entry this update contains the following features:

  • Exchange ActiveSync (EAS) (including remote wipe, PIN/password requirements, inactivity timeout, improved certificate handling and more)
  • support for emoticons in the messaging app
  • person reminders (“Next time you get a message or phone call from that person, a message pops up showing you a reminder to ask them about their vacation in Maui” ct. Palmblog)
  • and Palm webOS 1.1 re-enables Palm media sync with music, photos and videos with the current version of iTunes (8.2.1).

Got issues with the Update?

Our fellow Heise.de News (german only) recommend not to update your Palm Pre while it is connected to iTunes. In case you did that and your Palm Pre does not interact on USB anymore, do a hard reset with unplugging the battery.

[News] Apple Bar Palm Pre from Syncing with iTunes

With the latest update of iTunes 8.2.1 Apple eventually blocks Palm Pre users from syncing with iTunes. It seems Palm knew very carefully how to emulate the iPod verification protocol of iTunes. How comes?

Some major Palm Guys are former major Apple Guys

One could ask Palm’s CEO Jon Rubinstein, or Palm’s SVP of Product Development Mike Bell, or Palm’s spokeswoman Lynn Fox. As all of these three guys are former Apple guys. Rubinstein was Apple’s architect of the iTunes-iPod concept, Mike Bell was the Vice President of the Mac Hardware Division, and Lynn Fox was Head of PR at Apple.

Anyway Apple now decided to fix this issue and bar Palm Pre users from using iTunes for syncing. But what looks like a simple update in the first place may be viewed as a strategic answer to Palm’s boldness to make the Pre pretend being an iPod for iTunes.

Some Technical Aspects

According to DVD Jon the iPod emulation was not too complicated. Palm needed to emulate

  • the USB interface so that it responds with Apple’s Vendor ID and an iPod Product ID
  • the structure of an iPod filesystem
  • some XML info about the iPod device using a custom Apple USB command

But the the root USB node (IOUSBDevice) still identified the emulated iPod as a Palm Pre (find more details here).

David vs. Goliath

Does Apple fear Palm here? It seems like Palm is putting Apple under some pressure here. The Palm Pre is widely considered as the only real iPhone competitor and allowing it to sync with iTunes would make it more favourable for users who don’t like the proprietory iPhone concept. On the other hand Apple’s step to block it from iTunes again makes the iPhone and iPods the only choice for iTunes users. Anyway it shows obviously that a little fight is going on between Apple and Palm. This topic is under hot discussion on the PreCentral site.

Palm’s spokeswoman Lynn Fox just responded to Apple’s step “Palm’s media sync works with iTunes 8.2. If Apple chooses to disable media sync in iTunes, it will be a direct blow to their users who will be deprived of a seamless synchronization experience. However, people will have options. They can stay with the iTunes version that works to sync their music on their Pre, they can transfer the music via USB, and there are other third-party applications we can consider.”

[iPhone] HowTo Make MMS Work on iPhone 2G

NOTE: This walkthrough is for iPhone OS 3.0 only!

For MMS on iPhone 2G with firmware 3.1, buy SwirlyMMS on Cydia Store

I. Abstract

Many iPhone 2G users are not very amused about Apple’s update policy. As of iPhone OS 3.0, owners can eventually use MMS on their iPhones. All owners? No, not the ones who have iPhones from the very beginning.

The MMS feature is not officially available on the iPhone 2G, although there is no technical reason for the limitation – as we’ve seen with SwirlyMMS.

This seems to be one of Apple’s ways to tell you you need to get a new iPhone at least every two years. Quite expensive you think? Right, but get used to it as this seems to be Apple’s business strategy of lifecycles with many products.

Anyway, Apple provides one of the best user experiences for their products and that’s the point why you are here reading these lines.

To make things short. There is a way to make MMS work on the iPhone 2G with firmware 3.0. Kudos fly out to Geniusan for the ActivateMMS2G patch, and to Craig_16 (this walkthrough is based on his findings!).

II. Requirements

You need to have the following configuration:

  • an iPhone 2G with iPhone OS 3.0 (Warning don’t try this on an iPhone 3G or 3Gs, you’d be screwed!!!)
  • jailbroken (find Jailbreak HowTo here)
  • with Cydia running

Of course you’ve done a backup of your contacts, your calendar, and your photos, didn’t you?

And you need to have your carrier settings available (!!!!). Search MMS settings here before you proceed! In the following example we’re going to use a reseller of the german T-Mobile network called Callmobile. Callmobile got these settings:

Internet / Wap Callmobile Germany
APN internet.t-mobile
Username tm
Password tm
Visual Voicemail (not available!)
APN
Username
Password
MMS settings
APN mms.t-d1.de
Username t-mobile
Password mms
MMSC http://mms.t-mobile.de/servlets/mms
Proxy 172.28.23.131:8008

blank
III. Preparations

The preparation steps are intended for user who already have tempered to make MMS running but failed. Those steps help restoring the iPhone to a status where we can eventually enable the MMS feature. Our recommendation: if you didnot try to make MMS running yet, you may want to read these steps anyway and apply most of the steps as available.

Pre.Step 1: Resetting Cellular Data Profiles

If you already tempered with the network settings to make MMS work, you first need to reset the settings. On your iPhone go to

  • Settings » General » Network » Cellular Data Network
    If the Cellular Data Network menu is no available: that’s no problem, we’re gonna enable it later. Jump to Pre.Step 2.
  • Scroll down and click on Reset Settings

  • Confirm question with a click on the Reset button
  • Click the Network button to leave the settings menu and
  • Reboot your iPhone

Pre.Step 2:  Removing Cellular Profiles

On your iPhone go to

  • Settings » General » Profile

    Again: if this menu is not available, we’re gonna enable it later. Jump to Pre.Step 3.
  • Click Remove
  • Confirm Remove
  • Reboot your iPhone now

Pre.Step 3: Uninstalling ActivateMMS2G

On your iPhone go to

  • Cydia (available on jailbroken iPhones only! Wanna do a jailbreak now? Go here.) and
    Click Manage

  • Click Packages
  • Click ActivateMMS2G
  • Click Modify
  • Click Remove
  • Click Confirm
  • Click Reboot Device

IV. The Walkthrough

After having applied all the preparations we now have the situation that all of us should have almost the same conditions with the cellular network settings. This is an important condition.

Step 1. Installing ActivateMMS2G

On your iPhone go to

  • Cydia (available on jailbroken iPhones only! Wanna do a jailbreak now? Go here.)
  • Click Search,
    Enter manually ActivateMMS2G, and when found:
    Click ActivateMMS2G

  • Click Install and Confirm


  • Click Reboot Device

Step 2. Installing A Custom Profile

On your iPhone go to

  • Safari and open this website: http://help.benm.at (kudos!)
  • Scroll down and click Mobilconfigs create
  • now the fun part starts, as here many issues may occur if you don’t pay attention
  • In contrast to what the fields’ description show we enter in all fields the required mms settings, got it? According to our example for Callmobile we enter this:

    click Enable Thethering
    and click Generate
  • you’ll be asked if you wanna install a new profile: Click Install
  • Confirm with Install Now
  • Click Done
  • Now quit Safari
  • Don’t check the settings, but
  • again Reboot now

Step 3. Adding Appropriate Cellular Settings

On your iPhone go to:

  • Settings » General » Network » Cellular Data Network
  • Now you see, that the MMS settings are present in all fields, of course this is wrong.
  • Now remember one thing: don't touch or edit the following entries: MMS/APN, MMS/Username, and MMS/Password. Once edited manually they will be lost and missing, because they will not get saved after leaving the menu. You would then have to start over above with point III. Preparations. You got me, right?
  • Enter MMSC and MMS Proxy first.
  • For Callmobile Germany (see above)
    MMSC is http://mms.t-mobile.de/servlets/mms and
    MMS Proxy is 172.28.23.131:8008
  • The result will look like this:
  • Click the Network button to leave the settings menu and
  • do a Reboot now to make sure the iPhone has loaded the new MMS settings

Step 4. Sending two Test MMS’

What we here basically do is, we’re gonna send the MMS to us. This allows us to check if receiving works and this also auto-enables the MMS feature on many carriers worldwide (not with AT&T in the U.S., sorry). After sending the first MMS you may receive an SMS instead that tells you you can watch the MMS on the internet. This is because the carrier has not updated your MMS capability yet. Now wait about five minutes and send another MMS to your own iPhone. This time you should receive it.

This is how we do it. On your iPhone go to:

  • Messages
  • Click on New Message icon (also note that a camera icon will be left to the text field)
  • Enter your own iPhone cell number
  • Click the camera icon and take a photo


  • Back in the Messages app, click the Send button
  • Your first MMS will be send now
  • As already written above: you should be either receiving now a text message telling you to read the MMS on the internet or you receive the MMS. If you only get a text message wait a couple of minutes and try again.

If anything does not work: we recommend to check the internet for your carrier specific settings. In 99% of the cases it is not related to the iPhone, but due to wrong carrier settings. Or your carrier simply has deactivated the MMS feature for your subscription (i.e. AT&T)!

Step 5. Editing the EDGE/GPRS Internet Settings

Again on your iPhone ;-) go to:

  • Settings » General » Network » Cellular Data Network
  • Edit the Cellular Data fields
  • As written in the beginning, for Callmobile Germany take this:
    APN is internet.t-mobile
    Username is tm
    Password is tm
  • Click the Network button to leave the settings menu and
  • Reboot your iPhone

V. Final words

You should check if your EDGE/GPRS settings work by deactivating your Wi-Fi and go online via GPRS/EDGE only. People reported it may be slower than before. We cannot confirm this. EDGE/GPRS is slow like hell anyway. If you are running a subscription that supports Visual Voicemail you can also enter the appropriate information after reboot and test if it works.

Did we tell you about our sponsors? They help us maintaining this site free. You may visit them to check their coolest offers. Thanks! If you got questions, additions or shouts, don’t hesitate…