3gs syncing problem after itunes update to itunes 7

When syncing my 3gs with updated itunes7, will not complete sync because"session could not be started" and "connection could not be established". Ran diagnostic and all seemed fine.

Problem solved after upgrading to IOS6!

Similar Messages

Sync problems after iTunes Match update

iTunes Match has created an ongoing sync problem for me. If Match updates automatically based on songs I've purchased from the iTunes store, then I usually have no issues with the sync function. However, if I load a CD that is not in the Match library, or if I just manually do an update to Match, it causes my 160gb iPod to take 15-20 minutes to sync. Why is this happening?

I cannot sync my music but I get the message that it is connected but it is not recognised.
As advised on the error message I have reset the Nano and re-installed itunes with the same results.
Doublechecking. Have you tried a complete uninstall of both iTunes and all the other related software components and then a reinstall? If not, try the instructions from the following document:
Removing and reinstalling iTunes and other software components for Windows Vista, Windows 7, or Windows 8

Sync problems after itunes update!!!!!

I have had no problem with the Nan 6th Gen since new but since the last itunes update I cannot sync my music but I get the message that it is connected but it is not recognised.
As advised on the error message I have reset the Nano and re-installed itunes with the same results.
Has anyone had the same experience or can help?

I cannot sync my music but I get the message that it is connected but it is not recognised.
As advised on the error message I have reset the Nano and re-installed itunes with the same results.
Doublechecking. Have you tried a complete uninstall of both iTunes and all the other related software components and then a reinstall? If not, try the instructions from the following document:
Removing and reinstalling iTunes and other software components for Windows Vista, Windows 7, or Windows 8

Sync problem after iTunes update

Every time there is a new iTunes update and I go to sync my iPhone for the first time I end up with double calendar entries. I receive a "Sync Alert" that says this:
+"Syncing with Bob iPhone will change more than 5% of your Calendars on this computer."+
If I go ahead and allow the sync to continue I end up with double calendar entries throughout my entire calendar. I use Entourage, so I don't know if there is a conflict happening because of that, but I don't think so. The warning message has to do with syncing my iPhone with iCal.
Any thoughts on this and why it's always happening after an iTunes update?

Someone from Mactopia was able to help me figure this one out.

Syncing problems after iTunes created automatic playlist

Because I have more music in my library than can fit on my iPod Touch, iTunes created an automatic playlist that would serve as the folder for what would go on my iPod.
When this happened, only that playlist would sync with the iPod, so the applications I downloaded on my computer did not get synced onto the iPod, so I deleted the playlist.
Now, when I sync, nothing gets transferred onto the iPod.
How do I fix this problem? Also, how do I tell iTunes what particular songs I want on the iPod?

Click here and follow the instructions.
(38317)

Had a problem after download updated itune, error 7 (window error 126) cant open itune at all

Had a problem after download updated itune, it failed as Error code MSVCR80 and then next message is error 7 (window error 126), cant open itune at all

Had a problem after download updated itune, it failed as Error code MSVCR80 and then next message is error 7 (window error 126), cant open itune at all

Multiple Samsung Stratosphere problems after FF1 update

