Related
Hi guys, I have an issue with Sat Nav volume. I will try to break it down simply:
Sat Nav [CoPilot and Navigator tested]
Music app [PowerAMP and HTC Music tested]
Audio cable [3.5mm audio jack - plugged into car stereo]
Sound settings all full [set in Quick Settings and also manually set Navigation Volume when Google Navigator is running]
Audio is fine when any music app playing [with or without cable]
Audio is fine when any Sat Nav voice playing [with or without cable]
Audio is fine when any Sat Nav + any Music app both playing (music cuts out and voice becomes audible) [WITHOUT CABLE]
--- Sat Nav voices becomes too low to hear when both Sat Nav and Music playing with cable plugged in ---
This was working perfectly fine on stock HTC (both Froyo and GB) with kernel Buzz OCUV 1.0.6.
I have only seen this issue since flashing Android Revolution HD 5.1.9 > 5.1.10 > 5.1.11 . I have tried different kernels ( Stock ARHD > UnityV2 > UnityV3 ) and also retried Buzz OCUV 1.0.6 but the issue still remains.
Does anybody have any ideas as to what could be the problem?
Anybody have any ideas at all?
Sent from my Desire HD using XDA App
I've always had this issue too, All I have been doing is lower the music volume to half, set Navigation Volume to Full and then increase the car volume instead
According to google support forum, It looks like the issue is caused by GB 2.3.3, 2.3.2 does not have this problem so it seems downgrading is the only fix.
I have the same exact problem unfortunately.
I'm guessing you're using Google Navigation instead of HTC's Locations Premium Navigation?
I'm currently on 2.3.3, and I don't really have a problem with any bad navigation volumes. If you're not okay with paying to try out Locations Navigation, don't worry, you have a 1 month worldwide navigation license which you can activate and use for free without any restrictions.
Thanks for your 'input' Vious, but the issue remains no matter what satnav is used, premium or not.
It is a confirmed 2.3.3 issue with multiple threads on the google code forums
Sent from my Desire HD using XDA App
I hope they fix this soon. Such a GIGANTIC issue... i can't believe this isn't at all critical for them.
Same problem for me, Copilot support could not fix it for me also, claiming it was a problem with android not them. Used to work on Version 8.x.x.606
If this affects all versions of Android above 2.3.2 then it looks as if I have little choice but to buy an iphone or wp7 phone next, Google are unbelievable sometimes!
6 months and still no fix, I love Android and would hate to switch but this is a complete joke!!!
http://code.google.com/p/cyanogenmod/issues/detail?id=3165
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=794d84c209f5ad2d&hl=en
http://code.google.com/p/android/issues/detail?id=15690
I know this is an old thread, but I wanted to share my solution for this same problem that I've been having since upgrading to the new gingerbread. Note though that this is no longer an issue if you're using the latest google navigation app, but if you're like me and you like to use an offline nav app like CoPilot, then this solution should work for you.
Since this problem was introduced in gingerbread 2.3.3, I thought I would try replacing the libaudiopolicy.so library with one from a gingerbread 2.3.2 rom I had laying around and voila, that seemed to have solved the problem! I haven't tested this thoroughly, but it seems to be working so far. I hope this helps anyone else out there that is still suffering from this issue.
Could you post the file? Also, have you encountered any issues so far?
Perhaps post this in the previously mentioned google code pages for more testers....
Sent from my Desire HD using XDA App
Here you go! This one is for sense based roms.
No issues so far!!
Perhaps when I have a little bit more time, I'll post a link to this thread in those referenced google pages.
hexion said:
Here you go!
No issues so far!!
Perhaps when I have a little bit more time, I'll post a link to this thread in those referenced google pages.
Click to expand...
Click to collapse
Nice one I'll give this a try
I presume the libaudiopolicy.so file you posted is from a Sense ROM, it didn't work for me as I'm running BlackIce which is CM based.
Downloaded an early CM7 nightly based on 2.2.3, copied that file over and it worked!
I have updated the previously referenced Google pages.
Attached is the CM7 2.3.2 libaudiopolicy.so if anyone wants it.
rgrover said:
I presume the libaudiopolicy.so file you posted is from a Sense ROM, it didn't work for me as I'm running BlackIce which is CM based.
Downloaded an early CM7 nightly based on 2.2.3, copied that file over and it worked!
I have updated the previously referenced Google pages.
Attached is the CM7 2.3.2 libaudiopolicy.so if anyone wants it.
Click to expand...
Click to collapse
Yes, sorry, forgot to mention that. I've updated my post so now it won't confuse anyone else.
I'm glad the one from CM7 worked for you!
hexion said:
I know this is an old thread, but I wanted to share my solution for this same problem that I've been having since upgrading to the new gingerbread. Note though that this is no longer an issue if you're using the latest google navigation app, but if you're like me and you like to use an offline nav app like CoPilot, then this solution should work for you.
Since this problem was introduced in gingerbread 2.3.3, I thought I would try replacing the libaudiopolicy.so library with one from a gingerbread 2.3.2 rom I had laying around and voila, that seemed to have solved the problem! I haven't tested this thoroughly, but it seems to be working so far. I hope this helps anyone else out there that is still suffering from this issue.
Click to expand...
Click to collapse
Thanks hexion, you see this is exactly what I have been trying to say all this time - it must be something slightly changed in some audio file somewhere between 2.3.2 and 2.3.3 . I just have no idea about Linux / Android so never knew where to look for such things.
Now all we need is to compare these to see where the changes lie and try to patch the most current libaudiopolicy.so with only the previous Navigation settings, leaving all other new things as is.
rgrover said:
I presume the libaudiopolicy.so file you posted is from a Sense ROM, it didn't work for me as I'm running BlackIce which is CM based.
Downloaded an early CM7 nightly based on 2.2.3, copied that file over and it worked!
I have updated the previously referenced Google pages.
Attached is the CM7 2.3.2 libaudiopolicy.so if anyone wants it.
Click to expand...
Click to collapse
Hey rgrover, I'm also on CM7.1 Nightly. I tried renaming old file to libaudiopolicy.so.bak and copied the file you supplied into system/lib but now my device will not load past white HTC screen after reboot. Any advice?
UPDATE: it's OK it seems it was just a permissions problem. Everything working fine now
Hexion, you f**king treat !
My DHD is now pure perfection, with CM7.1 installed and this Sat Nav fix. Everything works at it should and I need nothing else from a phone (apart from battery life, but hopefully I can get Daemon Controller on CM7 at some point with better kernel).
If I had mone I would buy you a bottle JD (actually I would buuy myself one lol, maybe share with you XD )
Apparently, this fix for sat nav apps does not work for Google Navigation and TuneInRadio according to chykal1 on the google page. Music will not be lowered when the nav voice comes on. So if you use TuneInRadio a lot, you probably shouldn't apply this fix. Maybe when someone patches the latest libaudiopolicy.so, then we'll have a true solution.
Firstly, a big thanks to fellow kiwi developer "dzo" for this great port!
Official dev thread: http://forum.xda-developers.com/showthread.php?t=1492957
I'm unable to post in the dev section until I have 10 posts, so I thought I would start an issues thread here for people who also haven't made 10 posts yet.
***IF YOU DO HAVE AN ISSUE YOU WOULD LIKE TO POST ABOUT, IT MAY BE HELPFUL TO INCLUDE KERNEL AND ROM DETAILS***
e.g. Official 2.3.5 B522 as base, Aurora ICS version 1.6, used 5.5.0.4 Recovery
CURRENT TESTING VERSION - 1.8
Issues:
-Sound from the speaker is scratchy and distorted, everytime the phone emits sounds - especially noticeable in notifications.
-The volume from the speaker is too loud on the lowest volume setting.
-Product name/model needs to be changed from 'msm7630_surf' to 'Huawei u8800' in build.prop
-SD card sometimes doesn't mount (requires restart to mount)
-No panorama mode in camera. ---stock camera app
-Gallery app crashes when selecting Edit (random, sometimes the photo editor works, sometimes crashes).
-Movie Studio crashes when adding in/out transitions.
-Camera app crashes when selecting any "face effect" in video mode. ---stock camera app
Notes:
I used the B522 official Huawei 2.3.5 as base, and then loaded version 1.6 over top of that using Recovery 5.5.0.4.
Archived Issues:
-The lights on the backlit keys don't work all the time, even when it's dark. [It appears this is by design. Use auto-brightness for the keys to light automatically.]
-Mobile Networks --> Network Operators is unable to search for networks (both automatically and manually). It says "Error While Searching for Networks". [Seems to have been fixed with 1.8]
-UI is generally quite laggy across the whole system [Seems a lot better with 1.8]
-It probably needs a "file explorer app" installed as stock so you don't have to manually transfer one via USB. [ES File Explorer added in version 1.8]
-Red border appears momentarily on occasion (usually when a sound is playing - also happens when unlock pin code is being entered) [Hasn't happened with version 1.8]
-Playback of music tracks does not automatically go to next track after previous track is finished. ---beyond pod; stock music player [Fixed in version 1.8]
Version 1.6?
some people are complaining about slow Internet connection.. do you note that issue?
kickban said:
Version 1.6?
Click to expand...
Click to collapse
Yes, dzo's Aurora ICS U8800 port version 1.6.
kickban said:
some people are complaining about slow Internet connection.. do you note that issue?
Click to expand...
Click to collapse
I've only just loaded ICS on during the last few hours, so haven't had time to thoroughly test internet/browser. Will do eventually though.
The Ookla Speedtest app seemed to have good speeds. Although the upload speed seemed a little "out". It was up around the 1.7-1.8Mbps mark, when I know my upload speed is capped at 1.0Mbps.
Also, the mini graphs that show the upload and download speeds underneath the main "meter" was showing a weird streaky white block instead of the usual line graph. I wonder if others could test this too and report back.
I can add "slow internet" to the OP issue list if you like?
Can you explain it a little more for clarity?
Cheers.
i cant use any camera app, but stock one works just fine
Ookla Speedtest app gives me 100kbit/s down on a 2mbit/s internet connection.
When I press at the wifi it shows link speed 6Mbps.
Edit: speed ok after changing router
Great idea, I too have some issues I'd like to report but I'm unable due to the 10 posts limitations. Hopefully someone w/ access will bring this link to dzo's attention.
So far, the ones I think weren't reported yet:
No panorama mode in camera;
Gallery app crashes when selecting Edit (random, sometimes the photo editor works, sometimes crashes);
Movie Studio crashes when adding in/out transitions;
Camera app crashes when selecting any "face effect" in video mode;
Some background noise everytime the phone emits sounds - especially noticeable in notifications;
That seems to be it, will add more as I find them.
tiansial said:
i cant use any camera app, but stock one works just fine
Click to expand...
Click to collapse
I've just tried using CameraZoom and it worked.
Can you please list the camera apps that aren't working for you.
Cheers.
dzo just released version 1.7.
This guy never sleep
kilroystyx said:
dzo just released version 1.7.
This guy never sleep
Click to expand...
Click to collapse
It hasn't yet appeared on SourceFroge yet, but will testing it as soon as it's up to see if any of these issues have been addressed.
Indeed, dzo is a legend!!
Also, he probably does sleep, it's just that he sleeps when most of the rest of the world is awake... being that he is from New Zealand. ;-)
dp42 said:
It hasn't yet appeared on SourceFroge yet, but will testing it as soon as it's up to see if any of these issues have been addressed.
Indeed, dzo is a legend!!
Also, he probably does sleep, it's just that he sleeps when most of the rest of the world is awake... being that he is from New Zealand. ;-)
Click to expand...
Click to collapse
You're right, living in New Zealand ;-)
Version 1.7 is ready for download, let's test it ;-)
kilroystyx said:
Version 1.7 is ready for download, let's test it ;-)
Click to expand...
Click to collapse
Nope, unfortunately not for me yet.
SourceForge is being a bit buggy for some people at the moment (including me). Others on the main Aurora thread have said that 1.7 has appeared on SourceForge for them, but for others it hasn't yet.
Waiting... waiting.... ;-)
EDIT: It appeared for me momentarily on SourceForge, but when I went to click to download it said the file was unavailable to download. dzo has just uploaded it to Google Code, so downloading now.
Sourceforge was with a strange behavior, but now seems to be fine.
Try now, I'm sure now you can
1.8 is out.
I actually went back to stock B522 for the moment, as I just found the 1.7 UI too laggy, but I might load 1.8 on now.
OK, installed 1.8 yesterday and I don't know if it is the ROM, or if I did something different to install it, but it appears to be running a lot smoother UI wise.
Sound from the speaker is still terrible though. It sounds to me like it could be a sampling rate incompatibility.
dp42 said:
OK, installed 1.8 yesterday and I don't know if it is the ROM, or if I did something different to install it, but it appears to be running a lot smoother UI wise.
Sound from the speaker is still terrible though. It sounds to me like it could be a sampling rate incompatibility.
Click to expand...
Click to collapse
It's really weird because sound is only distorted when played through that back-speaker.
Ringtones are awfull, full of cracks and distortion... and always with hiss background noise.
This is a common problem on all those .35 custom rom's
hey guys,
ive a question about porting, im using a u9000 variant, similar hardware and on the u9000 forum w have devs that successfully port u8800 roms.. my question is, since u8800 roms are portable, may i know what is required for u guys before flashing to aurora ics? ie what kernel were u on before the flash? thanks for the help!
cheezzzz said:
hey guys,
ive a question about porting, im using a u9000 variant, similar hardware and on the u9000 forum w have devs that successfully port u8800 roms.. my question is, since u8800 roms are portable, may i know what is required for u guys before flashing to aurora ics? ie what kernel were u on before the flash? thanks for the help!
Click to expand...
Click to collapse
Aurora needs to flash on 2.3.5 stock roms. Stock .35 kernel required.
Tmp341 said:
Aurora needs to flash on 2.3.5 stock roms. Stock .35 kernel required.
Click to expand...
Click to collapse
i have 2.3.5 firmware with stock 2.6.35.7 kernel. however i think due to difference in device and the port, it may not be possible.
mine is u9000 with MSM8225 chipset 2.3.5 firmware n .6.35.7 kernel
aurora is built for u8800 with MSM7230 chipset, similar firmware and kernel
however u8860, the source that aurora used, is with MSM8255 chipset, not sure about firmware and kernel.
read somewhere that ports are device specific, so to get it working on u9000, id have to port from aurora, and fix whatever that doesnt work.. correct me if i am wrong.. dev/porters please advise!
thanks!
cheezzzz said:
i have 2.3.5 firmware with stock 2.6.35.7 kernel. however i think due to difference in device and the port, it may not be possible.
mine is u9000 with MSM8225 chipset 2.3.5 firmware n .6.35.7 kernel
aurora is built for u8800 with MSM7230 chipset, similar firmware and kernel
however u8860, the source that aurora used, is with MSM8255 chipset, not sure about firmware and kernel.
read somewhere that ports are device specific, so to get it working on u9000, id have to port from aurora, and fix whatever that doesnt work.. correct me if i am wrong.. dev/porters please advise!
thanks!
Click to expand...
Click to collapse
you're right it may harm your phone
hey!
i install tasker and i have problem....
i make profile when i open mx player so auto rotation become on...but isn't happend!
any one with cm10 can confirm tasker work for him?if yes you can try this profile and tell me if it work to you?
thanks!
someone?
Yeah, I think I try something similar for gallery, and it did not work for me.
Tapped from Defy+ with CM10 from quarx
mikrom.cz said:
Yeah, I think I try something similar for gallery, and it did not work for me.
Tapped from Defy+ with CM10 from quarx
Click to expand...
Click to collapse
version 1.3.1 work fine
problem solved!
Compiled for myself..Thought it was time to share with the community
Features:
Built from source cm 10.1(4.2.2)
Tablet UI(Single navbar at the bottom)
camera disabled for better battery(thanks drmarble)
Every bug from other cm10.1 builds still exists
Click to expand...
Click to collapse
Uploaded on my Google Drive
DOWNLOAD LINK:https://docs.google.com/file/d/0B14neSzxlb6oSFhteUdKTDNUSDA/edit?usp=sharing
fahd_freak said:
Compiled for myself..Thought it was time to share with the community
Uploaded on my Google Drive
DOWNLOAD LINK:https://docs.google.com/file/d/0B14neSzxlb6oSFhteUdKTDNUSDA/edit?usp=sharing
Click to expand...
Click to collapse
Nice to see some other forms come out. Does this ROM have the navigation ring feature? Does audio work when the display turns off?
reynoben said:
Nice to see some other forms come out. Does this ROM have the navigation ring feature? Does audio work when the display turns off?
Click to expand...
Click to collapse
Didn't look into navigation ring... And the audio doesn't seem to be working when screen goes off... Is it a bug with all the cm10.1 builds? Is it been fixed on other builds?.. Anyways I'll look into it...
Edit:navigation ring does appear, but it appears in the middle... Not usable.. Will fix in the next build..
Sent from my GT-N7000 using xda app-developers app
fahd_freak said:
Didn't look into navigation ring... And the audio doesn't seem to be working when screen goes off... Is it a bug with all the cm10.1 builds? Is it been fixed on other builds?.. Anyways I'll look into it...
Edit:navigation ring does appear, but it appears in the middle... Not usable.. Will fix in the next build..
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
I have only tried Shumash's ROM and the audio bug exists in that.
reynoben said:
I have only tried Shumash's ROM and the audio bug exists in that.
Click to expand...
Click to collapse
The bug also exists in all CM 10.1 ROMs, as well as the latest CM9 nightlies and JCSullin's latest CM10 preview ROM.
It's something that's been bugging me for a long time now
YOUCANNOTDENY said:
The bug also exists in all CM 10.1 ROMs, as well as the latest CM9 nightlies and JCSullin's latest CM10 preview ROM.
It's something that's been bugging me for a long time now
Click to expand...
Click to collapse
No it doesnt.. You most not know what bug he is talking about.
icy_gt said:
No it doesnt.. You most not know what bug he is talking about.
Click to expand...
Click to collapse
Of course I know what the bug is. Any locally played music stops playing immediately after the screen turns off. The music is interrupted with a tone that sounds similar to a system beep, akin to a sound that a piezoelectric speaker would make.
Just checked. Its fine in JCsulins's latest cm10 build. music doesnt stop when screen turns off, but it does happen in shumash's
The bug is there in SGA'S 4.2.2 rom also. Music stops playing when screen goes off.
chicle_11 said:
The bug is there in SGA'S 4.2.2 rom also. Music stops playing when screen goes off.
Click to expand...
Click to collapse
I've figured out a workaround... I've posted the rom in my other thread... It doesn't happen anymore.. But it's got high battery drain in sleep
Sent from my GT-N7000 using xda app-developers app
I could have sworn that the 4.2.2 ROMs that CDMoncrieff made dont have the issue with sound when the screen is off. Thats what I'm currently using.
fahd_freak said:
Just checked. Its fine in JCsulins's latest cm10 build. music doesnt stop when screen turns off, but it does happen in shumash's
Click to expand...
Click to collapse
Just wiped and did a clean install of JCSullin's latest build. The music plays fine for a while, and there appears to be no bug, but the bug comes back after playing music for a while.
YOUCANNOTDENY said:
Just wiped and did a clean install of JCSullin's latest build. The music plays fine for a while, and there appears to be no bug, but the bug comes back after playing music for a while.
Click to expand...
Click to collapse
Sounds like you need to acme uninstall everything and start fresh. I used jc's cm10 for a long time and played music very often. Never had a problem.
Sent from my HTC One S using xda app-developers app
I have a 2013 prius stock and a galaxy s4... When I had stock Rom my music information that showed on the prius screen came up but I was unable to change songs or go to playlists through the prius screen. I went to paranoid android Rom and now for all song music it is showing as unavailable and the contacts do not sync.... I have heard it might be the aosp or something like that.... is there ANY WAY to fix this
ncrispi said:
I have a 2013 prius stock and a galaxy s4... When I had stock Rom my music information that showed on the prius screen came up but I was unable to change songs or go to playlists through the prius screen. I went to paranoid android Rom and now for all song music it is showing as unavailable and the contacts do not sync.... I have heard it might be the aosp or something like that.... is there ANY WAY to fix this
Click to expand...
Click to collapse
No there is no way to fix this. AOSP-based roms do not have the correct AVCRP version to support this feature. Previously, CM9 or 10 supported this with bluestack's cherry pick, but bluestacks has not updated this iirc.
You're SOL, sorry.
chaosclarity said:
No there is no way to fix this. AOSP-based roms do not have the correct AVCRP version to support this feature. Previously, CM9 or 10 supported this with bluestack's cherry pick, but bluestacks has not updated this iirc....
Dang so there is no way to add this in with a script or such? Or Download an app that supports it? ..
Click to expand...
Click to collapse
You could flash the Google Edition 4.2.2 , while not aosp, it has the vanilla flavor, bout you miss out on customization. Once 4.3 is released we should be good as the new Bluetooth stacks will have it
Sent from my SGH-I337 using Tapatalk 4 Beta
so is there currently any ROM that has the qualifications to allow me to play and stream music info to my car?
Any ROM will stream music into your car.
NON TOUCHWIZ ROMS will not stream Music information into your car.
It's as simple as that.
Google doesn't support it. Samsung has to add that feature, so thats why it only works on Touchwiz.
It's been a problem ever since 4.2 came out. With 4.1, custom ROM's like Cyanogenmod could manually add the feature in, but since Google changed the bluetooth stack on 4.2, nobody has either A) figured it out or B) gave it time to look into it.
geoldr said:
Any ROM will stream music into your car.
NON TOUCHWIZ ROMS will not stream Music information into your car.
It's as simple as that.
Google doesn't support it. Samsung has to add that feature, so thats why it only works on Touchwiz.
It's been a problem ever since 4.2 came out. With 4.1, custom ROM's like Cyanogenmod could manually add the feature in, but since Google changed the bluetooth stack on 4.2, nobody has either A) figured it out or B) gave it time to look into it.
Click to expand...
Click to collapse
oh... Well thats a downer..
ncrispi said:
oh... Well thats a downer..
Click to expand...
Click to collapse
Yes.
Everyone says that 4.3 will support it, but since Google never said anything about it (and I assume it doesn't work on the leaked 4.3 ROM) I would say to just either tough it out, or stick with a TW ROM. And get Nova launcher or something.