Related
So with a few hours of Googling and some searching, me and a few others on IRC have found a mysterious D3 2.3.4 SBF. Of the time of writing, we're still downloading as the download is incredibly slow. Hopefully some of the people that are in the IRC will post mirrors on this thread as soon as they can get it uploaded.
http://www.diypda.com/zftp.action.p...763241688&md=71caf39d4e9a98681331bd16f2caa3f2
Download it at the very bottom of the thread. Mirrors will be up shortly. IRC people, please post mirrors if you have any.
MIRROR!!
Thanks to rigwig, we now have a mirror. Please thank him
http://www.multiupload.com/HKMICRBC6J
IMPORTANT!!:
DO NOT BY ANY MEANS FLASH THIS. THIS IS SIGNED WITH TEST KEYS, NOT RETAIL. FLASHING THIS WILL GUARENTEE A BRICK
here's your final warning message.
[13:25] whaatt: can we use rsdlite to flash this sbf?
[13:25] Adam: DO NOT FLASH THIS
[13:25] Adam: stop thinking about it
[13:25] Adam: stop thinking about thinking about it
[13:25] whaatt: lol
[13:25] whaatt: then what to do with it?
[13:25] royolpunk: DONT FLASH IT
downloading now. I'll have mirror up in a few mins
Edit:
Here is the Multiupload mirror
http://www.multiupload.com/HKMICRBC6J
*prays its real*
Time for some epic rooting methods!
This is as real as it gets. DOWNLOAD SPEED WILL BE 50KBps MAX.
Edit:
So we've got a few people on the IRC downloading away, one is at 50%. it'll take about another hour before we get everything cleared up. I'll try to update this thread ASAP.
p3 has also just joined us on IRC. we're doing our best
Any thoughts on this giving us root?
Sent from my DROID3 using XDA App
saintlikesniper said:
Any thoughts on this giving us root?
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
We're hoping to find vulnerabilities and holes in this Chinese SBF file, and see what we can do from there in terms of getting root.
we're hoping that this is a complete image of the phone (which it should be, considering it's at 222MB. we're going to go through the SBF step by step and look for more exploits that we can use to root this phone.
edit:
whaatt you ninja'd me -____-
This is /system/build.prop:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=5.5.1-1_GC-35
ro.build.display.id=cdma_solana-userdebug 2.3.4 5.5.1-1_GC-35 5.5.1-1_GC-35 test-keys
ro.build.version.incremental=5.5.1-1_GC-35
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.4
ro.build.date=Thu Jun 9 04:21:36 CDT 2011
ro.build.date.utc=1307611296
ro.build.type=userdebug
ro.build.user=hudsoncm
ro.build.host=il93lnxdroid48
ro.build.tags=test-keys
ro.product.model=XT883
ro.product.brand=moto
ro.product.name=SLNCT
ro.product.device=cdma_solana
ro.product.board=solana
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=motorola
ro.product.locale.language=zh
ro.product.locale.region=CN
ro.wifi.channels=
ro.board.platform=omap4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=solana
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=cdma_solana-userdebug 2.3.4 5.5.1-1_GC-35 5.5.1-1_GC-35 test-keys
ro.build.fingerprint=moto/SLNCT/cdma_solana:2.3.4/5.5.1-1_GC-35/5.5.1-1_GC-35:userdebug/test-keys
# end build properties
#
# system.prop for CDMA Droidwe
#
# rild.libpath=/system/lib/libril-moto-umts-1.so
rild.libpath=/system/lib/libmoto_ril.so
rild.libargs=-d /dev/ttyO0
ro.sf.lcd_density=240
ro.default_usb_mode=2
ro.mot.ril.danlist=611,*611,#611
persist.ril.ecclist=911,*911,#911,119,118,999,08,000,112,110
persist.ril.modem.mode =1
# This defines the max event window manager can
# handle in 1 s. We may adjust this # for performance
# reason later
windowsmgr.max_events_per_sec=55
# USB modes allowed for UI and switching
ro.ngp_available=1
ro.modem_available=0
# Default network type.
# 7 => GLOBAL.
ro.telephony.default_network=7
ro.com.google.clientid=android-motorola
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.cdma.home.operator.numeric=46003
ro.cdma.home.operator.alpha=CT
ro.config.vc_call_vol_steps=7
ro.cdma.subscription=0
# wlan interface
wifi.interface = tiwlan0
softap.interface = tiap0
# Time between scans in seconds. Keep it high to minimize battery drain.
# This only affects the case in which there are remembered access points,
# but none are in range.
wifi.supplicant_scan_interval = 45
# Indicate carrier OTA SP number schema
# refer to frameworks/base/telephony/java/com/android/
# internal/telephony/cdma/CDMAPhone.java for the schema:
ro.cdma.otaspnumschema=SELC,1,80,99
# The OpenGL ES API level that is natively supported by this device.
# This is a 16.16 fixed point number
ro.opengles.version = 131072
# This is a high density device with more memory, so larger vm heaps for it.
dalvik.vm.heapsize=32m
# our HTML browser (not WAP browser ) does not need to specify UAProf URL
ro.mot.hw.uaprof=http://uaprof.vtext.com/mot/xt862/xt862.xml
# Enable HAC to also display Call Setting Menu Option.
ro.mot.hw.HAC=1
# Motorola, a19622, 12/28/2009, IKSHADOW-204 / Location Settings for android
# Property to set enabling state of the location privacy setting feature.
# Motorola, a19622, 03/16/2010, IKSHADOW-2141 / Disable feature 33067
#ro.mot.settings.locprivacy=1
# ERI feature
# 0 OFF
# 1 ON
ro.mot.eri=0
# Motorol,a6889c,02/Feb/2010,IKSHADOW-619
# Proximity Sensor feature
# 0 disable
# 1 enable
persist.mot.proximity.touch=1
# End IKSHADOW-619
# BEGIN Motorola, a22976, 25-Feb-2010, IKSHADOW-702, FID 31841
# VZW Requirement Specifications: NETWORK BASED PLUS CODE DIALING
# 0 disable
# 1 enable
ro.cdma.nbpcd=0
# END IKSHADOW-702
# BEGIN Motorola, a22976, 12-Mar-2010, IKSHADOW-1784, Power Up Tone
# Motorola, a22976, 12-Apr-2010, IKSHADOW-3298, Remove temporary power up tone
# persist.mot.powerup.tone=/system/media/bootup.ogg
# END IKSHADOW-1784
persist.mot.usb.mediasync = 1
# persist.usb.android_config = 1
# System property for SMC
ro.service.start.smc=1
ro.HorizontalBUA=true
#Proximity sensor debounce time
mot.proximity.delay=450
# disable touch below 60 pixels
mot.proximity.distance=60
#inphone calibration backup support
ro.mot.hw.calibratedImager=1
# BEGIN Motorola, qpmc46, 05-Jul-2010, IKMAIN-311
persist.ril.mux.noofchannels = 8
# END Motorola, qpmc46, 05-Jul-2010, IKMAIN-311
#BEGIN Motorola, nfjb73, 21-jun-2010,
# this is for feature 34386, other features for vzw global phone
# could use this property too. IKMAIN-732
#1 this is verizon wireless globle phone
#0 this is not verizon wireless globle phone
ro.mot.phonemode.vzwglobalphone=1
# END Motorola, nfjb73, 21-jun-2010, IKMAIN-732
#ro.mot.phonemode.numsignalbars=4
# BEGIN Motorola, nfjb73 23-jun-2010, IKMAIN-624
# this is for feature 33860, when phone is activated, the cdma mdn is written.
persist.radio.vzw.cdma.mdn=
# END Motorola, nfjb73
# BEGIN Motorola, qmfd78, 14-Jul-2010, IKMAIN-884
# GSM SMS traffic needs to be routed/sent through North America SMSC.
# This is part of the VZW World-phone Feature. SMS are always sent to a US SMSC and then injected
# into that network. This allows for billing and give the user the impression that the device is
# still in the US.
# ro.telephony.gsm-routes-us-smsc = 1
# END Motorola, qmfd78, 14-Jul-2010, IKMAIN-884
# BEGIN Motorola, a22600 qmfd78, 16-Jul-2010, IKDROIDPRO-423
# For north american cdma operators, this flag should be 1.
# It enables number mangling when nbpcd (plus code dialing) is not supported.
# This is part of the VZW World-phone Feature.
#ro.cdma.home.operator.isnan=1
# END Motorola, a22600 qmfd78, 16-Jul-2010, IKDROIDPRO-423
# EDM feature - IKDROIDPRO-381 - Start
ro.mot.dpmext = true
# EDM feature - IKDROIDPRO-381 -End
# BEGIN Moto,IKDROIDPRO-430, a17673
# Feature33857 on DroidWE, support DualMode switch, UMTS/CDMA
ro.mot.FTR.33857=true
# END IKDROIDPRO-430
# BEGIN Moto, IKSTABLETWO-1284, nfjb73
# without this property, the lock screen would take global phone as UMTS
# block user to operate before setup
keyguard.no_require_sim = true
# End Moto
# BEGIN Moto, IKSTABLETWO-689, nfjb73, for 34387,33857
# when phone in Global mode, FW need to know the last phone mode beore power off
# when phone power up, it would use the right mode to avoid switch
persist.radio.ap.phonetype=2
# END IKSTABLETWO-689
# Motorola, IKHALFMWK-3, w001091
# Feature 32711, deep sleep mode support
ro.mot.deep.sleep.supported=true
# BEGIN Moto, IKMAIN-14097, gdr487, 33531 flex on for Solana
# true feature enabled
# false feature disabled
ro.mot.fid.33531.keylock_ecm=true
# END IKMAIN-14097
# BEGIN Motorola, A24124, 01-Mar-2011, IKMAIN-13570
ro.mot.bindervm.config = 210
# END IKMAIN-13570
#BEGIN Motorola, w30471, 16-Mar-2011, IKSTABLEFIVE-1796 35691 - Set configurable parameters for Verizon products
mot.mms.con.timeout = 30000
mot.mms.socket.timeout = 120000
mot.mms.tr.vc.timeout = 55000
mot.mms.trm.timeout = 240000
mot.mms.abort.prog.lim = 90
mot.mms.retry.pic.size = 512000
mot.mms.retry.default = false
mot.mms.retry.timeout.1 = 300000
mot.mms.retry.timeout.2 = 300000
mot.mms.retry.timeout.3 = 300000
mot.mms.retry.timeout.4 = 0
# END IKSTABLEFIVE-1796
#BEGIN Motorola, w36256, 6-Apr-2011, IKSTABLEFOURV-6808
# add latin encoding type for sms in cdma mode, this is only for vzw
ro.cdma.sms.latin_encode=true
#END IKSTABLEFOURV-6808
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.kernel.android.ril=yes
persist.ril.baudrate=230400
persist.ril.mux.noofchannels=8
persist.ril.mux.ttydevice=/dev/ttyO0
persist.ril.modem.ttydevice=/dev/ttySPI0
persist.ril.features=0x30E
persist.ril.mux.retries=500
persist.ril.mux.sleep=2
persist.mot.mdm_panicd.nopanic=no
ro.config.ringtone=DROID3.ogg
ro.config.notification_sound=pizzicato.ogg
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.default_usb_mode=0
ro.media.enc.aud.fileformat=qcp
ro.media.enc.aud.codec=qcelp
ro.media.enc.aud.bps=13300
ro.media.enc.aud.ch=1
ro.media.enc.aud.hz=8000
ro.telephony.call_ring.multiple=false
ro.telephony.call_ring.delay=3000
ro.setupwizard.enable_bypass=1
ro.cdma.homesystem=64,65,76,77,78,79,80,81,82,83
ro.cdma.data_retry_config=default_randomization=2000,0,0,120000,180000,540000,960000
ro.media.camcorder.1080p=mp4,h264,30,15000000,aac,128000,44100,2
ro.media.camcorder.720p=mp4,h264,30,10000000,aac,128000,44100,2
ro.media.camcorder.d1NTSC=mp4,h264,30,6000000,aac,128000,44100,2
ro.media.camcorder.vga=mp4,h264,30,4000000,aac,128000,44100,2
ro.media.camcorder.cif=mp4,h264,30,1500000,aac,128000,44100,2
ro.media.camcorder.qvga=mp4,h264,15,500000,aac,64000,44100,2
ro.media.camcorder.mms=3gp,h264,15,128000,amrnb,12200,8000,1
ro.media.camcorder.mmsres=qvga
ro.camcorder.zoom=true
ro.media.capture.maxres=8m
ro.media.capture.fast.fps=4
ro.media.capture.slow.fps=120
ro.media.capture.flash=led
ro.media.capture.flashMinV=3300000
ro.media.capture.torchIntensity=40
ro.media.capture.flashIntensity=70
ro.media.panorama.defres=3264x1840
ro.media.panorama.frameres=1280x720
ro.camera.dynamicFocus=true
ro.camcorder.videoModes=false
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=false
media.stagefright.enable-http=true
media.stagefright.enable-record=false
ro.media.camera.focal=3451.0,3451.0
ro.media.camera.principal=1632.0,1224.0
ro.media.camera.skew=0.0
ro.media.camera.distortion=0.0,0.0,0.0,0.0,0.0
ro.media.camera.calresolution=3264,2448
ro.mot.setuptype=2
ro.horizontalBUA=true
ro.horizontalVVM=true
ro.horizontalIM=true
ro.horizontalNGM=false
ro.horizontalVMM=false
ro.horizontalMOD=false
ro.horizontalVOD=false
ro.horizontalEmail=false
ro.mot.internalsdcard=1
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.mot.dpmext=true
ro.com.google.clientid=android-motorola
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.mot.hw.uaprof=http://uaprof.motorola.com/phoneconfig/MotoMB200/profile/MotoMB200.rdf
debug.mot.hprofdump=1
ro.build.version.full=Blur_Version.55.11.35.XT883.ChinaTelecom.en.CN
ro.mot.hidden_keyboards=evfwd
This is a listing of all the files in /system: http://pastebin.com/XGXbDSNR
So if this becomes flashable and can we not inject busybox superuser and other stuff to gain root into the sbf
Sent from my DROID3 using XDA App
Yeah
Sent from my DROID3 using XDA Premium App
Man, this is exciting!! I hope this makes it easier for the devs!
This is a user debug build with limited su in xbin so adb shell has root but not on the phone.
These builds are easily rooted of course, but cannot be flashed on secured hardware at all.
The value of this file is more from the ability to examine the code group structure so we can look at the bootchain and CDT to get a better understanding how the phone works. This also appears to be for older P2 hardware revision, whereas the VZW released devices are P3.
That is another reason not to flash this file to our phones under any circumstances.
Thanks for digging this up and P3 and I will be taking a look at it as I qm sure many others will.
This does not mean we are any closer to root on stock hardware but is very exciting nonetheless.
I see...darn I thought we were getting pretty close to root
Sent from my DROID3 using XDA Premium App
royolpunk said:
we're hoping that this is a complete image of the phone (which it should be, considering it's at 222MB. we're going to go through the SBF step by step and look for more exploits that we can use to root this phone.
edit:
whaatt you ninja'd me -____-
Click to expand...
Click to collapse
I downloaded a file a while ago called "D3 system dump" want a link?
Nah we've already been through that
Sent from my DROID3 using XDA Premium App
royolpunk said:
Nah we've already been through that
Sent from my DROID3 using XDA Premium App
Click to expand...
Click to collapse
Gotcha, thanks. Trying any lead I can haha.
Sent from my DROID3 using XDA Premium App
Woo! I can't wait to see what the devs can do with this. Gonna be the first thing I check when I wake up in the morning
Sent from my DROID3 using XDA Premium App
Nothing... it was pretty disappointing actually.
Sent from my DROID3 using XDA App
Sent from my DROID3 using XDA Premium App
Hey Ho
First of all I'm new to XDA so please excuse my mistakes.
I played a little bit with the sound chip of the 2x and got the audio routing for the FMRadio :victory:
First you need to flash this Download CWM by pengus77
Second you need Spirit FM by mikereidis
1) start Spirit FM
2) you can either execute the commands manualy in the terminal or you can download my script and execute it with "Script Manager"
Here are the commands:
EDIT: Updated version here
Now you should hear the station you selected through the headphones
PLEASE NOTE
The settings disappear after reboot
The settings disappear after a call
The settings disappear after you close Spirit FM
The settings might affect music playback and/or recording, to go back to normal reboot your phone or make a call
I'm not responsible if you damage your phone or your ears because of to loud music
The sound is only mono, because i don't have the paid version of Spirit FM and maybe it's a hardware limitation :/
Edit: This has been tested with ParanoidAndroid v2.6 - build 08 [Feb 22] and Kowalsky Kernel exp 112
I hope some developers stumble upon this and integrate it in their kernel/ROM
have fun
sudden36
Sweet!! Gonna include the FM radio patches of CM with a method to enable it in the next PA version, with credits to you of course
Will discuss with pengus if it's possible to apply this directly in the kernel.
Awesome man! I'll setup this path directly in the kernel via a sysfs switch so it's persistent
Really great sudden36 !
Thanks a lot !!!
The play store link for Spirit fm shows incompatible.
Thanks for the work.
Rom: pengus 0208
Kernel pengus 100p5
Sent from my LG-P990 using xda app-developers app
kekks said:
The play store link for Spirit fm shows incompatible.
Thanks for the work.
Rom: pengus 0208
Kernel pengus 110p5
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Grab it from here: http://forum.xda-developers.com/showthread.php?t=1059296
Thanks for the effort, been looking for working radio app for ages! Now I'm a happy camper :good:
One small problem though: when I turned on the FM radio, my phone mic picks up surrounding noise and channels it through my earphone (I'm on PA CM10 build 8 + kowalski 100p5 old bl). Could you please take a look at it?
komedol said:
Thanks for the effort, been looking for working radio app for ages! Now I'm a happy camper :good:
One small problem though: when I turned on the FM radio, my phone mic picks up surrounding noise and channels it through my earphone (I'm on PA CM10 build 8 + kowalski 100p5 old bl). Could you please take a look at it?
Click to expand...
Click to collapse
Thanks for your feedback
I actually made a mistake with the last audio path, here should be the correct one:
Code:
#! /bin/sh
echo "Configuring Input"
alsa_amixer sset "IN1R" "off"
alsa_amixer sset "IN1R PGA IN1RN" "off"
alsa_amixer sset "IN1R PGA IN1RP" "off"
alsa_amixer sset "IN1L" "off"
alsa_amixer sset "IN1L PGA IN1LN" "off"
alsa_amixer sset "IN1L PGA IN1LP" "off"
echo "Configuring Output Mixer"
alsa_amixer sset "Right Output Mixer IN1R" "off"
alsa_amixer sset "Left Output Mixer IN1L" "off"
alsa_amixer sset "Right Output Mixer Right Input" "on"
alsa_amixer sset "Left Output Mixer Right Input" "on"
echo "Configuring Input Mixer"
alsa_amixer sset "MIXINR IN1R" "off"
alsa_amixer sset "MIXINL IN1L" "off"
alsa_amixer sset "MIXINR IN2R" "off"
alsa_amixer sset "MIXINL IN2L" "off"
# change these values to adjust volume to your needs
alsa_amixer sset "MIXINR IN1RP" "5"
alsa_amixer sset "MIXINL IN1LP" "5"
echo "Configuring Headphone Mux"
alsa_amixer sset "Left Headphone Mux" "Mixer"
alsa_amixer sset "Right Headphone Mux" "Mixer"
echo "done"
I hope this time it works
kekks said:
The play store link for Spirit fm shows incompatible.
Click to expand...
Click to collapse
I marked it incompatible because it hasn't worked on custom ICS+ ROMs for the last year+.
I'm happy to see this. I'll try to integrate the ALSA settings into the existing "LG4 / P990" audio-> method tonight. I did a hopeful update to this method in November but only one person reported it working and only briefly.
Do note however that my experience is this:
Getting FM audio working basically, as has been done here, is often VERY difficult (unless you already know the magic incantations). But it's often only 10% or so of the problem.
The other 90% of the work is making audio work well in the midst of phone calls, audio notifications, screen off, headset plug-ins and outs and many "edge cases".
As I've said repeatedly, most of my work these days is with audio issues and not the FM chips and APIs. Android has no framework to support FM audio. And it seems every manufacturer, device/chipset and ROMs do it at least somewhat differently. And it's usually analog audio, injected late in the audio processing chain (ie "hacked in"), rather than going through the normal digital audio paths everything else does.
My point is that I can only officially support this in Spirit if it works well, with few problems, and without too much work from me and without my needing to buy one to test. Otherwise, it may work, but will remain unofficial support.
Glad to hear that,awaiting new version of spirit fm and penguses kernel
mikereidis said:
I marked it incompatible because it hasn't worked on custom ICS+ ROMs for the last year+.
I'm happy to see this. I'll try to integrate the ALSA settings into the existing "LG4 / P990" audio-> method tonight. I did a hopeful update to this method in November but only one person reported it working and only briefly.
Do note however that my experience is this:
Getting FM audio working basically, as has been done here, is often VERY difficult (unless you already know the magic incantations). But it's often only 10% or so of the problem.
The other 90% of the work is making audio work well in the midst of phone calls, audio notifications, screen off, headset plug-ins and outs and many "edge cases".
As I've said repeatedly, most of my work these days is with audio issues and not the FM chips and APIs. Android has no framework to support FM audio. And it seems every manufacturer, device/chipset and ROMs do it at least somewhat differently. And it's usually analog audio, injected late in the audio processing chain (ie "hacked in"), rather than going through the normal digital audio paths everything else does.
My point is that I can only officially support this in Spirit if it works well, with few problems, and without too much work from me and without my needing to buy one to test. Otherwise, it may work, but will remain unofficial support.
Click to expand...
Click to collapse
Hiya, in the p990 kernel there are a couple tweaks i can implement, exposing via sysfs the is_call_mode and is_fmradio_mode booleans so it's possible to tell the kernel that we're using the radio. Those variables are in the wm8994 code and ICS blobs set them via ioctl. We'll probably also have to mod a bit the phone/framework code in cm10.X to support the same switching, but i think it's "the right way". I'll investigate a bit in ICS to see if i'm correct on this assumption, but if i am we could maybe perform a couple tests in private and see if it works as it should. What do you think ?
I don't have any debug log showing these ALSA controls.
Someone send me a debug log from Spirit. Use Menu-> Test-> Email-> Logs and press Send after 20 seconds.
This is amazing, now we can hope we dont net this steps and the Dev can implement it or its can implement in the Kernel/Rom
mike you have an email
A question about spirit fm, is the core code to controll the fm chip anywhere openly published, i would like to look at it, just for curiosity
I think tomorrow i will try to record some radio :laugh:
sudden36 said:
mike you have an email
A question about spirit fm, is the core code to controll the fm chip anywhere openly published, i would like to look at it, just for curiosity
I think tomorrow i will try to record some radio :laugh:
Click to expand...
Click to collapse
My code is not published.
This phone uses a Broadcom BCM4329 FM/BT/WiFi combo chip.
The old CM7/MIUI FM app "driver" code is open and used hcitool to control the chip.
There's also a V4L driver written by Nokia for an earlier BCM chip that is more or less register compatible. BCM2048 if I recall correctly.
Beyond that, no open source code exists that I'm aware of, but I haven't really looked in the last 12+ months. The chips specs are secret and I've never found them, even on Chinese sites dedicated to confidential tech documents.
Thank you
Now my rom is perfect!!Thank you very much:victory:
Works great on the latest CM10.1 nightly and [email protected] Kernel 100p5
Thanks for the work everyone!
mikereidis said:
My code is not published.
This phone uses a Broadcom BCM4329 FM/BT/WiFi combo chip.
The old CM7/MIUI FM app "driver" code is open and used hcitool to control the chip.
There's also a V4L driver written by Nokia for an earlier BCM chip that is more or less register compatible. BCM2048 if I recall correctly.
Beyond that, no open source code exists that I'm aware of, but I haven't really looked in the last 12+ months. The chips specs are secret and I've never found them, even on Chinese sites dedicated to confidential tech documents.
Click to expand...
Click to collapse
In case it helps, here's the LG internal service manual which shows the technical paths and GPIOs etc.:
https://www.dropbox.com/s/etzanib7jgx7tp7/LG_P990_Optimus_2X_Star_Speed_service_manual.rar
What is the LG you have 990 or 970? Works on both?
bruno.u2 said:
What is the LG you have 990 or 970? Works on both?
Click to expand...
Click to collapse
I have a p990, I don't know if the p970 has the same audio chip and configuration.
You can try it if you want, as the settings are only temporary just reboot if it breaks anything
So far I'm liking the way Beats Audio enhances the sound coming out of the speakers and headphones. But when I stream it through my car, it sounds really bad. Ideally, there would be options to specify when Beats Audio should kick in based on where the sound is being produced (speakers, headphones, bluetooth). But the next best thing would be to have a way to turn it on or off from a profile manager like Llama or Tasker.
Does anyone know of a way to do this? Or at least a widget that can turn it on or off?
Thanks
kzibart said:
So far I'm liking the way Beats Audio enhances the sound coming out of the speakers and headphones. But when I stream it through my car, it sounds really bad. Ideally, there would be options to specify when Beats Audio should kick in based on where the sound is being produced (speakers, headphones, bluetooth). But the next best thing would be to have a way to turn it on or off from a profile manager like Llama or Tasker.
Does anyone know of a way to do this? Or at least a widget that can turn it on or off?
Thanks
Click to expand...
Click to collapse
It has been over a month, and I still haven't found a way to do this. Has anyone figured it out yet? From what I can tell, by looking at alogcat output after turning the option on and off in settings, it's just a broadcast intent to AudioService or something. But I couldn't figure out what to put into Llama's custom intent to make it work. Here's what I see in the log:
D/AudioService( 644): [HtcBeatsEffect]setSystemSoundEffect id=800
D/AudioService( 644): [HtcBeatsEffect]setSystemSoundEffect id=900
800 turns it off and 900 turns it on. If anyone can help me figure out how to do this from Llama or Tasker, I'd very much appreciate it.
Most I Could Find
Fairly new to Android after spending a long time with the Dark Side...
I cannot paste a link because I am a n00b, but on the HTC Dev site under the "Sound Enhancer" section is the following:
com.htc.HtcSoundEnhancerSetting.ShowSettingPage Opens the HTC Sound Enhancer settings page allowing the user to choose an audio effect
I don't know much about intents, but since there seems to be a want for this, can anyone do anything with this?
Anybody figure out how to do this with Tasker or the like? I can't get the intents to triggger. I have a Beats notify toggle too in Viper DNA, I thought maybe that could be used instead? I see multiple threads about this..
kzibart said:
It has been over a month, and I still haven't found a way to do this. Has anyone figured it out yet? From what I can tell, by looking at alogcat output after turning the option on and off in settings, it's just a broadcast intent to AudioService or something. But I couldn't figure out what to put into Llama's custom intent to make it work. Here's what I see in the log:
D/AudioService( 644): [HtcBeatsEffect]setSystemSoundEffect id=800
D/AudioService( 644): [HtcBeatsEffect]setSystemSoundEffect id=900
800 turns it off and 900 turns it on. If anyone can help me figure out how to do this from Llama or Tasker, I'd very much appreciate it.
Click to expand...
Click to collapse
Still no solution for this I think
But it is possible to set 800 or 900 with Tasker and Secure Settings:
In Tasker: Plugin -> Secure Settings -> Configuration
Then in Secure Settings: Actions -> Device Setting
Setting Table: system
Setting Name: audio.soundenhancer.effect
Setting Value: 800 or 900 (to disable or enable Beats Audio)
Then save and execute the Task.
The changes should now be set (I think in data/data/com.android.providers.settings/databases/settings.db)
But now I have to soft reboot the phone for the changes to take effect. The Beats Audio switch is now toggled.
Does anybody know what I can do for the new settings to take effect immediately? Like killing an app or reloading settings.db or something?
i have 2 pcs bionic... before, they are both 2.3.4, the first one I tried Radiocomm method and it works, with signal on gsm without Data, and also Force Close error when u open network settings..but have signal and can call and send msg..
i read something that if u upate to Jellybean, all band will work no need radiocomm...thats why i update to 4.1.2...
but i\now not working gsm, and can dongrade to GB...
anybody can help me? I am in Philippines...thats why i need it to work in GSM!
Did you try the Radiocomm method on Jellybean? It should work based on others' posts in that Bionic on Tmobile thread here on xda.
What is the frequency band your carrier is using? 900/1800 or 850/1900mhz GSM? I'm trying to make it work on 900/1800 band but it's not working for me. I'm on ICS.
uhm said:
Did you try the Radiocomm method on Jellybean? It should work based on others' posts in that Bionic on Tmobile thread here on xda.
What is the frequency band your carrier is using? 900/1800 or 850/1900mhz GSM? I'm trying to make it work on 900/1800 band but it's not working for me. I'm on ICS.
Click to expand...
Click to collapse
Where can I find the Radiocomm method for Jellybean for here in the U.S.? I have rooted using Easy root method w/Linux emulator, Installed Safestrap to install Patch which supposedly unlocks GSM and I followed the radiocomm edits found here: http :// w ww. internauta37.altervista.org/how-and-patch-fully-enable-gsm-verizon-cdma-phones-android I also did *#*#4635#*#* and it was set to CDMA auto (prl), when I change to CDMA preferred it force closes. Phone says no sim even though active ATT/straight talk sim is in. Thanks for any help.
Seems like builprop edits haven't been done otherwise in the phoneinfo, you should have seen a mode automatically selected that allows GSM, e.g. WCDMA preferred, GSM Auto(prl) etc. The factory reset is required after the builprop edits.
got it, thanks a lot for the help! Running At&t Straight talk. Calling/Texting works, I'm assuming I don't have data though as I don't see any 3G or other data indicators in the status bar. Is there something else that needs to be done to get data going?
my bionic is now working on GSM in philippines using this metohd:
Here are the steps that I performed to get my Jelly Bean working.
1. Make sure you are running factory OS. I am running 98.72.22.XT875 It's the latest Jelly Bean 4.1.2 release.
2. Root your phone. I used Easy Root http://forum.xda-developers.com/show....php?t=2256439 Just follow the instructions, it's very easy.
3. After it's rooted download ES File Explorer File Manager and Root Browser from the Play Store. Both are free.
4. Go into File Explorer. Tap the blue icon on top left then go to Tools. Turn on Root Explorer. It will ask you for a superuser access, you have to grant it.
5. Go into Root Browser. It too will ask for a superuser access. You have to grant it as well. Install updates if it asks you to.
6. In Root Browser navigate to system/bin. Find mount_ext3.sh file. Tap and hold the screen to bring up the menu. Select Open with... and choose RB Text Editor. Scroll to the end of the file. After the last line leave a blank line then add the following lines.
chmod 4755 /system/bin/su
chmod 4755 /system/xbin/su
chmod 4755 /system/app/Superuser.apk
Tap the save icon at the top of the screen when finished.
7. Using Root Browser rename your original build.prop file (It's located in /system folder).
8. Copy build.prop file from your PC onto the SD card and then copy it into the /system folder on the phone replacing the original. I used build.prop file below. It was posted earlier in this thread.
HTML Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=9.8.2O-72_VZW-22
ro.build.display.id=9.8.2O-72_VZW-22
ro.build.version.incremental=39
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.2
ro.build.date=Fri Mar 8 14:50:18 CST 2013
ro.build.date.utc=1362775818
ro.build.type=user
ro.build.user=hudsoncm
ro.build.host=il93lnxdroid48
ro.build.tags=release-keys
ro.product.model=DROID BIONIC
ro.product.brand=motorola
ro.product.name=XT875_verizon
ro.product.device=cdma_targa
ro.product.board=targa
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=motorola
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=omap4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=cdma_targa
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=cdma_targa_mmi-user 4.1.2 9.8.2O-72_VZW-22 39 release-keys
ro.build.fingerprint=motorola/XT875_verizon/cdma_targa:4.1.2/9.8.2O-72_VZW-22/39:user/release-keys
ro.build.characteristics=default
# end build properties
#
# system.prop for CDMA Droidwe
#
# rild.libpath=/system/lib/libril-moto-umts-1.so
rild.libpath=/system/lib/libmoto_ril.so
rild.libargs=-d /dev/ttyO0
ro.sf.lcd_density=240
ro.mot.ril.danlist=611,*611,#611
persist.ril.ecclist=911,*911,#911
persist.ril.modem.mode =1
# This defines the max event window manager can
# handle in 1 s. We may adjust this # for performance
# reason later
windowsmgr.max_events_per_sec=70
# USB modes allowed for UI and switching
ro.ngp_available=1
ro.modem_available=0
# Default network type.
# 4 => CDMA/EVDO. To be used until Targa has LTE SFN
# 7 => GLOBAL.
ro.telephony.default_network=0
ro.com.google.clientid=android-motorola
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.cdma.home.operator.numeric=310004
ro.cdma.home.operator.alpha=Verizon
ro.config.vc_call_vol_steps=7
# wlan interface
wifi.interface = wlan0
softap.interface = wlan1
# Time between scans in seconds. Keep it high to minimize battery drain.
# This only affects the case in which there are remembered access points,
# but none are in range.
wifi.supplicant_scan_interval = 90
# Indicate carrier OTA SP number schema
# refer to frameworks/base/telephony/java/com/android/
# internal/telephony/cdma/CDMAPhone.java for the schema:
ro.cdma.otaspnumschema=SELC,1,80,99
# The OpenGL ES API level that is natively supported by this device.
# This is a 16.16 fixed point number
ro.opengles.version = 131072
# our HTML browser (not WAP browser ) does not need to specify UAProf URL
ro.mot.hw.uaprof=http://uaprof.vtext.com/mot/xt875/xt875.xml
# Enable HAC to also display Call Setting Menu Option.
ro.mot.hw.HAC=1
# Motorola, a19622, 12/28/2009, IKSHADOW-204 / Location Settings for android
# Property to set enabling state of the location privacy setting feature.
# Motorola, a19622, 03/16/2010, IKSHADOW-2141 / Disable feature 33067
#ro.mot.settings.locprivacy=1
# ERI feature
# 0 OFF
# 1 ON
ro.mot.eri=0
# Motorol,a6889c,02/Feb/2010,IKSHADOW-619
# Proximity Sensor feature
# 0 disable
# 1 enable
persist.mot.proximity.touch=1
# End IKSHADOW-619
# BEGIN Motorola, a22976, 25-Feb-2010, IKSHADOW-702, FID 31841
# VZW Requirement Specifications: NETWORK BASED PLUS CODE DIALING
# 0 disable
# 1 enable
ro.cdma.nbpcd=0
# END IKSHADOW-702
# BEGIN Motorola, a22976, 12-Mar-2010, IKSHADOW-1784, Power Up Tone
# Motorola, a22976, 12-Apr-2010, IKSHADOW-3298, Remove temporary power up tone
# persist.mot.powerup.tone=/system/media/bootup.ogg
# END IKSHADOW-1784
persist.mot.usb.mediasync = 1
# persist.usb.android_config = 1
# System property for SMC
ro.service.start.smc=1
ro.HorizontalBUA=true
#Proximity sensor debounce time
mot.proximity.delay=150
# disable touch below 60 pixels
mot.proximity.distance=60
#inphone calibration backup support
ro.mot.hw.calibratedImager=1
# BEGIN Motorola, qpmc46, 05-Jul-2010, IKMAIN-311
persist.ril.mux.noofchannels = 8
# END Motorola, qpmc46, 05-Jul-2010, IKMAIN-311
#BEGIN Motorola, nfjb73, 21-jun-2010,
# this is for feature 34386, other features for vzw global phone
# could use this property too. IKMAIN-732
#1 this is verizon wireless globle phone
#0 this is not verizon wireless globle phone
ro.mot.phonemode.vzwglobalphone=0
# END Motorola, nfjb73, 21-jun-2010, IKMAIN-732
# BEGIN Motorola, nfjb73 23-jun-2010, IKMAIN-624
# this is for feature 33860, when phone is activated, the cdma mdn is written.
persist.radio.vzw.cdma.mdn=
# END Motorola, nfjb73
# BEGIN Motorola, qmfd78, 14-Jul-2010, IKMAIN-884
# GSM SMS traffic needs to be routed/sent through North America SMSC.
# This is part of the VZW World-phone Feature. SMS are always sent to a US SMSC and then injected
# into that network. This allows for billing and give the user the impression that the device is
# still in the US.
ro.telephony.gsm-routes-us-smsc = 1
# END Motorola, qmfd78, 14-Jul-2010, IKMAIN-884
# BEGIN Motorola, a22600 qmfd78, 16-Jul-2010, IKDROIDPRO-423
# For north american cdma operators, this flag should be 1.
# It enables number mangling when nbpcd (plus code dialing) is not supported.
# This is part of the VZW World-phone Feature.
ro.cdma.home.operator.isnan=0
# END Motorola, a22600 qmfd78, 16-Jul-2010, IKDROIDPRO-423
# EDM feature - IKDROIDPRO-381 - Start
ro.mot.dpmext = true
# EDM feature - IKDROIDPRO-381 -End
# BEGIN Moto,IKDROIDPRO-430, a17673
# Feature33857 on DroidWE, support DualMode switch, UMTS/CDMA
##### Override in cdma_targa.mk until LTE + Global support. ######
#ro.mot.FTR.33857=true
# END IKDROIDPRO-430
# This is necessary for framework to support
# the LTE and eHRPD capability.
##### Override in cdma_targa.mk until LTE + Global support. ######
#ro.mot.lte_on_cdma=1
# BEGIN Moto, IKSTABLETWO-1284, nfjb73
# without this property, the lock screen would take global phone as UMTS
# block user to operate before setup
keyguard.no_require_sim = true
# End Moto
# BEGIN Moto, IKSTABLETWO-689, nfjb73, for 34387,33857
# when phone in Global mode, FW need to know the last phone mode beore power off
# when phone power up, it would use the right mode to avoid switch
persist.radio.ap.phonetype=1
# END IKSTABLETWO-689
# Multimode RIL Paths
##### Override in cdma_targa.mk until LTE + Global support. ######
#lte_ril.libpath=/system/lib/lib-mot-lte-ril.so
#cdma_ril.libpath=/system/lib/libmoto_ril.so
#ril.rat=LTE
# Motorola, IKHALFMWK-3, w001091
# Feature 32711, deep sleep mode support
ro.mot.deep.sleep.supported=true
# BEGIN Motorola, A24124, 10-June-2011,IKTARGA-1744
ro.mot.bindervm.config = 251
# END IKTARGA-1744
# Give extra time for LTE bug dumps
ril.dumpstate.timeout=60
# make voice call, data call on targa
telephony.lteOnCdmaDevice=0
# BEGIN Motorola abp095, 4-Jan-2012, IKHSS7-2427 - Thumbnail property change
com.motorola.cg.lowres=1
com.motorola.cg.tnWidth=160
com.motorola.cg.tnHeight=160
com.motorola.cg.tndisplay=1
# END IKHSS7-2427
# BEGIN Motorola, w21549, 06/06/2012, IKHSS6UPGR-12234
ro.hdcp.support=2
# END IKHSS6UPGR-12234
# system prop for requesting Master role in incoming Bluetooth connection.
#
ro.bluetooth.request.master=true
#
# system prop for Bluetooth Auto connect for remote initated connections
#
ro.bluetooth.remote.autoconnect=true
# System Properties for enabling individula Bluetooth Profiles
ro.qualcomm.bluetooth.opp=true
ro.qualcomm.bluetooth.hfp=true
ro.qualcomm.bluetooth.hsp=true
ro.qualcomm.bluetooth.pbap=true
ro.qualcomm.bluetooth.ftp=true
ro.qualcomm.bluetooth.map=true
ro.qualcomm.bluetooth.nap=true
ro.qualcomm.bluetooth.sap=true
ro.qualcomm.bluetooth.dun=true
ro.mot.btdun.disable = false
#
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.google.clientidbase=android-motorola
ro.com.google.clientidbase.ms=android-verizon
ro.com.google.clientidbase.am=android-verizon
ro.com.google.clientidbase.yt=android-verizon
ro.com.google.clientidbase.gmm=android-motorola
persist.sys.usb.config=mass_storage
ro.kernel.android.ril=yes
persist.ril.mux.noofchannels=10
persist.ril.mux.ttydevice=/dev/ttyO0
persist.ril.modem.ttydevice=/dev/ttyUSB4
persist.ril.tcmd.ttydevice=/dev/usb/tty2-1:1.3
persist.ril.diag.ttydevice=/dev/usb/tty2-1:1.0
persist.ril.features=0x90A
persist.ril.mux.retries=500
persist.ril.mux.sleep=2
persist.ril.rssi.enable.param6=1
ril.wrigley.modem.tty=/dev/usb/tty1-2:1.10
persist.radio.lte.mm.disable=1
rild.libpath=/system/lib/moto-ril-multimode.so
gsm.sim.mot.simswap=1
ro.config.ringtone=DroidInvasion.ogg
ro.config.notification_sound=Droid.ogg
ro.mot.build.customerid=verizon
ro.mot.build.version.sdk_int=9
ro.mot.build.product.increment=2
ro.mot.build.version.release=9.2
ro.build.version.full=Blur_Version.98.72.22.XT875.Verizon.en.US
ro.mot.hw.HAC=1
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.1_r4
ro.HorizontalBUA=true
ro.HorizontalVVM=true
ro.horizontalNGM=false
ro.horizontalVMM=false
ro.horizontalMOD=false
ro.horizontalVOD=false
ro.horizontalEmail=false
ro.cdma.home.operator.numeric=310004
ro.cdma.home.operator.alpha=Verizon
ro.cdma.homesystem=64,65,76,77,78,79,80,81,82,83
ro.mot.eri=0
ro.cdma.nbpcd=0
ro.cdma.home.operator.isnan=0
ro.mot.ignore_csim_appid=true
ro.telephony.gsm-routes-us-smsc=1
ro.cdma.otaspnumschema=SELC,1,80,99
ro.mot.phonemode.vzw4gphone=0
ro.com.android.dataroaming=true
ro.bug2go.uid.type=TELEPHONY_DEVICE_ID
ro.bug2go.magickeys=24,26
ro.carrier=unknown
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapsize=128m
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
ro.cdma.subscription=0
ro.telephony.default_network=0
lte_ril.libpath=/system/lib/lib-mot-lte-ril.so
cdma_ril.libpath=/system/lib/libmoto_ril.so
ril.rat=GSM
lte_ril.netcfg_to=90
ro.telephony.ril.v3=signalstrength
ro.telephony.call_ring.multiple=false
ro.cdma.data_retry_config=max_retries=infinite,0,0,10000,10000,100000,10000,10000,10000,10000,140000,540000,960000
ro.gsm.data_retry_config=default_randomization=2000,max_retries=infinite,0,0,80000,125000,485000,905000
ro.gsm.2nd_data_retry_config=max_retries=infinite,default_randomization=2000,0,0,80000,125000,485000,905000
ro.mot.setuptype=2
ro.horizontalIM=true
ro.ril.svlte1x=true
ro.media.camcorder.1080p=mp4,h264,30,15000000,aac,128000,44100,2
ro.media.camcorder.720p=mp4,h264,30,10000000,aac,128000,44100,2
ro.media.camcorder.d1NTSC=mp4,h264,30,6000000,aac,128000,44100,2
ro.media.camcorder.vga=mp4,h264,30,4000000,aac,128000,44100,2
ro.media.camcorder.cif=mp4,h264,30,1500000,aac,128000,44100,2
ro.media.camcorder.qvga=mp4,h264,15,500000,aac,64000,44100,2
ro.media.camcorder.mms=3gp,h264,15,128000,amrnb,12200,8000,1
ro.media.camcorder.mmsres=qvga
ro.camcorder.zoom=true
ro.media.capture.maxres=5m
ro.media.capture.fast.fps=4
ro.media.capture.slow.fps=120
ro.media.capture.flash=led
ro.media.capture.flashMinV=3300000
ro.media.capture.torchIntensity=40
ro.media.capture.flashIntensity=70
ro.media.capture.classification=classF
ro.media.panorama.defres=3264x1840
ro.media.panorama.frameres=1280x720
keyguard.no_require_sim=true
ro.media.enc.aud.fileformat=qcp
ro.media.enc.aud.codec=qcelp
ro.media.enc.aud.bps=13300
ro.media.enc.aud.ch=1
ro.media.enc.aud.hz=8000
persist.service.aplogd.enable=1
ro.mot.lte_on_cdma=0
ro.mot.tmp.telephony.refactor=true
ro.hss6upgrade.hide.motocastid=TRUE
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
drm.service.enabled=true
9. This step is important so don't skip it!!! If permissions aren't set correctly your phone won't boot and you will need to reload the OS and start from scratch. In Root Browser tap and hold build.prop file. On a menu that pops up select permissions. Make sure that permissions are set to 0644. Read access should be checked for Owner, Group, Others. Write access should be checked for Owner. Excuse access should be unchecked for all.
10. Make sure your phone's USB setting is set for anything except Mass Storage.
Now on your PC run Radio Comm. I use version 11.12.2.
Go to Main - MA - CDMA1X - QSC60 x 5 Chipset base.
Then click on FTM Common 1 tab.
Under NVAccess drop down box find 1877, NV_RF_BC_CONFIG_I.
Then Click on Read. Read button should be green. If it's Red your phone is not communicating properly with your PC and it won't work.
In the Data: (Hex) field just below NVAccess drop down box you will see a bunch of numbers. Delete first 16 characters and replace them with 8703E804000200
Then click on Write. That should turn green as well.
11. Now power off your phone and power it back on. At this point after the phone rebooted I got com.android.phone has stopped unexpectedly.
12. Now power the phone off again. I had to pull the battery. Go into the recovery mode and wipe cache partition as well as wipe data/factory reset. Then reboot the device.
At this point it should boot up normally. You may still get com.android.phone has stopped unexpectedly but you can tap ok and it will load normally.
After this you will need to root your phone again. Download ES Explorer and Root Browser and delete STK.apk, STK.odex, VzwPhoneService.apk, VzwPhoneService.odex (All 4 are under /system/apps folder). This step is only required to get rid of the annoying SIM car unrecognized warning.
So far the only issue that I am seeing is poor signal strength. I see 2-3 bars. Perhaps someone has a fix for this?
Click to expand...
Click to collapse
My only problem is VERY VERY Low Signal
johnkill_dxb said:
my bionic is now working on GSM in philippines using this metohd:
My only problem is VERY VERY Low Signal
Click to expand...
Click to collapse
I'm in the U.S. but am also experiencing very low signal. I have 3G going but can't get reception to hold more than one bar if anything. Seems to be the common story with this hack. I'll stay posted to check for any radiocomm edits/work arounds for signal improvement
***UPDATE*** I left my house for the first time today since getting my phone going on GSM w/AT&T StraightTalk and I had 4 bars of reception and full 3g downloads and full messaging capabilities. I'm satisfied with the results and I think any difference in signal strength may come from having been spoiled on Verizon's coverage, even though I never got good reception at my house with verizon either so I guess I can't expect more from someone else.
johnkill_dxb said:
my bionic is now working on GSM in philippines using this metohd:
My only problem is VERY VERY Low Signal
Click to expand...
Click to collapse
Good to hear that it's working for you. What is the frequency band your carrier is using? 900/1800 or 850/1900mhz GSM?
900/1800mhz is the freq here in philippines
guys on my droid bionic jelly bean,i went to testing and then i selected radio band,i thought i would see a list of bands,but i saw only USA BAND but i didn't know what it was so i chose it and my network never came,i tried on a friend's phone i saw automatic in his list,but i cant see it on mine.please help me recover back to my network,am in africa
For those wanting to use the LG Camera app on the V40 but do not have an option to toggle the camera's sounds and want it, then the script below should enable the 'Shutter sound' setting.
*A disclaimer and a reminder that in Japan and Korea, and possibly other countries, by silencing the camera sounds you may be breaking the law iiuc - so do check! - I cannot be held liable if you are arrested, charged, fined, sent to jail, etc. - You do this at your own risk!*
That said, where I am based it is not, and I find the shutter sound annoying. There are modules around that will silence your LG Camera app, they work by changing the files containing the sound into silent/empty ones. Not a great solution if you want to have the choice about whether you want sound or not. However, there is already a setting for this buried inside the LG Camera app and this will enable it for you:
So, assuming you have Magisk installed on your phone, please run these commands from your computer:
Code:
adb shell
su
echo "resetprop ro.vendor.lge.build.target_operator TRF_VZW" > /data/adb/post-fs-data.d/enable_shutter_sound_setting.sh
chmod 755 /data/adb/post-fs-data.d/enable_shutter_sound_setting.sh
reboot
Once it restarts, load up the LG Camera app, tap the settings button (top left?), then if you scroll through the settings you should see a 'Shutter sound' setting you can toggle on and off. I've only tested this on my LM-V405EBW, it is possible other versions may be different.
If you'd like a bit more detail about what is going on here, then:
First (line) just starts up a shell on your phone
Second gives you root (you may need to grant access in Magisk)
Third writes a system property to a file to change the mobile operator your LG apps may believe they are running against. The TRF_VZW value is one of two that will allow the 'Shutter sound' setting to appear in the LG Camera app
Forth makes the file you just created executable to the android system
Fifth will reboot the phone and enable this property for the LG Camera app to use, and give you the 'Shutter sound' setting option
I should point out a caveat: this setting change may mean other LG apps may also make assumptions about what you can or cannot do as if you were a Tracfone phone. This only affects LG apps it seems though, so probably not too bad, but worth knowing perhaps :angel:. If you want to remove this change then please run:
Code:
adb shell
su
rm /data/adb/post-fs-data.d/enable_shutter_sound_setting.sh
reboot
Something I don't understand (yet) is why some report that turning the phone to silent/vibrate mode will also silence the LG Camera app's shutter sound too - this does not work on mine... not a big thing as this works well for me. Maybe it is something about starting with a LM-V405EBW V20a-IND-XX - if anyone knows, please leave a comment. Thank you
Finally, If you'd like far too much detail about this under the hood then please indulged yourself:
I downloaded the app from the phone at /system/product/priv-app/LGCameraApp/LGCameraApp.apk
Decompiled it and found this interesting piece of code in the playSound function of the SoundManager class:
Code:
if (!FunctionProperties.isSupportedShutterSoundSetting() || ... )
So looking at the isSupportedShutterSoundSetting function in the FunctionProperties class, we see that this is how it determines who has this setting:
Code:
ModelProperties.getCarrierCode() == 6;
Looking inside the getCarrierCode function of the ModelProperties class, we find that two carriers return a 6, and we also see the system property they use:
Code:
sCarrierCodeMap.put("VZW", 6);
...
if ("TRF_VZW".equals(SystemProperties.get("ro.vendor.lge.build.target_operator"))) {
sCarrierCode = 6;
So by setting the system property 'ro.vendor.lge.build.target_operator' to 'VZW' (Verizon Wireless, I'd guess) or 'TRF_VZW' (Tracfone on Verizon ¯\_(ツ)_/¯) we can enable seeing the 'Shutter sound' option in LG's Camera app's menu. Enjoy!
Update: So after playing around with other LG apps, Phone and Contacts had some issues using VZW. I didn't dig too deeply into this, but can imagine an if statement or two. I found TRF_VZW is largely an unknown operator which seems to default to OPEN, as you would probably want
Stone-cold stock on V405UA20F in USA. I'm guessing only where disabling it is illegal, will be interested. View attachment 4951499
Sent from my LM-V405 using Tapatalk
Einsteindks said:
Stone-cold stock on V405UA20F in USA
Click to expand...
Click to collapse
Thank you for the data point... I'll do a bit more digging later on.
For others: this image is what you should see, I should have posted one too, thank you @Einsteindks
Einsteindks said:
Stone-cold stock on V405UA20F in USA
Click to expand...
Click to collapse
So this stock is Verizon Wireless - so your build target operator will be VZW under the hood.
You may check this with:
Code:
adb shell
getprop ro.vendor.lge.build.target_operator
If I am correct, it should say 'VZW' - and why you have the 'Shutter sound' setting by default.
Before doing what the original post said, mine was set to 'OPEN' - which is what both my original and flashed firmwares were built with
Thanks, the small Code from #1 is working finde in my Android 12 LG V50 (500N40C). Korean Phone with 4G Vodafone.de