There have been multiple posts on various issues users have found after the recent Stratopshere FF1 update. Some were replys to older posts and some only touched on a single issue. I wanted to consolodate into one thread, and hopefully get teh attention of Verizon to maybe reply here.
For reference, a lot has been discuss here --> https://community.verizonwireless.com/message/874446
Summary: Verizon and Samsung have finally updated the Stratosphere almost 1 year after release. This updated the phone from Android 2.3.5 to Android 2.3.6. Going by filename, this is known as the FF1 update. This update went live at the end of August 2012, and most users were upgraded before mid September 2012.
There were some noticable changes in this update:
-Lock screen has changed. The puzzle piece and glass lock options have been removed. New options have been added, such as facial recognition unlock.
-Call answering screen has changed, introducing the option to ignore call with a message.
-Camera now has digital zoom ability.
-Ability to uninstall the 2 games the phone comes with (Need for Speed and Lets Golf)
-Phone icon has changed ever so slightly
-Wifi icon now included up and down arrows to indicate data is being sent or recieved
-Wallpaper no longer "stretches" over multiple screens - ie, it no longer scrolls as you move from screen to screen
-The visual voicemail app has been improved (I have personally not used this feature)
-Callback number is now supported in text / picture messages
-Android core OS updated from 2.3.5 to 2.3.6 (both versions are still Gingerbread)
-Update to how the device deals with the end of scrolling. It used to rubber-band bounce back, now it will just give a green bar and expand the bar as you scroll. (I cannot fault Samsung for this change as this was at teh core of an Apple lawsuit and has been changed in newer versions of Android.)
-(I am sure there are more. please list any others you may have noticed)
I have found some problems, and others have confirmed that this is (at least) somewhat widespread:
-The biggest problem is with wifi connectivity. Upon an initial connection to wifi, everything works great. After somewhere between 15minutes and 2 hours, problems start happening. Its as if the wifi keeps hanging or reconnecting. Download speeds (tested with the SpeedTest.com app) slow to about one third of normal. Apps like Facebook that require a constant connection will just time out.
-It appears the signal strength for 3g and 4g connections is lower. There are places where I used to get a 4g connection, and now I only get 3g. Some palces I fall back to just 2g digital.
Another minor issue i found was with text messages. When you reply to a message, it no longer automatically focuses the text in the input box. You have to first click into the box to start typing. Not a huge deal, but one more step to take over and over. Minor annoyence.
At my house, I struggle to get a 3g or 4g signal. I depend on wifi for my data connection. So with the wifi connection problem introduced by teh FF1 update, my phone is somewhat useless to me now while at home. Here are teh troubleshooting steps I have been through so far to attempt to fix the wifi problem:
-Complete factory reset on my phone. (did not help)
-Pull battery and SIM card out of phone for 15 minutes. (did not help)
-Went to a Verizon store. The guy at the store was helpful, and said he also had a Stratosphere and was getting the same wifi problems after the update. He said all he could do was to send me out a replacement phone. I got the replacement phone, and it had the same problems.
-I read in multiple palces that Android 2.3.6 has a bug within wifi and DHCP. Apparently if you have a DHCP lease set to "forever", the phone will keep requesting a new address. Setting the DHCP server on the router to something like 2 weeks, or using a static IP is supposed to solve this. I have a NetGear N900 router, and I can not change teh DHCP lease time. It appears, however, that my router is not sending out "forever" leases. But just to make sure, I gave my phone a static IP. (None of these steps made any difference).
The only thing that temporarily fixes the problem is a reboot of the phone. This will again give you anywhere from 15min to 2 hours of good wifi use before problems start happening.
I have now had this update for over a week, and on 2 phones. I still can't maintain a wifi connection for much longer than 15 minutes without problems starting up.
I am asking Verizon or Samsung to at least confirm this issue if possible. Maybe there are newer revs of the Stratopshere hardware that don't have this problem. Or there is something unique about my (and apparently others) situation. But it seems like Verizon's current stance is to offer a repalcement phone (as currently all Stratospheres are within their 1 year manufacture warranty as the phone has not been ouy for quite 1 year yet).
I am asking for a workaround for this problem, or a true fix adressed by a new software update, or at least allow us to roll back to the original Andorid 2.3.5 software.
I have had my original Stratosphere for almost a year with no wifi problems - then get the FF1 update and have had nothing but problems on 2 different phones.
Thank you for your time.

Thanks for starting a comprehensive thread on problems with this update. I want to add one more.
I have Bluetooth in my car (a 2004 model), and previously the phone has connected to it practically instantly when I start the car. Since the update, I have never been able to connect the phone to the car by Bluetooth. Several times the phone has made a standard notification sound at the moment it should be connecting to Bluetooth, though no notification appears. I have no idea what that could mean.The car's Bluetooth shows up as paired in the list of devices in Settings > Wireless & networks > Bluetooth settings. I haven't seen this widely reported as an update issue, but perhaps some others have experienced it too.
UPDATE: I finally did some testing, and found that the notification was to signal the extremely brief appearance of a dialog indicating that the car's Bluetooth was requesting a connection. Accepting that request let the phone connect with the car, and calls went to the car's sound system as they should. When I turned the car off and back on (just the electrical system; not wasting any gas on this!), the connection was established immediately, so apparently the acceptance only had to be done once. Nevertheless, it did have to be done, and the dialog notification disappears within seconds. I believe it would have been possible to go into Bluetooth settings and accept the connection request there if I missed the notification; but not seeing the notification, I might not know to do this.
One further observation: When I turned the phone's Bluetooth off and back on after a connection had been established, leaving the car on the whole time, the two did not reconnect. I believe that may be different from before the update, but I'm not really sure.
Message was updated by David Rensberger

EFI Problems after last update anyway to downgrade ??

