-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [ROM] Quattrimus JB (CM10, AOKP41)
- Thread starter tdm
- Start date
-
- Tags
- lg spectrum
tdm
Android Expert
I found something odd today... Wav files aren't playing on aokp. I thought it was double twist, but winamp won't ay the either... Just a stuttered, distorted sound. Not a big deal, but I wanted to document it.
Maybe neph can look at this, he is also looking at 1080p issues.
zacanger
Member
I found something odd today... Wav files aren't playing on aokp. I thought it was double twist, but winamp won't ay the either... Just a stuttered, distorted sound. Not a big deal, but I wanted to document it.
I'm still having issue 11 (Apollo crashes) so I use Rocket player. FLAC works fine. WAVs work depending on bitrate. 32-bit and 24-bit WAVs don't play, 16-bit WAVs work fine for me.
MrB206
Android Expert
Nice one, thx. That explains it because the wavs I tested were 24 bit.
zacanger
Member
No problem! I actually noticed that issue a while ago, didn't think anything of it. Some audio players on my PC have trouble with 32 and even 24 bit WAVs, I've noticed. I found out they don't work on my phone either when I decided to try mixing on my phone for a change (I'm a recording musician).
paruchuribros
Newbie
I am able to play 24 Bit Flac files with WinAmp player
.Sometimes I did noticed buzz sound for couple of seconds and after that it works fine.
I am not an audiophile but I use LG Spectrum+Fiio E17+Denon D5000 for my commute
MrB206
Android Expert
Same here... I run a label and I tested a file an artist uploaded for me but it wouldn't work. Standard export from daws like Cubase is 24 bit, so I assume that's what he sent. I thought it was odd since I was able to listen to fils like that before.
tdm
Android Expert
Finally got GPS to work on my Spectrum.
I plopped the GB version of gps.default.so onto the filesystem as gps.msm8660.so and *bam* there it is.
I'm assuming that this version won't work for the ICS OTA, but it would be really nice if it did. Anyone with ICS OTA and a working GPS want to give it a try?
http://getquattrimus.com/roms/quattrimus/iproj/gps-spectrum-gb.so
Backup your existing /system/lib/hw/gps.msm8660.so, then overwrite it with this file. Something like this (if you don't recognize what this does and how to revert the effects, please don't try)...
adb shell mount -o remount,rw /system /system
adb shell mv /system/lib/hw/gps.msm8660.so /system/lib/hw/gps.msm8660.so.save
adb push gps-spectrum-gb.so /system/lib/hw/gps.msm8660.so
adb shell chmod 644 /system/lib/hw/gps.msm8660.so
adb shell sync
adb reboot
I plopped the GB version of gps.default.so onto the filesystem as gps.msm8660.so and *bam* there it is.
I'm assuming that this version won't work for the ICS OTA, but it would be really nice if it did. Anyone with ICS OTA and a working GPS want to give it a try?
http://getquattrimus.com/roms/quattrimus/iproj/gps-spectrum-gb.so
Backup your existing /system/lib/hw/gps.msm8660.so, then overwrite it with this file. Something like this (if you don't recognize what this does and how to revert the effects, please don't try)...
adb shell mount -o remount,rw /system /system
adb shell mv /system/lib/hw/gps.msm8660.so /system/lib/hw/gps.msm8660.so.save
adb push gps-spectrum-gb.so /system/lib/hw/gps.msm8660.so
adb shell chmod 644 /system/lib/hw/gps.msm8660.so
adb shell sync
adb reboot
tdm
Android Expert
Yes, both GB and ICS vendor ROMs have gps.default.so.
The non-vendor ROMs name the same thing as gps.msm8660.so.
I don't know why LG chose to name it gps.default.so, but it really isn't an issue. I just renamed the file gps.msm8660.so to be consistent with the non-vendor builds.
There is a defined search order when looking for hardware libs. First the exact hardware name, then the hardware family name, then default. So in this case, the first of the following files found under /system/lib/hw will be used:
gps.iproj.so
gps.msm8660.so
gps.default.so
Well, I gave it a try, renaming the file you provided to gps.default.so, rebooted & such, & it would crash the GPS app & subsequently crash the launcher, though I could still issue adb commands via Android Commander (I know, I cheat, ha!).
I tried it out in Co-pilot as well as Google maps.
Hope that helps in some way.
I tried it out in Co-pilot as well as Google maps.
Hope that helps in some way.
tdm
Android Expert
Well, I gave it a try, renaming the file you provided to gps.default.so, rebooted & such, & it would crash the GPS app & subsequently crash the launcher, though I could still issue adb commands via Android Commander (I know, I cheat, ha!).
I tried it out in Co-pilot as well as Google maps.
Hope that helps in some way.
Yes that helps, though the outcome is not what I wanted.
So it sounds like I'll need to figure out some way to determine the vendor base version and install/swap the appropriate gps lib at runtime. I don't know exactly how that can be done. The simple solution is to use the baseband version, but since I posted flashable basebands, this isn't reliable. The brute force approach would be to checksum one of the non-baseband partitions, but I'd need to figure out which one to use. A better approach would be to find an API version somewhere ... maybe exposed by liboncrpc or something. In short, this is going to be a bit of a mess. I think I'll need to consult with rmcc to see what his thoughts are on the issue.
Yes that helps, though the outcome is not what I wanted.
So it sounds like I'll need to figure out some way to determine the vendor base version and install/swap the appropriate gps lib at runtime. I don't know exactly how that can be done. The simple solution is to use the baseband version, but since I posted flashable basebands, this isn't reliable. The brute force approach would be to checksum one of the non-baseband partitions, but I'd need to figure out which one to use. A better approach would be to find an API version somewhere ... maybe exposed by liboncrpc or something. In short, this is going to be a bit of a mess. I think I'll need to consult with rmcc to see what his thoughts are on the issue.
Well, might be wise to get a confirmation from another user who gives it a go. Who knows? Maybe mine was an anomaly.
I don't know if it'll help to try this file on your build of AOKP, but since i've taken the ICS OTA prior to flashing custom roms (one of the pre-requisites for gps to work)... I figure it might provide some insight.
Right off the the bat though, what I noticed... is that I have a gps.goldfish.so file that you didn't list in your search priority.
Copying your gps.msm8660.so on my device doesn't seem to affect gps at all.
I'm testing with the app, GPS Test from the market. Locked sats quick, and got to 85' accuracy within a matter of seconds.
Here's a logcat along with my existing 2 gps files in /system/lib/hw/.
http://dl.dropbox.com/u/1659941/gps.goldfish.so
http://dl.dropbox.com/u/1659941/gps.msm8660.so.backup
http://dl.dropbox.com/u/1659941/new_gps.so.txt
As I mentioned in the 4.2 thread... I'd be willing to send you one of my nandroids or a dd of my device. Looks like I also have a nandroid filed away from an ICS Stock rooted from when I took the OTA if that would help. If nothing else, it might give you the stock files.
Right off the the bat though, what I noticed... is that I have a gps.goldfish.so file that you didn't list in your search priority.
Copying your gps.msm8660.so on my device doesn't seem to affect gps at all.
I'm testing with the app, GPS Test from the market. Locked sats quick, and got to 85' accuracy within a matter of seconds.
Here's a logcat along with my existing 2 gps files in /system/lib/hw/.
http://dl.dropbox.com/u/1659941/gps.goldfish.so
http://dl.dropbox.com/u/1659941/gps.msm8660.so.backup
http://dl.dropbox.com/u/1659941/new_gps.so.txt
As I mentioned in the 4.2 thread... I'd be willing to send you one of my nandroids or a dd of my device. Looks like I also have a nandroid filed away from an ICS Stock rooted from when I took the OTA if that would help. If nothing else, it might give you the stock files.
tdm
Android Expert
Goldfish hardware is the emulator. It's not used, it's just along for the ride.
tdm
Android Expert
No let's keep cm10.1 separate. I specifically want to know if the gb version of this lib is compatible with the ics firmware on cm10/aokp41.
And a nandroid is not going to help. If I need anything it will be copies of the firmware partitions. But let's see if this works first.
GB .so with ICS radio files
ICS .so with ICS radio files
I received a lock with both, but only the ICS to ICS was able to pinpoint me down to 100ft. Also, the GB .so spammed this message like crazy
E/libloc ( 1009): loc client mismatch: received = 1492585512, expected = 0
Code:
I/ActivityThread( 3043): Pub com.google.android.maps.NavigationAvailabilityProvider: com.google.googlenav.provider.NavigationAvailabilityProvider
D/Maps ( 3043): Build: 6140205
D/overlay ( 245): FROM_STATE = OV_CLOSED TO_STATE = OV_BYPASS_2_LAYER
V/NFC ( 3043): this device does not have NFC support
D/libloc ( 1009): loc_eng_set_position mode, client = 0, interval = 0, mode = 1
I/LocationManagerService( 1009): request gps (pid 3043) 0 0
D/RPC ( 1009): 3000008c:00050000 sending call (XID 10).
D/RPC ( 1009): 3000008c:00050000 received REPLY (XID 10), grabbing mutex to wake up client.
D/RPC ( 1009): 3000008c:00050000 waiting for XDR input buffer to be consumed.
D/RPC ( 1009): 3000008c:00050000 call success.
D/RPC ( 1009): 3000008c:00050000 received CALL.
D/RPC ( 1009): 3000008c:00050000 dispatching RPC call (XID 1201, xdr 0xa87558) for callback client 3100008c:00050001.
D/RPC ( 1009): 3100008c:327681 sending RPC reply (XID 1201)
D/RPC ( 1009): 3000008c:00050000 sending call (XID 11).
D/RPC ( 1009): 3000008c:00050000 received REPLY (XID 11), grabbing mutex to wake up client.
D/RPC ( 1009): 3000008c:00050000 call success.
E/libloc ( 1009): loc client mismatch: received = 1492585512, expected = 0ICS .so with ICS radio files
Code:
I/ActivityThread( 2834): Pub com.google.android.maps.NavigationAvailabilityProvider: com.google.googlenav.provider.NavigationAvailabilityProvider
D/Maps ( 2834): Build: 6140205
V/NFC ( 2834): this device does not have NFC support
E/LocSvc_eng( 524): I/===> int loc_eng_set_position_mode(loc_eng_data_s_type&, LocPosMode&) line 583
D/LocSvc_adapter( 524): loc_eng_set_position mode, client = 0, interval = 1000, mode = 1
E/LocSvc_api_rpc_glue( 524): I/---> loc_ioctl line 557 RPC_LOC_IOCTL_SET_FIX_CRITERIA
E/LocSvc_eng( 524): I/===> int loc_eng_start(loc_eng_data_s_type&) line 444
I/LocationManagerService( 524): request gps (pid 2834) 0 0
D/RPC ( 524): 3000008c:00050000 sending call (XID 38).
E/LocSvc_api_rpc_glue( 524): I/---> loc_start_fix line 432 loc start fix
E/LocSvc_adapter( 524): I/<--- int32 loc_event_cb(void*, rpc_loc_client_handle_type, rpc_loc_event_mask_type, const rpc_loc_event_payload_u_type*) line 70 RPC_LOC_EVENT_IOCTL_REPORT
D/RPC ( 524): 3000008c:00050000 received REPLY (XID 38), grabbing mutex to wake up client.
D/RPC ( 524): 3000008c:00050000 call success.
D/RPC ( 524): 3000008c:00050000 received CALL.
D/RPC ( 524): 3000008c:00050000 dispatching RPC call (XID 919, xdr 0x86e690) for callback client 3100008c:00050001.
D/RPC ( 524): 3000008c:00050000 sending call (XID 39).
D/RPC ( 524): 3100008c:327681 sending RPC reply (XID 919)
D/RPC ( 524): 3000008c:00050000 received REPLY (XID 39), grabbing mutex to wake up client.
D/RPC ( 524): 3000008c:00050000 call success.I received a lock with both, but only the ICS to ICS was able to pinpoint me down to 100ft. Also, the GB .so spammed this message like crazy
E/libloc ( 1009): loc client mismatch: received = 1492585512, expected = 0
scottfan81
Member
Just a heads up. I know I saw someone post about this somewhere, but if you both are running cm10 in the same house at the same time WiFi doesn't seem to work. Mine works fine when my gf isn't home. As soon as she does I have to use data only. It is wierd
tdm
Android Expert
Both Bluetooth and WiFi mac addrs should be fixed in rc4. If not please let me know so I can figure out why not.
tdm
Android Expert
I think libloc is part of the GPS blobs. I'll verify and spin a test Rom with the complete gb GPS file set. Hopefully that will get rid of the messages and maybe improve performance.
I tested on the way home this evening. Took quite some time to get a lock but it did eventually go, and had me down to like 20ft or something.
If we can get this working, next stop is official cm support.
