You absolutely like Moog’s latest iOS application named Animoog and wanna control it from your Mac but it doesn’t work and you are running iOS 5 or iOS 5.01. So at the moment it seems there is an issue in Animoog related to a modification in Apple’s CoreMidi stack. On iOS 4.3.x devices the CoreMidi connection worked.
Walkthru
I. On your iOS device do the following:
I assume you already installed AniMoog, didn’t you?
Please shutdown the AniMoog app, in case it is running. Don’t just put it into the multitasking background (or just reboot the iPad or the iPhone)
then open the AppStore
download Pad MIDI
run Pad MIDI
put Pad MIDI into the multitasking background
start Animoog
II. On your Mac/HackMac/iMac/MacPro/whatever do the following:
The following solution has been reported to work on both systems. Chances are good that the solution might be working for you aswell.
Issues
You have been using the auto update feature in Mac OS X to update to 10.5.7. Instead of restarting your system crashs during reboot.
Solutions
You made a backup of your system before, right? Then Restore your backup of 10.5.6, if you didn’t backup: skip this step and give the rest a try anyway.
Native Apple Mac
Hackintosh
00. (restore backup of 10.5.6)
00. (restore backup of 10.5.6)
01. shutdown your Mac
01. shutdown your Hackintosh
02. turn it on again and immediately
02. turn it on again and in Darwin boot menu
03. keep holding the SHIFT KEY
03. in Darwin Boot Menu apply these parameters: -x -f
04. you Mac will boot into SAFE MODE
04. your Hackintosh will boot into SAFE MODE and recreate the MKext
Yesterday january 14th, 2008 Steve Jobs sent an eMail to his employees explaining that his health-related issues seem to be more complex than expected last week. He will take a medical leave of absence until the end of June. In the meantime Tim Cook will be responsible for Apple’s day to day operations.
Stock exchanges suspended trading Apple shares after they went down 10%.
According to forum reports the iPhone DFU mode, which is required to install custom firmware with PwnageTool, does not get detected properly after updating Mac OS X to 10.5.6.
That means you cannot Jailbreak or Unlock the iPhone currently. The iPhone Dev Team has investigated in to this issue and comes to the conclusion that this is not a countermeasure by Apple, but a bug in the new kernel.
The Phone Dev Team names possible fixes for 10.5.6. As always: you do this at your own risk!
1. Replace the following plugin kexts from within IOUSBFamily.kext with the ones from 10.5.5 and then rebuild kextcache (if you don’t understand this, then you shouldn’t attempt it!)
The PC version of the long awaited game Grand Theft Auto IV has yesterday been released to the european markets. First tests show the game is as outstanding as its console versions, released earlier this year. Anyway forums are full of bug reports by people using ATI based graphic cards. The game crashs even before it gets started. NVidia users also report issues, but at least it starts after some starting attempts.
The german Gamestar.de is currently doing a poll. This poll (with currently n=4787) shows that about 75% of the users experiencing heavy issues like permanent crashes. Only 5% say GTA runs seamless without issues.
You may rethink your Chrismas wishlist at this time. What about a Playstation 3? Besides the fact that the game plays wonderful on that device, it’s also got a Bluray/DVD/mp3/Xvid/DivX player included ;-)
It’s beginning we sympathize with MobileMe customers. MobileMe – the Apple’s new all-inclusive-service with email, addressbook etc. and successor of .Mac – hasn’t had performed too well in the last weeks. Even Steve Jobs said sorry and highlighted the service has started too early with too many features. MobileMe customers must have felt it is night again when they experienced problems again during the last few days.
Anyway Apple says only 1% or 2% of the MobileMe customers experiencing problems. Erm…
As said earlier: MobileMe would be a fantastic service for both MacOS X and Windows users. But since it is not working the way it should, we recommend to wait with subscriptions until chrismas. Until then problems should be solved.
MobileMe is this month’ Apple’s never ending story of issues. At first it was only minor problem: customers from Germany and France could not cancel their plans. But then too many eMails got lost and Apple needed about 10 days to fix this issue. Then silently the highly advertised Push-Feature got deactivated (see our report here). In contrast to Apple’s high quality when it comes to usability and features, MobileMe began to leave an impression like a not well tested software in beta stadium.
In the end Apple did the right thing and apologized by offering one month free of charge. All customers thought all of MobileMe’s issues are solved. But sadly they were wrong.
Now MobileMe got again issues. This time syncing of addresses and appointments with mobile devices did not and in some cases still does not work properly. But as Apple said, this problem is also solved now. In certain cases data may not be synced back to the mobile devices. In those cases customers need to activate syncing manually. Read here how to do it. Take a deep breath and be patient, re-syncing may take up to 15 minutes.
After some days of using a pwned iPhone 2G with firmware 2.0, we found some issues. As of now, we don’t know where they come from. But we definitly know: we don’t like them.
WiFi doesn’t stay connected, it falls “asleep” and takes time to reconnect
the more apps have been used, the longer it takes to see reactions
means: if you click on contacts and have used Safari, SMS and Youtube before, opening of contacts takes a lot longer than after an fresh reboot!
loading the contacts take 5-10 seconds
scrolling through contacts is jerky and freezes the view from time to time
scrolling through photos is jerky and freezes the view from time to time
launching the camera takes up to 10 seconds
the unlock slider may not react in time and you may miss a call
keyboard reacts slower than on 1.1.4
reaction time is heavily delayed (or seems not to react at all for more than 17 seconds – see video below)
We won’t blame anyone for this, because on the one hand this could be an effect of Pwning the iPhone and on the other hand these issues might be “features” of the original unmodified firmware 2.0 aswell.See update below, this is a firmware 2.0 issue.
Anyway we feel there are heavy problems with the memory management in firmware 2.0, that need to be addressed soon. Workflow was a lot faster with firmware 1.1.4.
As of now we just reboot the iPhone once a day, but this really is no working solution for such a device. We feel this reminiscent to Windows 95 times is not necessary.
Update: it has been reported this may come from Cydia. As we’re investigating this issue, we get back to you once we found a solution.
Update: Pumpkin of the iPhone Dev Team reports this most likely is an issue of the original firmware 2.0. Native iPhone users have also experienced this behaviour (see reports here in Apple’s forums). The internet is full of reports. Do a Google search you will find plenty of people reporting these issues.
