Database Info

Visual Voicemail not working in Fresh 1.1

Is anyone else having issues with visual voicemail in Fresh 1.1? When I first flash the ROM it works fine, but then a day or so later it stops working. The first time I flashed i didn't do a wipe, so I thought that maybe if I did a wipe then flash that would resolve my issue; that didn't work either same issue.
Any ideas?

What exactly is "not working"?

sorry to jack the thread, but mine isn't working either. I was running the AOSP 2.0.1 rom, and I switched back to Fresh 1.1. Now my visual voicemail is making me call my phone number. I'm also using modaco's custom kernel, if that helps.

Kcarpenter said:
What exactly is "not working"?
Click to expand...
Click to collapse
I can open the application and it shows me the voicemails, but when i open one it looks like it is playing, however, there isn't any audio.

Hmm...mine is working just fine on Fresh 1.1
I did have to turn up the volume using the rocker volume buttons as I thought there wasn't any audio at first too, and I know that sounds like a "you're a noob" answer, but it happens to the best of us
I think there's an apk of it floating around here somewhere, try to reinstall it if you're still having problems.

Bluetooth apk

Can anyone tell me which bluetooth apk controls pairing and phonebook downloads, and if there is any way to edit it
Thanks

nope
you cannot change the bluetooth file. once its made its made. you would have to make your own and to know all the codes you would need to be a developer. and why would you even want to change bluetooth files?

jordan5555 said:
you cannot change the bluetooth file. once its made its made. you would have to make your own and to know all the codes you would need to be a developer. and why would you even want to change bluetooth files?
Click to expand...
Click to collapse
I have a uconnect car bluetooth, had problems with phonebook downloading, so I renamed bluetoothpbab and no more problems, doesnt even ask to allow phonebook access. Just curious as to what's in the apk

nmandi said:
I have a uconnect car bluetooth, had problems with phonebook downloading, so I renamed bluetoothpbab and no more problems, doesnt even ask to allow phonebook access. Just curious as to what's in the apk
Click to expand...
Click to collapse
I'd really like to know how to read bluetoothpbap.apk if anyone can help

I seem to be having the same problems as you have and am curious if you have had luck resolving them. My Bluetooth won't download the phonebook and frequently disconnects after trying (paired to my car).
I have tried re-pairing and updated my ROM to Phoenix 4.1 when it came out. I didn't have this issue with the stock ROM but it started happening in Phoenix 3.5 and continues in 4.1. This is my only problem with Phoenix and I'd really like to have it fixed.

darkfus said:
I seem to be having the same problems as you have and am curious if you have had luck resolving them. My Bluetooth won't download the phonebook and frequently disconnects after trying (paired to my car).
I have tried re-pairing and updated my ROM to Phoenix 4.1 when it came out. I didn't have this issue with the stock ROM but it started happening in Phoenix 3.5 and continues in 4.1. This is my only problem with Phoenix and I'd really like to have it fixed.
Click to expand...
Click to collapse
Do you have root explorer, if you do, go to /system/app/bluetoothpbap.apk and rename to bluetoothpbap.apk.bak. reboot your phone and pair again with your car. It worked for me. Let me know if it works for you

nmandi said:
Do you have root explorer, if you do, go to /system/app/bluetoothpbap.apk and rename to bluetoothpbap.apk.bak. reboot your phone and pair again with your car. It worked for me. Let me know if it works for you
Click to expand...
Click to collapse
I tried your fix and gave it a day or two to make sure it kept working every time. It does! Thanks!
I am not sure what that module does, but I'm not missing anything noticeable. Thanks Again!

darkfus said:
I tried your fix and gave it a day or two to make sure it kept working every time. It does! Thanks!
I am not sure what that module does, but I'm not missing anything noticeable. Thanks Again!
Click to expand...
Click to collapse
Happy it worked for you
Sent from my SGH-I897 using XDA App

Definite issue with BT media and ICS ROMs

