Database Users

Curious, how many of you are running skype? Try this

This is just something I stumbled across a while ago but haven't had the time to post it. I'm not making any promises so this is just a head's up.
If anyone remembers my last post on skype here, you'll recall me saying that there's a Disable Codecs key in the registry. Well I didn't know the codecs but SkypeSmart over at Skype forums posted this tweak for his iPaq and it works a treat.
I'm running my Mini S with the original ROM and skype with my key reading: ILBC G729 EG711U
As a result it only uses the EG711A codec and guess what, it works, at stock speed too. My phone is an utter mess but it works at an acceptable level that is to say both parties can hear the conversation without any hiccups. Tested over a WiFi link but be warned you'll lose connectivity with echo123 and it also seems to me that Skype Linux doesn't have the EG711A or EG711U or even the G729 codecs so you won't be able to chat with them unless you enable ILBC.
One thing worth testing is to see what happens in a conference call (with a Windows machine as host and a Linux machine and the wizard with some of the codecs disabled) but I don't have the time to test so be my guest and post the results if you do test it.
By the way, I use Skype v2 Feb 14 release. If anyone wants to post their overclocked results or anything, great.

Indeed it does work and VERY well. I just called across a very sketchy broadband connection and audio in BOTH ways was clear. Before, I could be heard by the other party but could not hear them in return. Once I overclocked, I could actually have a couple of pragrams running in the background and still have acceptable resources left. Bravo to whoever came up with this tweak.

How far did you overclock? Also, I know a lot of people are viewing this thread but only one response so far...does that mean the rest of you are enjoying Skype? :shock:

i use skype with my wizard very well and i can use skypeout as well.
i installed for the high cpu usage, not low cpu usage. but i also use omapoverclock.
what i did, just installed skype, then change the content of d shortcut using total commander in windows/start menu/programs/skype.lnk with this one:
46#"\program files\omapclock.exe" -clock 240 -launch "\Program Files\Skype for Pocket PC\Skype.exe" -restore?Program Files\Skype for Pocket PC\Skype.exe,
in this case, i put omapclock file in 'program files' folder, and don't forget to use "," sign in the last content of skype. because it gives u back d skype icon, otherwise u'll see omapclock icon.
Gut luck!!! and i hope this can be useful 4 u...
_________________________________________________________________________
GET A FREE NOTEBOOK!!! --> http://notebook.GustoNetwork.com/index.php?mid=578275

i remember trying this on my wizard...i placed a call to a land phone and i could not hear the other phone ring or anything.. but t did call..
What am i doing wrong?

Thanks Ricky, that trick with Omapoverclock works a treat. By the way not sure if it is my imagination but sounds like the I am getting the call playing through my handsfree speaker and not the ear piece. Does anyone else get this or am I going mad????

jt_armstrong said:
Thanks Ricky, that trick with Omapoverclock works a treat. By the way not sure if it is my imagination but sounds like the I am getting the call playing through my handsfree speaker and not the ear piece. Does anyone else get this or am I going mad????
Click to expand...
Click to collapse
You're not. Apparently the M600 is the only phone which might support non-speakerphone chat on skype. I heard that its latest ROM does exactly what you want it do. I don't know if its a Skype specific issue or whether it's ROM specific but I have not seen any apps other than the phone app itself take advantage of the earpiece.
@guyver2077:
If you're referring to the tweak I listed, what does it do when you call PCs? I made a skype out call actually 3 of them and I could hear all of them clearly - 1 to Guam , 2 to HK and I'm in the UK.
@Ricky:
Does 240MHz eat away at the battery life, especially with WiFi on?
I just spent the last few days setting up a Linksys NSLU2 with DebianSlug and it works great; Samba works with the phone too 8). A little tempted to get a bluetooth dongle to stick to the slug so that I can connect to the net over bluetooth when possible but the BT stack on the mobile doesn't support BT networking does it?

ok.. so does this only work with speakerphone on?? i didnt hear anything through the actual phone ear reciever

guyver2077 said:
ok.. so does this only work with speakerphone on?? i didnt hear anything through the actual phone ear reciever
Click to expand...
Click to collapse
When I said speakerphone I meant simply that the sound is coming out at the same volume as media player, etc if that makes sense. There's no reason for you not to be able to hear a thing though. :?

Thanks AsGF2MX, It works great with the headfones I just don't normally use them.