Hello
EFI Problems after last update anyway to downgrade ??
i have updated my MacBook 2010 EFI to MB71.0039.B0E which is 2.1 version
after updating to this version the Boot time become much slower when i want to change boot partition
and shutdown become very much slower and startup too
i tried to install Mac OS X Lion again but it doesnt help
can i downgrade to this version 2.0 ???
or when Apple will release the new version ?
or where can i send a feedback regarding this issues !!!!
Thanks

These are user to user forums. If anyone knows the answer, they will give it.
You can always call Apple support which may charge a fee or you can patiently wait for an answer here, which is free.

Share and save problem after latest update

hello,
i have share and save problem after latest update - i have installed ps touch on nexus 5 about 2 months ago and until yesterday everything was good but after latest update i can't save and share images in ps touch ( i do reinstall this app but problem is still and app doesn't work properly ) how can i downgrade to the old version ? Could you fix this problem quickly ?

i use app which called "aLogcat"
--------- beginning of /dev/log/main
I/dalvikvm(24476): Enabling JNI app bug workarounds for target SDK version 11...
D/dalvikvm(24476): GC_CONCURRENT freed 174K, 2% free 17054K/17264K, paused 2ms+2ms, total 15ms
W/InputEventReceiver(24476): Attempted to finish an input event but the input event receiver has already been disposed.
W/InputEventReceiver(24476): Attempted to finish an input event but the input event receiver has already been disposed.
W/InputEventReceiver(24476): Attempted to finish an input event but the input event receiver has already been disposed.
--------- beginning of /dev/log/system
W/ViewRootImpl(24476): Dropping event due to root view being removed: MotionEvent { action=ACTION_MOVE, id[0]=0, x[0]=38.0, y[0]=-115.0, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=2, eventTime=27743080, downTime=27743066, deviceId=4, source=0x1002 }
W/ViewRootImpl(24476): Dropping event due to root view being removed: MotionEvent { action=ACTION_UP, id[0]=0, x[0]=38.0, y[0]=-115.0, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=0, eventTime=27743086, downTime=27743066, deviceId=4, source=0x1002 }
D/dalvikvm(24476): GC_FOR_ALLOC freed 122K, 1% free 17271K/17428K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 10K, 1% free 17434K/17604K, paused 7ms, total 7ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 65K, 2% free 17690K/17928K, paused 8ms, total 8ms
I/dalvikvm-heap(24476): Grow heap (frag case) to 17.615MB for 328336-byte allocation
D/dalvikvm(24476): GC_FOR_ALLOC freed 0K, 2% free 18010K/18252K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 18011K/18252K, paused 9ms, total 9ms
I/dalvikvm-heap(24476): Grow heap (frag case) to 18.073MB for 479536-byte allocation
D/dalvikvm(24476): GC_FOR_ALLOC freed 0K, 2% free 18479K/18724K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_CONCURRENT freed <1K, 2% free 18481K/18724K, paused 2ms+1ms, total 10ms
D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 6ms
I/dalvikvm-heap(24476): Grow heap (frag case) to 18.532MB for 479536-byte allocation
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 18949K/19196K, paused 9ms, total 9ms
D/dalvikvm(24476): GC_CONCURRENT freed <1K, 2% free 19418K/19668K, paused 1ms+1ms, total 10ms
D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 7ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 19592K/19844K, paused 8ms, total 8ms
I/dalvikvm-heap(24476): Grow heap (frag case) to 20.049MB for 933136-byte allocation
D/dalvikvm(24476): GC_FOR_ALLOC freed 0K, 2% free 20503K/20756K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_CONCURRENT freed <1K, 2% free 21416K/21668K, paused 1ms+1ms, total 12ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 50K, 2% free 22351K/22580K, paused 7ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 5K, 1% free 23900K/24140K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 1% free 25824K/26084K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 3411K, 14% free 24528K/28204K, paused 12ms, total 13ms
D/dalvikvm(24476): GC_CONCURRENT freed 2814K, 14% free 24256K/28204K, paused 2ms+1ms, total 11ms
D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 4ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 9266K, 1% free 17270K/17424K, paused 10ms, total 10ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 15K, 1% free 17575K/17748K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 22K, 2% free 17875K/18072K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 1K, 2% free 18195K/18396K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 18517K/18720K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 18838K/19044K, paused 11ms, total 11ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 19159K/19368K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 19480K/19692K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 19974K/20192K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 20616K/20840K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 21431K/21664K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 2% free 22714K/22960K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 182K, 2% free 24004K/24432K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 8478K, 33% free 17593K/26228K, paused 14ms, total 14ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 18K, 32% free 17895K/26228K, paused 12ms, total 12ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 18K, 31% free 18198K/26228K, paused 11ms, total 11ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 1K, 30% free 18519K/26228K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 29% free 18840K/26228K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_CONCURRENT freed <1K, 26% free 19482K/26228K, paused 2ms+1ms, total 14ms
D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 10ms
D/dalvikvm(24476): GC_CONCURRENT freed <1K, 23% free 20297K/26228K, paused 2ms+1ms, total 15ms
D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 11ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 19% free 21260K/26228K, paused 10ms, total 10ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 15% free 22543K/26228K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 182K, 9% free 23979K/26228K, paused 21ms, total 22ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 8485K, 33% free 17598K/26132K, paused 13ms, total 14ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 25K, 32% free 17894K/26132K, paused 12ms, total 12ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 12K, 31% free 18204K/26132K, paused 12ms, total 12ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 1K, 30% free 18524K/26132K, paused 12ms, total 12ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 28% free 18845K/26132K, paused 8ms, total 9ms
D/dalvikvm(24476): GC_CONCURRENT freed <1K, 26% free 19487K/26132K, paused 1ms+0ms, total 9ms
D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 7ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 23% free 20129K/26132K, paused 9ms, total 9ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 20% free 21091K/26132K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 15% free 22375K/26132K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 9K, 9% free 24011K/26132K, paused 14ms, total 14ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 2147K, 10% free 23855K/26456K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_CONCURRENT freed 8776K, 35% free 17337K/26304K, paused 3ms+2ms, total 20ms
W/InputEventReceiver(24476): Attempted to finish an input event but the input event receiver has already been disposed.
W/InputEventReceiver(24476): Attempted to finish an input event but the input event receiver has already been disposed.
W/ViewRootImpl(24476): Dropping event due to root view being removed: MotionEvent { action=ACTION_UP, id[0]=0, x[0]=564.0, y[0]=-50.0, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=0, eventTime=28190972, downTime=28190972, deviceId=4, source=0x1002 }
D/dalvikvm(24476): GC_CONCURRENT freed 186K, 31% free 17626K/25476K, paused 2ms+1ms, total 12ms
D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 4ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 63K, 30% free 17884K/25476K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 3K, 29% free 18201K/25476K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_CONCURRENT freed <1K, 27% free 18696K/25476K, paused 2ms+1ms, total 12ms
D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 9ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 25% free 19190K/25476K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 23% free 19831K/25476K, paused 9ms, total 9ms
D/dalvikvm(24476): GC_CONCURRENT freed <1K, 19% free 20794K/25476K, paused 2ms+0ms, total 12ms
D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 8ms
D/dalvikvm(24476): GC_CONCURRENT freed <1K, 14% free 22078K/25476K, paused 1ms+2ms, total 14ms
D/dalvikvm(24476): WAIT_FOR_CONCURRENT_GC blocked 12ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 7% free 23855K/25476K, paused 10ms, total 10ms
D/dalvikvm(24476): GC_CONCURRENT freed <1K, 6% free 24176K/25476K, paused 2ms+1ms, total 14ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 6440K, 26% free 19562K/26216K, paused 9ms, total 10ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 93K, 23% free 20207K/26216K, paused 10ms, total 10ms
D/dalvikvm(24476): GC_FOR_ALLOC freed 11K, 21% free 20935K/26216K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 18% free 21673K/26216K, paused 9ms, total 9ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 15% free 22499K/26216K, paused 8ms, total 8ms
D/dalvikvm(24476): GC_FOR_ALLOC freed <1K, 10% free 23695K/26216K, paused 9ms, total 9ms