FYI, there is an issue with pretty much all ICS ROMs and the BT stack included in them. I have a brand new, top of the line Jawbone BT that supports everything, works flawlessly in Cyanogen and non-ICS ROMs, but will barely work in ICS.
Basically, after a reboot, it connects and says Connected (no media), then switches to Connected. Everything works fine until I disconnect and reconnect again.
After that, it will work for only voice calls. Media will always go out the speaker. I have tried everything to fix it to no avail. The only resolution to get A2DP media streaming back is to reboot.
When it happens, the media checkbox is still there and checked, but it doesn't work. I switched back to HyperSensation (Cyanogen) and everything works as it is supposed to.
Apparently ICS bluetooth works fine for some BT headsets and not others. This also seems to be an ongoing problem for other phones as well, even non-ICS.
I am not well versed in reading the debug logs, but if anyone is interested I can post them here, provided they tell me which ones they want.

I'm having troubles to. My problem is I cannot start a call via the Bluetooth Dial button on my radio. It's as if the phone doesn't even recognize that you are pressing the button. Tried installing Vlingo, but the prompt doesn't even work anymore.
The old solution was to install the Voice_dialer.apk...but that doesn't seem to be compat either

I can confirm the issue with the virtuous ICS as well. I have bt stuff from Jawbones to BlueAnt's and all have the same issue. Prior to this was the issue of cutting out and now it's the off/on bt streaming. To "fix" the issue, is to reboot. Annoying yes. But ICS is still so sexy

I've got the same problem, ROM Elegancia ICS 1.0.6 and 1.1.0
After pairing with bluetooth headset, first time I play music everything is ok. after re-connecting, music controls works ok, but sound is thru phone's speakear not thru the headset.
After rebooting the phone the situation is the same- first connection everythings ok, another ones not.
Checked with SE MW600, Jabra extreme and car's bluetooth.
The problem occurs even with clear installation (before I restore backups).
Still can not find solution so I got back to GB.

So its not just me! I can confirm that my Beats Wireless acts exactly like described.. And with a reboot fixing it again!
I think the devs here might be able to fix it, but its properly not going to be an importent issue to fix.. Fingers crossed for a fix, or maybe the future leaks will have it done!
Sendt fra min HTC Sensation Z710e med Tapatalk

ftblstr2319 said:
I'm having troubles to. My problem is I cannot start a call via the Bluetooth Dial button on my radio. It's as if the phone doesn't even recognize that you are pressing the button. Tried installing Vlingo, but the prompt doesn't even work anymore.
The old solution was to install the Voice_dialer.apk...but that doesn't seem to be compat either
Click to expand...
Click to collapse
Vlingo has always been problematic for me... My solution (worked on ICS too) was to get it working on an older ROM (not sure which one anymore) then use titanium backup and back up APP+DATA on a ROM that it is working on. Then, restore APP+DATA on the new ROM.
The first time you hit the button on your headset it will ask you what app you want to use for voice dialing and give you Vlingo, Vlingo InCar, or Voice Search. Choose Vlingo and check the box to make it default and you are good to go.
Just make sure after you get it working on the new ROM to back it up again... then the next time you switch ROMs, restore whatever the latest backup is. I am not sure what it changes, but I have been through Cyanogen, all of the ARHD versions, all of the InsertCoin versions, and a few others (I can never make up my mind on ROMs) and this trick has worked in all of them.
IMPORTANT: Make sure in Titanium Backup to uncheck the option to restore system libraries in ROM (that can cause issues going between major versions of android), and make sure toenable the features in Titanium Backup for attempting to migrate data.

I also get the same issue when I try to connect my MW-600 with ARHD ICS 6.0.2.
Can anyone help?

You guys who just have to reboot your phone are getting off easy. When I lose Audio Streaming to my car head unit, I have to delete the device and re-pair it to my phone after a reboot.

Same here with mw600 on virtuous Inquisition 2.0.1. Only first connection plays music through headset.
I am sure that first 4.0.1 beta base was not affected. This bug came with 4.0.3
Sent from my HTC Sensation using Tapatalk

