Currently looking at iwconfig, somehow the txpower is set to 32dbm (1492mW). Iwlist eth0 txpower lists available txpower levels below such a number. 0dbm and 25dbm (255mW). I'm guessing this 32dbm is nowhere near correct. How can we manipulate txpower? Its nice to have these commands working now! BTW the formula for dBm is P =30+10log(W). In this case, W=1.492, so dBm is actually 31.74. Not that it matters, I think that's way out of spec.
Blades said:
Currently looking at iwconfig, somehow the txpower is set to 32dbm (1492mW). Iwlist eth0 txpower lists available txpower levels below such a number. 0dbm and 25dbm (255mW). I'm guessing this 32dbm is nowhere near correct. How can we manipulate txpower? Its nice to have these commands working now! BTW the formula for dBm is P =30+10log(W). In this case, W=1.492, so dBm is actually 31.74. Not that it matters, I think that's way out of spec.
Click to expand...
Click to collapse
I don't think that may be accurate. I compiled iwlist and when I look for channels it gives a bunch of channel 0's, with very odd values, many far from the 2.4ghz range. I may have renamed the wrong wireless(number).h to wireless.h before compiling. I'm curious if you have this problem as well? How did you compile iwlist?
Related
Has anyone tried this? If so did you notice any speed differences? can you post some screenshot comparisons of your mobile speed tests?
link: http://www.opendns.com/start/windows_mobile5.php
I´ve tried
No difference for me, in fact I enrolled to OpenDNS I got the DNS addresses and sometime after someone in this forum suggested to me to use exactly the same DNS addresses that I got when i enrolled. My question would be: Does everybody receive the same set of DNS addys?
I have been using openDNS for a while. And yes you notice an slight increase in speed of dns requests when compared with oranges dns.
Why do you want screenshots? What would that show? Theres so many things that could vary your dns speed.......
WWWeed said:
I have been using openDNS for a while. And yes you notice an slight increase in speed of dns requests when compared with oranges dns.
Why do you want screenshots? What would that show? Theres so many things that could vary your dns speed.......
Click to expand...
Click to collapse
i know... i guess i just wanted to see if the speed increases or lack thereof were that drastic.
i am wondering if anyone could explain what the menu options mean. i know a few of them. But am curious as to what the others mean. I am in a very rural area and have the options for 3g, and Satellite thats it. and i am trying to open up my phone with this or some other settings/rooting to get a better ping. i can get a 250 ping at 2AM, but at around 8PM ill have a 800-1500 ping. which is no good.
so if anyone could either help me out or point me in the right direction IE post a link to a forum that i may have overlooked, or flat out tell me what i have to do, or bits and pieces of the the puzzle come in one at a time. any information would help.
my signal is around -92 to -95. My reading and research states that a -60 is damn near perfect signal and a -112 is loosing calls.
EPST
-Data Profile
*active profile
-1
*SPI MN-HA
-4D2
*SPI-AAA
-4D2
*Reverse Tunnel Preferred
-Enabled
*Home IP address
-0.0.0.0
*primary Home Agent
-255.255.255.255
*secondary home agent
-(default 68.28.157.76) i changed it to 68.28.145.76 (Chicago HA closer then the default which is Roachdale,IN, Chicago is closer to my location.)
*HA Shared secret
-******
*AAA Shared Secret
-******
-EVDO
*DDTM(this disables incoming calls for something i dont know what..)
-disabled
*Preferred Mode
-automatic
#modify: automatic, HDR only, Digital Only, CDMA only
(i know that CDMA is 2g),CDMA HDR Only.
-Advanced
*MEID(Hex)
-a long code.. dont want to give out personal info..
*p_rev
-IS-2000 (6)
*SCM
-58
*Slot Mode
-enabled
*Slot Cycle Index
-2 (i know that this is Default, and that this is the rate at which the phone checks to see if you are receiving a phone call, i think that 2=3.24sec or something around there)
*MCC(mobile country code)
-310
*MNC(mobile network code)
-00
*msid
-looks to be a phone number 10 digits with my area code
*ACCOLC(Access Overload Class)
-5
*vocoder
-enabled
*EVRC-B
-disabled
*roam orig
-voice 13k
*LBS PDE IP
-<not available>
*LBS PDE Port
-<Not available>
*Home SID/NID #1
-4139/65535
-WiMAX
*standby time (minute)
-10
*scan rate (Minute)
-30
*center frequency
-2647000,2657000,2667000
*bandwith
-10,10,10
*NAPDIS
-000002 #modify: 000004
*NSPDIS
-000004 #modify: 000002
*WiMAX_scan_attempt_timeout(s)
-1
*WiMAX_scan_Retry(s)
-120
*Wimax_Idle_sleep(s)
-10
*WiMAX_Entry_RX(RSSI)(dBm)
- -60
*WiMAX_Entry_CINR(dB)
-4
*WiMAX_Entry_Delay(s)
-300
*WiMAX_Exit_CINR(dB)
-2
*WiMAX_Exit_Delay(s)
-2
*Handoff Threshold
-0
*Idle Mode Timer
-0
Which settings do you need in epst?
Sorry that was a mistake.
I need the shared secrets.
ha and aaa for frofile 1 and profile 0. after sending spc in qxdm and running "06:18:32.773 requestnvitemread ds_mip_ss_user_prof 0" i get all zeros in return for both secrets and both profiles. ugggg. cant get my data working.
Please remember to make a backup image of your phone before experimenting.
============ WARNING!! =============
The highest setting is VERY loud (as I found out) and could potentially rip apart the speaker on your phone!
Exercise extreme caution when using this. You risk permanent damage to your phone and your ears.
2013-Jan-20
-----------------
Thanks xda-developers members "skvalex" who wrote ALSAMixer and "chdlock" who is helping me figure out
how ALSA is mapping the audio chipset, we can now temporarily adjust the Digital Volume on the Nexus 4.
Unfortunately, the selected volume doesn't "stick" because the audio driver re-writes it every time it re-opens an audio stream.
A stream is usually opened when a music track begins to play so then the digital volume will reset back to default.
We need a kernel developer to modify the audio driver so it opens an audio stream using a user-selected Volume level.
***
If you don't mind setting the volume frequently or just want to try this out here's what you need:
1) Get ALSAMixer from the Play Store. It was updated recently and you need the latest version.
Please consider a donation to the author.
2) You can re-program the audio chipset by editing fields in ALSAMixer. Here is a list of what we can control so far.
Headphones volume:
Left: RX1 Digital Volume (numid=27)
Right: RX2 Digital Volume (numid=28)
Speaker volume:
RX3 Digital volume (numid=29)
Camcorder volume:
DEC6 Volume (numid=39)
Microphone volume:
DEC7 Volume (numid=40)
-----------------------------------------------
old OPs
-----------------------------------------------
2013-Jan-15
----------------
The creator of ALSAMixer updated it to correctly install for Nexus4. (Uninstall removes the app but the ALSA libraries remain on the phone.)
https://play.google.com/store/apps/details?id=com.skvalex.alsamixer&hl=en
Thank you so much!
--------
http://forum.xda-developers.com/attachment.php?attachmentid=1653124&d=1358438577
This is a piped output of "alsa_amixer -c 0 contents" from a stock Nexus 4 (4.2.1)
2013-Jan-13
-----------------
Is anyone successfully running ALSA on their Nexus 4?
If you do please share instructions to do so.
I am on stock 4.2.1(rooted/busybox) and I ran the AlsaMixer from
the Play Store but it doesn't seem to complete the installation.
http://forum.xda-developers.com/sho...ited Edition Kit★☆★ | aokp,minco,pa,rasbean |
Shameless promotion
Sent from my Nexus 4
Next you're going to tell me that you want systemd and PulseAudio on your device too, right?
I wiped to stock,
I installed AOKP-jb-mr1-build1,
then Nocturnal 1.4 LE for AOKP
and the ALSAMixer still doesn't work. It installs but I get the same blank screen with no settings.
What am I doing wrong?
I'm not sure what that app is, I just meant that some of the audio mods in the kit ROM referred to ALSA audio libs.
As you can tell I'm not the expert, sorry if that's not what you were referring too
Sent from my Nexus 4
I am looking for a way to control the audio stream parameters in particular the gain of the microphone.
Somebody suggested using ALSA and I'm trying get it going.
-Mindroid- said:
I am looking for a way to control the audio stream parameters in particular the gain of the microphone.
Somebody suggested using ALSA and I'm trying get it going.
Click to expand...
Click to collapse
I have only a Nexus 7, and the SoC is different from the Nexus 4, but look for alsa_amixer (installed by AlsaMixer) from within a console and execute
"alsa_amixer -c X contents" (without the quotes)
where X is one of the card numbers shown in your /proc/asound directory (e.g. card0 [X=0], card1 [X=1], etc). In my case, X=1 is the actual card where (a lot of) values can be set. One of those values is called "ADC Boost Gain"(I guess a programmable analog gain?).
I established a call with CSipSimple and successfully raised that parameter by 24dB in mid-call by executing "alsa_amixer -c 1 cset numid=20 2" [the default value was 0 and each step increases the level by 12dB]
You can query individual parameters by executing alsa_amixer -c X cget numid=Y
YMMV with the Nexus 4. Good luck!
Thank you! This looks really promising.
I only have "card0" aka [apq8064tablasnd].
When trying to execute "alsa_mixer -c 0 contents" I get an error stating that I'm missing
library "libasound.so". Any ideas what could be wrong?
I'm not sure whether libasound.so came with the AlsaMixer app. If it did you may need to copy the library into a system library path, e.g. /system/lib. If not, I could send you the library that I have. I actually forgot whether I found the library somewhere online or whether I cross-compiled it myself...
Sent from my Nexus 7 using xda app-developers app
ALSA on Nexus 4 sound capabilities
ALSAMixer in the Play Store was updated to support Nexus 4. See OP.
---------------------------------------------------------------
The attached file is the output of running
alsa_amixer -c 0
I'm new to ALSA and have trouble figuring out which one is the microphone gain control.
I have installed this app but unfortunately I don't know how to completely uninstall it help please?:thumbup:
..sent from space.
amarb70 said:
I have installed this app but unfortunately I don't know how to completely uninstall it help please?:thumbup:
..sent from space.
Click to expand...
Click to collapse
If I understand correctly the app is just an installer that puts the ALSA libraries on your system.
If you are not using them it probably doesn't matter if they are there or not. You can contact the app creator about it.
-Mindroid- said:
ALSAMixer in the Play Store was updated to support Nexus 4. See OP.
---------------------------------------------------------------
The attached file is the output of running
alsa_amixer -c 0
I'm new to ALSA and have trouble figuring out which one is the microphone gain control.
Click to expand...
Click to collapse
Post the output of
alsa_amixer -c 0 contents
Any labels containing "ADC gain" or "Boost" would be prime candiates
amarb70 said:
I have installed this app but unfortunately I don't know how to completely uninstall it help please?:thumbup:
..sent from space.
Click to expand...
Click to collapse
Restore your back up
Sent from my Nexus 4 using xda premium
alsa_amixer c- 0 contents
chdloc said:
Post the output of
alsa_amixer -c 0 contents
Any labels containing "ADC gain" or "Boost" would be prime candiates
Click to expand...
Click to collapse
Thank you for being so patient with me!
I'm such a Linux noob. It took me forever to figure out that I need 'su' to do anything.
I will update the OP to link to this file.
-Mindroid- said:
Thank you for being so patient with me!
I'm such a Linux noob. It took me forever to figure out that I need 'su' to do anything.
I will update the OP to link to this file.
Click to expand...
Click to collapse
Holy smokes! This is one complicated mixer! And I've seen many.
It may help in narrowing choices down by you capturing another
alsa_amixer -c 0 contents
while you are on a call and look at the diffs. While you do that (being on a call, but don't run anything else that may use audio such as music playback apps) also report the output of
cat /proc/asound/card0/pcm0p/sub0/status
to make sure that phone calls are actually routed through ALSA. Anything but "CLOSED" is good.
I do not have a Nexus 4 so I cannot help trying to find the best parameters for a given application. The app ALSAMixer should help I would think.
Does this program now actually display anything?
chdloc said:
Holy smokes! This is one complicated mixer! And I've seen many.
It may help in narrowing choices down by you capturing another
alsa_amixer -c 0 contents
while you are on a call and look at the diffs. While you do that (being on a call, but don't run anything else that may use audio such as music playback apps) also report the output of
cat /proc/asound/card0/pcm0p/sub0/status
to make sure that phone calls are actually routed through ALSA. Anything but "CLOSED" is good.
I do not have a Nexus 4 so I cannot help trying to find the best parameters for a given application. The app ALSAMixer should help I would think.
Does this program now actually display anything?
Click to expand...
Click to collapse
It's a long shot but if you are in the New York tri-state area I wouldn't mind meeting up and letting you mess around with the Nexus4.
The invitation is open to anyone with ALSA experience. I would love to learn more about it first-hand.
As far as I can tell:
- ALSAMixer installs the ALSA libraries and displays the control set. I tried modifying a value with it and it didn't work.
It's a matter of wrong syntax I think, I will contact the app creator about it.
- Terminal Emulator works. I was able to change the value of "AUX_PGA_LEFT Volume" with the following command:
alsa_amixer cset numid=54 39
I'm not sure what this one does yet but I will investigate later today.
- unfortunately, during a phone call "proc/asound/card0/pcm0p/sub0/status" (playback) as well as
"proc/asound/card0/pcm0c/sub0/status" (capture) report "closed". Earlier I tried recording a voice call from an app
and trying to prepare an audio stream with MediaRecorder.AudioSource.VOICE_CALL throws an exception.
- when recording an audio stream with MediaRecorder.AudioSource.MIC and CAMCORDER
"proc/asound/card0/pcm0c/sub0/status" reports audio stream parameters. I'm attaching the piped output of
"alsa_amixer -c 0 contents" during a voice call, recording with mic and recording with camcorder.
-Mindroid- said:
[...]
- when recording an audio stream with MediaRecorder.AudioSource.MIC and CAMCORDER
"proc/asound/card0/pcm0c/sub0/status" reports audio stream parameters. I'm attaching the piped output of
"alsa_amixer -c 0 contents" during a voice call, recording with mic and recording with camcorder.
Click to expand...
Click to collapse
This is fun...
There is certainly a difference between the "idle" set of parameters you had posted earlier and the ones that you took during a voice call.
I found some good information that explains the parameters here
https://github.com/psykick5/android_device_lge_mako/blob/master/snd_soc_msm_2x_Fusion3
Try to change numid=48 (i.e. 'ADC1 Volume') and numid=40 (i.e. 'DEC7 Volume'); these two parameters should change the microphone level, provided automatic gain control does not compensate for the changes.
(It bothers me, though, that the range of values shown by alsa_amixer and the ones shown in the above link don't match)
Make sure that the changes stick by issuing
alsa_amixer cget numid=X
For phone calls I would certainly change numid=65 (i.e. 'TX6 HPF cut off') from 0 (apparently really only a DC offset filter) to 2 (apparently a high-pass filter with a cutoff frequency of 150Hz), which would be good enough for HD voice.
chdloc said:
This is fun...
There is certainly a difference between the "idle" set of parameters you had posted earlier and the ones that you took during a voice call.
I found some good information that explains the parameters here
https://github.com/psykick5/android_device_lge_mako/blob/master/snd_soc_msm_2x_Fusion3
Click to expand...
Click to collapse
Great find! This seems to be exactly what we need.
Most intriguing there are also facilities for Voice Call and FM Radio audio streams. Those are not currently working on
the Nexus4 at the moment and this might shed some light on a possible solution.
I find some of their nomenclature confusing. They use "TX" for recording and "RX" for playback.
Also they seem to set values twice - :1:0 for turn off and :1:1 for turn on. Do I have to issue commands twice?
I confirmed with 'cget' that I am indeed setting values with 'cset'.
chdloc said:
Try to change numid=48 (i.e. 'ADC1 Volume') and numid=40 (i.e. 'DEC7 Volume'); these two parameters should change the microphone level, provided automatic gain control does not compensate for the changes.
(It bothers me, though, that the range of values shown by alsa_amixer and the ones shown in the above link don't match)
Make sure that the changes stick by issuing
alsa_amixer cget numid=X
Click to expand...
Click to collapse
It seems that DEC7 controls to the MICROPHONE stream and DEC6 the CAMCORDER.
I will focus my attention on these.
chdloc said:
For phone calls I would certainly change numid=65 (i.e. 'TX6 HPF cut off') from 0 (apparently really only a DC offset filter) to 2 (apparently a high-pass filter with a cutoff frequency of 150Hz), which would be good enough for HD voice.
Click to expand...
Click to collapse
I was wondering about that myself. There is very bad low frequency noise on video recordings so I will
definetly look into this.
-Mindroid- said:
I find some of their nomenclature confusing. They use "TX" for recording and "RX" for playback.
Click to expand...
Click to collapse
Actually, the nomenclature is quite common, TX, i.e. transmit [to the network] denotes the signal to be transmitted (taken from from microphone)
while RX is the receive signal [from the network] to be played back through a loudspeaker.
-Mindroid- said:
Also they seem to set values twice - :1:0 for turn off and :1:1 for turn on. Do I have to issue commands twice?
Click to expand...
Click to collapse
No, you will have to issue the command only once. Without having looked at the underlying code I tend to think that the first number denotes the type, i.e. integer vs string, and the second number the actual value.
Another interesting observation is that the SoC of the Nexus 4 seems to support SRS TruMedia via an effects mixer, which reportedly has potential to improve audio considerably (http://www.srstechnologies.com/content.aspx?id=1269 , I believe).
Hey guys i was looking arroun xda and stumbled appon this. http://forum.xda-developers.com/showthread.php?t=1961353.
EDIT: TESTED DOES NOT WORK!!
It says it
-Increase internet speed (EDGE, 3G, WLAN, VPN). Works with all browsers including Opera with all APNs.
- Compressing pages and then decompressing for less data usage & smooth browsing.
- Bypass slow downloads and let you full speed downloads from some file sharing site which requires premium account for fast downloads. Like depositfiles etc.
- Boosting network signal strength so to have no call drops.
Click to expand...
Click to collapse
I have been running iy for about 7 hours now, and have to say that it does do some of what it claims.
3g speed seems to have increased and remain steady at over 1mbps. However wifi (wlan) seems no faster but no worse either. I did not test vpn as i do not have one setup.
The browser compression also seems to work, as pages load quicker. It also seems the whole page loads all at once instead of piece by piece.
The full speed downloads dosent seem to work, at least not from depositfiles.
The network signal boot also dosent work, as my db's are the same as usual, high 80s to low 90s.
Even though several things dont seem to work, they dont break anything either. I think just for the 3g tweak and browser compression, it is worth it. Also i know it says for android 2.3.6+, but works fine on 2.3.4.
I don't expect much from these type of tweaks and think they're more placebo than anything. There's nothing on the ROM side that can improve signal.
Browser compression sounds like an interesting idea. If you're familiar with the protocol rsync, it can use compression to transfer and use less bandwidth. However, I haven't heard of compression remote webpages prior to sending them which is really the only way this would logically work. That doesn't mean it doesn't exist.
The 3g speed tweak I'm also wary of. I think it may be placebo as network speeds vary and Verizon can already achieve 1mbps+ on their network.
As far as the bypassing slow downloads, that's definitely possible; however, it sounds wrong.
The only differences between Android 2.3.6 and 2.3.4 are a few bug fixes.
Edit: A little extra feedback after viewing the script.
I don't think any of the service lines will actually work as some of these look designed for init.rc, not init.d which is shell scripts.
As far as the network signal strength booster, it calls a legacy device script (goldfish which is the emulator and not a real device).
Not sure about the speed tweaks or slow download bypassing.
tiny4579 said:
I don't expect much from these type of tweaks and think they're more placebo than anything. There's nothing on the ROM side that can improve signal.
Browser compression sounds like an interesting idea. If you're familiar with the protocol rsync, it can use compression to transfer and use less bandwidth. However, I haven't heard of compression remote webpages prior to sending them which is really the only way this would logically work. That doesn't mean it doesn't exist.
The 3g speed tweak I'm also wary of. I think it may be placebo as network speeds vary and Verizon can already achieve 1mbps+ on their network.
As far as the bypassing slow downloads, that's definitely possible; however, it sounds wrong.
The only differences between Android 2.3.6 and 2.3.4 are a few bug fixes.
Click to expand...
Click to collapse
The browser compression and 3g seem to work, pages load faster and seem snappier. I know vzw is capable of 1mbps, but i rarley ever got half that before the tweak. Now i get it consitentlty at all times of the day. I dont think its placedo, and the the poll on that thread suggest people are happy with it. Its worth a shot if you have some free time. And its easy to remove if you dont like it, just delete 2 files and a folder
cmlusco said:
The browser compression and 3g seem to work, pages load faster and seem snappier. I know vzw is capable of 1mbps, but i rarley ever got half that before the tweak. Now i get it consitentlty at all times of the day. I dont think its placedo, and the the poll on that thread suggest people are happy with it. Its worth a shot if you have some free time. And its easy to remove if you dont like it, just delete 2 files and a folder
Click to expand...
Click to collapse
Try running it from the terminal or adb shell by doing sh init.d script name and I'm pretty sure it will bomb out on you like it did for me. I tried the bottom one and the second attachment from the OP there.
Below is my error:
Code:
[email protected]:/storage/sdcard0 # sh netforks_tweak
netforks_tweak[12]: syntax error: '(' unexpected
tiny4579 said:
Try running it from the terminal or adb shell by doing sh init.d script name and I'm pretty sure it will bomb out on you like it did for me. I tried the bottom one and the second attachment from the OP there.
Below is my error:
Code:
[email protected]:/storage/sdcard0 # sh netforks_tweak
netforks_tweak[12]: syntax error: '(' unexpected
Click to expand...
Click to collapse
Lol, never even thought of trying that. Your right i het the same error. The init-goldfish.sh file that the init.d script runs also fails on execution, but that is a stock system file. I wonder why my 3g speeds are better? Im getting double what i usually get, and its actually consistent and not bouncing all over the place. Mabey vzw put up a new tower or something. And i guess with increased speed the browser would seem snappier. Oh well thought i stumbled on something cool, but its just garbage i guess. Thanks for clearing it up tiny.
cmlusco said:
Lol, never even thought of trying that. Your right i het the same error. The init-goldfish.sh file that the init.d script runs also fails on execution, but that is a stock system file. I wonder why my 3g speeds are better? Im getting double what i usually get, and its actually consistent and not bouncing all over the place. Mabey vzw put up a new tower or something. And i guess with increased speed the browser would seem snappier. Oh well thought i stumbled on something cool, but its just garbage i guess. Thanks for clearing it up tiny.
Click to expand...
Click to collapse
According to the dev, the ( error is ok.
So, if you want to test it again to verify, type getprop and see if anything shows from the tweaks script as far as the setprop lines. I have a feeling nothing will but I want to validate 100% that this doesn't work.
I've done some testing on my own by making shell scripts and confirming an error should not bomb out the whole script but just abort at the point of the error.
But really, this thing does nothing, even zeppelinrox shot it down.
tiny4579 said:
According to the dev, the ( error is ok.
So, if you want to test it again to verify, type getprop and see if anything shows from the tweaks script as far as the setprop lines. I have a feeling nothing will but I want to validate 100% that this doesn't work.
I've done some testing on my own by making shell scripts and confirming an error should not bomb out the whole script but just abort at the point of the error.
But really, this thing does nothing, even zeppelinrox shot it down.
Click to expand...
Click to collapse
No nothing from the script shows in getprop. I would say the whole things a bust.
I found this post here: http://forum.xda-developers.com/showpost.php?p=34644359&postcount=4899
- Squelch function, mostly intended for listening to sporadic emergency service broadcasts (Japan band in Germany), but may also be useful for anyone who wants audio muted when RSSI is low.
Set Menu-> Settings-> Alternate Frequency/Squelch-> AF Mode to "Squelch". Ensure Alt Freq = 0 and set AF RSSI Threshold to desired RSSI value. Default 16 seems OK on most FM chips.
Now, the RSSI will be checked every 0.5 seconds by default. Set AF Period to desired period in milliseconds to set. If RSSI is low, audio is muted, if high, un-muted.
Click to expand...
Click to collapse
I can't find that options in my Spirit2 App. Is there a way to get this working on Spirit2 or is this just a feature of Spirit1?
kl2e said:
I found this post here: http://forum.xda-developers.com/showpost.php?p=34644359&postcount=4899
I can't find that options in my Spirit2 App. Is there a way to get this working on Spirit2 or is this just a feature of Spirit1?
Click to expand...
Click to collapse
No, it's just a Spirit1 feature.
Spirit1 pretty much has all features of Spirit2, except the new UI, BTW.
mikereidis said:
No, it's just a Spirit1 feature.
Spirit1 pretty much has all features of Spirit2, except the new UI, BTW.
Click to expand...
Click to collapse
Is Spirit1 running on a LG G3 D855 with CM 12 ?!?
kl2e said:
Is Spirit1 running on a LG G3 D855 with CM 12 ?!?
Click to expand...
Click to collapse
I'm getting this Error on Spirit UL:
Error: NO FM accessible
SU: 2 Fm: ?? Su:1 Bt:0 Ht:0
Click to expand...
Click to collapse
Which Audio Method or FM-Chip do I have to configure to get this working... ???
kl2e said:
I'm getting this Error on Spirit UL:
Which Audio Method or FM-Chip do I have to configure to get this working... ???
Click to expand...
Click to collapse
I sent you a beta of Spirit1 that is needed for Lollipop Android 5+, and instructions to enable Squelch. But it may not work on all ROMs, and on some, SELinux may need to be disabled.
LG G3 is Qualcomm I think, But I've had little feedback about it.
Default audio is "Non-Digital" (actually, it is, but can't use EQ/BT etc.) If you want full digital audio like on Spirit2, set Audio-> Method to Digital Auto or Digital QCom near end of list.
Default settings are usually fine, but FM Chip is called "QC V4L (HTC)" on Spirit1.