1) google street view (I think this application crash my download in market)
Angry Birds RIO. It installed but my phone switches off when I try to launch it.
NHS2008 said:
Angry Birds RIO. It installed but my phone switches off when I try to launch it.
Click to expand...
Click to collapse
more reasons that these threads shouldn't be made by people who need to follow tutorials, if your system is configured properly this one should work.
EDIT: streetview works fine too.
yeah there's a fix for it
You have to edit asound.conf and set everything to "0".
Found nothing that is not working exept apps that need modem
and apps that need to be paid.
te_chnix said:
You have to edit asound.conf and set everything to "0".
Found nothing that is not working exept apps that need modem
and apps that need to be paid.
Click to expand...
Click to collapse
Thanks for the clarification.
Does that set all sounds to zero? And is this the fix for video playback too? also what about the bluetooth sound??
well the bluetooth module actually gets it's own link, which connects it between the Applications processor and the wm8994 chip, so i'm guessing that this link works, and the main one connecting the Applications processor to the wm8994 chip directly isn't being configured properly (bootloader) though it can't be completely certain, the fact that audio works when pbl-sbl is used seems to back it up :S .
nbates66 said:
well the bluetooth module actually gets it's own link, which connects it between the Applications processor and the wm8994 chip, so i'm guessing that this link works, and the main one connecting the Applications processor to the wm8994 chip directly isn't being configured properly (bootloader) though it can't be completely certain, the fact that audio works when pbl-sbl is used seems to back it up :S .
Click to expand...
Click to collapse
Thanks for reply!
huh? what is pbl-sbl?? and for the audio,
te_chnix posted a file, 'asound.conf' ,set everything to zero??
won't that disable all the audio??
Is this the way to go??
NHS2008 said:
te_chnix posted a file, 'asound.conf' ,set everything to zero??
won't that disable all the audio??
Click to expand...
Click to collapse
yes it will disable all audio, because currently all attempts to play audio (except through bluetooth devices apparently) cause a complete system lockup.
i play audio now from my laptop's speakers
it works really good and sounds to be continuous also due to fastness of Bluetooth 3.0
what was the problem, the audio! now I only care when unloading applications if the application specifies that the installation causes changes where Android is still lacking (mainly audio) ...
te_chnix said:
You have to edit asound.conf and set everything to "0".
Found nothing that is not working exept apps that need modem
and apps that need to be paid.
Click to expand...
Click to collapse
everything?? I set to 0 only this part
}
pcm.AndroidPlayback_Speaker_normal {
type hooks
slave.pcm {
type hw
card 0
device 0 # Must be of type "digital audio playback"
}
hooks.0 {
type ctl_elems
hook_args [
# Enable audio output from the DSP
{name "Playback Path" value 0} # 0:OFF 1:RCV 2:SPK 3:HP 4UAL 5:BT 6:RING_SPK 7:RING_HP 8:RING_DUAL 9:EXTRA_DOCK_SPEAKER 10:TV_OUT
]
the other no.. I have other set with the value 0??
}
aye /\ changing only that value is all that should be necessary
Hello Developers,
I'd like to know if its possible charging with an android wave? I really like to last my battery but it always pop up "Battery temperature is high or low..." Any solutions on it?
Thanks for clearing that. Can you tell me one thing, Why I keep getting input/output errors in my files? I can't seem to get it. So it keeps losing some features so I have keep on checking and repairing and recopying the affected files...over and over..?
i have the new kernel with audio installed, asound.conf was already set to 2.
worms hd works but the sound laggs, no matter if speaker or headphones.
Gangstar 2 closes directly after start.
modern combat 2 too, but it produces an unspecified error message
Lithophyses said:
i have the new kernel with audio installed, asound.conf was already set to 2.
worms hd works but the sound laggs, no matter if speaker or headphones.
Gangstar 2 closes directly after start.
modern combat 2 too, but it produces an unspecified error message
Click to expand...
Click to collapse
Modern Combat 2 works perfectly, don't know why it crashes for you (using kernel with working audio)
Did anyone managed to run GT Racing?
I get in to the first screen when it asked to d/l files. once done it just closes on me.
after that, the game doesnt even load. just dumps back to menu.
You can play GT Racing on bada.
baza14 said:
You can play GT Racing on bada.
Click to expand...
Click to collapse
**facepalm**
Related
Hi,
with WiMo i was able to play podcasts (h264/aac, 368x208, ~200kBit/s) somewhat smooth with TCMP. With android i get - well - with some luck a frame per minute. I would have said its because of a incomplete/non-optimized GPU-Driver but Youtube (SD) plays fine so for me this looks more like a codec/app-issue. Has anyone already looked for a solution? Any tips on codecs/apps that should work?
SD works, yes. HD/HQ youtube does not however, and I think it's related to a scaling issue.
We're not done with the port... I think this is a pretty minor bug considering the other major ones we have out there....
arrrghhh said:
SD works, yes. HD/HQ youtube does not however, and I think it's related to a scaling issue.
Click to expand...
Click to collapse
...hm… for me exactly this looked like a codec-thing… i dont know the mobile side but for pc i remember something like VP6 for SD and X264 for HD on Youtube. But thanks for the tip, i'll look into this direction too.
arrrghhh said:
We're not done with the port...
Click to expand...
Click to collapse
…and it will never be completely done - otherwise there would be no need for our lovely legacy-forums here
arrrghhh said:
I think this is a pretty minor bug considering the other major ones we have out there....
Click to expand...
Click to collapse
As you already said in another thread: Everyone has his own priorities
Just see this thread as my notepad - i collect my results/ideas here, if someone has made own tests he can add his results and if someone wants to have a look on his own he knows what has been tried already…
B2T: With the described movie i have about 10-20% free CPU-cycles so this should not be the bottleneck. hw3d has no effect (guess this doesnt really affect 2d acceleration). Changing from fullscreen/stretched to original size showed also no difference
adlerweb said:
Just see this thread as my notepad - i collect my results/ideas here, if someone has made own tests he can add his results and if someone wants to have a look on his own he knows what has been tried already…
B2T: With the described movie i have about 10-20% free CPU-cycles so this should not be the bottleneck. hw3d has no effect (guess this doesnt really affect 2d acceleration). Changing from fullscreen/stretched to original size showed also no difference
Click to expand...
Click to collapse
Not a bad idea, I'd like to see this bug squashed.
I've heard it was a scaling issue - have you tried different resolutions? I know someone tried the native resolution of our RHOD, but that didn't work either... I guess I'd be surprised if it is codec, as you can get frozen frames on YouTube HQ and audio plays just fine. I am by no means an expert here tho .
arrrghhh said:
Not a bad idea, I'd like to see this bug squashed.
I've heard it was a scaling issue - have you tried different resolutions? I know someone tried the native resolution of our RHOD, but that didn't work either... I guess I'd be surprised if it is codec, as you can get frozen frames on YouTube HQ and audio plays just fine. I am by no means an expert here tho .
Click to expand...
Click to collapse
I am no expert either but would not the codec be contained in the software such as Utube. And the Multimedia architecture would mostly bypass the Processor. So the problem to me would seem to be routing and timing issue. Thus the beggining frames play but stop due to the loss of coordination.
BigOnes69 said:
I am no expert either but would not the codec be contained in the software such as Utube. And the Multimedia architecture would mostly bypass the Processor. So the problem to me would seem to be routing and timing issue. Thus the beggining frames play but stop due to the loss of coordination.
Click to expand...
Click to collapse
I don't even get any frames to play at the beginning.
It starts with a black screen with audio...
If I skip ahead, I can randomly get freezes of images, but that's about it.
arrrghhh said:
I don't even get any frames to play at the beginning.
It starts with a black screen with audio...
If I skip ahead, I can randomly get freezes of images, but that's about it.
Click to expand...
Click to collapse
What you say supports what I am saying about routing and timing. I am thinking in general terms not specifics and I am no expert.
BigOnes69 said:
What you say supports what I am saying about routing and timing. I am thinking in general terms not specifics and I am no expert.
Click to expand...
Click to collapse
I would think its the processors job to coordinate the frame of reference for the timing. The actual MMS stuff would use that frame of reference to process the video according to the codec provided in the software. The routing and or timing could be screwed because HTC needs a way to get around patent laws. The could have done something as simple as changed polarity or phase or something more complicated as recode with another chip. The audio would works because its simple to process. Our drivers are not doing what needs to be done to process the information. It would have nothing to do with the codec which is contained in the software. Like I said I am guessing.
BigOnes69 said:
I would think its the processors job to coordinate the frame of reference for the timing. The actual MMS stuff would use that frame of reference to process the video according to the codec provided in the software. The routing and or timing could be screwed because HTC needs a way to get around patent laws. The could have done something as simple as changed polarity or phase or something more complicated as recode with another chip. The audio would works because its simple to process. Our drivers are not doing what needs to be done to process the information. It would have nothing to do with the codec which is contained in the software. Like I said I am guessing.
Click to expand...
Click to collapse
Then again the Architecture in our older phones might not be fast enough to process the HQ resolutions.
No, this isn't a question of processing power, it's a matter of having the right codecs installed. I've seen Youtube HQ working on my phone before, running one of tiad8's FroyoX builds with camera kernel, months ago.
The behavior you see where you can skip around and see one good frame, but otherwise nothing, is caused by the actual encoding of the video, and the current codec lacking support for it. (The difference between B frames, I frames, and P frames, if you care to look that up...)
highlandsun said:
No, this isn't a question of processing power, it's a matter of having the right codecs installed. I've seen Youtube HQ working on my phone before, running one of tiad8's FroyoX builds with camera kernel, months ago.
The behavior you see where you can skip around and see one good frame, but otherwise nothing, is caused by the actual encoding of the video, and the current codec lacking support for it. (The difference between B frames, I frames, and P frames, if you care to look that up...)
Click to expand...
Click to collapse
Interesting.
So what do we need to do to get the codec support? I'm assuming the kernel clocks are finally right as well...
found it.
http://www.youtube.com/watch?v=mYW1DIi4ZzY
yankees2450 said:
found it.
http://www.youtube.com/watch?v=mYW1DIi4ZzY
Click to expand...
Click to collapse
That is based off of Tiads cut and paste Blazn if I am correct which was good for video playback but everything else was buggy. This proves HQ can work on our phones.
My question here is wouldnt the Codec that was required by the utube app. be contained within that app. or if it was not when it tried to play back and the codec was missing you would get nothing or a reference to download the required codec such as happens with other operating systems.
Or if the codec is contained in our current version intact. Then it is not referencing the codec properly which goes back to what I originally said about timing and the coordination with the MMS architecture on the phone. It looks as though Tiad had found the proper channeling. Did he leave anyone any information about this before he left this forumn?
BigOnes69 said:
That is based off of Tiads cut and paste Blazn if I am correct which was good for video playback but everything else was buggy. This proves HQ can work on our phones.
My question here is wouldnt the Codec that was required by the utube app. be contained within that app. or if it was not when it tried to play back and the codec was missing you would get nothing or a reference to download the required codec such as happens with other operating systems.
Or if the codec is contained in our current version intact. Then it is not referencing the codec properly which goes back to what I originally said about timing and the coordination with the MMS architecture on the phone. It looks as though Tiad had found the proper channeling. Did he leave anyone any information about this before he left this forumn?
Click to expand...
Click to collapse
He never gave anyone anything useful from his builds.
He was just slapping stuff together, and would see what stuck to the wall.
I heard people had issues with his builds on HQ youtube, and I even tested his junk and wasn't able to get HQ to work... so I think it's just more BS from him.
yankees2450 said:
another junk from tiad8
could this be true?
http://www.neopeek.com/viewtopic.php?f=84&t=6544
Click to expand...
Click to collapse
There's a reason he's banned here. Let's not repost more of his crap here, thanks.
arrrghhh said:
I've heard it was a scaling issue - have you tried different resolutions?
Click to expand...
Click to collapse
Well... Most of my podcast have different resolutions and none worked so far. Also should scaling not be disabled when the Player is set to "original size"?
BigOnes69 said:
I am no expert either but would not the codec be contained in the software such as Utube.
Click to expand...
Click to collapse
I dont know for youtube but most 3rd party video-players i've seen say that supported codecs are device dependent so i guess they are in the rootfs, not the app.
BigOnes69 said:
because HTC needs a way to get around patent laws
Click to expand...
Click to collapse
OK, maybe, but afair do most companys not charge people/companys for playback - only encoding… And "free" codecs like theora or webm would not be affected
BigOnes69 said:
Then again the Architecture in our older phones might not be fast enough to process the HQ resolutions.
Click to expand...
Click to collapse
As said: 20% cpu left and works on Wimo -
I've managed to get "working" video with ffmpeg's default avi-output (think it was divx/mp3) but colors where disorted. My android died yesterday and i had no time to reinstall so i could not test further atm.
adlerweb said:
OK, maybe, but afair do most companys not charge people/companys for playback - only encoding… And "free" codecs like theora or webm would not be affected
Click to expand...
Click to collapse
I think I remember reading the issue the with getting decent video playback wit the MSM GPU is is getting information on the hardware. The codec used to play HQ video on Windows mobile comes from HTC and is written specifically for the MSM7x chipset using proprietary information - information which is not available to everyone, or can only become available for a price and an NDA.
Perhaps there is binary blob that can be used?
toadlife said:
I think I remember reading the issue the with getting decent video playback wit the MSM GPU is is getting information on the hardware. The codec used to play HQ video on Windows mobile comes from HTC and is written specifically for the MSM7x chipset using proprietary information - information which is not available to everyone, or can only become available for a price and an NDA.
Perhaps there is binary blob that can be used?
Click to expand...
Click to collapse
Perhaps a binary blob could be dug up, but we couldn't use it in the AOSP builds. Only custom builds would be able to use it, or individuals will just have to integrate it themselves.
arrrghhh said:
Perhaps a binary blob could be dug up, but we couldn't use it in the AOSP builds. Only custom builds would be able to use it, or individuals will just have to integrate it themselves.
Click to expand...
Click to collapse
That would be fine with me.
toadlife said:
That would be fine with me.
Click to expand...
Click to collapse
Ok... My point is, source is preferred.
If we can't get source, so be it - but a proprietary blob does very little good in the scope of this type of project. I want everyone to have the best Android experience possible, I don't want just a few builds working correctly and others borked. That sucks.
I've read all of hte dock threads, but can't find anyone that may have the same issue as I do.
Here's the history. I was running Calk/Clem, and could watch movies on my TV via the dock's HDMI connection. Everything looked brilliant, nice and crisp.
I decided to try out a HC rom, and went with Gtabcomb. I docked it and tried to watch a video, but the quality was pretty poor. it was pixelated extremely bad. The image on the tablet, though, was beautiful, comparitively.
Figuring that it might have something to do with the rom, and lack of acceleration, I decided to go back to a Froyo rom again. This time, I chose BC, which I had been on before, but didn't have the dock at the time. I, once again, docked it, and attempted to watch a movie, but it too was pixelated.
I flashed Clem's Kernel, thinking that it may have something to do with Pershoots Kernels (which are run on both BC and Gtabcomb) No go, still pixelated.
Wiped dalvik, wiped cache, wipe data/factory reset, reset permissions, repartitioned, flashed Calk/clem again, thinking it will be all right now, but nope, my videos still look perfectly fine on the gtablet, but are pixelated on the TV. They looked absolutely beautiful before, but not anymore. Even the home screens are pixelated, now.
I've tried Rockplayer (the original player when all was fine, software encoding, I get no sound when using hardware encoding) Moboplayer, stock movie player, "video player" that was in the Calk/Clem removed apps folder. Not one of them will play the videos properly on the TV, yet they look wonderful on the tablet itself.
Anyone have any ideas why my dock has started to transfer in a lower resolution than it had previously? I've changed no settings on my TV, and everything else plays fine through it (PC, WII, DVDs, Fios)
A few questions come to mind! Are you sure it's not the movies? Are you using anything different to encode the movies? At what resolution are you encoding the them?
I thought of that too. I don't actually encode any of them. I just ehem, <find> them online. Most are AVI movies. I still had one that I watched prior to the resolution messing up. It looked fine before, and doesn't now. Additionally, it's not just the videos, it's the home screen, the lock screen...everything is pixelated.
I was planning on editing the OP as well. I tried starting simple, and switched out the HDMI cable...It's not that, both cables lead to same results.
Could something have gone wacky with the dock itself, perhaps?
Does the TV detect the input (output from the dock) as 1080p? Have you tried manualy checking/switching display modes on the TV to see if any make a difference or maybe connecting to another TV.
Also. it is the Tegra2 that does the hardware upconvert from the native 1024x600 resolution to the 1080p (1920x1080) output. There are a couple of entries in build.prop that shouldn't change but you can take a look just to make sure...they are persist.tegra.dpy5.mode.width=1920 & persist.tegra.dpy5.mode.height=1080.
This happens to me using the HDMI cable for the gTablet. The homescreen is pixelated, movies are also but they are stil watchable. I've tried 2 tvs and same results on both.
Sent from my SPH-D700 using XDA Premium App
aabbondanza said:
Does the TV detect the input (output from the dock) as 1080p? Have you tried manualy checking/switching display modes on the TV to see if any make a difference or maybe connecting to another TV.
Also. it is the Tegra2 that does the hardware upconvert from the native 1024x600 resolution to the 1080p (1920x1080) output. There are a couple of entries in build.prop that shouldn't change but you can take a look just to make sure...they are persist.tegra.dpy5.mode.width=1920 & persist.tegra.dpy5.mode.height=1080.
Click to expand...
Click to collapse
just checked build.prop, and both of those lines exist...
edit: oh yeah, and I'm poor...only 1 TV available...I have tried changing TV settings with the same results, pixellation...I'm so confused. I wouldn't be surprised if it had been happening all along, but this is a new development, it's weird.
Try this, TJ:
Edit /system/lib/egl/egl.cfg to have these lines:
Code:
0 0 android
0 1 tegra
rajeevvp said:
Try this, TJ:
Edit /system/lib/egl/egl.cfg to have these lines:
Code:
0 0 android
0 1 tegra
Click to expand...
Click to collapse
they already exist...hmmm
TJEvans said:
they already exist...hmmm
Click to expand...
Click to collapse
Use Android's software renderer then:
Code:
0 1 android
0 0 tegra
Then, try switching between the Tegra renderer and Android rendered for display 1 (display 0, I believe, is the tablet screen--display 1 might be the HDMI output):
Code:
1 0 android
1 1 tegra
and
Code:
1 1 android
1 0 tegra
Code:
0 1 android
0 0 tegra
didn't change anything
Code:
1 0 android
1 1 tegra
Lost visual at 3rd splash screen when rebooting...had to reflash rom to get it back
Code:
1 1 android
1 0 tegra
didn't attempt becuase of what happened above, lol
edit: Is there a chance that something is wrong within the dock itself? Just curious, as it seems that the tablet is functioning properly,as is the TV, and the HDMI cable...the only variable not questioned so far has been the dock itself...
TJEvans said:
Lost visual at 3rd splash screen when rebooting...had to reflash rom to get it back
Click to expand...
Click to collapse
Yeah, that was my screw-up. I was in a hurry yesterday and I didn't check. Try these settings:
Code:
0 0 android
0 1 tegra
1 0 android
1 1 tegra
It enables the tegra HW renderer (which is the only one available going by the libs in /system/lib/egl) for both the LCD and the dock.
And, you don't need to reflash the ROM, just create a file with "0 0 tegra" in it (the GtabComb default egl.cfg file) and adb push the file into /system/lib/egl/egl.cfg. That will stop the boot loop.
rajeevvp said:
And, you don't need to reflash the ROM, just create a file with "0 0 tegra" in it (the GtabComb default egl.cfg file) and adb push the file into /system/lib/egl/egl.cfg. That will stop the boot loop.
Click to expand...
Click to collapse
yeah, I've never done the ADB thing before, and I've honestly NEVER had any experience with anything Linux...so, trust me, reflashing was probably the easiest thing that I could do, lol
Edit:
so, in your previous post, should all 4 lines be in the file?
TJEvans said:
Edit:
so, in your previous post, should all 4 lines be in the file?
Click to expand...
Click to collapse
Yeah, give it a try. And, if that doesn't work, I give up and you'll have to seek a higher power.
rajeevvp said:
Yeah, give it a try. And, if that doesn't work, I give up and you'll have to seek a higher power.
Click to expand...
Click to collapse
I am an Elder at my church, you'd think that would give me some "pull," right?
edit: nope, it's a no go, and the big guy wasn't any help either....
thanks for trying, man. one of these days, I'l probably just end up seeing it work...
TJEvans said:
I've read all of hte dock threads, but can't find anyone that may have the same issue as I do.
Here's the history. I was running Calk/Clem, and could watch movies on my TV via the dock's HDMI connection. Everything looked brilliant, nice and crisp.
I decided to try out a HC rom, and went with Gtabcomb. I docked it and tried to watch a video, but the quality was pretty poor. it was pixelated extremely bad. The image on the tablet, though, was beautiful, comparitively.
Figuring that it might have something to do with the rom, and lack of acceleration, I decided to go back to a Froyo rom again. This time, I chose BC, which I had been on before, but didn't have the dock at the time. I, once again, docked it, and attempted to watch a movie, but it too was pixelated.
I flashed Clem's Kernel, thinking that it may have something to do with Pershoots Kernels (which are run on both BC and Gtabcomb) No go, still pixelated.
Wiped dalvik, wiped cache, wipe data/factory reset, reset permissions, repartitioned, flashed Calk/clem again, thinking it will be all right now, but nope, my videos still look perfectly fine on the gtablet, but are pixelated on the TV. They looked absolutely beautiful before, but not anymore. Even the home screens are pixelated, now.
I've tried Rockplayer (the original player when all was fine, software encoding, I get no sound when using hardware encoding) Moboplayer, stock movie player, "video player" that was in the Calk/Clem removed apps folder. Not one of them will play the videos properly on the TV, yet they look wonderful on the tablet itself.
Anyone have any ideas why my dock has started to transfer in a lower resolution than it had previously? I've changed no settings on my TV, and everything else plays fine through it (PC, WII, DVDs, Fios)
Click to expand...
Click to collapse
Also running Calk+Celmv6. Just got my dock in today. I believe that is just the way it is. Home screen & all non hardware accelerated video are very grainy. Viewed mine on a 42". May look better on a smaller TV but probably not a whole lot better. Colors are very overdriven compared to what shows on the gTab.
Watching Netflix was kind of like watching an old VHS that you had recorded from the TV.
Played a converted DVD through Rockplayer in both soft decode & hardware decode. Soft decode was grainy as well. Hardware decode looks MUCH better.
No problem with sound.
Didn't try Moboplayer since on my gTab doesn't play well with it...automatically reduces the volume to 50% and won't go any higher (even though it says it at 100%). I can verify this by exiting Moboplayer & turning up the volume which is at the 50% levelo
Al
I get the same thing with mobo player and sound. With rockplayer, if I choose hardware decoding, I get no sound whatsoever, not just through the dock, but when run undocked, I don't get any sound at all.
TJEvans said:
I get the same thing with mobo player and sound. With rockplayer, if I choose hardware decoding, I get no sound whatsoever, not just through the dock, but when run undocked, I don't get any sound at all.
Click to expand...
Click to collapse
I had some problems with the intial version of Rockplayer that was on v6, especially after I installed Remote Media Center (RMC). RMC said it only works with Mobo & Rock Lite so I downloaded Rockplayer Lite & it worked. The version of Lite was newer so I looked for newer version. Downloaded v1.7.2 and now no problems with rockplayer, even with RMC so uninstalled Lite.
I just finished Final fantasy 4 (android), and I wanted to have the remastered soundtracks from it. But on the internet the remastered version is not available yet, I could only find the old soundtracks.
I tried screencast recorder, z screen recorder etc(to record video+audio then extract audio), but they all record audio from the microphone, so that didn't work out.
So is there a way to extract the audio from the game somehow, or some on screen audio recorder for android devices?
thanks
You might be able to plug your phone into a computer and run a program that just records what the sound card is putting out on your phone
Androideka5 said:
You might be able to plug your phone into a computer and run a program that just records what the sound card is putting out on your phone
Click to expand...
Click to collapse
thanks! Do you know of any software in particular that'll do that?
I'd start by pulling any game files on your Phone apart first.
...Sent from Zed
XperienceD said:
I'd start by pulling any game files on your Phone apart first.
...Sent from Zed
Click to expand...
Click to collapse
+1, game music is indeed located in the game files
If you're responding to me, make sure to quote me so I get an immediate Email
Some people can't make viper4android work on the new Lollipop update so I'm doing a simple guide:
Requirements:
-Root
-Busybox
-Custom recovery
Installation:
1.- Deactivate NuPlayer in developer options.
2.- Deactivate any other equalizer.
3.- Set selinux to permissive with an app like this one https://play.google.com/store/apps/details?id=com.mrbimc.selinux&hl=en
4- Install through recovery the zip located below then reboot.
5.- Open viper4android and install the driver you want and then reboot.
6.- Done, enjoy high quality sound.
these are the only versions of audio_effects and audio_policy i found that work with streaming apps. can you elaborate a bit more about them where did you find them or maybe you have an idea what was modified in them in order for streaming audio to work? thanks!
Good job! But how can I increase the power of the speaker, like in KitKat using Mixer app, but in Lollipop?
mannequin said:
these are the only versions of audio_effects and audio_policy i found that work with streaming apps. can you elaborate a bit more about them where did you find them or maybe you have an idea what was modified in them in order for streaming audio to work? thanks!
Click to expand...
Click to collapse
+1
I use those 2 files from the zip file to make v4a works for poweramp
My previous v4a installation only works on stock music & video player, now works for poweramp and mx player too.
Another note, disabling NUplayer not necessary for me...
Thanks again for this awesome guide :good:
Edit: I found using stock audio_policy.conf is possible to by remove this part:
Deep buffer
deep_buffer {
sampling_rates 44100|48000
channel_masks AUDIO_CHANNEL_OUT_STEREO
formats AUDIO_FORMAT_PCM_16_BIT
devices AUDIO_DEVICE_OUT_SPEAKER|AUDIO_DEVICE_OUT_EARPIECE|AUDIO_DEVICE_OUT_WIRED_HEADSET|AUDIO_DEVICE_OUT_WIRED_HEADPHONE|AUDIO_DEVICE_OUT_ALL_SCO|AUDIO_DEVICE_OUT_AUX_DIGITAL|AUDIO_DEVICE_OUT_PROXY|AUDIO_DEVICE_OUT_ANLG_DOCK_HEADSET|AUDIO_DEVICE_OUT_FM|AUDIO_DEVICE_OUT_FM_TX
flags AUDIO_OUTPUT_FLAG_DEEP_BUFFER
}
Note: removing compress offload not necessary, as stated in dorimanx lp kernel thread. So removing deep buffer part only is enough.
didhiy said:
Edit: I found using stock audio_policy.conf is possible to by removing this 2 sections:
Click to expand...
Click to collapse
do you mean just by removing these 2 sections stock audio_policy and audio_effects can be used instead?
btw, these two .conf files from OP zip break screen casting functionality of chromecast so i'm wondering if your solution will work.
edit: i think it does!
Thanks so much, it really helped
didhiy said:
+1
I use those 2 files from the zip file to make v4a works for poweramp
My previous v4a installation only works on stock music & video player, now works for poweramp and mx player too.
Another note, disabling NUplayer not necessary for me...
Thanks again for this awesome guide :good:
Edit: I found using stock audio_policy.conf is possible to by removing this 2 sections:
1. Compress offload
compress_offload {
sampling_rates 8000|11025|12000|16000|22050|24000|32000|44100|48000|64000|88200|96000|176400|192000
channel_masks AUDIO_CHANNEL_OUT_STEREO
formats AUDIO_FORMAT_MP3|AUDIO_FORMAT_AAC|AUDIO_FORMAT_PCM_24_BIT_OFFLOAD
devices AUDIO_DEVICE_OUT_EARPIECE|AUDIO_DEVICE_OUT_SPEAKER|AUDIO_DEVICE_OUT_WIRED_HEADSET|AUDIO_DEVICE_OUT_WIRED_HEADPHONE
flags AUDIO_OUTPUT_FLAG_DIRECT|AUDIO_OUTPUT_FLAG_COMPRESS_OFFLOAD|AUDIO_OUTPUT_FLAG_NON_BLOCKING
}
2. Deep buffer
deep_buffer {
sampling_rates 44100|48000
channel_masks AUDIO_CHANNEL_OUT_STEREO
formats AUDIO_FORMAT_PCM_16_BIT
devices AUDIO_DEVICE_OUT_SPEAKER|AUDIO_DEVICE_OUT_EARPIECE|AUDIO_DEVICE_OUT_WIRED_HEADSET|AUDIO_DEVICE_OUT_WIRED_HEADPHONE|AUDIO_DEVICE_OUT_ALL_SCO|AUDIO_DEVICE_OUT_AUX_DIGITAL|AUDIO_DEVICE_OUT_PROXY|AUDIO_DEVICE_OUT_ANLG_DOCK_HEADSET|AUDIO_DEVICE_OUT_FM|AUDIO_DEVICE_OUT_FM_TX
flags AUDIO_OUTPUT_FLAG_DEEP_BUFFER
}
Click to expand...
Click to collapse
So, i've been having this huge problem on Nexus 7 2013 w\power amp and 5.1.1 cm12.1 and getting convolver and irs files to work properly.
two questions,
are your irs files working?
also, is the audio policy config on this thread flashable or pushable?
masri1987 said:
So, i've been having this huge problem on Nexus 7 2013 w\power amp and 5.1.1 cm12.1 and getting convolver and irs files to work properly.
two questions,
are your irs files working?
also, is the audio policy config on this thread flashable or pushable?
Click to expand...
Click to collapse
No problem with irs & convolver on my D802, both working normally. I don't know for other devices.
The file from op is flashable from recovery. You can try that.
Just for comparison, I use other methods, I installing v4a manually then install the drivers from the app. Imho audio effect config will change when v4a installing driver. Most useful part from this thread for me only the audio policy config that solve my problem make other apps like poweramp work with v4a. Then I found that audio policy config from D802 stock rom can be use too by removing 2 parts. I believe this solution is better because I only lost 2 features from stock rom, not as much as the policy config from op.
didhiy said:
No problem with irs & convolver on my D802, both working normally. I don't know for other devices.
The file from op is flashable from recovery. You can try that.
Just for comparison, I use other methods, I installing v4a manually then install the drivers from the app. Imho audio effect config will change when v4a installing driver. Most useful part from this thread for me only the audio policy config that solve my problem make other apps like poweramp work with v4a. Then I found that audio policy config from D802 stock rom can be use too by removing 2 parts. I believe this solution is better because I only lost 2 features from stock rom, not as much as the policy config from op.
Click to expand...
Click to collapse
Yeah, i flashed the file above and did everything properly, but IRS convolver files aren't exactly being 'used', not all irs files are working properly.
Should i be doing anything to the audio policy config file ? I use power amp too (although it did tell me it was processing under power amp),
IRS is crucial to me because i use my N7 2013 in my car as my in-dash.
masri1987 said:
Yeah, i flashed the file above and did everything properly, but IRS convolver files aren't exactly being 'used', not all irs files are working properly.
Should i be doing anything to the audio policy config file ? I use power amp too (although it did tell me it was processing under power amp),
IRS is crucial to me because i use my N7 2013 in my car as my in-dash.
Click to expand...
Click to collapse
I think that's unrelated to the audio policy config thing, this thread already prove the way v4a working for D802. Solved the major problem why v4a only works for stock music & video player.
I suggest you to ask in the v4a main thread or maybe ask the dev that creates your favorite irs that didn't work. I only use 2 irs files & both working normally.
this is kind of off topic but perhaps somebody is experiencing the same. i'm having a weird audio issue on LP which wasn't present on KK in any way and not V4A related.
no matter what the audio source is (playing mp3s or lossless, tons of EQ on or off, YouTube video, game, video, etc) there's a totally random, short sound corruption that sounds like garbled, sped up noise. it's impossible to trace any pattern when and why does it appear and perhaps it's related to radio since it tends to appear more when the signal is switching from Wi-Fi to cellular or cellular signal comes online, etc but not necessarily. i tried to look at the logs and don't see anything suspicious regarding sound there at all.
there's also a theory on other devices forums that Qualcomm's mpdecision is the cause since it always leaves only one core for the sound online and on LP apparently you need more. that doesn't seem right, however, since it does happen when the phone is doing a lot too and not just with the screen off.
any ideas are welcomed.
mannequin said:
this is kind of off topic but perhaps somebody is experiencing the same. i'm having a weird audio issue on LP which wasn't present on KK in any way and not V4A related.
no matter what the audio source is (playing mp3s or lossless, tons of EQ on or off, YouTube video, game, video, etc) there's a totally random, short sound corruption that sounds like garbled, sped up noise. it's impossible to trace any pattern when and why does it appear and perhaps it's related to radio since it tends to appear more when the signal is switching from Wi-Fi to cellular or cellular signal comes online, etc but not necessarily. i tried to look at the logs and don't see anything suspicious regarding sound there at all.
there's also a theory on other devices forums that Qualcomm's mpdecision is the cause since it always leaves only one core for the sound online and on LP apparently you need more. that doesn't seem right, however, since it does happen when the phone is doing a lot too and not just with the screen off.
any ideas are welcomed.
Click to expand...
Click to collapse
You can try if the theory was right or wrong by temporary disabling mpdecision. I think the setting is in /mpt/enable file. Change the value from 1 to 0, than compared the results. Don't forget to enable it again by changing the value on that file back to 1. If still no different, I guess the theory was invalid.
doesnt work for me I flashed the zip and then got "viper 4 Android stopped working" on Start, now I cannot install it in the normal way. Every Reboot that "viper 4 Android stopped working" thing comes and idk what to do
didhiy said:
+1
I use those 2 files from the zip file to make v4a works for poweramp
My previous v4a installation only works on stock music & video player, now works for poweramp and mx player too.
Another note, disabling NUplayer not necessary for me...
Thanks again for this awesome guide :good:
Edit: I found using stock audio_policy.conf is possible to by removing this 2 sections:
1. Compress offload
compress_offload {
sampling_rates 8000|11025|12000|16000|22050|24000|32000|44100|48000|64000|88200|96000|176400|192000
channel_masks AUDIO_CHANNEL_OUT_STEREO
formats AUDIO_FORMAT_MP3|AUDIO_FORMAT_AAC|AUDIO_FORMAT_PCM_24_BIT_OFFLOAD
devices AUDIO_DEVICE_OUT_EARPIECE|AUDIO_DEVICE_OUT_SPEAKER|AUDIO_DEVICE_OUT_WIRED_HEADSET|AUDIO_DEVICE_OUT_WIRED_HEADPHONE
flags AUDIO_OUTPUT_FLAG_DIRECT|AUDIO_OUTPUT_FLAG_COMPRESS_OFFLOAD|AUDIO_OUTPUT_FLAG_NON_BLOCKING
}
2. Deep buffer
deep_buffer {
sampling_rates 44100|48000
channel_masks AUDIO_CHANNEL_OUT_STEREO
formats AUDIO_FORMAT_PCM_16_BIT
devices AUDIO_DEVICE_OUT_SPEAKER|AUDIO_DEVICE_OUT_EARPIECE|AUDIO_DEVICE_OUT_WIRED_HEADSET|AUDIO_DEVICE_OUT_WIRED_HEADPHONE|AUDIO_DEVICE_OUT_ALL_SCO|AUDIO_DEVICE_OUT_AUX_DIGITAL|AUDIO_DEVICE_OUT_PROXY|AUDIO_DEVICE_OUT_ANLG_DOCK_HEADSET|AUDIO_DEVICE_OUT_FM|AUDIO_DEVICE_OUT_FM_TX
flags AUDIO_OUTPUT_FLAG_DEEP_BUFFER
}
Click to expand...
Click to collapse
OMG! thanks.
mannequin said:
this is kind of off topic but perhaps somebody is experiencing the same. i'm having a weird audio issue on LP which wasn't present on KK in any way and not V4A related.
no matter what the audio source is (playing mp3s or lossless, tons of EQ on or off, YouTube video, game, video, etc) there's a totally random, short sound corruption that sounds like garbled, sped up noise. it's impossible to trace any pattern when and why does it appear and perhaps it's related to radio since it tends to appear more when the signal is switching from Wi-Fi to cellular or cellular signal comes online, etc but not necessarily. i tried to look at the logs and don't see anything suspicious regarding sound there at all.
there's also a theory on other devices forums that Qualcomm's mpdecision is the cause since it always leaves only one core for the sound online and on LP apparently you need more. that doesn't seem right, however, since it does happen when the phone is doing a lot too and not just with the screen off.
any ideas are welcomed.
Click to expand...
Click to collapse
Iam having the exact same issue also convolver are not working.
gozzaa said:
Iam having the exact same issue also convolver are not working.
Click to expand...
Click to collapse
after much experimenting i can confirm that the only way to fix that issue is to always keep 2 or more CPU cores online, nothing else solves it at all.
with stock kernel the only option is to disable mpdecision and enable "multicore power saving" and "soc temperature throttle" for further heat control because without mpdecision you'll be keeping all 4 cores online.
mannequin said:
after much experimenting i can confirm that the only way to fix that issue is to always keep 2 or more CPU cores online, nothing else solves it at all.
with stock kernel the only option is to disable mpdecision and enable "multicore power saving" and "soc temperature throttle" for further heat control because without mpdecision you'll be keeping all 4 cores online.
Click to expand...
Click to collapse
Ah i will try that, Iam using dorimanx.
Did you get convolvers to work? They dont have any effect for me. Also the effect of viper4android is very small on lollipop. I can hear a difference but its nothing compared to kitkat
gozzaa said:
Ah i will try that, Iam using dorimanx.
Did you get convolvers to work? They dont have any effect for me. Also the effect of viper4android is very small on lollipop. I can hear a difference but its nothing compared to kitkat
Click to expand...
Click to collapse
I had someone trouble getting convolvers to work as well. Converting viper to a user app with titanium uninstalling the driver then reconverting it to a system app worked for me.
Manbot27 said:
I had someone trouble getting convolvers to work as well. Converting viper to a user app with titanium uninstalling the driver then reconverting it to a system app worked for me.
Click to expand...
Click to collapse
after converting back to system app you install the drivers again or when its user app?
Edit: it worked! Iam using it as user app and its working flawless! Kudos to you
gozzaa said:
Ah i will try that, Iam using dorimanx.
Did you get convolvers to work? They dont have any effect for me. Also the effect of viper4android is very small on lollipop. I can hear a difference but its nothing compared to kitkat
Click to expand...
Click to collapse
obviously using a custom kernel gives way more options to keep those 2 cores online in less destructive manner.
no problems with V4A here, everything works exactly like on KK. like mentioned above the key is to use it as a system app, modify selinux mode and edit audio policies files.
I have the mx player pro. recently acquired the LG G Pad 8.0 x. I could not get the mx player to play my gopro 4 silver videos at 2.7k 30p (protune turned on) using hw or hw+. the software decoder is not able to playback without serious lag. I searched the forum for LG G pad but didn't find any hits regarding this. hoping there could be a workaround or updates to allow hw or hw+ playback.
rcboosted said:
I have the mx player pro. recently acquired the LG G Pad 8.0 x. I could not get the mx player to play my gopro 4 silver videos at 2.7k 30p (protune turned on) using hw or hw+. the software decoder is not able to playback without serious lag. I searched the forum for LG G pad but didn't find any hits regarding this. hoping there could be a workaround or updates to allow hw or hw+ playback.
Click to expand...
Click to collapse
It means your device doesn't support hardware acceleration for that profile. Can you collect the bugreport immediately after playing the video that has issues & share here..?
Sent from my SM-G900H using Tapatalk
ktsamy said:
It means your device doesn't support hardware acceleration for that profile. Can you collect the bugreport immediately after playing the video that has issues & share here..?
Sent from my SM-G900H using Tapatalk
Click to expand...
Click to collapse
Thank you for the reply. Attached is the bug report. I played the video using software decoder, then tried to switch to HW, it tells me HW decoder is not supported, and I pulled the report right after.
rcboosted said:
Thank you for the reply. Attached is the bug report. I played the video using software decoder, then tried to switch to HW, it tells me HW decoder is not supported, and I pulled the report right after.
Click to expand...
Click to collapse
Your logs are insufficient. It only contains the logs when MX Player has closed the video.
Kindly save the bug report as soon as you open the video in HW/HW+ decoder.
Sent from my SM-G900H using Tapatalk
double post...
ktsamy said:
Your logs are insufficient. It only contains the logs when MX Player has closed the video.
Kindly save the bug report as soon as you open the video in HW/HW+ decoder.
Sent from my SM-G900H using Tapatalk
Click to expand...
Click to collapse
Ok I did it again, I guess I didn't do it right. I opened the file, clicked on HW+, clicked off the prompt, ran the report. I did it both for HW and HW+
Just wondering if the new logs I pulled are sufficient.
rcboosted said:
Just wondering if the new logs I pulled are sufficient.
Click to expand...
Click to collapse
It's still same.
Sent from my SM-G900H using Tapatalk
ktsamy said:
It's still same.
Sent from my SM-G900H using Tapatalk
Click to expand...
Click to collapse
I'm not sure what I'm doing wrong. I open mx player, open the video, it starts to play in sw, i switch to hw, it immediately gave me the error message, I click away(I have to) I open the menu to create the bug report. is there any step that I missed? what else can I do to get you an usable report?
rcboosted said:
I'm not sure what I'm doing wrong. I open mx player, open the video, it starts to play in sw, i switch to hw, it immediately gave me the error message, I click away(I have to) I open the menu to create the bug report. is there any step that I missed? what else can I do to get you an usable report?
Click to expand...
Click to collapse
The method is right. It seems that either your system uses low log buffer or any other process is generating more logs. Logs in android memory is limited. So, when the buffer overflows it will erase old logs in order to make space for new logs.
In Developer Options, Increase the Log Buffer Size to Max value. In my device it's 16M. Then repeat the same procedure you have used earlier to collect the bug report. It may be helpful.
I will check it. If it's not yet complete, only option is connect to PC & collect the logs through ADB.
ktsamy said:
The method is right. It seems that either your system uses low log buffer or any other process is generating more logs. Logs in android memory is limited. So, when the buffer overflows it will erase old logs in order to make space for new logs.
In Developer Options, Increase the Log Buffer Size to Max value. In my device it's 16M. Then repeat the same procedure you have used earlier to collect the bug report. It may be helpful.
I will check it. If it's not yet complete, only option is connect to PC & collect the logs through ADB.
Click to expand...
Click to collapse
I turned on developer options and changed the log buffer size to 16M as you have then ran the report. The size is still very small, not sure if that's an indication of anything. Ran it twice.
rcboosted said:
I turned on developer options and changed the log buffer size to 16M as you have then ran the report. The size is still very small, not sure if that's an indication of anything. Ran it twice.
Click to expand...
Click to collapse
The current report has enough logs. But, the playback has failed with a uncommon error code (9001). The error code is not defined in standard android mediaplayer api. Probably the ROM developer or OEM might have defined the custom error. So, It's very hard to identify the exact reason.
For me it looks like, the profile is not supported by the Hardware Decoders.
As I have pointed in many other places, without hardware acceleration, playback may laggy depends upon the video parameters.
Sent from my SM-G900H using Tapatalk
ktsamy said:
The current report has enough logs. But, the playback has failed with a uncommon error code (9001). The error code is not defined in standard android mediaplayer api. Probably the ROM developer or OEM might have defined the custom error. So, It's very hard to identify the exact reason.
For me it looks like, the profile is not supported by the Hardware Decoders.
As I have pointed in many other places, without hardware acceleration, playback may laggy depends upon the video parameters.
Sent from my SM-G900H using Tapatalk
Click to expand...
Click to collapse
That's unfortunate. Since you don't have the definition of these uncommon error code, is there anything that can be done to get the code and possible get a profile to work?
rcboosted said:
That's unfortunate. Since you don't have the definition of these uncommon error code, is there anything that can be done to get the code and possible get a profile to work?
Click to expand...
Click to collapse
Try contacting LG about this. They could release an update to patch this. http://www.lg.com/us/support-mobile/lg-LGV521WG