dante-fu said:
Same here with mw600 on virtuous Inquisition 2.0.1. Only first connection plays music through headset.
I am sure that first 4.0.1 beta base was not affected. This bug came with 4.0.3
Sent from my HTC Sensation using Tapatalk
Click to expand...
Click to collapse
really??.. Im gonna try an old backup then.
Edit:
Backup was removed sadly.. :/ cant test it, but maybe someone else can?

Well, the ROMs are still there to download
With 4.0.1 I was on radio version 10.59. I am not expert on radios and RILs but I guess these things affect also BT performance. Right?
Sent from my HTC Sensation using Tapatalk

Shidapu said:
really??.. Im gonna try an old backup then.
Edit:
Backup was removed sadly.. :/ cant test it, but maybe someone else can?
Click to expand...
Click to collapse
I reverted back to the virtuous 4.0.1 build from the most recent (having the new fw and radio) and has fixed the Bluetooth issue. Now I just have to live with messed up signal bars and a browser that randomly exits.
Sent from my HTC Sensation using xda premium

Hi,
Reporting this BT issue for me (SGS 2 with ICS 4.0.3, XXLP2 that can be found on XDA, originally from samfirmware):
I try to send files from my laptop to my SGS 2, 1 at a time and the transfer will suddendly halt some of the way through and ICS looks like it's rebooting but it's actually not, I mean not a full proper reboot; the phone does not switch off, the boot anim plays as if restarting, first BT is off then the icon come up in the top bar...
Hopefully, the Simple & Clean, ICS version, is round the corner ;o)
beng

using arhd 6.1.1 here on sensation XE with SE mw600 headset, no issues, calls and media working as normal

BT connectivity seems to be fixed in the latest leaked ICS + Sense RUU.
Is the sensation supposed to support any other remote control features than pause and play over BT?

I can confirm that on my Galaxy s2 using the 'official' ICS rom released yesterday still causes my phone to reboot.
This happens when bluetooth is paired with my car stereo and streaming audio or voice calls. It causes a reboot, usually happens after 10-15 minutes.
Never happened on gingerbread of any version. And has happened on all versions of ICS leading up to 'official' release.

I can confirm that bluetooth will cut off and be off completely quite randomly while listening to music or Pandora.
Only a reboot gets bluetooth to turn back on.
I have experienced this on two Motorola S9-HD headsets on various ICS roms
Sent from my HTC Sensation Z710e using Tapatalk

UCLD2 Bluetooth Problems

I'm one of the unlucky few who can't get Bluetooth to work with UCLD2 leak ICS.
It doesn't affect everyone. Just some folks.
It crashes for me and I've tried three different ROM's.
UCALC4 doesn't have the problem with bluetooth for me.
Just wondering if anyone out there has come up with a fix for it, or if you have found any custom ROM's that don't have the problem?
Please don't say CM9 because it's using the older Bluetooth code from Gingerbread (IMO) and has a couple other issues that aren't working out for me. Great ROM otherwise though.

CZ, u tried sky ics ucld2 base with the different cwm flashable Bluetooth fixes seanscreamz has? It seems he tried to import the stack from uclc4

icenight89 said:
CZ, u tried sky ics ucld2 base with the different cwm flashable Bluetooth fixes seanscreamz has? It seems he tried to import the stack from uclc4
Click to expand...
Click to collapse
Yep, tried the base by itself, then also tried the #1 and #2 bluetooth fix.
None work for me.
Had to go back to SkyICS UCALC.
My stereo is the double-din JVC unit.

bluetooth fix
I read that a new base is out for SKY ICS and a lot of people are saying that it fixes the bluetooth issue for them.

Tried it. Twice.
Sent from my SAMSUNG-SGH-I727 using xda premium

Duplicate post
Sent from my SAMSUNG-SGH-I727 using xda premium

CZ Eddie said:
Tried it. Twice.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Are you using darkside to wipe between flashes if so don't. And check your md5s with the files on the SD
Sent from my SGS2 LTE