guyver2077 said:
ok.. so does this only work with speakerphone on?? i didnt hear anything through the actual phone ear reciever
Click to expand...
Click to collapse
If you think about it, it makes sense. This is Skype for Pocket PC, most Pocket PCs don't have the phone built in.
Do you have a BT headset? If so open the audio gateway (either using the program posted in this forum or via Voice Command press BT button and just say "Open Skype", the Audio gate will stay open).
This should allow you to use your BT headset for Skype calls.

kyphur said:
guyver2077 said:
ok.. so does this only work with speakerphone on?? i didnt hear anything through the actual phone ear reciever
Click to expand...
Click to collapse
If you think about it, it makes sense. This is Skype for Pocket PC, most Pocket PCs don't have the phone built in.
Click to expand...
Click to collapse
I suppose you're right, that would explain things but is there an option to actually channel audio to the ear piece? If not, then it's definitely an issue with the way the device ROMs are designed (assuming that there is a way for software to utilize the ear piece).
Well, I'm glad a few people found it useful and I hope it's working for the rest of you as well. I might just pick-up OMAP clock a little later and try to see how well an overclock fares on my device but first, I'm going to try a few apps I've been wanting to try for a while.

Great tip!
I have previously tried Skype on my Qtek 9100 but have always found the audio quality quite bad, even when overclocking to 240.
After changing the DisableCodecs as suggested here, the audio quality is now really good, also when using SkypeOut to a Fixednet phone.

Thanks for the tip!

Yes Great tip, thanks

Can someone point me in the direction of the program that opens the audio gateway?
I don't have MS Voice Command, I only have the default "Voice Speed Dial".
EDIT: FOUND IT!!!
Therez two actually. one is btAudio, and the other is VjVolubilis

After Skype Install - Alarm clock chaos
Hi
I have been reading this thread with interest. I own an old XDA (one with aerial) and now the XDA Mini S. Have had it now for about 6 months and sync up to 2 pc's, have multiple email accounts, use the Wifi/msn - so use pretty much all of functionality. Happy so far!
I installed the pocket pc version of Skype last night - and found that this morning my alarm went off - but with no options displayed on the screen to snooze/dismiss alarm! Consequently - the alarm/vibrate goes off every 5 minutes - and only thing i can do is remove the battery -so phone basically unusable. Soft reset does not help - and would rather not hard reset as then will have to redo email settings etc.
Anyone out there had this problem before? Your help would be appreciated (think you are calling the XDA mini a wizard)
OS Build: 5.1.70 (14406.1.1.1)
ROM: 1.5.4.2 WWE
ROM date: 11/8/05
Radio: 01.09.10
Protocol: 4.0.13.20
ExtROM: 1.5.4.103

Have you removed the Skype software already?

After Skype Install - Alarm clock chaos
Hi - Yes, I have removed Skype from the XDA Mini. Soft-reset again - no difference.

I had that alarm problem once.
I'd had my cingular 8125 (HTC wizard) for a week or two and had been putting apps on it and messing with the registry, then one morning my alarm went off, I reached over to silence it, pushed some random button accidentally, and the alarm kept on going. I opened my eyes and sat there for a minute waiting for my brain to boot up because I wasn't seeing the notice showing me which softkey to press. After awhile, I realized that I was completely awake, and there really was no way to turn the alarm off!
I messed around with that thing forever. Scrolling through menus, doing soft resets, etc. Nothing would silence the alarm. I tried reseting the time/date and doing a soft reset, but every time the device booted up, it would go nuts with alarm tones (they kept multiplying! Every time I would reset the time after having set it back, another alarm would go off and they started piling up!).
Boy, that really ruined my morning.
I ended up having to do a hard reset to fix the problem. And when I ran my latest backup, the problem came right back! So I had to do another hard reset and roll back to an earlier backup.
I really don't know what the problem was, but I think I might have a slight idea. I had downloaded some program called CheckNotifications by Scarybear software (I now know it's not meant for WM5) and I think I must have deleted that alarm notification from the "notification database". (No, I don't actually know what any of that means, I'm just regurgitating words I read online in a manner which seems to make a little sense). So some parte of the OS somewhere remembered the alarm, and turned it on at the right time, but the part of the OS responsible for giving you the facility to turn it off was screwed. But that's just a wild guess.
Maybe you also have some issue with your notification database.
Good luck! Of course, if you were anywhere near as annoyed as I was, you probably already said a few (dozen) choice curse words and did a hard reset.
(edit: clarified phone)

