Hey guys,
My bluetooth headphones work perfectly on my G Tablet (CyanogenMod 7.1RC REPACK build 21), until I fire up wifi. Whenever there is data transfer on wifi, the audio skips, badly.
Is there any solution for this problem?
Cheers,
Jason
galapogos01 said:
Hey guys,
My bluetooth headphones work perfectly on my G Tablet (CyanogenMod 7.1RC REPACK build 21), until I fire up wifi. Whenever there is data transfer on wifi, the audio skips, badly.
Is there any solution for this problem?
Cheers,
Jason
Click to expand...
Click to collapse
Is the abtfilt program running?
Nope. Can't find that in PS output or on the filesystem.
galapogos01 said:
Nope. Can't find that in PS output or on the filesystem.
Click to expand...
Click to collapse
Alright, then. Install the attached zip file using CWM and see if adding the abtfilt program (from my GtabComb-b3.3-bl11) fixes the BT audio drop issue. This is what's done in CyanogenMod to fix the problem on Android phones.
Tried it tonight. Completely broke audio, lots of errors in logcat. Killing the daemon didn't stop the errors when attempting to play nor fix the audio.
I reflashed the nightly 21 build as I use this thing daily. Without about bt audio, though
Jason
galapogos01 said:
Tried it tonight. Completely broke audio, lots of errors in logcat. Killing the daemon didn't stop the errors when attempting to play nor fix the audio.
Click to expand...
Click to collapse
So much for that quick fix, then. Get me a dmesg and logcat output (see this post for the commands to use).
And, for the next time, you can simply a) either delete /system/bin/abtfilt or b) rename it and then reboot the system--there is no need to reflash the ROM.
Not so sure about that. I'm using the 'CM7 build 21 repack' with 1.2bl. I think the .zip did funny things to /boot.
Do you want the logs with or without abtfilt?
galapogos01 said:
Not so sure about that. I'm using the 'CM7 build 21 repack' with 1.2bl.
Click to expand...
Click to collapse
Apologies. I don't have bluetooth headphones, so this script I didn't test before sending it out. I got the order of the tests wrong (along with a couple of other inconsequential bugs) in one of the scripts so the command to start the abtfilt program was never added to /init.rc.
Try the new attachment in my post.
I think the .zip did funny things to /boot.
Click to expand...
Click to collapse
Define funny here. I doubt my script will screw up your /boot, but, feel free to send me your /init*.rc files if you feel otherwise.
Do you want the logs with or without abtfilt?
Click to expand...
Click to collapse
Both, preferably.
abtfilt was definitely running with the original file from the first post.
When I can handle reflashing this thing again I will give it a shot. Last time I lost 2 hours to it! I should have tested the stock TnT rom.
galapogos01 said:
abtfilt was definitely running with the original file from the first post.
Click to expand...
Click to collapse
Yeah, the abtfilt program is not present in the ROM zip file, but, is still started in /init.nvidia.rc.
Related
As most of you know, alankila published a modified AudioFlinger library that gives rooted Android installations much-needed DSP capabilities. (See here.) This has been upstreamed to Cyanogen-6 development branch and has been released in CM6 stable and a few other cooked ROMs. However, there wasn't much information on installing it on stock ROMs with locked bootloaders/recovery images (i.e. will only accept Google-signed update ZIPs), so here's a tutorial on how to do that. This has been tested working on my Nexus One running FRF91 and the stock HTC Passion bootloader and recovery image.
NOTE. You must be root!
1) Download the attached dsp-signed update ZIP. I'm not sure which version this is, but it lets you control both the speaker and headset curves independently.
2) Extract its contents to a local folder or to the SD card on the phone.
3) Using ADB, drop to a root shell (adb shell, then su.) and remount the system partition as read-write.
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Afterwards, make a backup of libaudioflinger so that you can restore it in case your phone blows up.
Code:
mv /system/lib/libaudioflinger.so /system/lib/libaudioflinger_bak.so
. Finally, copy DSPManager.apk to /system/app and the modified libaudioflinger on your SD card to /system/lib.
Code:
mv [path-to-files]/DSPManager.apk /system/app/
Code:
mv [path-to-files]/libaudioflinger.so /system/lib/
4) Reboot.
If your phone fails to boot, just delete the libaudioflinger library you copied over and restore the original from the backup you made.
Enjoy! It's fantastic!
This works great on my Incredible with stock 2.2!
Thanks!
Of course, you could also just install ROM Manager, then flash a custom recovery image and install the update ZIP that way if it's easier.
Does this app control ear piece, speaker and headphones? also does it apply the settings to calls as well as music? thanks. I have it on my phone for evils sense rom but not really noticing much of a difference. thanks.
This works great, I just wish the sliders were a bit more responsive.
installed through clockwork recovery on LeoFroyo rom 2.0.1Beta3, and it works like a charm. the sliders could use + and - icons on side to help change the numbers.
All the dsp settings do is make my speakers clip...
Sent from my Nexus One using XDA App
I would be careful with equalizing the speaker; if it's like most phone speakers, it's pretty fragile...
@jdub: It works for speakers, headphones and bluetooth devices. It affects all sound on the phone.
dgart08 said:
All the dsp settings do is make my speakers clip...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Same here, no matter how slightly (0.3dB or so) I change the level of any band, it clips when connected to my car stereo, with headphones the issue is also present but less annoying.
will this work for bluetooth streaming
danimar1 said:
Same here, no matter how slightly (0.3dB or so) I change the level of any band, it clips when connected to my car stereo, with headphones the issue is also present but less annoying.
Click to expand...
Click to collapse
I found if you have your Nexus connected to your car stereo, the speakers will not clip if you turn the headset volume down one or two notches below 100%.
GchildT said:
I found if you have your Nexus connected to your car stereo, the speakers will not clip if you turn the headset volume down one or two notches below 100%.
Click to expand...
Click to collapse
I think I already tried that, but I'm not totally sure though ... I will flash it again and give it a try. Thanks for the tip!
can this be installed on miui as per the OP?
mtw4991 said:
can this be installed on miui as per the OP?
Click to expand...
Click to collapse
The framework etc. in MIUI is not compatible with this mod. will cause bootloops... But if you find a solution please share, I'm really missing the DSP Manager and Trackball Alerts in succession on the MIUI Rom!!
cyberspaced said:
The framework etc. in MIUI is not compatible with this mod. will cause bootloops... But if you find a solution please share, I'm really missing the DSP Manager and Trackball Alerts in succession on the MIUI Rom!!
Click to expand...
Click to collapse
I am running DSPManager v1.0 on my N1 using Rodriquez v1.1 ROM. I actually used Titanium Backup to install from a backup. The apk is in my /data/app folder. APK is listed as com.bel.android.dspmanager-1.apk
Docmjldds said:
I am running DSPManager v1.0 on my N1 using Rodriquez v1.1 ROM. I actually used Titanium Backup to install from a backup. The apk is in my /data/app folder. APK is listed as com.bel.android.dspmanager-1.apk
Click to expand...
Click to collapse
Yes, you can install and run the app, but i doubt it will actually do anything, might also be the reason Rodriguez removed the app from his ROM....
cyberspaced said:
Yes, you can install and run the app, but i doubt it will actually do anything, might also be the reason Rodriguez removed the app from his ROM....
Click to expand...
Click to collapse
I could have sworn on his first version I did hear a difference. Just checked with v1.1 and you're right. Nada. My bad....but appreciate the reply.
droid x 2.2 fails to boot, stuck on motorola logo.
someone *please* make this work!
To preven cliping enable audicompression to lowest level. Works for me
I badly want to try the DSP manager. Can I use this with my rooted vibrant running stock android 2.1?
This thread is for installation, help,
known bugs
and infos/faqs
for the shortly released build of cyanogen for the gen 8 archos
it is only "recommended" to use it with the a101 or the 70
link: http://www.openaos.org
installation:
install sde
install open aos recovery
Download the last Cyanogen img file from here: http://download.openaos.org/bubu/gen8/android/Rename the file to openaos-gingerbread then copy it to the root of your Archos
edit the menue.lst (with notepad++) to:
Archos|ARCHOS|ARCHOS|/init|0
Angstrom||/rootfs.img|/sbin/init|1
Ginger-bread||/openaos-gingerbread.img|/init|0
(add an empty line at the end)
unix breaks must be enabled in notepad++ if you are on windows.
Reboot your Archos and hold down VOL - (Down) Button, select "Developer Edition" and select in the Boot Menu "Ginger-bread".
if nothing is helping try(wont boot/ wont show ginger-bread):
http://www.filesonic.com/file/1302552154/menu.lst
bugs:
Not working:
Bluetooth
accelerated Video decoding
Suspend
TS calibration on A28/A32/A43
orientation has it hickups
Known problems:
general instability / random crashes
hard to use on resistive TS models due to missing calibration
faq:
What's working ?
Currently working:
SGX/EGL 3D acceleration
WiFi
Touchscreen
Orientation
Android Market
alot more...
screan not working on normal orientation on the a101?
activate 180* in settings-cyanogensettings-display
updating:
just exchange the img
historyin unseperated datetime)
initial 20110623
update1 20110626
update2 20110628
update3 20110629
Update4 20110708 more stability, faster
developing........ in a real guide and how to......
all credits to the geniuses of openaos and especially bubu.
and thank them(bubu,@dm8tbr and divx) for this guide too they been super helpfull
sent from my droid (not the one you are looking for)
Great!!!!!!!!!!!!!!!!!!!
I'm very excited to finally have an actual file in hand for CM7. Just FYI though, before you flash too soon:
Not working:
Audio
Bluetooth
Accelerometer
accelerated Video decoding
Suspend
TS calibration on A28/A32/A43
Known problems:
general instability / random crashes
Touchscreen has problems on the A101
hard to use on resistive TS models due to missing calibration
There's still some work to be done before it's a daily use ROM, but hopefully we can help out and fix some of these issues.
Great news guys! Look forward to testing it.
How do I edit the list?
Code:
Cyanogen||/cyanogen.img|/sbin/init|1
Update
This is really great, but you can notice this is an alfa version
coen22 said:
How do I edit the list?
Code:
Cyanogen||/cyanogen.img|/sbin/init|1
Update
This is really great, but you can notice this is an alfa version
Click to expand...
Click to collapse
see how to.....
Greeaaat
but i'll wait until its a "daily use"rom like ninja said
for now, Urukdroid is great for me
Lenn said:
Greeaaat
but i'll wait until its a "daily use"rom like ninja said
for now, Urukdroid is great for me
Click to expand...
Click to collapse
what a helpfull post again
sent from my droid (not the one you are looking for)
gbohm said:
what a helpfull post again
sent from my droid (not the one you are looking for)
Click to expand...
Click to collapse
3 guys above e posted exactly the same, but whatever...
ok i cant get this to show in the boot menu. i have put the .img file on my tab with the usb. then i edited the list like this : Cyanogen||/cyanogen.img|/sbin/init|1
what did i do wrong?
saprano614 said:
ok i cant get this to show in the boot menu. i have put the .img file on my tab with the usb. then i edited the list like this : Cyanogen||/cyanogen.img|/sbin/init|1
what did i do wrong?
Click to expand...
Click to collapse
what is the images name?
please follow my how to to the letter....
sent from my droid (not the one you are looking for)
it is cyanogen.img i think the problem is that i can get it to copy to the root. when i use sufile browser it is in the sdcard folder. and when i try to copy it to the root it says i dont have enough space. is there a way to have this on the sdcard and still work?
saprano614 said:
it is cyanogen.img i think the problem is that i can get it to copy to the root. when i use sufile browser it is in the sdcard folder. and when i try to copy it to the root it says i dont have enough space. is there a way to have this on the sdcard and still work?
Click to expand...
Click to collapse
not that i know copy it to your pc mount your archos then copy it to root and please name it like i wrote and edit your menue file like i wrote
Sent from my A101IT using XDA Premium App
Gr888888, i think we must support them, we should donate what we committed before.
gbohm said:
not that i know copy it to your pc mount your archos then copy it to root and please name it like i wrote and edit your menue file like i wrote
Sent from my A101IT using XDA Premium App
Click to expand...
Click to collapse
i did and still nothing. i will try again i just reset android
saprano614 said:
i did and still nothing. i will try again i just reset android
Click to expand...
Click to collapse
i will post my menue.lst if you want
sent from my droid (not the one you are looking for)
saprano614 said:
i did and still nothing. i will try again i just reset android
Click to expand...
Click to collapse
you have to modify it and name it openaos-gingerbread.img did you gunzip it? it should have 5xxmb.
btw put an empty line at the end of the menue.lst
sent from my droid (not the one you are looking for)
gbohm said:
i will post my menue.lst if you want
sent from my droid (not the one you are looking for)
Click to expand...
Click to collapse
please do and i will try later.
saprano614 said:
please do and i will try later.
Click to expand...
Click to collapse
no garantie it won't kill your phone
http://www.filesonic.com/file/1302552154/menu.lst
Lenn said:
3 guys above e posted exactly the same, but whatever...
Click to expand...
Click to collapse
That's probably why you got such a response funny enough im sure you was one of the first crying out for Cyanogen on gen8 at least we have something and not just a topic with users slagging each other off!!
Thankyou gbohm openaos and especially bubu for all of your hard work, great start
So sorry for being so new to this and confused but i've downloaded Bodhi from the posts (That insist it's for Archos gen8) but i can NOT figure out how to actually install it. I've tried Updating my FW via Recovery, several times with sever different things and also I've tried flashing (but Bodhi is in the wrong format) nothing is seeming to work.
-Can someone either point me in the direction of a TUT(link) or just give me the run down here, I will be IMMENSELY grateful
P.S. Ive been at this for about a week now :/
kartkid said:
So sorry for being so new to this and confused but i've downloaded Bodhi from the posts (That insist it's for Archos gen8) but i can NOT figure out how to actually install it. I've tried Updating my FW via Recovery, several times with sever different things and also I've tried flashing (but Bodhi is in the wrong format) nothing is seeming to work.
-Can someone either point me in the direction of a TUT(link) or just give me the run down here, I will be IMMENSELY grateful
P.S. Ive been at this for about a week now :/
Click to expand...
Click to collapse
You really need to read up on your device and how it works. Have installed the SDE or the openAOS boot menu? Google is your friend, instructions have been posted on multiple websites. If you have installed the SDE, and only want Bodhi and the stock Android, just download the bodhi image and replace the rootfs.img on your internal storage with the bodhi image. Then boot into Developer Edition by holding the volume key down and selecting Developer Edition.
If you want more than 2 OSes, install the openAOS boot menu. Here's an entire wiki just for our gen8s. http://dev.openaos.org/wiki/SettingUpMultiRootGen8
msticninja said:
If you want more than 2 OSes, install the openAOS boot menu. Here's an entire wiki just for our gen8s. http://dev.openaos.org/wiki/SettingUpMultiRootGen8
Click to expand...
Click to collapse
Here is a big full instructions thread from me
http://forum.xda-developers.com/showthread.php?t=1153522
msticninja said:
You really need to read up on your device and how it works. Have installed the SDE or the openAOS boot menu? Google is your friend, instructions have been posted on multiple websites. If you have installed the SDE, and only want Bodhi and the stock Android, just download the bodhi image and replace the rootfs.img on your internal storage with the bodhi image. Then boot into Developer Edition by holding the volume key down and selecting Developer Edition.
If you want more than 2 OSes, install the openAOS boot menu. Here's an entire wiki just for our gen8s. http://dev.openaos.org/wiki/SettingUpMultiRootGen8
Click to expand...
Click to collapse
I did read up, i have UrukDroid installed and I believe i have done what u insisted to multiple times with no success.
Lenn said:
Here is a big full instructions thread from me
http://forum.xda-developers.com/showthread.php?t=1153522
Click to expand...
Click to collapse
Thnx man, I've seen you help others with their problem and to be honest i was hoping that it'd be you who helped me as well.
I've heard good things about the OpenAOS but bad things for it on the Arcos 101. I'll give it a try though i suppose tho i only want bodhi and Archos OS
TY for all the help thus far to both of you.
kartkid said:
Thnx man, I've seen you help others with their problem and to be honest i was hoping that it'd be you who helped me as well.
I've heard good things about the OpenAOS but bad things for it on the Arcos 101. I'll give it a try though i suppose tho i only want bodhi and Archos OS
TY for all the help thus far to both of you.
Click to expand...
Click to collapse
If you have Urukdroid, then you have more than just Archos and Bodhi. Urukdroid uses the developer edition's OS slot, so you are actually trying to use three OSes. If you want to keep Uruk, you'll need the openAOS boot-menu, which is a better solution, in my opinion, than $auron's AlternativeOS menu.
I'm on a 101, so I had to do some stuff to make Uruk and Bodhi display correctly. All this stuff has been added to Lenn's tutorial. If you want to keep Uruk and have Bodhi, it's the best way. If you can deal with just having the stock Archos firmware and Bodhi, then you can just use reinstall the sde and overwrite the rootfs.img(sde must be reinstalled though, uruk has overwritten it).
kk thnx, so i just reinstall SDE?
and also the zImage file in http://download.openaos.org/bubu/gen8/ keeps DLing as a txt file. can u help me with that? :/
please and thankyou.
kartkid said:
kk thnx, so i just reinstall SDE?
and also the zImage file in http://download.openaos.org/bubu/gen8/ keeps DLing as a txt file. can u help me with that? :/
please and thankyou.
Click to expand...
Click to collapse
Just reinstall SDE and copy the rootfs.img if you don't need Urukdroid. If you want multiboot, use Bubu's initramfs and zimage. Just rename the zimage.txt to zimage, it will still work.
msticninja said:
Just reinstall SDE and copy the rootfs.img if you don't need Urukdroid. If you want multiboot, use Bubu's initramfs and zimage. Just rename the zimage.txt to zimage, it will still work.
Click to expand...
Click to collapse
That doesnt work..
kartkid said:
That doesnt work..
Click to expand...
Click to collapse
Did you tried it according to my How to ?
download link of Bodhi for Archos 101it
Hi, this is an old post, but I would like to post the link where I downloaded Bodhi for my Archos 101it. I have been using it for more than a year and it's awesome. It's just a pity the project has been abandoned. I hope some illuminated genius could retake it and configure the system for sound, videos and camera, which aren't working.
The link is:
mirror.transact.net.au/pub/sourceforge/b/project/bo/bodhilinux/ARM/ALPHA/
New link
The above link seems to be dead. I have uploaded the file here:
dl.dropboxusercontent.com/u/38867415/bodhi-linux-archos-g8.zip
Just write https:// before that.
ulyses3 said:
The above link seems to be dead. I have uploaded the file here:
dl.dropboxusercontent.com/u/38867415/bodhi-linux-archos-g8.zip
Just write https:// before that.
Click to expand...
Click to collapse
Someone should really make a new index of roms and iso's for the g8, anyway if u want help on setting up sound you can ask me, cause I used this for a while and I know how to start the sound, but it will have a "glitch" when no sound is playing (as in the tab will make odd sounds randomly). If you fixed that already then sorry, I read ur last comment before this one and even if it was in may I was thinking I may help.
I would greatly appreciate if you can help me configure sound with Bodhi linux, so I don't have to change to stock android firmware to play videos or music. I don't mind the glitch, though.
Did you install any codecs? I have been playing with the settings of the recognised Wolfson audio card, but without any luck.
ulyses3 said:
I would greatly appreciate if you can help me configure sound with Bodhi linux, so I don't have to change to stock android firmware to play videos or music. I don't mind the glitch, though.
Did you install any codecs? I have been playing with the settings of the recognised Wolfson audio card, but without any luck.
Click to expand...
Click to collapse
So as I can understand u know how to access alsamixer in terminal, I don't remember what the settings I left on were, but I know I enabled everything and set all volumes to maximum and then I started playing music and disabled the settings one by one till I was left with only the needed settings enabled, hope it helps, if u want I can reinstall bodhi and do the settings on Monday and post them here.
Sound problem solved
Thank you, as you suggested, I set all volumes to the maximum in alsamixer. Then I selected the alsa Wolfson driver under the audio preferences in smplayer2, and the both the music and videos are playing well now! The only problem I find is with the video drivers, with the videos not playing smoothly, but they're ok.
ulyses3 said:
Thank you, as you suggested, I set all volumes to the maximum in alsamixer. Then I selected the alsa Wolfson driver under the audio preferences in smplayer2, and the both the music and videos are playing well now! The only problem I find is with the video drivers, with the videos not playing smoothly, but they're ok.
Click to expand...
Click to collapse
There is nothing to do about that, I was trying to build lubuntu as described at the openaos site (cause that seems to be 100% functional....or at least as much as it can be) but ended up being unable so I am now using debian with lxde (works way better), but it took a bit to setup the screen to auto turn off and I didn't manage to set long press as right click.
EDIT: Also I didn't manage to get e17 to work on it so I am kinda stuck with lxde, too bad, really loved e17 on bodhi.
I'd like to start by saying, I am a new member so, I was not able to simply ask in that thread and this is the most relevant place to ask. Here is the link to that thread, http://forum.xda-developers.com/showthread.php?t=2293133 . Now, I am on the ME7, so, no TWRP or CWM and I searched all through that file in root explorer and couldn't find any of text required to change, the audio hack is confirmed working for I545. I already searched that thread, no luck. Now that you know my situation, is it possible to download those flash-able files, and either flash them in stock recovery, or take each individual file and place them in the correct directory using root explorer, fix the permission and it work? I'd prefer not to take risks with this locked bootloader, a simple problem with this phone turns it into a paper weight.
Banana Republic said:
I'd like to start by saying, I am a new member so, I was not able to simply ask in that thread and this is the most relevant place to ask. Here is the link to that thread, http://forum.xda-developers.com/showthread.php?t=2293133 . Now, I am on the ME7, so, no TWRP or CWM and I searched all through that file in root explorer and couldn't find any of text required to change, the audio hack is confirmed working for I545. I already searched that thread, no luck. Now that you know my situation, is it possible to download those flash-able files, and either flash them in stock recovery, or take each individual file and place them in the correct directory using root explorer, fix the permission and it work? I'd prefer not to take risks with this locked bootloader, a simple problem with this phone turns it into a paper weight.
Click to expand...
Click to collapse
You cant flash in stock recovery but you should be able to extract the files and then copy/paste them. Make sure they have the right permissions and you should be go to. I would add .bak extension to the stock ones just in case you dont like the mod and want to revert back to stock.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
If you want a great sound app get Viper4Android.
Tool Belt said:
If you want a great sound app get Viper4Android.
Click to expand...
Click to collapse
Did a search on the market for this and the only one I can come up with is all in chinese.
Look here, you will find links in the second post, but read one, two and three.
http://forum.xda-developers.com/showthread.php?t=2191223
Tool Belt said:
Look here, you will find links in the second post, but read one, two and three.
http://forum.xda-developers.com/showthread.php?t=2191223
Click to expand...
Click to collapse
Tried to install everything and to say the least it was unsuccessful I couldn't get the drivers working I tried A8 Neon and A9/A15 Neon neither worked
All I can tell you is it works fine for me and ROCKS PowerAmp
Tool Belt said:
All I can tell you is it works fine for me and ROCKS PowerAmp
Click to expand...
Click to collapse
What drivers did you use and did you put the apks in system/apps or did you install it normally?
Banana Republic said:
Tried to install everything and to say the least it was unsuccessful I couldn't get the drivers working I tried A8 Neon and A9/A15 Neon neither worked
Click to expand...
Click to collapse
Lol, You got one step further than me. Seems I'm too stupid to follow that thread so I didn't even attempt.
Banana Republic said:
What drivers did you use and did you put the apks in system/apps or did you install it normally?
Click to expand...
Click to collapse
I placed it in /system/app
Sorry, I don't recall what driver. I think it suggested on when I installed it. There is a ton of information as to FAQ's and troubleshooting in that thread.
I am also in the same boat...
In call volume on S4 ME7 sucks. Was looking for volume booster specific to S4 ME7.
Found 2 threads:
1. Volume booster mod: http://forum.xda-developers.com/showthread.php?t=2298946
2. Viper4Android http://forum.xda-developers.com/showthread.php?t=2191223&page=640
Tried to read through both treads...
Have couple Q, still unclear for me regarding above:
1. Applying 1st mod - does it distort the sound quality?
2. Does Viper actually allow to INCREASE VOLUME besides improving quality of decoding lossy music files?
PS. Does it make sense to even try those volume improving apps from market? (Volume +, Music volume EQ, ect?)
Thanks!
Don't know if V4a will increase call volume, but it will boost the hell out of your earphone volume on music apps. BUT as the boost increases, so does the noise.
lazer9 said:
Lol, You got one step further than me. Seems I'm too stupid to follow that thread so I didn't even attempt.
Click to expand...
Click to collapse
Some guy on that thread rewrote the installation guide(apparently the guy is Chinese explains EVERYTHING) his guide required wiping dalvik and this good ol' ME7 just won't tolerate any kind of customization
Banana Republic said:
Some guy on that thread rewrote the installation guide(apparently the guy is Chinese explains EVERYTHING) his guide required wiping dalvik and this good ol' ME7 just won't tolerate any kind of customization
Click to expand...
Click to collapse
And yet, following the instructions on the thread I linked to it works very well on my ME7. I wish I could I could do more to help you.
Sorry.
Have you tried this post http://forum.xda-developers.com/showpost.php?p=42944438&postcount=22 in this thread http://forum.xda-developers.com/showthread.php?t=2335869&page=2 ?
Tool Belt said:
And yet, following the instructions on the thread I linked to it works very well on my ME7. I wish I could I could do more to help you.
Sorry.
Have you tried this post http://forum.xda-developers.com/showpost.php?p=42944438&postcount=22 in this thread http://forum.xda-developers.com/showthread.php?t=2335869&page=2 ?
Click to expand...
Click to collapse
I want to make sure I'm doing everything correct this is what I did
1. Download latest zip files
2. copy apks to /system/apps
3. reboot just because I wanted to
4. start apps grant root and download A8 neon drivers and Ax Neon
5. reboot once more
6. Check driver status, enabled: no
7. settings>sound>ViperFx
8. Repeat 1-7 with no justification
Am I skipping a step here, getting the wrong drivers, or what?
I am just using the XHIFI with (I think) xA8 with neon. I copied it to /system/app, I did boot to recovery and wiped cache, but the little android dude looked dead and I am not sure it worked. With root explorer I changed the permission to owner read, write execute, then opened the app, update the driver, enabled it under sound.
I did this a bit ago, and I think this is what I did. But given the difficulty people are having I am not interested in uninstalling and trying to document how I re-install. Keep at it, it does make a big difference.
Tool Belt said:
I am just using the XHIFI with (I think) xA8 with neon. I copied it to /system/app, I did boot to recovery and wiped cache, but the little android dude looked dead and I am not sure it worked. With root explorer I changed the permission to owner read, write execute, then opened the app, update the driver, enabled it under sound.
I did this a bit ago, and I think this is what I did. But given the difficulty people are having I am not interested in uninstalling and trying to document how I re-install. Keep at it, it does make a big difference.
Click to expand...
Click to collapse
The universe aligned just right to allow it to FINALLY work thank you for all your help the ultimate solution was to go into build.prop and edit the 3 lines he suggested I assumed samdung wouldn't do this I will no longer assume anything else for samdung
Banana Republic said:
The universe aligned just right to allow it to FINALLY work thank you for all your help the ultimate solution was to go into build.prop and edit the 3 lines he suggested I assumed samdung wouldn't do this I will no longer assume anything else for samdung
Click to expand...
Click to collapse
EXCELLENT. Play with it for a while and tell me (us!) what you think!!!
Tool Belt said:
EXCELLENT. Play with it for a while and tell me (us!) what you think!!!
Click to expand...
Click to collapse
I would have liked a little bit more of a boost in volume but the quality boost overall is tremendous Compatibility mode is broken they work well separately I'd say so far that it was well worth the trouble I went through
You can keep boosting volume with Playback Gain Control..... but noise will raise its angry head
Sent from my SCH-I545 using XDA Premium 4 mobile app
Over at the Chromecast forum they're building a compatibility list for mirroring with Chromecast. DNA isn't officially supported (yet), but I aim to build a list of ROMS that mirror successfully with the MirrorEnabler app.
TESTED WORKING:
Google Play Edition
Nusense Six
Cyanogen (all music players force close
LiquidSmooth (audio only)
NOT WORKING:
AOKP
Carbon
Paranoid
Dirty Unicorns
Viper
Anyone willing to report on tested and working ROM's please chime in....
Credit goes to r3pwn for his original thread HERE (
r3pwn and I got things rolling on cm-11 so that is confirmed. In the case of DNA ROMs any aosp and cm based should work without issue with v3. It seems the only folks having problems right now is because their ROMs did not compile in r_submix support.
Sent from my HTC6435LVW using XDA Free mobile app
mattgyver83 said:
r3pwn and I got things rolling on cm-11 so that is confirmed. In the case of DNA ROMs any aosp and cm based should work without issue with v3. It seems the only folks having problems right now is because their ROMs did not compile in r_submix support.
Sent from my HTC6435LVW using XDA Free mobile app
Click to expand...
Click to collapse
I noticed the headway made over there with v3 and v4. v4 seems to cast without gps fc but only a black screen. Going to try v3 if i can find it now that the app has been updated.
xlxcrossing said:
I noticed the headway made over there with v3 and v4. v4 seems to cast without gps fc but only a black screen. Going to try v3 if i can find it now that the app has been updated.
Click to expand...
Click to collapse
Here is how mine got working, mind you post these instructions I never had to flash past v2. If you already flashed v3 or greater then you probably don't need to do steps 1 and 2 because Mirror enabler handles that part.
Install and enable mirror enabler v2
execute the following commands in a root terminal
Code:
su
/data/data/com.r3pwn.mirrorenabler/lib/libhackyworkaround.so /data/data/com.google.android.gsf/databases/gservices.db
insert into overrides (name, value) values ('gms:cast:media:use_tdls', 'true');
.exit
exit
Code:
su
/data/data/com.r3pwn.mirrorenabler/lib/libhackyworkaround.so /data/data/com.google.android.gsf/databases/gservices.db
insert into overrides (name, value) values ('gms:cast:remote_display_enabled ', 'true');
.exit
exit
Update /etc/audio_policy.conf and in the global_configuration append to the end of the "attached_input_devices" line
Code:
|AUDIO_DEVICE_IN_REMOTE_SUBMIX
Now, this is something to ask r3pwn but I believe hes pushing a rather generic version of audio_policy.conf and not the device specific policy which means there could be an error related to the generic version. I am not sure if Mirror Enabler is backing up the original audio_policy.conf and putting it back in place after its "disabled" and then uninstalled. What I suggest if you are post v3 is to extract the specific audio_policy.conf from the original ROM and follow step 3 only then reboot. That may be worth attempting to see if it fix.
OK so extracted default audiopolicy, added the submix edit and pushed to system/etc. I am able to receive sound while casting but TV screen is black.
xlxcrossing said:
OK so extracted default audiopolicy, added the submix edit and pushed to system/etc. I am able to receive sound while casting but TV screen is black.
Click to expand...
Click to collapse
Two questions;
What rom are you using?
Did you place the file in /etc/ or /system/etc ? It goes in /etc/
Also make sure the file is owned by root and has 644 perms
I can confirm, NusenseSIX RC 6.4 works as well.
mattgyver83 said:
Two questions;
What rom are you using?
Did you place the file in /etc/ or /system/etc ? It goes in /etc/
Also make sure the file is owned by root and has 644 perms
Click to expand...
Click to collapse
Liquid Smooth. The paths are the same. The permissions are set as they should be. My issue with liquid is no video so tinkering with the audio policy file doesn't seem like a remedy. Ive rebooted Chromecast and the phone to no avail. Can anyone else confirm only audio on LiquidSmooth?
xlxcrossing said:
Liquid Smooth. The paths are the same. The permissions are set as they should be. My issue with liquid is no video so tinkering with the audio policy file doesn't seem like a remedy. Ive rebooted Chromecast and the phone to no avail. Can anyone else confirm only audio on LiquidSmooth?
Click to expand...
Click to collapse
Sorry, I cant directly confirm this for Liquid Smooth but like I said if it can be confirmed by the ROM developer that REMOTE SUBMIX support is compiled into the ROM then using mirror enabler _should_ work. I would suggest contacting the developer to see if this is the case. I can confirm that on my DNA using CM11 m8 snapshot all audio and video works flawless across all applications (including apollo, etc). I would suggest for anyone having issues running that ROM (or possibly others) to attempt the steps I noted earlier to see if using a more "pure" audio_policy.conf. Based on what we learned by testing with my device somehow the audio_policy.conf does in fact have something to do (were not entirely sure what) with ensuring that all the data gets across to the chromecast, he saw a few logcats of users who had audio and no video which were corrected after implementing the "force close fix" that pushes the updated audio_policy.conf. Now while a one size fits all audio_policy.conf is the best method and not causing other issues is hard to say.
Sorry I couldn't be of more help, Good luck!
Edit: I did a few more tests when i got home to make sure I'm not completely full of it and it turns out yeah i am. Apollo is in fact not working for me and does cause a fc then causing mirroring FC's but it appears the force closes settled down after a reboot also plex decided to give me a fit while also while mirroring but otherwise i didn't get any other grief.