mr_clean5953 said:
Are you using darkside to wipe between flashes if so don't. And check your md5s with the files on the SD
Sent from my SGS2 LTE
Click to expand...
Click to collapse
I do use darkside.
Sometimes before wiping and sometimes after.
Have downloaded UCLD2 twice, so that's *probably* not the problem.
I hope this Canadian ICS release has some additional Bluetooth fixes.
Otherwise, I may go back to Gingerbread before long.

did you install the radio following Sean's instructs:
http://forum.xda-developers.com/showthread.php?t=1600420
My first ICS rom was a bust.
Then I installed the radio and afterwards installed Sean's 4.2d9:
http://forum.xda-developers.com/showthread.php?t=1602216
I did it exactly, no superwipe, used the cwm touch he said to. Installed the base, then the update. Did not install the bluetooth mods. Only thing I installed was a different battery to fix the ics signal bars from greay to blue.
BT works better than it ever has. I was streaming Slacker and running nav on the way via BT to my Ford truck via Sync to test.
(Sync in my 2010 has always been twitchy; never worked right with my Atrix <previous phone>)
Also BT to a home speaker system is great, also.

rpolansky said:
did you install the radio following Sean's instructs:
http://forum.xda-developers.com/showthread.php?t=1600420
My first ICS rom was a bust.
Then I installed the radio and afterwards installed Sean's 4.2d9:
http://forum.xda-developers.com/showthread.php?t=1602216
I did it exactly, no superwipe, used the cwm touch he said to. Installed the base, then the update. Did not install the bluetooth mods. Only thing I installed was a different battery to fix the ics signal bars from greay to blue.
BT works better than it ever has. I was streaming Slacker and running nav on the way via BT to my Ford truck via Sync to test.
(Sync in my 2010 has always been twitchy; never worked right with my Atrix <previous phone>)
Also BT to a home speaker system is great, also.
Click to expand...
Click to collapse
You should go on sync my ride site make an account and ask them when are you getting a SYNC update, I got my usb and sd car(with new map) two weeks ago, and my car is 2011. The new SYNC is amazing, smooth.
---------- Post added at 03:40 PM ---------- Previous post was at 03:35 PM ----------
I am Running Seans Sky Ice, amazing ROM
Issue for me is car bluetooth, and after working for couple of days it started to connect and reconnect again, after I've been listening to music, so my guess (and this is after testing new radios and few other things) is stock music player does something to bluetooth or bluetooth permissions (as as well as phone it also connects to the car) and once there some connection issues when trying to turn it on through the car, the whole thing just does not work properly.
I never had a problem from update 1 to 6, it started on 8 and seems to happen on 9 again. So for the threads out there that say I've tried all the ROM and it's the same, no it's not it was fine on Update 6 here.
If you are running any other ROM, do a back up and flash Fix 2 first and then if it does not for flash Fix 1, thank you to seanzscreams.
Possible Fix:
What I did is i did a nandroid restore ( and yes it is a good idea to do a back up right after you flashed both base and update and set up LTE, to keep a clean copy)
!!!1) Before setting up or even turning it on, in Titanium Back up, freeze stock music player. !!! and it is important to do so before touching BT, as it may affect permission and this will not work(make sure not to touch MusicFX as it also affect BT permissions)
2) Reboot the device
3) Open Google Music Player and set up your music( please note if you have more then one playlist, make sure you set them up right as songs wont play continually and you will not have ability to skip them using car controls)
Google Play is same as stock, meaning same functionality, same car features and all, so you are not really loosing anything.
4) No close it
5) Go ahead set up BT with the car, you should get two messages one to permit access to phone book and one to permit accesses to call history (well it depends on the car, but if you have a newer system in it they yes) check mark the box so it does not ask you again and click yes/accept.
6) Enjoy. Should be good from now on, I've been listening for it all day, will test it more and let you know.
Please also share your experience and thought on the problem, so maybe I am wrong and it's not the issue and it's something else and we can all get it fixed.
Thank you.