IPhone 4s got problem after I update to 7.1.1. Battery drain so fast

iPhone 4s got problem after I update to 7.1.1. Battery drain so fast

The Ultimate Guide to Solving iOS Battery Drain
<http://www.overthought.org/blog/2014/the-ultimate-guide-to-solving-ios-battery-d rain>

Please Read This To Reduce or Eliminate Problems after Software Update

Hi all, I have been reading quite a handful of Mac users here reporting problems ranging from minor ones like slow downs to major ones like application crashes, and many of them blame the new OS and/or Security Updates.
Without learning more from the details of how did they perform their Software Updates and Install, I am making a huge assumption that it maybe something they did or didn't do, one of the key things they did not do is Repair Disk Permission
Below is what I called, the "ritual procedure" needed to perform before and after a Software Update, and also any other major software installation - to help reduce or eliminate "hiccups" afterwards, I cannot gaurantee that all macs all over the world will not suffer any problems after an update, but by doing so, you may help reduce it; I have 4 macs all together and so far I have not encounter any major problems after many versions updates.
Anyway, I didn't come out with this series of procedures, I read it off somewhere in this Discussion quite a while ago, and thought I share it again with all of you:
1.Before starting Software Update, unplug all external devices, FireWire, USB, hubs etc etc, not just turning them off but unplug the cables off your Mac, leave only your keyboard, mouse and internet connection on (unless you are using a wireless keyboard and/or mouse or on wireless internet)
2.Repair Disk Permission
3.Restart the Mac, then start your SU, do not run any other apps.
4.After finishing SU, restart your mac; If you are updating OS or Security Updates, Restart is required.
5.Repair Disk Permission again
6.Shutdown and re-plug in everything and start up your mac as normal.
I know the procedure is pretty long and "troublesome", especially the unplugging and restarting part, but so far it really has done my macs good, so I am going to "swear" by it... my FireWire, USB devices etc still work as normal.
This is really contrary to that "Macs are easy to use", yes, no doubt about it, but the software updates etc is just well, put it this way: The Mac OS when it comes to updates, is very very delicate... so handle with it great care, it will just turn out okay.
Cheers