HD2 issues: Any assistance?

Hello all,
I purchased my HD2 on release day and so far I love it. For the most part the phone has been problem free and everything works perfectly. However recently I ran into a few issues.
1) When playing music with Windows Media player or the Music Player I will sometimes get odd skipping in songs. I looked at my screen and the microphone symbol at the top of the screen was blinking like crazy and I could hear a voice asking me to repeat commands again. I believe it was the voice dialing feature. One time it actually called someone. My phone started dialing out in the middle of a song and I had to pull the battery to make it stop calling people.
2) Text messaging.. The text messaging app has some serious bugs. Hopefully there is an update or a better solution out there. Some of the problems I have with texting are: Phone goes to a crawl when a text comes in, when typing texts it will just stop showing what I am typing. I have to click all around the window and sometimes can get it to come back up. If I cannot get my text to come back I have to close the app down and then go back in.
3) I am not sure if this is related to the sms app or not but I tried to edit a contact and the phone become incredibly unstable. It restarted itself and when sense loaded it popped up a message saying that swipe was not designed for my phone type. After that reboot my phone acted up a lot until I restarted it about 6 times. Then it was stable but the texting app was worse than ever.
I did a bunch of google searches and couldn't come up with any fixes for these issues. So any input would be welcome.
My phone is stock. I have no interest in flashing a new rom. I blame all these problems on sense (WinMo actually seems perfect despite what the uneducated spew across the net daily).
Thanks for reading

1) Sounds like you're simply activating the MSVC, which is done buy a long press off the send key (you're probably accidentally long pressing the 'play/send' button on the headphones.
Two solutions: 1) Simply disable MSVC (Settings>personal>Voice Command; Uncheck Enabled) 2) Be more careful so you don't accidentally press the button.
2)Just click the text input area (just above the keyboard where the text is suppose to be) and everything you typed will show up and continue to show up.
3) Never heard or seen this.
I don't know how much stuff/time you've put on/into this phone, but you might want to consider a hard reset.

Thank you for your response:
I was not using the headphones. I had it connected to my stereo in my Jeep. The HD2 was sitting alone on the seat next to me with nothing around it. It's done it several times now - so I don't think it was anything environmental.
Clicking in the text area used to work fine but not anymore. I have to click the last text message that came in and it will open a option menu, close that and then click in the open text area several times. This started happening once I tried to edit my contacts and my phone lost it's mind.
I don't want to do a hard reset but it might have to come to that. I have all the apps I like installed and everything seems to be working nicely with those few exceptions.
Ohh and one last complaint. Slacker >< why does it stop playing songs so much? I read other people were having problems with that too but I cannot seem to find any fix. Should I just give up on it and go to Pandora?

Streaming Audio To Bluetooth W/o A2DP

So I have been trying to figure this out for a while. But I figured maybe we could get some community involvment with it.
If you weren't aware:
In 1.5 you could dial ** on your dialer, hit Call and it would redirect all audio (music, games, notifications) to your paired BlueTooth headset.
This no longer works in 2.1 - if you dial ** you get the 'p' and then when you hit call it almost immediatiely disconnects. But you can hear the audio for a split second in the BT.
If anyone can figure this out - or maybe dig a little deeper into Dialer.apk?
Maybe just a few people typing random stuff into their dialer to see if anything will work.
EDIT:
SOOOOOOOOOOOO
Watching LOGCAT when I dial this it calls a SpecialCharSequenceMGR
MY GUESS:
This one is different than the 1.5 dialer - Maybe tonight I cna merge with success....we shall see. Unless someone else wants to take a look before then.

my question would be whether the dialer in 2.1 got an upgrade. i guess it did since this feature doesnt exist (obvs), so any reason you cant flash on a dialer from 1.5?
i dont know much about how the internals of them work otherwise id help in the search, well after i finish this semester in two weeks. yep yep.
pardon me if my reply was a bit simplistic and if you tried that already, then sorry :/
good luck!

bump.
Updated top post.

Looking forward to your results. Hope you succeed.

On my Hero, long clicking on the device in Bluetooth Settings (in both 1.5 and 2.1), allows me to change the settings of that bluetooth connection including turning on and off both Phone and Media audio.
My only problem is that they have never played well together. If I'm playing media and a phone call comes in, the media properly pauses, but the phone either switches in on the phone's speaker or is totally silent causing me to miss the call.