BLUETOOTH IS WORKING NOW!!!!
Unfortunately, none of the possible fixes listed above ever worked for me or other JVC car stereo guys that I know about.
But the newest leak, UCLE2 is working just fine.
Thought it took much longer to recognize my stereo than normal (could just be a one-time issue), it was buzz free, error free and playing my Pandora perfectly!
Here's the leak download:
http://forum.xda-developers.com/showthread.php?t=1652679

CZ Eddie said:
BLUETOOTH IS WORKING NOW!!!!
Unfortunately, none of the possible fixes listed above ever worked for me or other JVC car stereo guys that I know about.
But the newest leak, UCLE2 is working just fine.
Thought it took much longer to recognize my stereo than normal (could just be a one-time issue), it was buzz free, error free and playing my Pandora perfectly!
Here's the leak download:
http://forum.xda-developers.com/showthread.php?t=1652679
Click to expand...
Click to collapse
Ha! Finally! alright, good deal man

Did this fix the timeout issue as well? I'm running UCLE2 as well but still get the timeout once in a while

mine seems to be working fine now on UCLE2 but I've only tested it for a day.

[Q] ROM and Bluetooth issue S3 - Help

Just installed CleanROM 6 R2. Very nice ROM! I do have a continuing issue I want to put out there, see if any others have it? Confirm it?
This isn't due to the ROM, but with the new ROM installed, the problem continues, so I am curious. (Going to try another soon)
When I have pattern security, and using my Q2 Blueant Bluetooth headset, I try to make a voice call. (S Voice disabled, Assistant used for voice commands currently) When trying to make the call, I hear the tone from the phone, to start talking, but I get a "Not supported by phone" message on the headset.
If I attempt the same test, with NO lock screen security it works fine.
I attempted this test, with pattern security on a S4 for ATT, works. S4 for Verizion, NOT working. Same for the S3.
I test with the same bluetooth on a Verizon Rezound (GF phone), works perfectly.
Why does it fail on the S3, with stock 4.2.1 and now with CleanROM? I figured it was some kind of software from Verizon... maybe the firmware somehow? Remaining software of some kind?

bigb78 said:
Just installed CleanROM 6 R2. Very nice ROM! I do have a continuing issue I want to put out there, see if any others have it? Confirm it?
This isn't due to the ROM, but with the new ROM installed, the problem continues, so I am curious. (Going to try another soon)
When I have pattern security, and using my Q2 Blueant Bluetooth headset, I try to make a voice call. (S Voice disabled, Assistant used for voice commands currently) When trying to make the call, I hear the tone from the phone, to start talking, but I get a "Not supported by phone" message on the headset.
If I attempt the same test, with NO lock screen security it works fine.
I attempted this test, with pattern security on a S4 for ATT, works. S4 for Verizion, NOT working. Same for the S3.
I test with the same bluetooth on a Verizon Rezound (GF phone), works perfectly.
Why does it fail on the S3, with stock 4.2.1 and now with CleanROM? I figured it was some kind of software from Verizon... maybe the firmware somehow? Remaining software of some kind?
Click to expand...
Click to collapse
I don't have this BT issue on Clean or any other TW or ASOP rom. I use PIN lockscreen. I have used my ERA and Blueant BT with Cyberon voice commander, and both work fine. On ASOP, I get a 5 second delay in acknowledging the command bit it eventually works.

jlokos said:
I don't have this BT issue on Clean or any other TW or ASOP rom. I use PIN lockscreen. I have used my ERA and Blueant BT with Cyberon voice commander, and both work fine. On ASOP, I get a 5 second delay in acknowledging the command bit it eventually works.
Click to expand...
Click to collapse
Can you switch to pattern lock and test again with the blueant BT? I am set to immediate lock on power button. Patter required immediately. Also, are you using a Q2 Blueant?
Thanks