Thank you for posting that. I posted a similar set of suggestions here:
http://www.macmaps.com/backup.html
Disclaimer: Reference to links I make to my Macmaps.com website are a for your information only type reference. I do not get any profit from this page, and it is open to the public.

Sync-Problems since iTunes 8.1.1-Update

Since the iTunes 8.1.1-Update I have the problems with the iPhone sync (Windows Vista). iTunes always tells me that I need to activate it otherweise all my apps will be deleted.
Whe I activate iTunes once again, it says that the computer already has been activated. Deleting the SCInfo-Folder (TS1389) does not resolve the problem. Has anybody an idea what to do?
Regards, Olaf

I have spent 2 days with the same problem following installation of 8.1.1 trying to authorize my apps to no avail. I've restored the iPhone, reinstalled iTunes, de-authorized and reauthorized the computer in multiple different sequences, tried each app separately, etc, all with the same result. I can download directly on my iPhone and apps work, but once I sync with the computer, I can no longer manage them. Any one know the answer?

Syncing problem with itunes after restoring to a new PC from iPod

My old PC crashed and I copied my iTunes libray to a new PC from my iPod. The libray includes several songs taken from CD's I purchased plus several songs that I had purchased from iTunes. I also "authorized" the new PC. However, when I sync now none of the purchased songs from my new iTunes file will copy back to the iPod. It will only sync the songs from my personal CD collection. I get a message that the iPod is not authorized for these songs. Any suggestions for a fix?

Try deauthorising your PC and authorise it over again, this can sometimes clear a "not authorised" problem: About iTunes Music Store Authorisation and Deauthorisation
You could also have a look at this article: iPod does not play content purchased from the iTunes Music Store
If you continue to have problems you can email Customer Services from this page, they may be able to help: iTunes Music Store - Authorization FAQ

Smart Playlist problems after iTunes upgrade 10.6.1.7

Hi, I updated my version of iTunes to 10.6.1.7 and since then my smart playlists are not syncing to my iPhone properly. The selection of songs is scrambled, and so I have a variety of my top rated, audiobooks and other random songs. I have tried removing and resyncing the smart playlists to my iphone, but this has the same outcome. Also, the sync doesn't complete all stages so I end up with roughly half of my music from my smart playlist on my iPhone.
Not sure if this is an iTunes problem or iPhone problem, but it definitely only started after I upgraded iTunes.
Any others out there with the same issue or any suggestions?

Yepper.. got the same issue.. it is not sync'ing my Itunes play lists to my I pod touch.

New Outlook sync problem after update!!!

I had the 'original' Outlook sync problem, which went away after the iTunes update to 7.3.1, but now, after the iPhone update last night, I have an entirely NEW Outlook sync problem!!
When I sync the iPhone, right when it gets to the 'syncing contacts' part (that you see in the top box/window in iTunes) I get an error message that I haven't seen before. It says "AppleMobileDeviceHelper has encountered a problem and needs to close..." and it gives me the option to send an error report. I dismiss the error box, and the sync process hangs, and iTunes becomes unresponsive.
If I open Outlook, the two Apple sync oblects are still enabled, and get no error message. If I re-open iTunes and try to sync again, it only syncs iTunes content, and never even tries to sync my contacts or calendar.
Anyone having anything similar since last night? The only thing different is the iPhone firmware update.

I just cancelled the sync by using the slider. I didn't realize I could do that. The phone seems fine. I may try it again and see what happens.

3gs syncing problem after itunes update to itunes 7

Similar Messages

Maybe you are looking for