• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Motorola Triumph In Review

jmatherly411

jmatherly411

Android Enthusiast
Hello fellow Android users,

I have recently purchased the Motorola Triumph, but was very skeptical in purchasing as of reading some of the issues this phone was riddled with. I broke down and decided to purchase this phone as I use to have to the LG Optimus coming from Sprint (was tired of paying $80 a month) so coming off my contract decided to give Virgin Mobile a go as they are a Sprint accquired company. The only thing that dissapoints me at the moment is 2.2.2 on this device. I have stressed tested this phone to see if the bugs would start showing their ugly face, so far so good. Phone runs smooth and very snappy (Qualcomm MSM8255 chipset 1GHz Snapdragon "Scropion" CPU w/ Adreno 205 GPU) as some have said in other websites this is the same hardware that the HTC Thunderbolt uses. I don't see a blue tint to the screen as some people have encountered with there Triumph. GPS seems to lock on in about 10 seconds using Google Maps (I've tried this many times to see if it took longer than normal but got about the same results everytime). I've tried the video chat using the front facing VGA camera, it is low quality but you can see yourself just be sure to be in a lit room. As far as some complaining about the phone rebooting itself I have not encountered this problem as of yet and hope I don't. As far as benchmarks, Quadrant gave the phone a score of 1810 being on stock 2.2.2. I really love the large 4.1'' display makes texing a bit easier coming from a 3.2'' display. The phone has the look and feel of a Droid. The software version on this phone is 1010_2_039 and was manufactured on 12/11 <----says this on the phone and the battery lid has a date of Nov. 2011. I don't know if there was some manufacturing issues when this phone first came out and people that purchased the first few batches had the riddled problems. As any electronic device it seems these days it's always best to wait a few months before you purchase a device. That being said I hope Motorola does not sit and twiddle their thumbs as they need to update this phone to Gingerbread or ICS during Q1 or Q2. If not just tell the Triumph owners that there will not be a update, don't leave us hanging on a thread.
 
Sounds like you got a good one, or their manufacturing process has improved. If you want Gingerbread now, or even an alpha ICS ROM, go to the root section of the forum. It's pretty safe & hard to really brick the phone.
 
Thanks for the tip, I think ill hold out for a bit and see what Motorola does, if nothing is announced i'll be rooting for sure.
 
Glad you love the phone, I agree on the key points you have said, I had a LG Optimus V for a few months but upgraded for the 4.1" screen and the fastest processor in it's class. I love my Triumph and you will too. Welcome to AndroidForums as well. :D

PS: I gave the Optimus to my sister, still a great phone to start with. :o
 
BTW, do you ever notice any missed touches on the touchscreen? This seems like a very common problem, and I'm wondering if it's fixed in the latest Triumphs.
 
u may want to hold out for an official rom.

but no official rom will ever run as smooth as cyanogen. they just arent optimized the same. they are usually full of bloat and background processes that dont need to be there.

the stock rom is a good amount of bugs as well that keep it from running at full potential.

you are seriously missing out by sticking to the stock rom, but its your choice :D
 
I wouldn't have too much faith in VM/Motorola updating the Triumph. Once you install a new rom on there, you'll be asking yourself why you didn't do it sooner :)
 
I got the same results with my triumph! Mine is perfectly fine. No bugs. No glitches. But ....I am waiting for my fav rom to support hdmi so I can put it on there
 
Hmm, I'm wondering if the newer MT's are using updated binary GPS (& other) drivers if they're able to fix so quickly. And if so if we can pull them out of them and use it to build for other MT devices (CM7 & CM9).

