Alex asked me to put a test together for Jerome's new audio routing code. This is a prerequisite to Bluetooth audio, so we'd like to get it into the mainline as soon as possible. This test is for Froyo only.
Update: See post #2 for info on testing Bluetooth with this code.
This includes a new kernel and modules, plus a set of new libraries. You will also need to add a couple commands to your /init.rc to make it work. You also need to copy all of the *.csv files from your \Windows directory to the root of your SDcard.
With this installed your in-call audio should be more reliable, with fewer glitches (e.g. suddenly turning on speakerphone at random) etc. Also, for me, this fixed the audio track in video recording. (Before, I got no audio from the camcorder, now it's there.)
In your /init.rc you'll need to add
Code:
chmod 666 /dev/htc-acoustic_wince
chmod 666 /dev/tpa2016d2
Search through the init.rc for "XDAndroid" and you'll see a block of chmod commands. Just add this to those others. Remember that normally the rootfs copies /init.cfg/init.froyo.rc to /init.rc on bootup, so you need to edit the init.cfg file if you want your change to take effect. And you must reboot for it to take effect. (If you're using my rootfs, you just edit /init.rc directly.)
The libraries need to be installed in /system/lib. The easiest thing will probably be to bind mount them in your user.conf. If you've been testing other features here you should already know how to do that so I won't explain in this thread.
Note:
In addition to all of the 20110510_201546 autobuild kernel code, this kernel also has WisTilt2's power manager and framebuffer fixes, as well as button lights. Also, it has my sleep LEDs - solid green means a wakelock is present, blinking green means the phone is asleep. Don't confuse this with WisTilt2's previous testing kernels.
The libraries were built from the froyo branch of this repo https://gitorious.org/~jbruneaux/xdandroid/hardware_msm7k_libacoustic
The kernel patches were taken from the htc-msm-2.6.27-libacoustic branch of this repo https://gitorious.org/~jbruneaux/linux-on-qualcomm-s-msm/linux-msm-home-work, commit ID 0fe09c9cb680ebff94bbd9bf30f787a2d5da6e9b and cleaned up to apply against the mainline kernel source.
Update: I've been getting a lot of failed wakes/SoDs with the 01323 kernel. We have a suspicion that it's due to the latest framebuffer patch from the mailing list, so I've reverted that specific patch and uploaded the resulting 01324 kernel. It's kind of sloppy of me to mix two different experiments together like this, but if you experience hangs with 01323, post a response here and try 01324 instead.
And what I should have done from the beginning... The 01319 kernel here is just the autobuild kernel plus the audio patches, nothing else.
Bluetooth! - already included in FRX07
All of this has already been integrated in FRX07. Ignore this.
OK. I was curious; supposedly the kernel has had complete support for Bluetooth for a while now but we're still missing some stuff in userland. Well, I chased down the missing pieces, tried it, and it works!
I only know how to set this up for Rhodiums, using the Broadcom radio chip. If you're on some other phone, with TI chip, I don't know how to help you.
You need to copy the BCM4325*.hcd files from your \Windows directory onto the root of your SDcard. On my phone there were two files, BCM4325D0..(bunch of crap).hcd and BCM4325D1..(bunch of crap).hcd. The BCM4325D1 file is the one that worked for me. You may have to try them both out.
You will have to edit your /init.rc and replace the current hciattach info with this instead:
Code:
service hciattach /system/bin/brcm_patchram_plus -r --enable_hci \
--enable_lpm --baudrate 4000000 \
--patchram /system/etc/BCM4325.hcd /dev/ttyHS1
I copied my hcd file to /system/etc/BCM4325.hcd but you may just want to create a symlink to the file on your SDcard. Whatever you do, you have to make sure that this is pointing to a valid hcd file.
Remember that normally the rootfs copies /init.cfg/init.froyo.rc to /init.rc on bootup, so you need to edit the init.cfg file if you want your change to take effect. And you must reboot for it to take effect. (If you're using my rootfs, you just edit /init.rc directly.)
You must use the brcm_patchram_plus binary that I've attached here. The source for it is in JB's repo https://gitorious.org/system_bluetooth/system_bluetooth . Remember to chmod it 755 after you extract it and install it.
Once the files are installed, reboot and it should all be working. I've tested an audio headset and OBEX file transfers, both worked without any trouble. I believe the OBEX stuff will work in the autobuild kernel too, but you need the audio routing support in this kernel to get Bluetooth audio.
[reserved...]
Hmmm...on my Rhod400 (Sprint) I have added the zimage/modules, added the chmod line to the conf file and bind mounted the files and now I do not have any "non-call" audio...phone calls sound great and I do not hear any static when in speakerphone (although the volume control does not seem to raise/lower speakerphone volume)...it is getting late though so I think I will get some sleep and see if I screwed something up in the morning...
I am very excited about this though!
Did you also copy the *.csv files?
Thanks, highlandsun!
But, you can compile your test kernel with modules that supports tiwlan?
If it not so hard.
Uh... This is the TouchPro2/Tilt2 *RHODIUM* section. I thought it would be obvious that this test is only for Rhodium. Rhodium only uses Broadcom.
Sorry guys, the first kernel I uploaded was from an incomplete revision of the audio patches. I've uploaded another one kernel-01323.zip that has everything. This corresponds to the autobuild plus all of the audio code in JB's tree as of April 12.
highlandsun said:
Did you also copy the *.csv files?
Click to expand...
Click to collapse
Yes I did...not sure what else to do...don't see anything weird in the logcat...anyone else with a Rhod400 try this yet?
pdawg17 said:
Yes I did...not sure what else to do...don't see anything weird in the logcat...anyone else with a Rhod400 try this yet?
Click to expand...
Click to collapse
I have, still not working... Trying to retrace the steps, everything *looks* correct...
arrrghhh said:
I have, still not working... Trying to retrace the steps, everything *looks* correct...
Click to expand...
Click to collapse
Same problem then? No audio other than in-call?
pdawg17 said:
Same problem then? No audio other than in-call?
Click to expand...
Click to collapse
I'm just trying out BT, haven't really even tested audio...
After trying a phone call, I get no audio on incoming or outgoing calls. I surely messed something up here... I don't even hear the ringing sound on the outbound call .
arrrghhh said:
I'm just trying out BT, haven't really even tested audio...
After trying a phone call, I get no audio on incoming or outgoing calls. I surely messed something up here...
Click to expand...
Click to collapse
Maybe BT isn't working for you because the underlying audio part in post #1 is not working right for Rhod400...I haven't even tried to get BT going...
pdawg17 said:
Maybe BT isn't working for you because the underlying audio part in post #1 is not working right for Rhod400...I haven't even tried to get BT going...
Click to expand...
Click to collapse
I'm gonna start over. I don't know what I messed up, but I obviously messed something up. In trying to verify everything, it all *looks* ok... but it most certainly is not ok! I'll start with a fresh build, no messin around .
I realize GRX is not the focus of this, but figured the feedback may be useful nonetheless.
Audio: Almost completely broken by the patches. Made 4 phone calls, 3 had no sound whatsoever (including ringing), 4th had sound for a split second and then cut out with no sound. Toggling speakerphone made no difference. Audio played by the Music app has no sound, ringtones have no sound.
Bluetooth: No surprises here given how unfinished Bluetooth is on GRX, but doesn't work. Attempting to turn it on displays turning on for a few seconds, and then it reverts to the unturned on state.
manekineko said:
I realize GRX is not the focus of this, but figured the feedback may be useful nonetheless.
Audio: Almost completely broken by the patches. Made 4 phone calls, 3 had no sound whatsoever (including ringing), 4th had sound for a split second and then cut out with no sound. Toggling speakerphone made no difference. Audio played by the Music app has no sound, ringtones have no sound.
Bluetooth: No surprises here given how unfinished Bluetooth is on GRX, but doesn't work. Attempting to turn it on displays turning on for a few seconds, and then it reverts to the unturned on state.
Click to expand...
Click to collapse
Same for Froyo? I'd use Froyo as a baseline, and then see what works in GB... if it doesn't work in Froyo, it certainly won't in GB (at least that seems like a fairly safe assumption ).
I'm having the sound issues as well, but fully blame my coding errors. If someone gets a complete working build for us Rhod400 users and would like to share, that would be awesome.
In the meantime, I'll keep plugging away at my very limited ability to modify system files...
Hrm, fresh build of FRX06 with just the first post audio changes - not even touching BT until I get that first post solid... no audio. It's completely muted, incoming calls, outgoing calls, anything in the UI... no audio from the system whatsoever.
Hmmmm.... I can't seem to find any .csv files in my /windows folder. Anyone seen these guys yet? How many are there? Maybe an actual file name?
Thanks!
Serren said:
Hmmmm.... I can't seem to find any .csv files in my /windows folder. Anyone seen these guys yet? How many are there? Maybe an actual file name?
Thanks!
Click to expand...
Click to collapse
AudioFilterTable.csv
AudioPara.csv
AudioPara3.csv
AudioPara3_ATT.csv
AudioPara3_Boot.csv
AudioPara3_TMO.csv
AudioPreProcessTable.csv
DualMic.csv
DualMic_ATT.csv
DualMic_TMO.csv
TIAGC.csv
If you use Total Commander and touch the header for filename/ext it will sort by extension.
Serren said:
Hmmmm.... I can't seem to find any .csv files in my /windows folder. Anyone seen these guys yet? How many are there? Maybe an actual file name?
Thanks!
Click to expand...
Click to collapse
They are hidden files.
Use total commander to find them and copy them.
Related
Any chance this can happen? My old Droid Incredible could do this stock or rooted. It really comes in handy when you're trying to take pics discretely in public.
You can turn your media sounds to quiet. That's the only workaround setting at the moment. But yeah +1 to this mod/app/whatever.
if there is no app and you're rooted just move /system/media/audio/ui/camera_click.ogg to another folder when you want it silent.
i used to just delete it in my themes for the desire.
Or with tasker set it to mute volume when in the camera app, easiest automated workaround
Sent from my Galaxy Nexus using XDA App
I just turn the phone main volume down. On the side of the phone. Works for me.
str355 said:
if there is no app and you're rooted just move /system/media/audio/ui/camera_click.ogg to another folder when you want it silent.
Click to expand...
Click to collapse
Just rename it to camera_click.ogg.bak
itch808 said:
Any chance this can happen? My old Droid Incredible could do this stock or rooted. It really comes in handy when you're trying to take pics discretely in public.
Click to expand...
Click to collapse
If your phone is rooted, you can replace the audio file.
The original file can be foun in: system/media/audio/ui/camera_click.ogg
adb root
adb remount
adb shell
mv system/media/audio/ui/camera_click.ogg system/media/audio/ui/camera_click.ogg.bak
I just delete the camera_click.ogg file, been doing it that way for quite awhile. Quick and easy. Only issue is that I have to repeat this when I install new ROM.
I may be missing something obvious here, but is there a way to disable the "tap to focus" sound as well? I had no trouble disabling the "click" ogg, but none of the other files in the directory seem to be the one that the camera makes when focusing.
Protected
I have Galaxy Nexus. Not rooted. Therefore volume down does not kill the 'click' of the shutter and the file ...ogg cannot be deleted. In simple words, seems no solution to silent camera's click.
This is done to comply with US laws relating to privacy, and imposed by Samsung (or Google) worldwide... Whether we like it or not (I don't like it, btw) - is not a matter to debate in this technical forum
root or not, it works, try again
rllek said:
I may be missing something obvious here, but is there a way to disable the "tap to focus" sound as well? I had no trouble disabling the "click" ogg, but none of the other files in the directory seem to be the one that the camera makes when focusing.
Click to expand...
Click to collapse
yeah, i thought it was fairly obvious...
rename/move camera_focus.ogg which is in the same location as camera_click.ogg
Deleting them works fine. I have deleted almost all of the sounds in the media folder.
The GNex's camera isn't that great for upskirt pics anyway.
mikisi said:
I have Galaxy Nexus. Not rooted. Therefore volume down does not kill the 'click' of the shutter and the file ...ogg cannot be deleted. In simple words, seems no solution to silent camera's click.
This is done to comply with US laws relating to privacy, and imposed by Samsung (or Google) worldwide... Whether we like it or not (I don't like it, btw) - is not a matter to debate in this technical forum
Click to expand...
Click to collapse
There is a 'phone mods' section in my ToolKit to rename the camera/camcorder sounds. Stock Rom users are covered as the ToolKit can boot an insecure boot image to your phone to give it temporary root access and allow the files to be renamed.
Mark.
mrvirginia said:
yeah, i thought it was fairly obvious...
rename/move camera_focus.ogg which is in the same location as camera_click.ogg
Click to expand...
Click to collapse
That only works in 4.0.3 Roms. In earlier builds renaming or deleting the file doesnt mute the focus sound although the other sounds can still be muted.
Mark.
This app can mute the shutter and doesn't require root.
http://forum.xda-developers.com/showthread.php?t=1475098
EP2008 said:
This app can mute the shutter and doesn't require root.
http://forum.xda-developers.com/showthread.php?t=1475098
Click to expand...
Click to collapse
Probably because it set the sounds internally within the app itself and doesnt use the external system sounds. That way they can be enabled/disabled from within the app without needing root to rename the existing files
Shame the free version has ads in the worst possible location lol..
Mark.
mskip said:
That only works in 4.0.3 Roms. In earlier builds renaming or deleting the file doesnt mute the focus sound although the other sounds can still be muted.
Mark.
Click to expand...
Click to collapse
Works for me though on Android Revolution HD ROM on 4.0.2
Focus sound is nowhere to be seen! Not in the same directory as the shutter sound.
Audio Modifications
DISCLAIMER:
I am not responsible for problems you may incur.
Please do some research if you are a first timer.
Only you can choose to use this software.
By downloading you agree to these terms.WHAT THIS TWEAK DOES:
This flash-able Volume-tweak.zip includes both mods simultaneously.
1) Silent Camera!
Volume.db
Replacing the existing volume.db file, the one I'm including disables all shutter sounds (which I may change to one of the shutter sounds), autofocus sounds, and other obnoxious camera tones. I understand that Samsung's idea is to make people aware that others may be photographing them, privacy stuff and all, but let's be honest shall we? Creepers are going to creep one way or another, and the autofocus 'beep' disturbs the baby and makes the dog bark! It also disables the boot sound. Best part of this tweak, it doesn't even touch the actual camera apk!
2) Volume Enhancing!
default_gain.conf
The next is a mod adapted from the developer Meltus. You may know him for other awesome volume modifications, but this one he made for the GSIII international. This should make the phone overall louder in all respects. I have, however, adjusted it from his original settings to keep the volume from reaching 'crackling' volumes and possibly damaging the speakers. This level sounds loud and still sounds good. :good:
DOWNLOADS:
Flash the following file through CWM:
Volume-Tweak [MIRROR]
Hand-Tested on my stock rooted SPH-L710.
CREDITS:
A Huge thanks to Meltus for the volume modifications. Meltus' Thread
Want to make or edit your own personal rom?
Take a look at my personal kitchen!
Files Modified
Files located\installed under system\etc:
Volume.db - Controls system sounds.
default_gain.conf - Amplifies system volume.
Do you have this mod working on your device? I ask because I got burned on the teh kernel, and I'm a little more cautious about what I flash from now on.
swampy67 said:
Do you have this mod working on your device? I ask because I got burned on the teh kernel, and I'm a little more cautious about what I flash from now on.
Click to expand...
Click to collapse
It's brilliantly simple. Most android phones come with these settings ingrained into the kernel, but Samsung has left them out. In theory, one could make these adjustments from on the phone itself, if you can open a .db file. Very simple, nothing that can break a phone. Just be careful not to blow out your speaker or your ears.
Sweet, Camera sounds really annoys me.
Time to creep!!! (on my kids ) lol
edit: flashed and tested camera. No sounds on focus and snapshot so :good:
bizdady said:
Sweet, Camera sounds really annoys me.
Time to creep!!! (on my kids ) lol
Click to expand...
Click to collapse
Lmao
Sent from my SPH-D700 using XDA Premium App
bizdady said:
edit: flashed and tested camera. No sounds on focus and snapshot so :good:
Click to expand...
Click to collapse
Sweet! :highfive:
As an addendum, this tweak is even neater because it disables the camera noises on a system level. I've seen a supposed higher-resolution camcording camera apk floating around that 'supposedly' disables camera noises as well... but it doesn't matter if it does because this tweak stays in effect. I don't believe this will affect other camera apps... but any Samsung camera variant should be muted.
Random you rock. Great to see you here. Your OG epic stuff was awesome. Thanks for the sound free camera!
Randomking ive seen your work before amazing stuff glad this got ported i was gonna try to port the volume mod but still no phone yet =( thanks a million anyways
Thanks for this mod. It works great. Would it be possible to mute the lock/unlock noises? I love water but I'm a little tired of hearing water droplets every time I use my phone.
Sent from my SPH-L710
Hiro14 said:
Thanks for this mod. It works great. Would it be possible to mute the lock/unlock noises? I love water but I'm a little tired of hearing water droplets every time I use my phone.
Sent from my SPH-L710
Click to expand...
Click to collapse
Settings\Sound Scroll down to Screen Lock Sound.
Hiro14 said:
Thanks for this mod. It works great. Would it be possible to mute the lock/unlock noises? I love water but I'm a little tired of hearing water droplets every time I use my phone.
Sent from my SPH-L710
Click to expand...
Click to collapse
You can turn that off in Settings > Sound.
Untick Touch Sounds and Screen lock sound
I cannot believe I missed that for so long.
Many thanks kind sir(s).
Sent from my SPH-L710
Hiro14 said:
Thanks for this mod. It works great. Would it be possible to mute the lock/unlock noises? I love water but I'm a little tired of hearing water droplets every time I use my phone.
Sent from my SPH-L710
Click to expand...
Click to collapse
You can disable this already without mods.
Settings> Sound> uncheck Screen lock sound and Touch sound
For the sound boost (using the international tweak) you used the config file, correct?
That file does not, by default, exist on our US variants. I've personally included the tweak in my ROM over on T-Mobile. I've had a person or two say it made no difference. Me personally, I thought it was louder then hell (changed speaker boost from 0 to 40 and headphones from 0 to 25). If I put the volume on the lowest possible setting, its very audible still. With my headphones, I put it on three ticks and it was loud. Putting it up fully made me feel like my eardrums were going to pop.
What are your feelings on the tweaks? Do you think they actually work? Considering the config file doesn't exist by default, do you think they're actually pointed to in our system to be used?
uoY_redruM said:
For the sound boost (using the international tweak) you used the config file, correct?
That file does not, by default, exist on our US variants. I've personally included the tweak in my ROM over on T-Mobile. I've had a person or two say it made no difference. Me personally, I thought it was louder then hell (changed speaker boost from 0 to 40 and headphones from 0 to 25). If I put the volume on the lowest possible setting, its very audible still. With my headphones, I put it on three ticks and it was loud. Putting it up fully made me feel like my eardrums were going to pop.
What are your feelings on the tweaks? Do you think they actually work? Considering the config file doesn't exist by default, do you think they're actually pointed to in our system to be used?
Click to expand...
Click to collapse
I too noticed that the file isn't there, and was momentarily skeptical. But as the base coding is likely fundamentally identical, I thought I'd give it a chance. It's hard to fully test while at work... but I can hear my mp3 alarms quite clearly now. I had made a thread days ago regarding how my songs play fine in the player, but at half volume as alarms. The alarm was much much louder! And I generally have a fairly discerning ear.
That said, I now have to experiment the individual settings I think.
RandomKing said:
I too noticed that the file isn't there, and was momentarily skeptical. But as the base coding is likely fundamentally identical, I thought I'd give it a chance. It's hard to fully test while at work... but I can hear my mp3 alarms quite clearly now. I had made a thread days ago regarding how my songs play fine in the player, but at half volume as alarms. The alarm was much much louder! And I generally have a fairly discerning ear.
That said, I now have to experiment the individual settings I think.
Click to expand...
Click to collapse
I agree the coding is likely identical. My skepticism comes more from the fact that the file doesn't exist by default. If it doesn't exist, and we add it, does anything in our system actually point to the config file in order for it to actually take effect?
Regardless, I'm pretty positive it works. I just was hoping someone had a better understanding of how it works and if it's actually pointed to.
When you play around with it, mind PMing me your results? I'm curious what you get.
For one, change the headphone settings and try with your headphones plugged in. I think they're extremely loud with the boost set to 25..
uoY_redruM said:
I agree the coding is likely identical. My skepticism comes more from the fact that the file doesn't exist by default. If it doesn't exist, and we add it, does anything in our system actually point to the config file in order for it to actually take effect?
Regardless, I'm pretty positive it works. I just was hoping someone had a better understanding of how it works and if it's actually pointed to.
When you play around with it, mind PMing me your results? I'm curious what you get.
For one, change the headphone settings and try with your headphones plugged in. I think they're extremely loud with the boost set to 25..
Click to expand...
Click to collapse
Certainly. If different values draw drastically different effects... I'll probably be making a "Louder but comfortable" version and an "Extremely loud, hearing damage may ensue" version. :good:
Revert.zip???
Any way to revert this?
jdmusicman72 said:
Any way to revert this?
Click to expand...
Click to collapse
There will be, but I have to write up the script to delete the conf file later. The volume.db file need only be replaced by the stock one.
Made This because i see the same question/bugs referenced in the cm thread over and over for each build so I figured id place them all here so people wont have to look. And will know its a problem to start with and to keep the general talk out of the original development forum/aid the developers with a plain list of bugs/workarounds.
Feel free to add anything im missing.
To enable developer options:
settings---) about ---) scoll to the bottom and tap build number like 8x
now power menu reboot options are there also as a safety feature
Build
Jan 24 2013
A2DP IS NOW FIXED
headphone button hangup does not work
wifi tethering on stock kernel dont work (use kt's or a kernel that says wifi fixed)
Enabling "AirPlane" mode when Bluetooth is on and in-use causes it to forever be stuck in "Turning off Bluetooth..." status. Only a reboot will fix it.
when calling an 800 or automated number you cant dial a number at a prompt. For instance "Press 1 for english" doesn't work sometimes hapens when trying to answer gv with call screening every 1 in 10 or so
Can someone pleaseee confim that bluetooth is 100% fixed it works fine for me on kt
Build
Jan 4 2013
Keyboard/touch screen a little wonky try changing the hwoverlay settings in developer options works for some.. fixed in 1/3?
Call volume low:
The in call volume bug will continue to exist until the audio enhancements ( IE DUAL MIC) are finished and merged in. For now goto phone > settings and uncheck "Noise suppression". its not a fix but it helps.
Click to expand...
Click to collapse
music players not working or fc? [/QUOTE]Download rom toolbox and open the build.prop editor search for lpa.decode=true and change it to lpa.decode=false[/QUOTE] Seems to be working as of 1/3
Camera Crashes :
just close it and clear data start again works fine from there on out
Click to expand...
Click to collapse
Bluetooth A2DP :
bluetooth voice dial does not work in cm10 or cm10.1. It opens but cannot "hear" any commands.
Disable voice dial in "manage apps", then install "Bluetooth launch" from the play store. After this, set it to launch activity "com.Google.android.googlequicksearchbox.voicesear chactivity" under the "Google search" application.
Now connect your Bluetooth device, press the button you would normally use to initiate voice dial, and tap "Bluetooth launch" when prompted, then tap always use.
have to use the voice command button twice, but it works like a charm!
Click to expand...
Click to collapse
BT A2DP not functioning properly some say to make a call and hang up using bluetooth
GPS shows locked in notification drawer even after being turned off
Camera:
gtuansdiamm said:
When using ffc on camera mode switching to video mode screws color
Work around. Using the 8mp camera I in video mode and switch to ffc
Color is fixed but it is still a bit wonky
Click to expand...
Click to collapse
* unconfirmed
NO GPS?
flash back to any tw rom get a lock and then flash back to cm/aokp
Memory:
CNexus said:
"I can't find my apps and/or documents and/or anything thats supposed to be on my sdcard!"
From JB and up everything that was on the root of the sdcard (in previous versions) is now located inside the "0" folder
Click to expand...
Click to collapse
Screen wakes: screen wake only on stock kernel use ktoonsez kernel make sure min mhz is stock * possibly fixed in 1/3?
4g: ehrdp hand off still a bit wonky toggle airplane mode if it has trouble not sure. some reports of it working find others its.*
App switcher bug please confirm?
anything else? submit a reply and ill ad it to the op! your help is appreciated!
Bug fixed? as bugs get squahsed ill remove them again this is ment as a running list cuz theres no bug tracker
Dreamlogix said:
Made This because i see the same question/bugs referenced in the cm thread over and over for each build so I figured id place them all here so people wont have to look. And will know its a problem to start with and to keep the general talk out of the original development forum/aid the developers with a plain list of bugs/workarounds.
Feel free to add anything im missing.
To enable developer options:
settings---) about ---) scoll to the bottom and tap build number like 8x
Build
Jan 1 2013
Keyboard a little wonky try changing the hwoverlay settings in developer options works for some..
you think the call volume is too low? get volume+ in the play store
music players not working? Download rom toolbox and open the build.prop editor search for lpa.decode=true and change it to lpa.decode=false
Camera Crashes on first start: just close it and clear data start again works fine from there on out
random Bluetooth problems? not sure. some reports of it working find others its a lil buggy possible work around is make a call and hang up then streaming works.
GPS shows connected even after being turned off
Click to expand...
Click to collapse
Volume+ is a placebo
Sent from my SPH-L710 using xda premium
When using ffc on camera mode switching to video mode screws color
Work around. Using the 8mp camera I in video mode and switch to ffc
Color is fixed but it is still a bit wonky
Sent from my SPH-L710 using xda premium
Edit: it could have been that I had the color effect neon on
I though it did nothing since it was on top and in 8mp camera mode it did nothing
The color effect none is on the bottom
rrmzr1 said:
Volume+ is a placebo
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
how about voodoo? i know it wasent on the s2 and s1 it allowed positive db amp
"I can't find my apps and/or documents and/or anything thats supposed to be on my sdcard!"
From JB and up everything that was on the root of the sdcard (in previous versions) is now located inside the "0" folder
--
Btw, really good idea OP :good:
rrmzr1 said:
Volume+ is a placebo
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Ya I don't see a option for the earpiece speaker. Just the main back speaker. Anything else that will fix the low in call volume?
Sent from my SPH-L710 using Tapatalk 2
ooxteme said:
Ya I don't see a option for the earpiece speaker. Just the main back speaker. Anything else that will fix the low in call volume?
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Try voodoo
Just installed cm10.1 again and the screen randomly flashes sometimes. Fix for that?
Sent from my SPH-L710 using xda app-developers app
DerIdiot said:
Hey all, any idea why when I try to play music or videos with sound the phone freezes hard? I have been having the issue on CM nightly 12-24, 29 and 30th. I'm sure there's just an app that needs data wiped.
Any help appreciated.
Click to expand...
Click to collapse
DerIdiot said:
Hey all, found a solution:
Use "File Explorer" with root access, go into /system/build.prop - scroll down until you see lpa.decode=true and change it to false, save and close and reboot.
Seems to work for now, though I imagine any new nightlies will require doing this at least for a while until they fix it.
Click to expand...
Click to collapse
---
@haynesr07, did you do a complete wipe? several times even? Sometimes stuff can leak through from your last rom and mess with your settings in your new rom, try clearing everything a couple times (2 or 3 times per item) and flash again
Also if you restored any data, that might be it, I've seen weird problems when people do that...I don't think this issue is rom specific though or it wouldnt be stable enough to be released
CNexus said:
---
@haynesr07, did you do a complete wipe? several times even? Sometimes stuff can leak through from your last rom and mess with your settings in your new rom, try clearing everything a couple times (2 or 3 times per item) and flash again
Also if you restored any data, that might be it, I've seen weird problems when people do that...I don't think this issue is rom specific though or it wouldnt be stable enough to be released
Click to expand...
Click to collapse
aye thanks m8
CNexus said:
---
@haynesr07, did you do a complete wipe? several times even? Sometimes stuff can leak through from your last rom and mess with your settings in your new rom, try clearing everything a couple times (2 or 3 times per item) and flash again
Also if you restored any data, that might be it, I've seen weird problems when people do that...I don't think this issue is rom specific though or it wouldnt be stable enough to be released
Click to expand...
Click to collapse
I wiped everything as usual...Hm, wonder what happened. Happened on liquid too..
haynesr07 said:
I wiped everything as usual...Hm, wonder what happened. Happened on liquid too..
Click to expand...
Click to collapse
you wiped system and factory reset and caches and then fixed permissions.
http://db.tt/GJ2NYrlb
This is the current build props i use. Leave out the Bootanimation one if you want to keep your boot animation. Do not edit buildprop if you have no experience. Look up the proper way to use them, Dreamlogix explainsto use rom toolbox above. Dont add all in. Check if value exists and change to the new value. If an entry is missing add it but dont assume its not there because double entries cause issues and if you mess up your build prop you might not boot. Have the rom file ready in case. One would need to dirty flash to get back to current install or a backup. If on a custom kernel after reinstalling rom, run kernel cleaner and reinstall kernel. Gapps will work on the dirty install without reinstalling them.
Use at your own risk i am not responsible for damages to ones phone. This is my build prop values i add or use not my actual build prop just the values and entries that i add or change.
The file is in plain text file format
GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
mw86 said:
http://db.tt/GJ2NYrlb
This is the current build props i use. Leave out the Bootanimation one if you want to keep your boot animation. Do not edit buildprop if you have no experience. Look up the proper way to use them, Dreamlogix explainsto use rom toolbox above. Dont add all in. Check if value exists and change to the new value. If an entry is missing add it but dont assume its not there because double entries cause issues and if you mess up your build prop you might not boot. Have the rom file ready in case. One would need to dirty flash to get back to current install or a backup. If on a custom kernel after reinstalling rom, run kernel cleaner and reinstall kernel. Gapps will work on the dirty install without reinstalling them.
Use at your own risk i am not responsible for damages to ones phone. This is my build prop values i add or use not my actual build prop just the values and entries that i add or change.
The file is in plain text file format
GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
Click to expand...
Click to collapse
what else did you change other than hw and ipa ?
and if you use inverted gapps you have to reflash.
Dreamlogix said:
what else did you change other than hw and ipa ?
and if you use inverted gapps you have to reflash.
Click to expand...
Click to collapse
Thanks i didn't remember inverted gapps you are right. I changed and added all of the values in the txt document i posted. They weren't for a fix, i always use them. Thats a list if the values i use.
Edit: most of them all add performance in some way. I didn't use any network build props so it could be more universal for other roms...
GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
I confirmed this morning that ktoon kernel (12/29) breaks audio (pandora, google music, 8tracks, etc) while stock kernel is fine on 1/1 nightly (clean flashed). On stock kernel, BT audio (google music) will play ok for 10-20 secs and then start fading in and out at a faster playback speed. You can reset this by making a phone call, but then you get another 10-20 secs of good audio before it starts up again. Someone should mention this on the dev thread at some point.
Also: if you're having problems with stock 1/1 nightly...do a clean flash. all my problems went away.
Dreamlogix said:
Try voodoo
Click to expand...
Click to collapse
I havent found a compatible version of Voodoo for the SG3, can you share yours?
livito said:
I havent found a compatible version of Voodoo for the SG3, can you share yours?
Click to expand...
Click to collapse
me either im on the search for a fix as wee speak have you tried the headset gain in phone settings? seems to be implemented couple of nightlys ago
mw86 said:
Thanks i didn't remember inverted gapps you are right. I changed and added all of the values in the txt document i posted. They weren't for a fix, i always use them. Thats a list if the values i use.
Edit: most of them all add performance in some way. I didn't use any network build props so it could be more universal for other roms...
GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
Click to expand...
Click to collapse
agreed thanks for thoes prop tweaks whats your network tweaks i assume they only effect 3g
zkz90 said:
I confirmed this morning that ktoon kernel (12/29) breaks audio (pandora, google music, 8tracks, etc) while stock kernel is fine on 1/1 nightly (clean flashed). On stock kernel, BT audio (google music) will play ok for 10-20 secs and then start fading in and out at a faster playback speed. You can reset this by making a phone call, but then you get another 10-20 secs of good audio before it starts up again. Someone should mention this on the dev thread at some point.
Also: if you're having problems with stock 1/1 nightly...do a clean flash. all my problems went away.
Click to expand...
Click to collapse
there is a workaround in the op for streaming music players not working on kt kernel
Dreamlogix said:
agreed thanks for thoes prop tweaks whats your network tweaks i assume they only effect 3g
there is a workaround in the op for streaming music players not working on kt kernel
Click to expand...
Click to collapse
Your welcome, ui should be smooth with those.
I am not using any network build props is what i mean. I didn't want to play with tt for now to ensure my network works fine. So that txt document has none in it either. It is a bunch of tweaks gathered but no real network adjustments (i didn't want to negatively effect my setup or others)
GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
Coming from a 6p where I was able to edit a couple values in mixer_paths.xml to increase output volume. Once I got the PXL rooted I was unable to get the same results modifying values in the system files, but the directory seems to be set up differently and I found multiple locations with a mixer paths file and didn't want to go through all of them in a trial and error.
Is there a mixer paths file that I can edit and increase the volume? If not, is there another method to increase volume? I looked into some audio mods(Viper4Android) but couldn't get them to work, seemingly because in on 8.0.
EDIT: I'm looking to increase volume in Play Music, I heard another file(maybe audio effects) may effect it's volume independently of mixer paths.
Did you ever find a solution? I'm running a nougat ROM, and changes to the mixer_paths file in /system/etc have no effect. I even made some drastic changes to test and no effect. I've successfully modified mixer_paths before on other phones, so I have some idea what I'm doing, but this thing has me scratching my head.
It's like the phone doesn't use that file. There has to be one somewhere...
Follow this guide worked flawlessly for me when I was on 8.0 to have Viper4Android. (on 8.1 preview right now so can't have it) https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-install-arise-pixel-xl-t3677238
loeffler23 said:
Follow this guide worked flawlessly for me when I was on 8.0 to have Viper4Android. (on 8.1 preview right now so can't have it) https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-install-arise-pixel-xl-t3677238
Click to expand...
Click to collapse
Man I wish you'd posted this sooner. I just updated my phone to 8.1 yesterday. Are you sure the process isn't the same getting it to work or is an update necessary from Viper before it can be loaded?
TBacker said:
Did you ever find a solution? I'm running a nougat ROM, and changes to the mixer_paths file in /system/etc have no effect. I even made some drastic changes to test and no effect. I've successfully modified mixer_paths before on other phones, so I have some idea what I'm doing, but this thing has me scratching my head.
It's like the phone doesn't use that file. There has to be one somewhere...
Click to expand...
Click to collapse
I never found anything that worked for me. Another poster replied right after you posted with a method to get Viper4Android on 8.0. I've already upgraded to 8.1, but maybe that will work for you.
mbp1865 said:
I never found anything that worked for me. Another poster replied right after you posted with a method to get Viper4Android on 8.0. I've already upgraded to 8.1, but maybe that will work for you.
Click to expand...
Click to collapse
I mean tbh you can always try it,the worst that happens is it doesn't work you reflash the thing and just click unistall on the ones you installed, Lemme know if it works for you.
I'm aware of viper. I like to use it lightly for multimedia, but I don't like having to leave Selinux permissive.
Using Viper to boost levels works by doing some heavy compression & limiting which I'm personally not a fan of. I prefer the final gain be higher on the speaker / earpiece amps, but the audio system on PXL roms seems to have limited gain adjustment options that work (mixer_paths).
My biggest issue was earpiece / handset gain (I work in noisy environments). I'm using the ElementalX kernel now which has a gain adjustment that works.
Roddy 84:lo encontre en system/vendor/etc/mixer-paths esto es en android 8.1.0 oreo
Hi.
Is there a way to increase bluetooth headphones volume? To listen to music louder. Android 8.1
Since there is no way in a GSI (without recompiling stuff) to add proper support for the screen slider, I'm going to see if I can write a shell script to run on update of the value for the sensor that detects the position of the display, however,I don't actually know what sensor this is.
After a bit of testing, I believe there's a magnetic field sensor that detects the change in the field as the screen moves (since moving a magnet over the device can activate the slider detection ) however I am unsure about this.
ambitiousButRubbish said:
Since there is no way in a GSI (without recompiling stuff) to add proper support for the screen slider, I'm going to see if I can write a shell script to run on update of the value for the sensor that detects the position of the display, however,I don't actually know what sensor this is.
After a bit of testing, I believe there's a magnetic field sensor that detects the change in the field as the screen moves (since moving a magnet over the device can activate the slider detection ) however I am unsure about this.
Click to expand...
Click to collapse
I'm not sure how useful it will be to identify the hardware. Somewhere, there must be a driver, and there must also be some way, in the stock rom/kernel, to register an action associated with that driver.
It's a magnetic sensor
and I know this because when i slide it into my magnet dash holder, it activates the slide.
then I tried just sliding a magnet across the back, and yes it activates the slider lol
invisiblewave said:
I'm not sure how useful it will be to identify the hardware. Somewhere, there must be a driver, and there must also be some way, in the stock rom/kernel, to register an action associated with that driver.
Click to expand...
Click to collapse
if i can identify the sensor, i can try to find the file associated with its value in the 'sys' partition, and read this to detect changes, when it changes, this can be used to assign an event etc...
in the same way that i did my flashlight fix for huawei phones with GSIs, this would just be a bash script running accessing the specific files associated with the hardware, as remember android is linux (is unix), so everything is a file, this includes the state of the sensor, so it can be read
ambitiousButRubbish said:
if i can identify the sensor, i can try to find the file associated with its value in the 'sys' partition, and read this to detect changes, when it changes, this can be used to assign an event etc...
in the same way that i did my flashlight fix for huawei phones with GSIs, this would just be a bash script running accessing the specific files associated with the hardware, as remember android is linux (is unix), so everything is a file, this includes the state of the sensor, so it can be read
Click to expand...
Click to collapse
i understand. I'm not an Android developer, but i work in a similar industry
There is also the possibility that the magnetic switch actually pushes some sort of "button" inside the phone, it could even be some sort of magnetic film where a magnet pushes two membranes together to complete a physical circuit like a button.
would "show input touches" or some sort of log viewer be able to see what that input is?
i killed tupac said:
i understand. I'm not an Android developer, but i work in a similar industry
There is also the possibility that the magnetic switch actually pushes some sort of "button" inside the phone, it could even be some sort of magnetic film where a magnet pushes two membranes together to complete a physical circuit like a button.
would "show input touches" or some sort of log viewer be able to see what that input is?
Click to expand...
Click to collapse
judging by the teardown, there's no physical switch.
ive tried aida64, but it doent list all sensors, there is however a hall sensor that does not display a value, that looks somewhat promising, i will investigate this more.
the input is over gpio or similar so show input touches wouldn't work, however, a logcat output might
It's in kernel:
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/blob/perseus-p-oss/drivers/halls/halls.c
AndroPlus said:
It's in kernel:
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/blob/perseus-p-oss/drivers/halls/halls.c
Click to expand...
Click to collapse
Thanks! As I suspected. All we need now is a kernel programmer who can merge it into the AOSP kernel for the MM3!
I'll still see if I can 'hack' a temporary solution, I'm not a kernel dev (and know very little C) so will try my bash script solution.
Anyways, flashing a GSI doesn't alter the kernel, it's down to the system to communicate with kernel modules, if the system doesn't implement the features, even if it's in the kernel, it won't work.
ambitiousButRubbish said:
I'll still see if I can 'hack' a temporary solution, I'm not a kernel dev (and know very little C) so will try my bash script solution
Click to expand...
Click to collapse
But without the driver in the kernel, there'll be no external notification.
invisiblewave said:
But without the driver in the kernel, there'll be no external notification.
Click to expand...
Click to collapse
True for a custom kernel, but not if you flashed the GSI onto a stock kernel since the driver already exists, it's down to Android to communicate with the kernel, if the communication methods don't exist in the Android system then it doesn't work, conveniently it may however be possible to read the value of the hall sensor through a bash script, and subsequently an app. In the same way that you can turn on an off the flashlight by changing the values in /sys/class/LEDs, regardless of what system (stock kernel though) you are running, will work the same for the hall sensor.
I just need to find what file the system uses as it's interface with the kernel driver, looks like it's over GPIO, which means finding it will be 'fun'
ambitiousButRubbish said:
I just need to find what file the system uses as it's interface with the kernel driver, looks like it's over GPIO, which means finding it will be 'fun'
Click to expand...
Click to collapse
Would the event not be logged in dmesg or kern?
invisiblewave said:
Would the event not be logged in dmesg or kern?
Click to expand...
Click to collapse
i can view events written to logcat, but its simply a log stating the sensor was polled when the screen slides, not what io is being checked, though, looking at the kernel source, gpio 49 and 113 are used, which i cant find in /sys/class/gpio, there is a 'halls' folder under /sys/devices/virtual/misc, which corresponds to the sensor, but it doesn't contain anything of any use, apart from the uevent details, which i cant do nything with anyway
ambitiousButRubbish said:
i can view events written to logcat, but its simply a log stating the sensor was polled when the screen slides, not what io is being checked, though, looking at the kernel source, gpio 49 and 113 are used, which i cant find in /sys/class/gpio, there is a 'halls' folder under /sys/devices/virtual/misc, which corresponds to the sensor, but it doesn't contain anything of any use, apart from the uevent details, which i cant do nything with anyway
Click to expand...
Click to collapse
That's one step further, at least you know the kernel knows about the sensor. I checked dmesg on mine (non-GSI) and I don't see any sign of it. The "everything is a file" mantra is great, but I spend half my life trying to find files in Linux when I have a problem...... I wish IBM would take it and rework it all to make it logical and useable, or better yet, make the IBM i run Linux apps.
invisiblewave said:
That's one step further, at least you know the kernel knows about the sensor. I checked dmesg on mine (non-GSI) and I don't see any sign of it. The "everything is a file" mantra is great, but I spend half my life trying to find files in Linux when I have a problem...... I wish IBM would take it and rework it all to make it logical and useable, or better yet, make the IBM i run Linux apps.
Click to expand...
Click to collapse
im on stock checking all of this, but since im looking in /sys, flashing a GSI or any other system image doesn't affect that, so i know, if i can make it work on stock, chances are, it will work on non stock too, however, should your system flash overwrite /sys, then you may have an issue.
ambitiousButRubbish said:
im on stock checking all of this, but since im looking in /sys, flashing a GSI or any other system image doesn't affect that, so i know, if i can make it work on stock, chances are, it will work on non stock too, however, should your system flash overwrite /sys, then you may have an issue.
Click to expand...
Click to collapse
Yes. Hence my previous comment about merging the driver into the AOSP kernel. It'll be a cold day in hell before I go back to MIUI.
invisiblewave said:
Yes. Hence my previous comment about merging the driver into the AOSP kernel. It'll be a cold day in hell before I go back to MIUI.
Click to expand...
Click to collapse
i understand your point now, theres quite a bit more than just the slider implementation you need though for the device to function correctly with an AOSP kernel. To be fair to MIUI, having come from an honor 9, i only suffered EMUI for a month before i got rid of it, becasue it was so unbearable, MIUI, i dont really mind that much, its actually designed well, and is pretty nice to look at, obviously i still prefer stock android, hence the idea of this, because i could just flash a GSI and still have a somewhat semi functional slider.
ambitiousButRubbish said:
i understand your point now, theres quite a bit more than just the slider implementation you need though for the device to function correctly with an AOSP kernel. To be fair to MIUI, having come from an honor 9, i only suffered EMUI for a month before i got rid of it, becasue it was so unbearable, MIUI, i dont really mind that much, its actually designed well, and is pretty nice to look at, obviously i still prefer stock android, hence the idea of this, because i could just flash a GSI and still have a somewhat semi functional slider.
Click to expand...
Click to collapse
Yes, I know, but the work has already been done on the AOSP kernel, since we have a bunch of non-GSI roms now running (I'm assuming they don't use the OEM kernel, otherwise the driver would be present and the interrupt would work). With the driver merged into the whatever kernel the non-GSI roms are running, we'd then be at the same point with the non-GSI roms as we are with the GSI, at least as far as detecting the slider action goes. Then your app/script would work on either.
invisiblewave said:
Yes, I know, but the work has already been done on the AOSP kernel, since we have a bunch of non-GSI roms now running (I'm assuming they don't use the OEM kernel, otherwise the driver would be present and the interrupt would work). With the driver merged into the whatever kernel the non-GSI roms are running, we'd then be at the same point with the non-GSI roms as we are with the GSI, at least as far as detecting the slider action goes. Then your app/script would work on either.
Click to expand...
Click to collapse
as i said earlier, the GSI (im talking about where you just flash the SYSTEM image, nothing else) ROMs wont detect the event since its handled by the MIUI framework, so whilst the event does take place, the only way of knowing it takes place is having something poll the data the kernel outputs for the event, which would either mean a third party program, or somehow getting the MIUI framework working on AOSP, but you then have the issue of it being MIUI, which you want to get rid of. maybe its worth me looking a the code for the slider implementation in the MIUI framework, if its open source.
ambitiousButRubbish said:
as i said earlier, the GSI (im talking about where you just flash the SYSTEM image, nothing else) ROMs wont detect the event since its handled by the MIUI framework, so whilst the event does take place, the only way of knowing it takes place is having something poll the data the kernel outputs for the event, which would either mean a third party program, or somehow getting the MIUI framework working on AOSP, but you then have the issue of it being MIUI, which you want to get rid of. maybe its worth me looking a the code for the slider implementation in the MIUI framework, if its open source.
Click to expand...
Click to collapse
You've already proved that it's not the ROM detecting the event, it's the kernel. GSI - Xiaomi kernel, slider event detected, no framework in ROM to handle the event. Non-GSI - AOSP kernel, slider event not detected, no framework in ROM to handle the event. If the driver is merged into the AOSP kernel, then GSI & non-GSI roms are in the same boat, needing either an app or your script to handle the event.