Database Users

Navigation Volume too low

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.

Rebooting during navigation & apps that use nav

I am getting reboots while using the Uber Partners or Lyft apps when they use google navigation (they integrate with a nav app for navigation). This only happens when using an AOSP based Lollipop rom but not stock (specifically tried Blisspop, Fusion and CM). I do not change or alter the kernels when trying any of the roms. I have not found any known issues where rebooting occurs with google navigation by itself, but I could be wrong of course. I would really like to use an AOSP rom rather than stock but cannot with this issue. Any suggestion to get around this, if this is known and I just need to wait, or any other suggestions would be great. Thank you.

Hi, I use a lot GPS apps, tried Lyft on my phone (S5-gm900f, with Phoenix ROM v6.3 + Kernel) and it's working fine.
It's the most stable and powerful ROM I've ever used on my S5.

1989andres said:
Hi, I use a lot GPS apps, tried Lyft on my phone (S5-gm900f, with Phoenix ROM v6.3 + Kernel) and it's working fine.
It's the most stable and powerful ROM I've ever used on my S5.
Click to expand...
Click to collapse
Thank you for the reply. I don't think that rom is available for me (g900t). Do you use the Lyft map or let it switch to google map navigation?

You're right, its only for gm900f ,
And I made a mistake, I tested Uber and it worked fine, saw the drivers and set the pick up location
Since I'm outside USA couldn't check my phone number with Lyft.
Sorry

1989andres said:
You're right, its only for gm900f ,
And I made a mistake, I tested Uber and it worked fine, saw the drivers and set the pick up location
Since I'm outside USA couldn't check my phone number with Lyft.
Sorry
Click to expand...
Click to collapse
Thank you again. Also, this is on the driver side where the driver uses driver app which in turn integrates with a navigation app such as google maps.

Recently reported bugs and fixes [2015-9-16 Updated]