(or maybe it's just better GPS hardware chips)

Anyone with the newer fast GPS fixing MT run linux & have adb installed?
 
Whyzor said:
Hmm, I'm wondering if the newer MT's are using updated binary GPS (& other) drivers if they're able to fix so quickly. And if so if we can pull them out of them and use it to build for other MT devices (CM7 & CM9).

(or maybe it's just better GPS hardware chips)

Anyone with the newer fast GPS fixing MT run linux & have adb installed?
Click to expand...


gps hardware? idk. isnt the gps processor built into the snapdragon cpu? thats why the S2 can now access glonass, its not a seperate chip on the mainboard that can be replaced at manufacture time. anything outside the cpu is just the antennas no?
 
Good point, forgot about that. Trying to figure out how the newer MT's can get fast GPS locks other than having newer binary drivers, maybe that's exactly it. Ok, if someone does have linux installed and has a newer MT on stock ROM (with fast GPS fixes & very few problems), can you install ADB & run this script to extract the binary drivers and 'tar' up the file and post it somewhere. The rest of the MT community may find this VERY helpful.

Code: 
#!/bin/sh

VENDOR=motorola
DEVICE=triumph

mkdir ~/android/device/motorola/triumph
cd ~/android/device/motorola/triumph
mkdir -p ../../../vendor/$VENDOR/$DEVICE/proprietary

# Radio binaries
adb pull /system/bin/qmuxd  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/hci_qcomm_init  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/hciattach  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/rmt_storage  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/netmgrd  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/wpdiagd  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/port-bridge  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/btwlancoex  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/rild  ../../../vendor/$VENDOR/$DEVICE/proprietary

# Sensor binaries
adb pull /system/bin/thermald  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/geomagneticd  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/orientationd  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/proximityd  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/lightd  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/hdmid  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/bluetoothd  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/cnd  ../../../vendor/$VENDOR/$DEVICE/proprietary

# MM
adb pull /system/bin/mm-abl-test  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/mm-adec-omxaac-test  ../../../vendor/$VENDOR/$DEVICE/propri
etary
adb pull /system/bin/mm-adec-omxadpcm-test  ../../../vendor/$VENDOR/$DEVICE/prop
rietary
adb pull /system/bin/mm-adec-omxamr-test  ../../../vendor/$VENDOR/$DEVICE/propri
etary
adb pull /system/bin/mm-adec-omxamrwb-test  ../../../vendor/$VENDOR/$DEVICE/prop
rietary
adb pull /system/bin/mm-adec-omxevrc-test  ../../../vendor/$VENDOR/$DEVICE/propr
ietary
adb pull /system/bin/mm-adec-omxmp3-test  ../../../vendor/$VENDOR/$DEVICE/propri
etary
adb pull /system/bin/mm-adec-omxQcelp13-test  ../../../vendor/$VENDOR/$DEVICE/pr
oprietary
adb pull /system/bin/mm-adec-omxwma-test  ../../../vendor/$VENDOR/$DEVICE/propri
etary
adb pull /system/bin/mm-adspsvc-test  ../../../vendor/$VENDOR/$DEVICE/proprietar
y
adb pull /system/bin/mm-aenc-omxaac-test  ../../../vendor/$VENDOR/$DEVICE/propri
etary
adb pull /system/bin/mm-aenc-omxamr-test  ../../../vendor/$VENDOR/$DEVICE/propri
etary
adb pull /system/bin/mm-aenc-omxevrc-test  ../../../vendor/$VENDOR/$DEVICE/propr
ietary
adb pull /system/bin/mm-aenc-omxqcelp13-test  ../../../vendor/$VENDOR/$DEVICE/pr
oprietary
adb pull /system/bin/mm-audio-alsa-test  ../../../vendor/$VENDOR/$DEVICE/proprie
tary
adb pull /system/bin/mm-audio-ctrl-test  ../../../vendor/$VENDOR/$DEVICE/proprie
tary
adb pull /system/bin/mm-audio-mvs-test-int  ../../../vendor/$VENDOR/$DEVICE/prop
rietary
adb pull /system/bin/mm-audio-mvs-test-ext  ../../../vendor/$VENDOR/$DEVICE/prop
rietary
adb pull /system/bin/mm-audio-native-test  ../../../vendor/$VENDOR/$DEVICE/propr
ietary
adb pull /system/bin/mm-audio-voem_if-test  ../../../vendor/$VENDOR/$DEVICE/prop
rietary
adb pull /system/bin/mm-jpeg-dec-test  ../../../vendor/$VENDOR/$DEVICE/proprieta
ry
adb pull /system/bin/mm-jpeg-enc-test  ../../../vendor/$VENDOR/$DEVICE/proprieta
ry
adb pull /system/bin/mm-omx-devmgr  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/mm-qcamera-test  ../../../vendor/$VENDOR/$DEVICE/proprietar
y
adb pull /system/bin/mm-qcamera-testsuite-client  ../../../vendor/$VENDOR/$DEVIC
E/proprietary
adb pull /system/bin/mm-vdec-omx-test  ../../../vendor/$VENDOR/$DEVICE/proprieta
ry
adb pull /system/bin/mm-venc-omx-test  ../../../vendor/$VENDOR/$DEVICE/proprieta
ry
adb pull /system/bin/mm-venc-omx-test720p  ../../../vendor/$VENDOR/$DEVICE/propr
ietary
adb pull /system/bin/mm-video-driver-test  ../../../vendor/$VENDOR/$DEVICE/propr
ietary
adb pull /system/bin/mm-video-encdrv-test  ../../../vendor/$VENDOR/$DEVICE/propr
ietary

# Camera
adb pull /system/lib/libcamera.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/liboemcamera.so  ../../../vendor/$VENDOR/$DEVICE/proprietar
y
adb pull /system/lib/libmmjpeg.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libmmipl.so  ../../../vendor/$VENDOR/$DEVICE/proprietary

# Audio
adb pull /system/lib/libaudio.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libaudioalsa.so  ../../../vendor/$VENDOR/$DEVICE/proprietar
y
adb pull /system/lib/liba2dp.so  ../../../vendor/$VENDOR/$DEVICE/proprietary

# EGL
#adb pull /system/lib/egl/libEGL_adreno200.so  ../../../vendor/$VENDOR/$DEVICE/p
roprietary
#adb pull /system/lib/egl/libGLESv1_CM_adreno200.so  ../../../vendor/$VENDOR/$DE
VICE/proprietary
#adb pull /system/lib/egl/libGLESv2_adreno200.so  ../../../vendor/$VENDOR/$DEVIC
E/proprietary
#adb pull /system/lib/egl/libq3dtools_adreno200.so  ../../../vendor/$VENDOR/$DEV
ICE/proprietary
#adb pull /system/lib/libgsl.so  ../../../vendor/$VENDOR/$DEVICE/proprietary

# Sensors
#adb pull /system/lib/hw/sensors.triumph.so  ../../../vendor/$VENDOR/$DEVICE/pro
prietary

# OMX
adb pull /system/lib/libOmxEvrcEnc.so  ../../../vendor/$VENDOR/$DEVICE/proprieta
ry
adb pull /system/lib/libOmxAacDec.so  ../../../vendor/$VENDOR/$DEVICE/proprietar
y
adb pull /system/lib/libOmxQcelp13Dec.so  ../../../vendor/$VENDOR/$DEVICE/propri
etary
adb pull /system/lib/libOmxAmrEnc.so  ../../../vendor/$VENDOR/$DEVICE/proprietar
y
adb pull /system/lib/libOmxAdpcmDec.so  ../../../vendor/$VENDOR/$DEVICE/propriet
ary
adb pull /system/lib/libOmxEvrcDec.so  ../../../vendor/$VENDOR/$DEVICE/proprieta
ry
adb pull /system/lib/libOmxAmrDec.so  ../../../vendor/$VENDOR/$DEVICE/proprietar
y
adb pull /system/lib/libOmxAmrwbDec.so  ../../../vendor/$VENDOR/$DEVICE/propriet
ary
adb pull /system/lib/libOmxWmaDec.so  ../../../vendor/$VENDOR/$DEVICE/proprietar
y
adb pull /system/lib/libOmxQcelp13Enc.so  ../../../vendor/$VENDOR/$DEVICE/propri
etary
adb pull /system/lib/libOmxMp3Dec.so  ../../../vendor/$VENDOR/$DEVICE/proprietar
y
adb pull /system/lib/libOmxAmrRtpDec.so  ../../../vendor/$VENDOR/$DEVICE/proprie
tary
adb pull /system/lib/libOmxAacEnc.so  ../../../vendor/$VENDOR/$DEVICE/proprietar
y
adb pull /system/lib/libmm-adspsvc.so  ../../../vendor/$VENDOR/$DEVICE/proprieta
ry
adb pull /system/lib/libomx_aacdec_sharedlibrary.so  ../../../vendor/$VENDOR/$DE
VICE/proprietary
adb pull /system/lib/libomx_amrdec_sharedlibrary.so  ../../../vendor/$VENDOR/$DE
VICE/proprietary
adb pull /system/lib/libomx_amrenc_sharedlibrary.so  ../../../vendor/$VENDOR/$DE
VICE/proprietary
adb pull /system/lib/libomx_avcdec_sharedlibrary.so  ../../../vendor/$VENDOR/$DE
VICE/proprietary
adb pull /system/lib/libomx_m4vdec_sharedlibrary.so  ../../../vendor/$VENDOR/$DE
VICE/proprietary
adb pull /system/lib/libomx_mp3dec_sharedlibrary.so  ../../../vendor/$VENDOR/$DE
VICE/proprietary
adb pull /system/lib/libomx_sharedlibrary.so  ../../../vendor/$VENDOR/$DEVICE/pr
oprietary
adb pull /system/lib/libOmxCore.so  ../../../vendor/$VENDOR/$DEVICE/proprietary

# RIL
adb pull /system/lib/libril.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libril-qc-1.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libreference-ril.so  ../../../vendor/$VENDOR/$DEVICE/propri
etary
adb pull /system/lib/libril-qcril-hook-oem.so  ../../../vendor/$VENDOR/$DEVICE/p
roprietary
adb pull /system/lib/libril-qc-1.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libril-qc-qmi-1.so  ../../../vendor/$VENDOR/$DEVICE/proprie
tary
adb pull /system/lib/libdiag.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/liboncrpc.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libqmi.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libqmiservices.so  ../../../vendor/$VENDOR/$DEVICE/propriet
ary
adb pull /system/lib/libdsm.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libqueue.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libdll.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libcm.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libmmgsdilib.so  ../../../vendor/$VENDOR/$DEVICE/proprietar
y
adb pull /system/lib/libgsdi_exp.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libgstk_exp.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libwms.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libnv.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libwmsts.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libpbmlib.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libdss.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libauth.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libqdp.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libidl.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libdsutils.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/liboem_rapi.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libdsi_netctrl.so  ../../../vendor/$VENDOR/$DEVICE/propriet
ary
adb pull /system/lib/libnetmgr.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/liboncrpc.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libpdapi.so ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libpdsm_atl.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libuim.so  ../../../vendor/$VENDOR/$DEVICE/proprietary

adb pull /system/lib/libgemini.so  ../../../vendor/$VENDOR/$DEVICE/proprietary

# GPS
adb pull /system/lib/libcommondefs.so  ../../../vendor/$VENDOR/$DEVICE/proprieta
ry

(cat << EOF) | sed s/__DEVICE__/$DEVICE/g | sed s/__VENDOR__/$VENDOR/g > ../../.
./vendor/$VENDOR/$DEVICE/$DEVICE-vendor-blobs.mk
There may be another simpler way if we can get a rom dump, basically need those /system/bin and /system/lib binary files.

EDIT: On second thought, they probably wouldn't update the drivers without also making some other updates too to the kernel & have the revision number changed. It's probably just because of better or properly connected GPS antennas.
 
I got mine in December, and it got gps lock fairly quick. I'm using your rom, the late January one, and it still locks quick.
 
Whyzor said:
There may be another simpler way if we can get a rom dump, basically need those /system/bin and /system/lib binary files.

EDIT: On second thought, they probably wouldn't update the drivers without also making some other updates too to the kernel & have the revision number changed. It's probably just because of better or properly connected GPS antennas.
Click to expand...

stock phone, factory reset. replace recovery with cwm. nandroid complete bone stock rom, upload it, then flash custom rom?

that'd be easy for anyone to do with any computer, and you get their stock rom

would that work or am is it just wishful thinking
 
Whyzor said:
Good point, forgot about that. Trying to figure out how the newer MT's can get fast GPS locks other than having newer binary drivers, maybe that's exactly it. Ok, if someone does have linux installed and has a newer MT on stock ROM (with fast GPS fixes & very few problems), can you install ADB & run this script to extract the binary drivers and 'tar' up the file and post it somewhere. The rest of the MT community may find this VERY helpful.

Code: 
#!/bin/sh

VENDOR=motorola
DEVICE=triumph

mkdir ~/android/device/motorola/triumph
cd ~/android/device/motorola/triumph
mkdir -p ../../../vendor/$VENDOR/$DEVICE/proprietary

# Radio binaries
adb pull /system/bin/qmuxd  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/hci_qcomm_init  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/hciattach  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/rmt_storage  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/netmgrd  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/wpdiagd  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/port-bridge  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/btwlancoex  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/rild  ../../../vendor/$VENDOR/$DEVICE/proprietary

# Sensor binaries
adb pull /system/bin/thermald  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/geomagneticd  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/orientationd  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/proximityd  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/lightd  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/hdmid  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/bluetoothd  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/cnd  ../../../vendor/$VENDOR/$DEVICE/proprietary

# MM
adb pull /system/bin/mm-abl-test  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/mm-adec-omxaac-test  ../../../vendor/$VENDOR/$DEVICE/propri
etary
adb pull /system/bin/mm-adec-omxadpcm-test  ../../../vendor/$VENDOR/$DEVICE/prop
rietary
adb pull /system/bin/mm-adec-omxamr-test  ../../../vendor/$VENDOR/$DEVICE/propri
etary
adb pull /system/bin/mm-adec-omxamrwb-test  ../../../vendor/$VENDOR/$DEVICE/prop
rietary
adb pull /system/bin/mm-adec-omxevrc-test  ../../../vendor/$VENDOR/$DEVICE/propr
ietary
adb pull /system/bin/mm-adec-omxmp3-test  ../../../vendor/$VENDOR/$DEVICE/propri
etary
adb pull /system/bin/mm-adec-omxQcelp13-test  ../../../vendor/$VENDOR/$DEVICE/pr
oprietary
adb pull /system/bin/mm-adec-omxwma-test  ../../../vendor/$VENDOR/$DEVICE/propri
etary
adb pull /system/bin/mm-adspsvc-test  ../../../vendor/$VENDOR/$DEVICE/proprietar
y
adb pull /system/bin/mm-aenc-omxaac-test  ../../../vendor/$VENDOR/$DEVICE/propri
etary
adb pull /system/bin/mm-aenc-omxamr-test  ../../../vendor/$VENDOR/$DEVICE/propri
etary
adb pull /system/bin/mm-aenc-omxevrc-test  ../../../vendor/$VENDOR/$DEVICE/propr
ietary
adb pull /system/bin/mm-aenc-omxqcelp13-test  ../../../vendor/$VENDOR/$DEVICE/pr
oprietary
adb pull /system/bin/mm-audio-alsa-test  ../../../vendor/$VENDOR/$DEVICE/proprie
tary
adb pull /system/bin/mm-audio-ctrl-test  ../../../vendor/$VENDOR/$DEVICE/proprie
tary
adb pull /system/bin/mm-audio-mvs-test-int  ../../../vendor/$VENDOR/$DEVICE/prop
rietary
adb pull /system/bin/mm-audio-mvs-test-ext  ../../../vendor/$VENDOR/$DEVICE/prop
rietary
adb pull /system/bin/mm-audio-native-test  ../../../vendor/$VENDOR/$DEVICE/propr
ietary
adb pull /system/bin/mm-audio-voem_if-test  ../../../vendor/$VENDOR/$DEVICE/prop
rietary
adb pull /system/bin/mm-jpeg-dec-test  ../../../vendor/$VENDOR/$DEVICE/proprieta
ry
adb pull /system/bin/mm-jpeg-enc-test  ../../../vendor/$VENDOR/$DEVICE/proprieta
ry
adb pull /system/bin/mm-omx-devmgr  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/bin/mm-qcamera-test  ../../../vendor/$VENDOR/$DEVICE/proprietar
y
adb pull /system/bin/mm-qcamera-testsuite-client  ../../../vendor/$VENDOR/$DEVIC
E/proprietary
adb pull /system/bin/mm-vdec-omx-test  ../../../vendor/$VENDOR/$DEVICE/proprieta
ry
adb pull /system/bin/mm-venc-omx-test  ../../../vendor/$VENDOR/$DEVICE/proprieta
ry
adb pull /system/bin/mm-venc-omx-test720p  ../../../vendor/$VENDOR/$DEVICE/propr
ietary
adb pull /system/bin/mm-video-driver-test  ../../../vendor/$VENDOR/$DEVICE/propr
ietary
adb pull /system/bin/mm-video-encdrv-test  ../../../vendor/$VENDOR/$DEVICE/propr
ietary

# Camera
adb pull /system/lib/libcamera.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/liboemcamera.so  ../../../vendor/$VENDOR/$DEVICE/proprietar
y
adb pull /system/lib/libmmjpeg.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libmmipl.so  ../../../vendor/$VENDOR/$DEVICE/proprietary

# Audio
adb pull /system/lib/libaudio.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libaudioalsa.so  ../../../vendor/$VENDOR/$DEVICE/proprietar
y
adb pull /system/lib/liba2dp.so  ../../../vendor/$VENDOR/$DEVICE/proprietary

# EGL
#adb pull /system/lib/egl/libEGL_adreno200.so  ../../../vendor/$VENDOR/$DEVICE/p
roprietary
#adb pull /system/lib/egl/libGLESv1_CM_adreno200.so  ../../../vendor/$VENDOR/$DE
VICE/proprietary
#adb pull /system/lib/egl/libGLESv2_adreno200.so  ../../../vendor/$VENDOR/$DEVIC
E/proprietary
#adb pull /system/lib/egl/libq3dtools_adreno200.so  ../../../vendor/$VENDOR/$DEV
ICE/proprietary
#adb pull /system/lib/libgsl.so  ../../../vendor/$VENDOR/$DEVICE/proprietary

# Sensors
#adb pull /system/lib/hw/sensors.triumph.so  ../../../vendor/$VENDOR/$DEVICE/pro
prietary

# OMX
adb pull /system/lib/libOmxEvrcEnc.so  ../../../vendor/$VENDOR/$DEVICE/proprieta
ry
adb pull /system/lib/libOmxAacDec.so  ../../../vendor/$VENDOR/$DEVICE/proprietar
y
adb pull /system/lib/libOmxQcelp13Dec.so  ../../../vendor/$VENDOR/$DEVICE/propri
etary
adb pull /system/lib/libOmxAmrEnc.so  ../../../vendor/$VENDOR/$DEVICE/proprietar
y
adb pull /system/lib/libOmxAdpcmDec.so  ../../../vendor/$VENDOR/$DEVICE/propriet
ary
adb pull /system/lib/libOmxEvrcDec.so  ../../../vendor/$VENDOR/$DEVICE/proprieta
ry
adb pull /system/lib/libOmxAmrDec.so  ../../../vendor/$VENDOR/$DEVICE/proprietar
y
adb pull /system/lib/libOmxAmrwbDec.so  ../../../vendor/$VENDOR/$DEVICE/propriet
ary
adb pull /system/lib/libOmxWmaDec.so  ../../../vendor/$VENDOR/$DEVICE/proprietar
y
adb pull /system/lib/libOmxQcelp13Enc.so  ../../../vendor/$VENDOR/$DEVICE/propri
etary
adb pull /system/lib/libOmxMp3Dec.so  ../../../vendor/$VENDOR/$DEVICE/proprietar
y
adb pull /system/lib/libOmxAmrRtpDec.so  ../../../vendor/$VENDOR/$DEVICE/proprie
tary
adb pull /system/lib/libOmxAacEnc.so  ../../../vendor/$VENDOR/$DEVICE/proprietar
y
adb pull /system/lib/libmm-adspsvc.so  ../../../vendor/$VENDOR/$DEVICE/proprieta
ry
adb pull /system/lib/libomx_aacdec_sharedlibrary.so  ../../../vendor/$VENDOR/$DE
VICE/proprietary
adb pull /system/lib/libomx_amrdec_sharedlibrary.so  ../../../vendor/$VENDOR/$DE
VICE/proprietary
adb pull /system/lib/libomx_amrenc_sharedlibrary.so  ../../../vendor/$VENDOR/$DE
VICE/proprietary
adb pull /system/lib/libomx_avcdec_sharedlibrary.so  ../../../vendor/$VENDOR/$DE
VICE/proprietary
adb pull /system/lib/libomx_m4vdec_sharedlibrary.so  ../../../vendor/$VENDOR/$DE
VICE/proprietary
adb pull /system/lib/libomx_mp3dec_sharedlibrary.so  ../../../vendor/$VENDOR/$DE
VICE/proprietary
adb pull /system/lib/libomx_sharedlibrary.so  ../../../vendor/$VENDOR/$DEVICE/pr
oprietary
adb pull /system/lib/libOmxCore.so  ../../../vendor/$VENDOR/$DEVICE/proprietary

# RIL
adb pull /system/lib/libril.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libril-qc-1.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libreference-ril.so  ../../../vendor/$VENDOR/$DEVICE/propri
etary
adb pull /system/lib/libril-qcril-hook-oem.so  ../../../vendor/$VENDOR/$DEVICE/p
roprietary
adb pull /system/lib/libril-qc-1.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libril-qc-qmi-1.so  ../../../vendor/$VENDOR/$DEVICE/proprie
tary
adb pull /system/lib/libdiag.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/liboncrpc.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libqmi.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libqmiservices.so  ../../../vendor/$VENDOR/$DEVICE/propriet
ary
adb pull /system/lib/libdsm.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libqueue.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libdll.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libcm.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libmmgsdilib.so  ../../../vendor/$VENDOR/$DEVICE/proprietar
y
adb pull /system/lib/libgsdi_exp.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libgstk_exp.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libwms.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libnv.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libwmsts.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libpbmlib.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libdss.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libauth.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libqdp.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libidl.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libdsutils.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/liboem_rapi.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libdsi_netctrl.so  ../../../vendor/$VENDOR/$DEVICE/propriet
ary
adb pull /system/lib/libnetmgr.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/liboncrpc.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libpdapi.so ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libpdsm_atl.so  ../../../vendor/$VENDOR/$DEVICE/proprietary
adb pull /system/lib/libuim.so  ../../../vendor/$VENDOR/$DEVICE/proprietary

adb pull /system/lib/libgemini.so  ../../../vendor/$VENDOR/$DEVICE/proprietary

# GPS
adb pull /system/lib/libcommondefs.so  ../../../vendor/$VENDOR/$DEVICE/proprieta
ry

(cat << EOF) | sed s/__DEVICE__/$DEVICE/g | sed s/__VENDOR__/$VENDOR/g > ../../.
./vendor/$VENDOR/$DEVICE/$DEVICE-vendor-blobs.mk
There may be another simpler way if we can get a rom dump, basically need those /system/bin and /system/lib binary files.

EDIT: On second thought, they probably wouldn't update the drivers without also making some other updates too to the kernel & have the revision number changed. It's probably just because of better or properly connected GPS antennas.
Click to expand...

I've got linux and ADB. I'm getting a triumph hopefully within the week, if not the next ten days. I know it's a wait, but I'll get right on this before I flash a new ROM.
 
I would have to say VM is never going to update to 2.3. I would bet they would introduce another 2.2 after ICS really starts going mainstream. I really don't think VM cares about their customers, that being said I'm still with them...
 
rcarter10 said:
I got mine in December, and it got gps lock fairly quick. I'm using your rom, the late January one, and it still locks quick.
Click to expand...

It'd be interesting if someone does grab the stock binaries from a newer phone BEFORE they flash another rom, but I doubt it would improve things for others as this case demonstrates. The software doesn't matter, fast GPS lock on stock and custom ROM on the same phone, so it must be hardware related.
 
Whyzor said:
BTW, do you ever notice any missed touches on the touchscreen? This seems like a very common problem, and I'm wondering if it's fixed in the latest Triumphs.
Click to expand...

I haven't noticed any missed touches on the touchscreen. Its very snappy as soon I touch an app it loads almost instantly. I can barely touch the letters texting and it types them. The phone itself feels very solid, on another note I have read some users having the light bleed through the bottom left corner where the gorilla glass meets the phone itself, this the rubber meets the glass where the touch buttons are located resulting in light not bleeding through. Its possible that engineering did some tweeking. 3G also seems to hold very solid about 900kbps download 600kbps download (4PM test) but this also depends on where you live. Wireless never looses connection and links right up with my wireless N netgear gigabit router. :D
 
Whyzor said:
It'd be interesting if someone does grab the stock binaries from a newer phone BEFORE they flash another rom, but I doubt it would improve things for others as this case demonstrates. The software doesn't matter, fast GPS lock on stock and custom ROM on the same phone, so it must be hardware related.
Click to expand...

Looks like I'll be getting my Triumph today, so even if they won't improve things, I'll still grab those. Gives me something to do since I don't work today.

Edit: My ride out of town fell through, so I'll be getting it tomorrow. I'll report back, then.
 
shmackshmack said:
u may want to hold out for an official rom.

but no official rom will ever run as smooth as cyanogen. they just arent optimized the same. they are usually full of bloat and background processes that dont need to be there.

the stock rom is a good amount of bugs as well that keep it from running at full potential.

you are seriously missing out by sticking to the stock rom, but its your choice :D
Click to expand...

I juSt yesterday I went from stock to MIUI and ohh boy is it a ridiculous change... woooooooow dont waste your time waiting like i did !!
do it
ASAP
:)
 
You must log in or register to reply here.
Back
Top Bottom