Bump for the hell of it and a question.
Does anyone know where Dialer is in a 1.5 rom? I downloaded a fresh 1.1 to grab the apk and its not in system/app...wtf???

Las_Vegas said:
On my Hero, long clicking on the device in Bluetooth Settings (in both 1.5 and 2.1), allows me to change the settings of that bluetooth connection including turning on and off both Phone and Media audio.
My only problem is that they have never played well together. If I'm playing media and a phone call comes in, the media properly pauses, but the phone either switches in on the phone's speaker or is totally silent causing me to miss the call.
Click to expand...
Click to collapse
I think this might be because you have an A2DP capable headset. Mine doesn't give me this option.

Ive been looking
I also have been looking for somthing along these lines, as well as some other members. I started this thread : http://forum.xda-developers.com/showthread.php?t=660519 earlier trying to get help, there are actually a few bounties out now....Check it out

Ok so if any one who knows more linux than I do can try to figure out how to pipe the audio from one output to another it would be cool.
I was thinking it would be something lile MediaPlaybackService | AudioHardwareMSM72XX
But I am not sure if that is even remotely close. It doesn't work for me, I guess we just need to get the right services.

Audio and Data issues after firmware upgrade

Not sure what numbers I should give you so Im going to give you everything.
Current firmware version : PDA:LPD / PHONE:LPB / CSC:LPD (TMU)
Model number : GT-I9100
Android version : 4.0.3
Baseband version : I9100BVLPB
Kernel version : [email protected]#3
Build number : IM74K.BVLPD
The phone is a UK SGS II, has not been rooted. It is running the official T-Mobile ICS Rom.
A couple of days ago I noticed an intermittent but significant loss of data. I could be in the same place for hours and it would happen, I could be on the move and it would happen. I decided to use Samsung Kies to see of there was a firmware upgrade and would reset the phone. This was done yesterday.
Today I have had lots of issues. Data again will come and go at will, the data icon in the taskbar will disappear intermittently. I have also lost SOME audio. By some I mean the following:
No audio from media via the speaker, either stored on the phone or over the internet. Tried BBC iPlayer, Youtube, Samsung Music Hub. Audio on the phone played through headphones was fine.
Ringtones work fine, but when I answer a call there is nothing from the earpiece. Switch to speaker and I can hear the caller.
Notification tones seem to be working fine.
No keypad tones from phone screen. I have checked to make sure that keypad tones is activated.
No 'system sounds'.
I have been into the menu for volumes (Menu, Settings, Sound, Volumes) and:
if I move the media slider I hear nothing (though I do get the 'harmful' warning when the slider is pushed all the way to the right
if I move the Ringtone Slider I can hear the ringtone playing back in relation to the slider position
if I move the Notification slider I can hear the notification tone playing back in relation to the slider position
if I move the System slider I hear nothing at all
The odd thing is that earlier in the day it was working, then part way through the afternoon I got nothing.
I have spoken to T-Mobile who were less than useless. First of all they said that T-Mobile did not recommend upgrading from Gingerbread to ICS, this is despite the rom in the phone being the official T-Mobile branded ICS rom that they released and I upgraded to through Samsung Kies. Their only answer was to take it back to the shop and they would send it away to be downgraded back to Gingerbread.
Is this likely to solve the problem? I am sceptical. The phone has been running fine on ICS for maybe a month, or since the official ICS rom was released anyway, its only in the past couple of days that I have had a problem.
I cant see it being a hardware issue as the speaker is obviously working for me to hear ringtones and be able to hold a phone call on speakerphone (though that doesnt rule out a hardware issue with the earpiece). I was originally thinking more a software conflict somewhere, so thats why I decided to try a reset and firmware upgrade. I have run it with just a couple of apps from Google Play, Facebook and Tunein Radio to be precise and it still had the same issues, and then tried it without installing anything from Google Play, just transferring a single music file from my PC to the phone and that didnt work either. The track played, but there was no audio to hear via the speaker. If I connect headphones to the 3.5mm socket I can hear the audio perfectly fine.
Im hoping someone has some input on this before I go to the store with the phone tomorrow. Has anyone experienced similar issues?
Cheers in advance

Ive been looking a bit further into this and Im wondering if the headphone socket may be to blame?
Ive had a couple of people take a look at the headphone socket, and the general consensus is that it doesnt look right. One thinks that maybe a pin is bent and the bottom of the socket just looks 'wrong'. Thoughts?

Incoming Calls / Black Screen ?

Not sure why but after the last system update the phone will only come out of black screen sleep mode if I use the fingerprint sensor when theres an incoming call.
Any Ideas ?

This happened to me today too.

Hello, me too! Oreo Beta 2

Anyone ?

going_home said:
Anyone ?
Click to expand...
Click to collapse
Not me, I've never experienced this issue since I got the phone from N then updated to OB2, and now OB3.

Sounds like the proximity sensor may have an issue.
Do you have a screen protector or case?
I don't have that issue with a screen protector and Tudia case and B3.

It's a bug in the latest Google Dialer app. I fixed it be deinstalling the new version/updates then clearing cache and data in the dialer app. It's affecting the Pixel2 XL running 8.1 also. Fixed my issue and I won't let it install the newer dialer version from the play store

In Beta 3, I haven't experienced that problem. I did heavily on 7.1.1

Just got another update and still having black screen on incoming calls....
I'm about ready to ditch this phone and get a Pixel 2 XL.
I read where Essential is skipping the 8.0 update because of instability and going straight to 8.1.

going_home said:
Just got another update and still having black screen on incoming calls....
I'm about ready to ditch this phone and get a Pixel 2 XL.
I read where Essential is skipping the 8.0 update because of instability and going straight to 8.1.
Click to expand...
Click to collapse
happened to me last week too.. it only happened after I locked the phone, 5-10 minutes later incoming call or when unlocking the phone the phone shows back screen only for a few seconds then it went back to normal.
the problem went away after I turned off the bluetooth radio.

I've been having this issue for a while now and just today I figured out the cause. At least the cause of my specific issue. I came here to see if anyone else is having similar issues so I'll explain exactly where I'm at.
If a Bluetooth headset is connected to my phone, when a call comes in the screen stays black and I can't see who's calling. If I turn off, or disconnect the BT device, when a call comes in the screen lights up with caller ID like normal. This also affects the missed call notification that happens after a missed call. With a BT device connected, the missed call notification will not show until I wake the phone with the power button, though the notification LED will light.
I'm on stock 7.1.1 and I verified that this is also an identical issue with two other phones which were not on a stock ROM, though I can't remember what they were running. This started happening to me before the NMK24B update. I remember because I was hoping that the update would fix it. I believe it started with NMJ88C because I got my phone on NMJ32F, it updated to NMJ51B shortly after and it was fine in the beginning months.

DrvLikHell said:
I've been having this issue for a while now and just today I figured out the cause. At least the cause of my specific issue. I came here to see if anyone else is having similar issues so I'll explain exactly where I'm at.
If a Bluetooth headset is connected to my phone, when a call comes in the screen stays black and I can't see who's calling. If I turn off, or disconnect the BT device, when a call comes in the screen lights up with caller ID like normal. This also affects the missed call notification that happens after a missed call. With a BT device connected, the missed call notification will not show until I wake the phone with the power button, though the notification LED will light.
I'm on stock 7.1.1 and I verified that this is also an identical issue with two other phones which were not on a stock ROM, though I can't remember what they were running. This started happening to me before the NMK24B update. I remember because I was hoping that the update would fix it. I believe it started with NMJ88C because I got my phone on NMJ32F, it updated to NMJ51B shortly after and it was fine in the beginning months.
Click to expand...
Click to collapse
I had the black screen issue as well for incoming calls. I just switched to Drupe Dialer from the Play Store and set that as my default dialer. Now my screen lights up with the incoming caller ID and works as it should. By the way, hate to sound like an add, but Drupe Dialer is just awesome and has a ton of functionality, give it a shot. I know that's not the perfect answer as we would expect the native Android dialer to work out of the box with our OS, but it is what it is.

Jank4AU said:
I had the black screen issue as well for incoming calls. I just switched to Drupe Dialer from the Play Store and set that as my default dialer. Now my screen lights up with the incoming caller ID and works as it should. By the way, hate to sound like an add, but Drupe Dialer is just awesome and has a ton of functionality, give it a shot. I know that's not the perfect answer as we would expect the native Android dialer to work out of the box with our OS, but it is what it is.
Click to expand...
Click to collapse
I tried two other dialers and it didn't make a difference on my phone. Drupe did work to make the screen show who's calling again, but wow, Drupe has too much.... just, everything. All I want in a dialer is basic functions in a standard format. Drupe is like a carnival of a dialer. I'll keep trying dialers though, since that one did work, maybe another one will too. Thanks for the suggestion.

Yeah, if you just take the Drupe dialer phone icon and put that on your home screen, whenever you select it you'll go right to the normal looking dialer. :good:You may want to try ExDialer. That used to be one I'd use a lot.

Jank4AU said:
I had the black screen issue as well for incoming calls. I just switched to Drupe Dialer from the Play Store and set that as my default dialer. Now my screen lights up with the incoming caller ID and works as it should. By the way, hate to sound like an add, but Drupe Dialer is just awesome and has a ton of functionality, give it a shot. I know that's not the perfect answer as we would expect the native Android dialer to work out of the box with our OS, but it is what it is.
Click to expand...
Click to collapse
Before using Drupe...
There should be a warning that goes out to all your contacts saying "I'm about to completely betray you and share EVERYTHING about you online with a company I know nothing about... Please enjoy these spam calls on me"
Sent from my PH-1 using Tapatalk

rignfool said:
Before using Drupe...
There should be a warning that goes out to all your contacts saying "I'm about to completely betray you and share EVERYTHING about you online with a company I know nothing about... Please enjoy these spam calls on me"
Click to expand...
Click to collapse
10 million downloads...good enough for me. I've used it for a long time and it's been better for me than the stock dialer. Just my opinion, no one has to use it but it sure beats a black screen when the phone rings.

I have the same problem on the pixel 2 xl. And so do lots of others. I uninstalled the phone update from the play store, and turned off auto update. So far so good. And I am on 8.1 But we will see. And it only happens when I'm on Bluetooth. Unfortunately I use it all the time for work
Sent from my Pixel 2 XL using Tapatalk

I read about some people being able to fix it by uninstalling dialer updates. Unfortunately, the Essential doesn't have any to uninstall. I'm working around it by using Drupe as my default dialer, but setting the stock dialer as the default app for dialing, if that makes any sense (When an event pops up that requires the dialer, it asks which dialer to use, I selected the stock dialer and told it always use that.) This way incoming calls trigger Drupe, which acts the way it's supposed to on Bluetooth, but I can still use the stock app for making calls and missed calls and such.

bricky23 said:
I have the same problem on the pixel 2 xl. And so do lots of others. I uninstalled the phone update from the play store, and turned off auto update. So far so good. And I am on 8.1 But we will see. And it only happens when I'm on Bluetooth. Unfortunately I use it all the time for work
Click to expand...
Click to collapse
Yeah, I'm thinking there's a Bluetooth issue (yeah,I know, news flash). But it's been widely reported that some folks are having trouble connecting to their cars Bluetooth. I use a Bluetooth adapter in my car and wireless headphones in the office. No real big issues connecting, but it can be finicky. However, once an event triggers Bluetooth, like streaming a song with Google Play to the adapter, my phones volume buttons become unresponsive. I can only change volume by going into the settings menu or from the Bluetooth device. Sucks. Waiting for the 8.1 beta to do a total clean install. Just bought the device used from Swappa and it came with beta 3 installed, not 100% sure the steps it took getting here. I guess what I'm asking is, does anyone else experience issues with their volume buttons not working occasionally?

Jank4AU said:
Yeah, I'm thinking there's a Bluetooth issue (yeah,I know, news flash). But it's been widely reported that some folks are having trouble connecting to their cars Bluetooth. I use a Bluetooth adapter in my car and wireless headphones in the office. No real big issues connecting, but it can be finicky. However, once an event triggers Bluetooth, like streaming a song with Google Play to the adapter, my phones volume buttons become unresponsive. I can only change volume by going into the settings menu or from the Bluetooth device. Sucks. Waiting for the 8.1 beta to do a total clean install. Just bought the device used from Swappa and it came with beta 3 installed, not 100% sure the steps it took getting here. I guess what I'm asking is, does anyone else experience issues with their volume buttons not working occasionally?
Click to expand...
Click to collapse
My volume buttons always work fine, BT or otherwise. Stock 7.1.1. Your issue could very well be related to OB3. I had a little bit of an issue connecting/reconnecting to some BT devices at first, but not lately, so it must have been fixed in the last few patches.