All information is from Chinese official MIUI fourm (http://www.miui.com/thread-2894668-1-1.html)
I just translated to English for us to know what have been reported and fixed from latest developer version.
1. Touchscreen is not very sensitive, likely to lost the input.
A: This is a big trouble for user, we've fixed it on dev. 5.9.2 will soon release the stable version with the fix.
2. Some of the apps especially banking apps get FC. (This my Chinese app specific)
A: This is because Note 2 is based on latest Google code, the reason is the apps is not compatible well with Android 5.0. We are working on this.
3. Get FC/lags/reboot when switch/connect to Wifi.
A: We've contact with some of the user and get the logcat. We need more time to fix this because it related to some driver problem.
update: On dev. 5.9.10+, we've fix this issue on dev. 5.9.15. For normal user, please wait for the update on Friday.
4. Screen cause battery drain.
A: We've optimized the system on dev. 5.9.2+ please update your MIUI and report again.
update: On dev. version 5.9.10+, we've optimized on wifi, please update your MIUI and report your experience again.
5. Laggy when playing "doudizhu" or literally "battling the landlord". (This is Chinese app specific)
A: We've fix this issue on dev. 5.9.2
6. Volume key - can't wake the device after long time standby.
A: Sorry, we need more time to figure out the issue.
7. We noticed Note 2 have memory leak.
A: We've found the solution and solved it on dev. 5.9.2, Fixes on stable version will release soon.
8. There have a chance to get "SD card is corrupt" when using c10 SD card.
A: We are testing a fix for this, please be patient for this fix.
update: We've fixed this on dev. 5.9.10
9. When playing games, we notice some noisy crack sound when lowest volume.
A: We received this report and trying to fix it, please be patient.
update: We've fix this crack sound when playing games and receive the call on dev. 5.9.16 [2015-9-16]
10. Screen keep flicker in low brightness when playing videos.
A: We are looking for the solution.
update: We fix this on latest beta v5.9.15 please update your MIUI or wait for dev. version on Friday.
update: There's still some of the user reporting flicker, we will fully fix this on dev. 5.9.17, please be patient [2015-9-16]

Awesome!
Good to know they are aware of the sound and brightness issues.

great post, thanks mate

It's good that they mention the sound in games, but what about the sound issues over A2DP and at times out of the headphone jack? Hope they are aware of them as separate issues.

Ouzo said:
It's good that they mention the sound in games, but what about the sound issues over A2DP and at times out of the headphone jack? Hope they are aware of them as separate issues.
Click to expand...
Click to collapse
I hope this is the mirror bugs related to crack sound, they've solved just on today's dev. release
If you can download the latest dev. version, you can be the first one confirm this is solved:good:

jwchen119 said:
I hope this is the mirror bugs related to crack sound, they've solved just on today's dev. release
If you can download the latest dev. version, you can be the first one confirm this is solved:good:
Click to expand...
Click to collapse
I have a feeling that the problem with stereo Bluetooth might be different, but I'll be very happy indeed if I'm wrong.
I have limited data each month so I'll have to wait until Friday when Xiaomi.EU release their multi language ROM.

can someone request Chinese Dev to add double tap to wake feature.

mzeshanhakeem said:
can someone request Chinese Dev to add double tap to wake feature.
Click to expand...
Click to collapse
Does the screen support it? I know the SoC does, in theory (it also supports MHL but were not going to get that).
If you install a third party launcher like Nova, you can add a shortcut to the home screen via activities that will let you get to a more default looking version of settings. In there you will find a setting to enable double tap to wake, but of course enabling it doesn't work.

Gesture support is not enabled in redmi note 2 kernel that is why it does not work and MIUI has not released kernel source yet.
Users requested for this feature on en.miui.com (worst forum i have ever experianced)
will wait and see.....

One critical bug:
Apps from Google play store can't be installed without WLAN.
I try to explain it with my limited English.... When trying to download the app, the popup appears telling something like; the file is very big, do you want to install it with WiFi or not. Answering I DO NOT want to use WiFi, the download bar appears with text; waiting for WiFi connection.
So, without WiFi the phone is useless because this bug.
I have 150Mb LTE but cannot install anything
I live in Finland and I have to get overseas data roaming checked to get data connection (LTE) working.

Icemint said:
One critical bug:
Apps from Google play store can't be installed without WLAN.
I try to explain it with my limited English.... When trying to download the app, the popup appears telling something like; the file is very big, do you want to install it with WiFi or not. Answering I DO NOT want to use WiFi, the download bar appears with text; waiting for WiFi connection.
So, without WiFi the phone is useless because this bug.
I have 150Mb LTE but cannot install anything
I live in Finland and I have to get overseas data roaming checked to get data connection (LTE) working.
Click to expand...
Click to collapse
I saw a way to download large apps from the Play Store without WiFi mentioned in this Note 2 FAQ http://en.miui.com/thread-144562-1-1.html
Here:
http://en.miui.com/thread-18396-1-1.html

Go to Downloads,tap ...(right upper corner),Settings, download size limit, unlimited.

Million thanks!!! :victory:
I would have never found it. Tried to look it at the settings of play store.
---------- Post added at 07:17 PM ---------- Previous post was at 07:12 PM ----------
Now when in here...Does anyone know how to tell the phone it is in Finland now? I really dont want to use overseas tethering to get mobile data working.

Today's multi language ROM from xiaomi.EU seems to fix some bugs. I think stereo Bluetooth is stutter free now, though the quality of audio seems to have deteriorated (if you see what I mean). Sound in Dead Space is as bad as ever. Epic Citadel seems better.

Hi, I have the same problem in MIUI 66.66.74.00 but the catch is that i wont' see any "download" app if the vendor has deleted it by mistake how could I get it?
thanks Alberto

Thanks...

nice

[CLOSED] GPS problem on 64 Bit roms?

Yo, what's up with GPS/Location services when I use maps? Its not even funny about how bad it isn't working. If anyone knows a manual fix very very soon that would be great. A kernel or a flashable "GPS Fix" zip file

I think this has been discussed in almost every ROM Forum that since the sensor drivers are still 32 bit, the sensors will not be working! It will be available once it is fixed, there is no point in asking this again and again!
If you need GPS stick to nougat like me!

TheNintendoRejection said:
Yo, what's up with GPS/Location services when I use maps? Its not even funny about how bad it isn't working. If anyone knows a manual fix very very soon that would be great. A kernel or a flashable "GPS Fix" zip file
Click to expand...
Click to collapse
Please use search (on XDA or via your favourite engine) - closed as multiple duplicate...

Oreo and Android Auto

Anyone using Android Auto with the Oreo ROM? Wondering if there are any issues or if Waze and Dialer will work properly now?
Rebranded to L29-C432 so might as well give a few more things a try, but the fRomFuture ROM I'm using is pretty stable so want to check before I jump to another...

syscal said:
Anyone using Android Auto with the Oreo ROM? Wondering if there are any issues or if Waze and Dialer will work properly now?
Rebranded to L29-C432 so might as well give a few more things a try, but the fRomFuture ROM I'm using is pretty stable so want to check before I jump to another...
Click to expand...
Click to collapse
I'm currently using it, the dialer issue is still there (I am using the modded Google dialer from Martin.077 to solve that problem).
Waze behaves the same for me as before - works fine for about a month, sometimes longer, and then one day just black screens and then the only fix is to re-install Android Auto.
I now also have a new problem with Google Play Music with the Oreo update - it does not output any sound when connected via Android Auto. Navigation prompts still work though.
The fix is to use an equalizer app - no idea why it works, but it does, I'm using Equalizer FX.
So yeah, no issues solved, and one additional one added in my case.