bigb78 said:
Can you switch to pattern lock and test again with the blueant BT? I am set to immediate lock on power button. Patter required immediately. Also, are you using a Q2 Blueant?
Thanks
Click to expand...
Click to collapse
I was using the Q2 with pattern lock. I now use the jawbone with PIN lock. Sorry for the confusion.

Thanks.
But... DAMN! LOL I can't figure out why this is happening. I will try Cyberon, but S Voice and Assistant failed for me.

http://support.verizonwireless.com/pdf/system_update/galaxy_s3.pdf
I am guessing that JZO54K.I535VRBMF1:
"Access phone screen without
unlocking device when connected via
Bluetooth headset"
Has something to do with my issue? (Wishful thinking)

bigb78 said:
http://support.verizonwireless.com/pdf/system_update/galaxy_s3.pdf
I am guessing that JZO54K.I535VRBMF1:
"Access phone screen without
unlocking device when connected via
Bluetooth headset"
Has something to do with my issue? (Wishful thinking)
Click to expand...
Click to collapse
I hope it helps you. I have been very frustrated since the JB update with BT voice dialing. ICS worked 100% better. Both S voice and Google now have been very disappointing for voice dialing. I find Cyberon to work more than 95% of the time.

jlokos said:
I hope it helps you. I have been very frustrated since the JB update with BT voice dialing. ICS worked 100% better. Both S voice and Google now have been very disappointing for voice dialing. I find Cyberon to work more than 95% of the time.
Click to expand...
Click to collapse
Yeah, I hope so too. Maybe when CleanROM is updated with MF1 I will find out.
I have been happy with Assistant, as far as quality of voice dialing interpretation. I even bought the paid version, although not needed really.
S Voice is horrible, the S3 version. My buddy has the S4 on ATT, and S Voice is WAY better. (And my BT works with patter lock on his S4. But NO WAY I got to ATT. Hahaa)

bigb78 said:
Yeah, I hope so too. Maybe when CleanROM is updated with MF1 I will find out.
I have been happy with Assistant, as far as quality of voice dialing interpretation. I even bought the paid version, although not needed really.
S Voice is horrible, the S3 version. My buddy has the S4 on ATT, and S Voice is WAY better. (And my BT works with patter lock on his S4. But NO WAY I got to ATT. Hahaa)
Click to expand...
Click to collapse
There are a couple of TW roms, including Bone Stock and Hyperdrive that give you the option to choose S4 S Voice to install. If you are on a stock kernel, you can probably flash the MF1 firmware and not bork your camera. You should check the clean rom thread to see if anyone has done that yet.

jlokos said:
There are a couple of TW roms, including Bone Stock and Hyperdrive that give you the option to choose S4 S Voice to install. If you are on a stock kernel, you can probably flash the MF1 firmware and not bork your camera. You should check the clean rom thread to see if anyone has done that yet.
Click to expand...
Click to collapse
Yep, I am watching the forum. Don't want to be the first one to try it, I don't yet have the skills to fix undocumented problems.
I think my problem though, is the Bluetooth security bypass. Not the Voice app..... but time will tell.

Just flashed the MF1 firmware and the Stock ROM for MF1, and no luck on bluetooth!
Anyone out there with a BlueAnt Q2 bluetooth and a S3, stock or another ROM that could test for me? Killing me not being able to control my phone on the motorcycle, my HTC never had the problem, only S3 and S4 on Verizon... S3 and S4 on ATT works.
I'll put a bounty on this... need to figure it out!

bigb78 said:
Just flashed the MF1 firmware and the Stock ROM for MF1, and no luck on bluetooth!
Anyone out there with a BlueAnt Q2 bluetooth and a S3, stock or another ROM that could test for me? Killing me not being able to control my phone on the motorcycle, my HTC never had the problem, only S3 and S4 on Verizon... S3 and S4 on ATT works.
I'll put a bounty on this... need to figure it out!
Click to expand...
Click to collapse
Try this link: http://forum.xda-developers.com/showthread.php?t=1896171