Could anyone who understands the inner workings of the CM and chopsticks crews shed some light on the bug resolution process.
I'm particularly interested in the bluetooth audio problems when making or receiving a call on the cars BT system. Seems it's wide spread and discussed on many threads but I've never seen it mentioned outside of forums like XDA and other Android user forums. Do you think it is on their list? Can someone post a link to a bug reporting site. I have bugzilla but I think thats for the AOKP roms .
Nobody?
Sent from my SAMSUNG-SGH-I727 using xda premium
stoopendis said:
Nobody?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Someone correct me if im wrong but isnt BT kernel related??? If so BT wont be stable until samsung releases a JB kernel for our phone
Sent from my SGH-I727 using xda app-developers app
Bluetooth
I also use the Bluetooth in my car and would like for someone to post any way on how to fix it. I'm using orthus 3 ROM works great.
skyrocke8 said:
I also use the Bluetooth in my car and would like for someone to post any way on how to fix it. I'm using orthus 3 ROM works great.
Click to expand...
Click to collapse
If there was a fix it would be widely known already. From what roger_n posted in the Paranoid Android thread (I think it was that one) the issue is in audio routing, not BT audio, and needs to be fixed by a core CM dev, as it's not skyrocket specific.
rpr69 said:
If there was a fix it would be widely known already. From what roger_n posted in the Paranoid Android thread (I think it was that one) the issue is in audio routing, not BT audio, and needs to be fixed by a core CM dev, as it's not skyrocket specific.
Click to expand...
Click to collapse
So the fact that it's been around so long is because these core CM devs are super busy..or are they even aware there IS a problem, or is it just low pri.
I can't speak for the devs, but I do believe it's a time issue, not that they don't know about it.
rpr69 said:
I can't speak for the devs, but I do believe it's a time issue, not that they don't know about it.
Click to expand...
Click to collapse
Well here's hoping they find the solution soon. I'm a little concerned about a work-around I've heard about where you turn off the blue tooth and then back on after the initial connection....Very dangerous while driving. And costly too. Here In B.C. there's a $175 fine for fiddling with your cell phone while driving.
stoopendis said:
So the fact that it's been around so long is because these core CM devs are super busy..or are they even aware there IS a problem, or is it just low pri.
Click to expand...
Click to collapse
Most likely a low priority, as there is not a Samsung released JB rom for the Skyrocket.
stoopendis said:
Well here's hoping they find the solution soon. I'm a little concerned about a work-around I've heard about where you turn off the blue tooth and then back on after the initial connection....Very dangerous while driving. And costly too. Here In B.C. there's a $175 fine for fiddling with your cell phone while driving.
Click to expand...
Click to collapse
I know it's lame, but what I ended up having to do in this issue was to even before I moved out of park I would disconnect and reconnect my BT. Often times though I found that just switching off the car radio (BT enabled Parrot Rythm-N-Blu), remove the face plate, count to 15 and put the face plate back on then turn the radio back on would do the "trick."
MasterDecker said:
Most likely a low priority, as there is not a Samsung released JB rom for the Skyrocket.
I know it's lame, but what I ended up having to do in this issue was to even before I moved out of park I would disconnect and reconnect my BT. Often times though I found that just switching off the car radio (BT enabled Parrot Rythm-N-Blu), remove the face plate, count to 15 and put the face plate back on then turn the radio back on would do the "trick."
Click to expand...
Click to collapse
I can pull down the menu and toggle BT easier than I can dial a number while driving...and yes, Ontario has the same fines.
aii for the last time just use a different rom. im using JB official by CM9 for skyrocket - stable version 2.
it's no cm10 but full BT car audio talk the works!!! it works, end of story cm9 SOLD!!!
Try the new official nightly
Sent from my SGH-I727 using xda app-developers app
AOK now. Perhaps we can have this thread shut down.
Sent from my SAMSUNG-SGH-I727 using xda premium
There's already similar posts on this. CM10 doesn't have the fix yet, if you want a working BT grab the official CM9 stable version - I've reverted back to as I have the same issue as you ie: car BT is a big deal for me.
charbar85 said:
There's already similar posts on this. CM10 doesn't have the fix yet, if you want a working BT grab the official CM9 stable version - I've reverted back to as I have the same issue as you ie: car BT is a big deal for me.
Click to expand...
Click to collapse
Fixed in CM10 as of last Wednesday.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Related
Hey,
i know this has been discussed in many threads..just want to have some answers.
i bought my Nexus S a few months ago, it's the I9020 not I9023, from UK.
i really love the phone itself, it's just awesome. had a htc hero before.
but i hate those random reboots, happens to me ~1 time per day. the screen wents really dark and a never ending bootloop happens. have to pull out battery to get it back to work, most times i don't even notice this and the phone is dead after a while of bootlooping... no fix yet right? anyway i "can" live with this but hope to get a fix soon...
GPS and Compass were unuseable since i have it. even my hero has a faster and especially safer GPS-Fix, GPS on Nexus S just loose fix every few seconds and compass does not jump around 50-100°. THIS really sucks! I have already searched around on google and XDA and wherever if this is a hardware or software issue and if there is a possible fix for it but i haven't found a real answer yet and this is what i want to know now.
is this hardware or software related?
is there a fix possible?
like i said, love the phone itself but these issues would make me resell it...
hope i'll get some answers and don't be rude, my english issn't the best.
Best regards and happy easter
Flo
edit: im using latest CM7 with latest Netarchy-Kernel with no additions.
The boot loop/reboot problem is definitely a CM7 issue. None of the other ROMS have this problem.
Sent from my Nexus S using XDA Premium App
Vandam500 said:
The boot loop/reboot problem is definitely a CM7 issue. None of the other ROMS have this problem.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Thanks! so they will probably fix it soon
but whats with the GPS/Compass issues?
that really really sucks! can't use it at all...
floomat said:
Hey, i know this has been discussed in many threads..just want to have some answers.
Click to expand...
Click to collapse
You could still have bumped an older thread, though. Like mine: http://forum.xda-developers.com/showthread.php?t=1035005.
I think if all the people with GPS problems could get together in one thread (needn't be mine, of course, there's lots), this issue would get more exposure and eventually be fixed.
floomat said:
is this hardware or software related? is there a fix possible?
Click to expand...
Click to collapse
No idea, but since the Nexus One and the Galaxy S with 2.3.3 have similar issues, I'm still hoping it's software. There is no known fix at this time.
fallenguru said:
...
I think if all the people with GPS problems could get together in one thread (needn't be mine, of course, there's lots), this issue would get more exposure and eventually be fixed...
Click to expand...
Click to collapse
i guess you are right, and im doing my share here. i have at least 2, 3 random reboots everyday, even if its a clean install, everything wiped. there's something buggy in every cm7 based rom
I guess its the radio problem, for the gps,
Sent from my GT-I9003 using Tapatalk
All the Skype video calls I was making used to be outputting their sound over the phone speakers. Recently, however, this seems to have changed. The sound is now only outputted via the earpiece, and I do not seem to be able to find the cause of the change, nor how to change it back. There is no speaker toggle button. Makes the video calling fairly cumbersome, since I have to put on the headphones (or Bluetooth), and cannot have a couple of people take part in the call at my end. The recent upgrade (2.5) did not correct the problem. What is annoying is that it was working OK before. I am just not sure before what. Any ideas anybody? Android 2.3.4 (stock HTC/T-Mobile), Skype is most recent stock version.
Sent from my HTC Sensation 4G using XDA App
Hrvoje said:
All the Skype video calls I was making used to be outputting their sound over the phone speakers. Recently, however, this seems to have changed. The sound is now only outputted via the earpiece, and I do not seem to be able to find the cause of the change, nor how to change it back. There is no speaker toggle button. Makes the video calling fairly cumbersome, since I have to put on the headphones (or Bluetooth), and cannot have a couple of people take part in the call at my end. The recent upgrade (2.5) did not correct the problem. What is annoying is that it was working OK before. I am just not sure before what. Any ideas anybody? Android 2.3.4 (stock HTC/T-Mobile), Skype is most recent stock version.
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
try viber.
I just used this like 2hrs ago, Toggle the mic button. I thinks it's a red icon, I've had this problem before. If not then try clearing the data. Let's us know.
Switching to another tool (viber) is not an option - it would take me less time to re-code Skype from scratch myself than to get my parents on a different program.
This is still an issue. The only way I am able to work around it is to quickly plug in my earphones and the unplug them. That seems to force skype to switch to the speaker away from the earpiece. I guess I'll have to deal with this until a future version takes care of it (hopefully).
Hrvoje said:
Switching to another tool (viber) is not an option - it would take me less time to re-code Skype from scratch myself than to get my parents on a different program.
This is still an issue. The only way I am able to work around it is to quickly plug in my earphones and the unplug them. That seems to force skype to switch to the speaker away from the earpiece. I guess I'll have to deal with this until a future version takes care of it (hopefully).
Click to expand...
Click to collapse
I have the excact same issue on mY Sensation. Seems to be a bug...
It's a Skype bug. Not the phone.
Sent from my HTC Sensation Z710e using xda premium
secano said:
It's a Skype bug. Not the phone.
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
i wish you had right about that but as i learn from developers it's about kernel and if anyone will fix this then it's have to be a developer. if i found a solution then i let you know.
agsalman said:
i wish you had right about that but as i learn from developers it's about kernel and if anyone will fix this then it's have to be a developer. if i found a solution then i let you know.
Click to expand...
Click to collapse
You just woke up a 2011 thread
Mark376 said:
You just woke up a 2011 thread
Click to expand...
Click to collapse
my problem still fresh and thanks for link.
So, just curious why most (all?) of the custom ROM's need to have the speaker toggled on/off on the first call after a reboot. Is this another one of those things like HDMI that's very difficult to fix?
I'm wondering if a workaround is possible. Such as taking the code to toggle the speaker on/off and adding it to the Call button. If it was toggled every time a call was made, but before the first ring it'd be pretty much transparent that it's doing it. A second workaround might be to check the last time the phone was rebooted (I'm assuming that date is stored somewhere) and if a call hasn't been made since then, toggle the speaker.
Then again, maybe I have no idea what I'm talking about
SleepyDad said:
So, just curious why most (all?) of the custom ROM's need to have the speaker toggled on/off on the first call after a reboot. Is this another one of those things like HDMI that's very difficult to fix?
I'm wondering if a workaround is possible. Such as taking the code to toggle the speaker on/off and adding it to the Call button. If it was toggled every time a call was made, but before the first ring it'd be pretty much transparent that it's doing it. A second workaround might be to check the last time the phone was rebooted (I'm assuming that date is stored somewhere) and if a call hasn't been made since then, toggle the speaker.
Then again, maybe I have no idea what I'm talking about
Click to expand...
Click to collapse
All I know is that it's a Hellraiser issue having to do with i9000 ROMs. If Linux hasn't fixed it yet, then it must be one hell of an issue to fix because Linux is one smart guy when it comes to this stuff, haha.
Sent from my SAMSUNG-SGH-I997 using xda premium
If you don't want that issue, use based on stock/leak roms, they are fine. Also, Bluetooth audio on hellraised roms doesn't work.
Sent from my SAMSUNG-SGH-I997 using XDA App
Perpetrator said:
If you don't want that issue, use based on stock/leak roms, they are fine. Also, Bluetooth audio on hellraised roms doesn't work.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
The issue isn't that bad given the benefits of the custom Rom's. To me (a programmer, just not a ROM one), it just seems like something that could be handled with one of the workarounds I mentioned. Granted, that means some one would actually have to do it
Maybe the final GB ROM will be out soon and this won't be an issue.
Perpetrator said:
If you don't want that issue, use based on stock/leak roms, they are fine. Also, Bluetooth audio on hellraised roms doesn't work.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
Bluetooth audio works fine for me on Mosaic 8.
Sent from my Mosaic 8 Infuse
First, yes, bluetooth DOES work with most Hellraised ROMs. There are some with pairing issues for certain folks, but it's hit or miss there. Second, the first call issue I never really looked into. It didn't bother me much, and there was an easy workaround, so I focused my time on other things once the issue was discovered. So it may be possible to fix I just never got around to looking into it.
LinuxBozo said:
First, yes, bluetooth DOES work with most Hellraised ROMs. There are some with pairing issues for certain folks, but it's hit or miss there. Second, the first call issue I never really looked into. It didn't bother me much, and there was an easy workaround, so I focused my time on other things once the issue was discovered. So it may be possible to fix I just never got around to looking into it.
Click to expand...
Click to collapse
Sorry for spreading misinformation
Sent from my SAMSUNG-SGH-I997 using XDA App
Does this have to do with the leaked ICS radio? If not, how do I fix this because I know this would be really annoying if I heard my own echo.
noise suppression
It could be a bad phone. The first one I got did the same thing on every single call. Everyone I spoke to heard an echo. I had AT&T replace it and the new one works perfect.
How do I disable noise suppression? I don't see it in any settings option
Sent from my SAMSUNG-SGH-I727 using xda premium
Girn said:
How do I disable noise suppression? I don't see it in any settings option
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Settings/call/additional settings
xcrazydx said:
Settings/call/additional settings
Click to expand...
Click to collapse
Its not in there and I'm on sky ics [the real thing]
Sent from my SAMSUNG-SGH-I727 using xda premium
Girn said:
Its not in there and I'm on sky ics [the real thing]
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
That is not an option on ICS, its in the in call menu now. I was referring to GB builds.
there was another user with a similar issue, noise suppression was a problem on pics, and he had to disable it each call. I may actually have a damaged skyrocket, I recommend warranty action
Girn said:
Does this have to do with the leaked ICS radio? If not, how do I fix this because I know this would be really annoying if I heard my own echo.
Click to expand...
Click to collapse
Do you have a case on the phone? If so, take it off and see how it works. On GB, people that had the "echo" problem usually could handle it by disabling "noise suppression", but ICS needs it to be disables on a call by call basis. It is one of the things (along with the "contacts" tab) that I hope the devs can add back into the ICS builds.
I didn't have the "echo" problem with GB, but it is there with ICS when I have a case on the phone. I get around it by using bluetooth most of the time.
scott14719 said:
Do you have a case on the phone? If so, take it off and see how it works. On GB, people that had the "echo" problem usually could handle it by disabling "noise suppression", but ICS needs it to be disables on a call by call basis. It is one of the things (along with the "contacts" tab) that I hope the devs can add back into the ICS builds.
I didn't have the "echo" problem with GB, but it is there with ICS when I have a case on the phone. I get around it by using bluetooth most of the time.
Click to expand...
Click to collapse
Was just here to post this, I discovered the Noise reduction setting but you have to set it from the in call settings menu (as in while you are on the call).
Weird issues
Hey guys, I'm new here and im having some weird things going on, I had that echoing problem so I used odin to go back to stock, now when I'm in a call the mic seems to cut in and out, any ideas?
Mine is being sent back for warranty work.
The echo won't go away no matter what I try.
Sammy didn't even flinch. Just issued a repair ticket. Sucks that I will be without it while they fix/replace it.
Lilbrian15 said:
Hey guys, I'm new here and im having some weird things going on, I had that echoing problem so I used odin to go back to stock, now when I'm in a call the mic seems to cut in and out, any ideas?
Click to expand...
Click to collapse
Same thing here bro, for most people going into settings-call-additional settings then turning off noise suppresion works. To test it do that then call your home or some voice mail and as your speaking run your finger back and forth over the tiny hole by the headphone input (that is the noise canceling mic)
If you can do that and you dont go in and out anymore then you should be good to go. I myself get the same problem and have to send in for repair.
HA HA! I got this problem solved!
I bought a outterbox case for my I9100,
and same time I cought this problem!
I thought that there is a problem with the demultiplexation, changed a lot of modems and kernels...
What a funny pill was to take off the CASE!
The case is very tight and problaly because of that it transports vibration(sound) from speaker to mic! Same moment as I took it of the problem was solved!!!
Hi.
A couple of days ago I've picked up my new phone moded (GSM SIM slot mod) by CornholiGSM. The phone is now rooted and running CM 10.2 (cm-10.2-20131001-NIGHTLY-skrilax-xt897).
Everything so far seems to be working except the mic, every time I make a call I have to shout so the recipient could hear me. I've can also hear a little buzzing sound in the front speaker but this is probably a faulty capacitor.
Is there any option to change the gain of mic? Did any one else experienced this problem, the search function doesn't work so I'm unable to check forums.
I am on 10-5-2013 and yes the mic volume is low.
In cm 10.2 thread , there was talk about mic volume being low they fixed it once.
Sent from my XT897 using XDA Premium 4 mobile app
rbeavers said:
I am on 10-5-2013 and yes the mic volume is low.
In cm 10.2 thread , there was talk about mic volume being low they fixed it once.
Click to expand...
Click to collapse
Only a part of the original issue was fixed so far.
I've already pushed this: https://github.com/razrqcom-dev-tea...mmit/051c249e974db135e0da0e69934d84eb005c8768
But I haven't found the time so far to extract and push the proprietary libaudcal libs for the other devices we share the CM development with, which is required for the change to be pushed to the repos from which the CM nightly builds are actually made.
I'll try to finish it soon, if my free time will permit (but they demand my attention constantly, it's almost impossible to touch the keyboard and focus on anything at this time ).
Thanks for your hard work!
Sent from my XT897 using XDA Premium 4 mobile app
kabaldan said:
Only a part of the original issue was fixed so far.
I've already pushed this: https://github.com/razrqcom-dev-tea...mmit/051c249e974db135e0da0e69934d84eb005c8768
But I haven't found the time so far to extract and push the proprietary libaudcal libs for the other devices we share the CM development with, which is required for the change to be pushed to the repos from which the CM nightly builds are actually made.
Click to expand...
Click to collapse
Thanks, appreciate your work.
saint_tm said:
I've can also hear a little buzzing sound in the front speaker but this is probably a faulty capacitor.
Click to expand...
Click to collapse
I noticed this on CM10.2 as well (along with a hang on reboot), which went away when I dropped back to 10.1. So the buzz is likely part of the audio library issues rather than the cap. Just a heads up. Hopefully the bad library isn't over-driving the hardware causing permanent damage.
cmags said:
I noticed this on CM10.2 as well (along with a hang on reboot), which went away when I dropped back to 10.1. So the buzz is likely part of the audio library issues rather than the cap. Just a heads up. Hopefully the bad library isn't over-driving the hardware causing permanent damage.
Click to expand...
Click to collapse
The Photon Q specific libaudcal has been merged very soon after I pushed it and has been used since the early October CM 10-2 nightlies. That's not an issue any more.
The cause of the high pitch buzz in earpiece during calls is the mic bias enabled.
It will be fixed by this commit: http://review.cyanogenmod.org/51949 .
Running nightly from 29/11/2013 (GSM) the low mic gain is driving me crazy, will this ever be fixed
UPDATE:
This is now fixed with CM11