Problems after SW update and then *#7370# reset on...
I updated my E63 software to 510.21.010 using the NSU available from CNET. Whatever applications were installed on the memory card were not visible in the installations folder but i could see "installed" in the application manager. So i saved all my things on the computer and did the *#7370# restore and formated the card as well. Now the Nokia store doesn't open and when i go to the Nokia site it asks me to download a different phone's nokia store(i deleted the nokia store from installations as well)....please help
Thanks in advance.
Solved!
Go to Solution.
@siddharth2694
For a S60 3rd FP1 device like your E63 provided that you used "Backup phone memory" to memory card and most of applications installed upon memory card would have been easily recoverable after "hard reset", although there would be some strange alphanumeric titles at top of installed applications requiring re-installation; it wasn't a particularly good time to chosse to re-format memory card.
You need OviStore_31_prdSrv_1_22_015_18376.sisx which is the same for a number of S60 3rd FP1 devices.
Happy to have helped forum with a Support Ratio = 42.5
Similar Messages
-
Camera problems after Lolipop update and 60 fps on 1080p
Need help! After updating to Android 5 Lolipop, back camera doesn't work! When I press button to make a picture, it is just freeze and do nothing, but front camera works fine. How can I fix it? I did factory reset, trying to update my phone again, and nothing, still the same problem
Yeah! I got the same idea and downloaded "Camera360 Ultimate" from Market, I heard this is most popular app for camera and HAVE THE SAME THING!
Front camera is ok, but main camera don't want to take pictures too, that's made me really sad -
after my update iOS7 then I am facing the problem
of cannot update my purchase software & keep on showing
that I am in US store although I updated in Singapore. Only things is i was traveling to US & Europe recently. How to fix?Try This...
Close All Open Apps... Sign Out of your Account... Perform a Reset...
Reset ( No Data will be Lost )
Press and Hold the Sleep/Wake Button and the Home Button at the Same Time...
Wait for the Apple logo to Appear...
Usually takes about 15 - 20 Seconds... ( But can take Longer...)
Release the Buttons... -
Photoshop CS 5 crashes after updating and then using File -- Automate -- Batch
I am running Photoshop CS5 (build 12.0.4 x32) on my XP 32-bit machine and have done so without major problems until about a week ago.
Then all of a sudden when accessing File --> Automate --> Batch the program crashes and I have to force it shutting down manually after which I can restart Photoshop. When trying to access the batch command hereafter the same crash reappears rendering batch commands useless.
I thought about posting here but then decided to reinstall Photoshop again. This enables the fully working software including batch commands once again. However after a short while the update software asks to download and install some patches for all programs. After doing so the same problem happens again in regards to the batch command. Photoshop crashes when accessing it and won't work at all.
I now repeated this procedure twice and have no idea what to do about it.
Is there anybody that has had this experience or knows about a solution?
Do I have to contact Adobe with an error report?
Any help and comment is welcome and mostly appreciated.Chris Cox wrote:
Yes, a change in the Adobe update made the existing scanner bug show up more frequently. No, that does not make your statement correct. The bug exists in the scanner driver, and existed before the Adobe update.
The Adobe update is not the cause of the bug, it just made some unrelated change that made the bug appear more frequently. That could be something as simple as putting different values in different locations of memory. We don't know. Only the authors of the scanner driver can know for sure why it is crashing more often now.
Photoshop supports the TWAIN standard, but cannot be responsible for the bugs in the third party drivers that attempt to implement that standard.
The high frequency of bugs in TWAIN drivers is what made us move the TWAIN plugin to "optional" status in the first place -- because too many people were crashing, had a hard time figuring out the cause, and blamed Adobe for something completely beyond our control.
And we already do inform scanner vendors about all the bugs we find in their drivers. But we cannot force them to fix their bugs, nor can we know the nature of all of their bugs to code around them.
I understand that you're angry. But please stop trying to blame an innocent bystander.
Adobe cannot do anything to fix the bugs in your scanner driver. Only the authors of your scanner driver can fix the bugs in your scanner driver.
Until they provide an update to fix the bugs in the driver, your choices are to keep crashing, or not use that buggy scanner driver.
I am going to make this short.
It depends on how you look at it. From your angle, Adobe did their's and the scanner companies are to blame for their buggy software. What you are saying here would be - if compared - resemble a situation where you would go to a car dealer, buy a car, then drive away just to find that the trailer tow hitch you attached your old trailer to would keep falling off all the time. When confronting the dealer about the issue he would reply to you that you have to talk to the manufacturer of the trailer because the problem is their responsibility. How would you as a client react...?
Maybe it is true that the driver software is buggy. However it still did work though under other conditions before this update. That means that you updated something that made these things appear frequently. Maybe you don't know and only they do. Fair enough. But us customers don't have to work these problems out or live with them nor do we have to use our time on posting and fixing companies' errors and mistakes. That's what we pay you for. We only need to use this application hassle free on the spot. Maybe you should start crash testing in an controlled environment before you apply these updates and then post them. Or make a deal with those companies to do so for you. Maybe they will then ignore you or won't tell you about possible bugs to hike their own skin. Fair enough as well. Create some sort of program, a label or whatever that you apply and hand out only to those companies that are "certified by and working with Adobe software" and that they can put on their products or you on your very own Adobe website for all us customers to see and to use as a type of guidance in order to have working hardware and applications and avoid these errors.
There is this saying that goes...
"Where there's a will, there's a way"...! -
After the last up date for Safari (Mac OS X 10.8.5 in a iMac mid 2011 21.5 inch 2.8GHz Intel Core i7)
The window don't open or they are there and only in an outline, kind of like they're behind the screen.
I have also done a system update and then a system reinstall.
What now? incident nr, 526941222.After the last up date for Safari (Mac OS X 10.8.5 in a iMac mid 2011 21.5 inch 2.8GHz Intel Core i7)
The window don't open or they are there and only in an outline, kind of like they're behind the screen.
I have also done a system update and then a system reinstall.
What now? incident nr, 526941222. -
Sudden thin white line acroos the top of my screen after software update. Can NPRAM reset help to solve or is it permanent pixel problem?
Try PRAM reset.
Reset PRAM: http://support.apple.com/kb/PH14222
Best. -
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 -
my phone is still disabled after software update and i cannot seem to reset my passcode someone please help
Does the Ipod see the network?
It sure sound like the drop cause some other internal damage like breaking/loosening the connection to the antenna. See:
http://www.ifixit.com/Teardown/iPod-Touch-4th-Generation-Teardown/3562/3 -
I don't have enough space to update my iPhone 5s. I back it up every night. I'm wondering if I can reset, update and then add the data back to my phone. Is there a better way? I've tried deleting pics and apps but still can't get enough room.
Try updating it via iTunes on a computer.
Also, to find out what is taking up so much storage go to Settings>General>Usage>Manage Storage. It will list what is taking up your storage starting with the one that is taking up the largest amount.
Cheers,
GB -
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 -
Xperia z1 Problem AFTER system update to latest software 14.3.A.0.681
Hello people, First of all let my just say that I am new into the ''smartphones world'' so please excuse my queries if they proof to be 'obvious' to you! I have carried out a system update to my Xperia Z1 phone yesterday (Android 4.4.2. kitkat, latest available software 14.3.A.0.681). The update seem to have been correctly performed. However I have since encounter the following issues/problems with my phone and do not know how to fix them: 1) First of all my phone will no longer rotate...why is this? Is this related to the update?? Pictures/photos can no longer rotate and also phone screen does no longer rotate! Why is this..? 2) Second the 'Notifications Bar' structure has changed : is this also the result of the update or can I do something in settings to fix it and make it as before? When I scroll dawn the notifications bar, the icons are no longer displayed at the top line but are instead spread underneath BUT this is AFTER I press 'Quick settings'. 3) Battery signal icon has changed completely: no lines included inside icon to show usage but instead usage %age is now displayed. Also, when I charge my phone, there is no icon flashing as before and now lights flashing.. 4) Also when I want to use the phone after it has remained unused for sometime it states 'swipe to unlock' and makes a 'funny' note upon performance of the act: this was not the case before.. Can you please help me with the above? I am freaking out because I am excited with my new phone and would love to make full use of it properly but it is a bit hard for me since I have no clue how to fix issues/problems appearing every now and then since I am new into these things.. Thanking you in advance
Hi there,
I think you have fixed your 1st issue.
2) Yes, Kitkat has changed the Notification Bar structure. Its a bit annoying, but to get around it you can use Widgets - Tools and select the Icon, such as WIFI to be placed on your home screen to avoid multiple clicks. You cant do anything in the settings to make it like before.
3) Battery Signal Icon - Again a Kitkat update has done that. The good thing is that it has enhanced Battery life considerably.
4) I am assuming you are stating about the "sound note" it makes when you swipe in. Thats again a Kitkat feature and you can get rid of it though Sound settings if you dont like it.
Reality is that Kitkat runs very well on Google Nexus 5. Apart from that it has issues on every other Android power Smartphone out there. I also own a Nexus 4 who recently got upgraded to Kitkat and compared it with Nexus 5. Was not impressed to be honest.
As of my upgrade on Z1, I have been facing Volume issues. When I play a video the volume is minimized for some reason. Pause and play again and it goes to Normal. I have to reboot it sometimes to play normally. It also takes ages to connect to my 3G provider, whereas previously it was fast enuf. I hope the next upgrade will fix those issues. -
Many problems after last update
Ok, I will tell my actions step by step, because this update and my Arch now = big mess.
I started the update (yaourt -Syu) in the end of January. Because my internet connection is not always working properly, I have to repeat this many times to start the actual update (after downloading ALL the packages). This time, I couldn' t download all the packages and then I went on my winter break. After I returned home, I continued update (1/2 Feb). Firstly I' ve done yaourt -Su to end this old update and then yaourt -Syu to download rest of the packages. And then I restarted my Arch...
What happened first was, that Entrance (I use e17 as my graphical environment) was not working. Using LiveCD (the consoles are not working - agetty is broken, but it had been broken long before this update) I changed it to GDM. Also not working. Then I switched to KDM from KDEmod. It worked. I couldn' t start E and in LXDE panel was broken. I started KDEmod and everything from Qt worked fine. But all GTK was broken, and I couldn' t start any NetworkManager client. And not only. I discovered, that many of programs need older version of libpng (libpng12.so.0) and some of them also libjpeg (libjpeg.so.7). I borrowed these files from my friend, who also have Arch, but hardly ever updates it and copied to /usr/lib. The programs started working. But soon, all KDE and stuff broke. I discovered, that newer versions of libraries are not detected. I switched to GDM. Now I am running GNOME. Qt(mod) is not working since it needs newer versions of libraries. And for more, none of my network interfaces is working. I tried to connect to wireless network and by cable and nothing of it worked (with NetworkManager). I can' t even connect with my loopback interface to eg. CUPS (I can' t print) or MPD (I can' t connect to server by MPD client)!!!
And now I need your help...
What I want:
1. WORKING NETWORK!
2. Programs - how to make them use newer versions of libpng and libjpeg.
3. Entrance - all I know is "Id "x" respawning too fast. Disabled for 5 minutes"
4. Enlightenment - it' s not working anymore! How to get it to work?
If someone knows, I would need also help with consoles. I installed fbgetty (agetty is not in repo anymore) - how to configure it to make the consoles? Or how to get agetty to work? ("Id "c<number from 1 to 6>" respawning too fast. Disabled for 5 minutes" - all I know about consoles not working). I have changed them from /dev/vc/<number> to /dev/tty<number>. but it wasn' t working. And it isn' t now.
Please help me!I tried starting enlightenment_start from console, and here is the result:
phitherek@phitherek-laptop ~ $ enlightenment_start
E - PID=15643, do_precache=0, valgrind=0
ESTART: 0.00000 [0.00000] - begin
ESTART: 0.00009 [0.00008] - signals done
ESTART: 0.00012 [0.00003] - determine prefix
DYNAMIC DETERMINED PREFIX: /usr
ESTART: 0.00037 [0.00025] - prefix done
ESTART: 0.00040 [0.00003] - eina init
ESTART: 0.00057 [0.00017] - intl init
ESTART: 0.00060 [0.00003] - parse args
ESTART: 0.00061 [0.00001] - arg parse done
ESTART: 0.00063 [0.00002] - ecore init
ESTART: 0.00405 [0.00342] - ecore_file init
ESTART: 0.00426 [0.00021] - more ecore
ESTART: 0.00427 [0.00001] - x connect
/usr/bin/enlightenment: symbol lookup error: /usr/lib/libecore_x-ver-pre-svn-05.so.0: undefined symbol: XIQueryVersion
Can somebody help me with this. I have the latest packages from ftp.archlinux.org. I guess libecore is the problem...
EDIT: Maybe not. I made scripts, which logs output of enlightenment_start and enlightenment, linked them to KDM Enlightenment Session, logged out and tried to run e...
Here is the log from enlightenment_start:
phitherek@phitherek-laptop ~ $ cat e_start_log
ESTART: 0.00000 [0.00000] - begin
ESTART: 0.00007 [0.00007] - signals done
ESTART: 0.00010 [0.00003] - determine prefix
DYNAMIC DETERMINED PREFIX: /usr
ESTART: 0.00030 [0.00020] - prefix done
ESTART: 0.00036 [0.00007] - eina init
ESTART: 0.00051 [0.00015] - intl init
ESTART: 0.00055 [0.00003] - parse args
ESTART: 0.00056 [0.00001] - arg parse done
ESTART: 0.00058 [0.00002] - ecore init
ESTART: 0.00401 [0.00343] - ecore_file init
ESTART: 0.00424 [0.00022] - more ecore
ESTART: 0.00425 [0.00002] - x connect
Log from enlightenment is empty...
Can someone help?
EDIT2: ok, I tried arche17 script and e works now quite fine (not including strange fonts in menu and modules, desktop problems like disability to move icons and double launch of programs after clicking a shortcut).
So, finally, after long time since update, my system is working more or less like before it (When I say system, I don' t mean Arch itself, but Arch with my favourite WM and my settings). I won' t update it for a longer time now, because I want it to work
Thank you everybody who helped!
Last edited by Phitherek_ (2010-02-14 19:13:13) -
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
-
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.
CheersThank 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. -
I have an iPhone 4, and I go to Settings, General, Software Update, and it says iOS 5.1.1 and I tap on the Install Now, and Agree, then i get the verifying update, and then it says "unable to install update, an error occured installing iOS 5.1.1
I have exactly the same problem. iPhone 4S, never been jailbroken. Not behind a firewall and it happens whether I am on my home compute (iTunes) or directly thru Settings_Update.
Looks like loads of people are having the same problem - and as far as I can see, Apple's sole reply is jailbreak or behind firewall/ security settings/anti-virus. None of those apply here!
Maybe you are looking for
-
Hi, While i m trying to drop a user it shows the following error: ora -04021:timeout occurred while waiting to lock object sys.dbms_lock; The user is not dropped.How to avoid this error??? Thanx..
-
when i burn videos to a dvd-r disc it works on my macbook but not on a windows/pc or my dvd player. How can i make it work on all the above and not just a mac product?
-
Characteristic infoprovider not available while creating query
Hi All, I have a characteristic infoprovider(user defined) in both Dev and Prod(transported-same properties), i can create new query in dev using query designer(BI 7) but not in production. It is defined as infoprovider in the business expl tab of in
-
when i sync my ipod touch to my itunes to change the music it doesnt give me the option to manually sellect playlist or songs as it did previously. is wifi the only way to play music now? i just want to add 2 play lists and it wont let me
-
[SOLVED] Fonts antyaliasing in KDE 4.3
I cannot see any option to turn antyaliasing on in system-settings (this is new install with KDE 4.3 installed kde-meta-kdebase, kde-meta-kdeadmin). Which package should I install to be able to enable antyaliasing ? TIA Last edited by hadrurus (2009-