Welcome to Vodafone Community
The headphone problem seems to have occurred with other models of phones when being upgraded.
I tested this app https://play.google.com/store/apps/details?id=com.
It's not ideal, as you have to manually change it to direct the sound to the inbuilt speakers or bluetooth, but might be a workaround for those that can't listen to their music/podcasts the way they like until a better fix comes along.
Hopefully Vodafone wil cover the cost of this paid app until they fix the problem they created.......VODAFONE - any updates - have you replicated the bug? What have you done? Or are you just going to bore us out and do nothing and hope we go away which is their normal strategy in such cases - perhaps a "were working on it and will let you know" approach as usual i.e. dont call us we (wont) call you!
Wow, you people are babies.
I number of people have mentioned the app before - thank you to them - sorry I didnt click thanks on thjis one
I tried it but a messgage said it was only free for a few days to help you decide i you want it or not - then you have to pay - I apologise if i got this wrong. Can someone advise please. The poster also said there may be an issue with volume on the app?
I consider the aux issue to be a major and unacceptable fault and it should not exist. I am currently ussing my Nokia N95 to connect to the stereo - if that can manage it a modern phone should - plus how about people who need to connect to incar hands free.
Vodafone got the software right before on the first version but when they introduce a number of bugs with a software update I consider it unacceptable. This is the most major one. I expect things to be right and that I can power my stereo off my phone as I have sonce my P910i!
I do not appreciatre being called a baby - please keep it polite and your insults to yourself. I have owned smartphones for years but this is the biggest bug introduced yet in my experience. £100 phone or not it should get the basics such as this right.
I had experience along with a number of people with data freezing issues on a Galaxy S2 and Vodafone were hopeless at resolving this - we never got a fix. Thus I am keen to keep some pressure on with them to avoid a repeat where it was a constant "we are looking at this" but no resolution.
"I apologise if i got this wrong. Can someone advise please."
You are wrong. See my post above.
Or ask the poster whom you think is worth of your thanks (but I notice you didn't thank them either)
Gracious response. Thanks.
Absolutely Vodafone should fix it.
As for soundabout, the message that pops up is that Pro features cost money, but they will give you a free taste. As far as I can tell from the list of pro features, none of them are required to make simple headphones/speakers work.
Also, there seems to be a widget included that lets you change from wired headphone to inbuilt speaker. That would probably be essential to make it usable.
Since I did the recent update, my Smart Ultra 6 has gone literally CRAZY!!! Have a look by yourself:
Has anyone experienced the same?
The phone is literally unmanageable – like a crazy horse.
I am desperate as I have already reset it to factory setting twice, without reinstalling any app whatsoever. Nothing has changed.
Anyone from the Tech Team able to help?
@rinopucci1 that looks like a hardware bug to me. Like the phone is detecting the overview (right) button is being repeatedly pressed.
If mine was doing that, I'd take it in to a vodafone shop.
I am abroad at the moment but on Tuesday first thing I'll go to a Vodafone shop. It definitely sounds like a bug, hearing that also others have been affected only confirms this assumption.
I'll make mention of other similar cases and I'll keep you posted!
Thread title includes 'app problems' but I see other Marshmallow upgrade issues so can I add mine here?
After upgrading my Smart Ultra 6 from 5.1.1 to 6.0.1 it reports that the Micro SD Card is corrupt. The only thing it will let me do it set it up again, i.e. it asks me if I want to format it, which I'd prefer to avoid. I took the card out and can read it fine on my Mac, so there's nothing wrong with the card. Anyone else had this?
I tried the steps here but didn't fix the issue. http://www.tomsguide.com/faq/id-3063631/fix-card-r
Hi, yes, a factory reset and reinstalling all my apps (including corporate settings and connections) sounds more effort than the SD card backup/reformat/restore that I was hoping to avoid by there being a fix. Seems the latter is unavoidable.
So 'reformatting' the SD card on my phone is not working. It says card is ready to use, but then it still appears as corrupt to my phone and, after supposedly formatting it on my phone, I put the card back into my Mac and all the data is still on it!
Sometimes when you update an Android device, depending on the data that’s stored on the SD Card, it can become unresponsive or corrupted. If your Mac can read the card but not view anything, it’s defiantly corrupted.
This primarily includes any .apk data. It’s strange that it’s readable on your Mac and not your phone - I’d recommend reformatting the SD card while it’s in your Mac.
Once you’ve formatted it to a universal format like FAT or FAT32 (FAT32 is the preferred format for most Android ROMs), it should start working in your phone.
Make sure you back up any information from the SD card before formatting - you can do this in Disk Utility on your Mac.
Let me know how you get on
I already tried formatting it on my Mac using SDFormatter, both Quick Format and Overwrite Format in that tool. Both showed successful completion, but when re-inserting the card (via an SD adaptor as it's a microSD card) into my Mac the previous data all appeared. I can open .jpg, .mp3 and other files from the card, on my Mac, after it was supposedly formatted. Mac reports the format as ExFAT, for what it's worth. Card unreadable on phone.
edit: running Disk Utility/First Aid on the card shows the following, but rerunning it keeps giving the same error, so it's not being fixed even though it claims to be.
Repairing file system.
Checking main boot region.
Checking system files.
Checking upper case translation table.
Checking file system hierarchy.
Incorrect checksum for directory entry set.
Checking active bitmap.
The bitmap needs to be repaired.
Rechecking main boot region.
Rechecking alternate boot region.
The volume was repaired successfully.
File system check exit code is 0.
Updating boot support partitions for the volume as required.