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...
Related
Hi everybody!
I've installed Sygic MM09 7.71.7857 on the N1 but the audio (both voice and sound effects) doesn't work. Is this a compatibility issue between Sygic and Android 2.1? Is there a fix?
Thanks!!
Dave
Seems it's not compatible with android 2+. There was a post somewhere that mentioned sygic have a patch you can apply but that you have to contact them for it.
Don't know why they don't highlight this on their site...
Found it, if you look on ipmart they have the patch available in the sygic thread. Just installed from sd card & voices are now working!
previn said:
Found it, if you look on ipmart they have the patch available in the sygic thread. Just installed from sd card & voices are now working!
Click to expand...
Click to collapse
Yeah, you can get voices working on N1, but you only get a couple of instructions before all hell breaks loose and you are lucky if you get a force close option to shut it down! Usually the only way out is to pull the battery!
Unless I'm doing something wrong. Can you please confirm what version you have on your N1, I have 7.71 | Build: 7857 D
And failing that, could you please say exactly what you did to get it to work, ie. install v7737 then intall patch.apk over it, etc.
hello can you post the link for the Sygic Sound patch? thanks
I've heard Sygic 10 works fine on the N1, using the maps from Sygic 9.
Hello,
in the Thread of the Apocalypse rom I read
- Camera.apk bug(Solved)
Click to expand...
Click to collapse
Is it true? Has anybody tested it yet, is it possible to take pictures with the "use wireless networks" option on?
Is it possible to port this change to another ROM, maybe by just copying the camera.apk from the Apocalypse ROM?
The point is, I a running on the stock ROM and I don't want to switch to Apocalypse (since there are some changes that I don't like). But having the camera bug fixed would be perfect!
currently I am using camera360, but it take too long to start and also doesn't write location information into the pictures...
I am using the BVJP9 (Orange) firmware, but as far as I know ALL stock Froyo roms so far have this issue:
When the GPS is turned off and the Wireless network Setting is on, the Camera tries to get your location through the wireless networks as soon as you take a picture, but failes. The Phone vibrates one time, and another two times and you get a "camera error" message without the picture being taken.
It doesn't happen at every time, but far to often to honestly use the stock camera.
With the stock camera it only works reliable when either both, gps and wireless network setting in the location and security settigns are turned off, or if the gps is on and has a fix.
Yeah, thats my problem so far. And when I look into various threads I am not alone with it. The only solution besides deactivation the wireless networks option seems to use another camera app.
Yup the camera bug is fixed..i tested it...check out the Apocalypse rom topic someone posted the bug free cam.apk yu can use....
Sent from my GT-I5800 using XDA App
Alright, found it! Well, or at least I found a file called camera.apk in the thread - lets see if it's the fixed one
If im right not yet. But guys from Apocalypse may look if its possible.
Someone posted something about resolution change but no one yet posted if change something in files do anything.
rueolps said:
Alright, found it! Well, or at least I found a file called camera.apk in the thread - lets see if it's the fixed one
Click to expand...
Click to collapse
Did this fix it for you? I had no luck with the camera.apk posted in the Apocalypse topic... Also the SGSTools hacked camera.apk didn't work.
Edit: OK, sgstools has 2 camera fixes, the second one works
noreason83 said:
Did this fix it for you? I had no luck with the camera.apk posted in the Apocalypse topic... Also the SGSTools hacked camera.apk didn't work.
Edit: OK, sgstools has 2 camera fixes, the second one works
Click to expand...
Click to collapse
Which version of SGSTools do u use?
Im using V 4.1.9 there ist just one hacked Camera.apk.
I didn't have a FC with this one.
Version 4.7.3 of the captivate sgs tools, found on the market.
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.
I have to post this in here because i cant post in the other forum i have noticed that in this rom the magnetic field sensor is not working neither are apps like super compass thanks for such a great rom though i hope this can be fixed.
Compass should work, but I too see a problem with compass apps... Works on google maps though
something is definitely up if you use the app androsensor reboot the phone and then open up androsensor some of the sensor readings don't show up but if you leave it a while they do show up but the app SuperCompass does not work when it did on the stock firmware.
Great rom however but could this bug please be investigated thanks very much and keep up the great work on this amazing rom
Nebulauk said:
I have to post this in here because i cant post in the other forum i have noticed that in this rom the magnetic field sensor is not working neither are apps like super compass thanks for such a great rom though i hope this can be fixed.
Click to expand...
Click to collapse
try this: extract this at system->lib and set the same permissions as the previous libsensorservice.so file. Reboot and check if it works
That file has fixed the problem partially although the compass jumps around alot it displays accurate reading but then the compass jumps to another direction and then back to the correct one thanks this problem seems to be nearly fixed now.
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.