[FIX] Video playback and slow dl speeds on new radio - Nexus One Android Development

The new radio does break the video playback,
however I have found that if you add these entries:
ro.media.enc.file.format = 3gp,mp4
ro.media.enc.vid.codec = m4v,h263
ro.media.enc.vid.h263.width = 176,352
ro.media.enc.vid.h263.height = 144,288
ro.media.enc.vid.h263.bps = 64000,800000
ro.media.enc.vid.h263.fps = 1,30
ro.media.enc.vid.m4v.width = 176,352
ro.media.enc.vid.m4v.height = 144,288
ro.media.enc.vid.m4v.bps = 64000,800000
ro.media.enc.vid.m4v.fps = 1,30
into the build.prop file within the /system/ folder this allows all video playback to work properly again. This means that you can keep your new radio
oh yeah and also add
ro.ril.hsxpa=2 (1 if in US)
ro.ril.gprsclass=12 (11 if in US)
and this will increase your dl and ul speed
all you need is notepad++ to edit the build.prop and then use
adb remount
adb push (c:/location build.prop /system/
adb shell reboot
I have attached my own build.prop
Credit to Cyanogen, I researched his build.prop cheers dude
good luck
Dave

Thank you so much!
Good work, man.

Thanks man ! this is awesome.
-------------------------------------
Sent via the XDA Tapatalk App

think you need to edit the title, you need to be clear that this is for the people who flashed froyo and reverted back to a different rom. Thus leaving them with a NEW radio.

thanks. edited my own build.prop and giving it a try!

dibdab214 said:
ro.ril.hsxpa=2 (1 if in US)
ro.ril.gprsclass=12 (11 if in US)
Click to expand...
Click to collapse
Why do you suggest using 1 and 11 if in the US? I've been using 2 and 12 and never noticed a big difference between the two.

m00moo said:
think you need to edit the title, you need to be clear that this is for the people who flashed froyo and reverted back to a different rom. Thus leaving them with a NEW radio.
Click to expand...
Click to collapse
Maybe it works with Froyo as well? Also can someone clarify, though I think I know the answer, I flashed Pershoots kernel with Froyo - this is totally different from that, correct?

alternative approach
I went into /system/etc/media_profiles.xml
and edited it.
Below are the values that work best from my testing:
(do with this what you will, I'm rarely around for questions)
- <MediaSettings>
- <!-- Each camcorder profile defines a set of predefined configuration parameters
-->
- <CamcorderProfiles>
- <EncoderProfile quality="high" fileFormat="mp4" duration="60">
<Video codec="h264" bitRate="3000000" width="720" height="480" frameRate="30" />
<Audio codec="amrnb" bitRate="12200" sampleRate="8000" channels="1" />
</EncoderProfile>
- <EncoderProfile quality="low" fileFormat="3gp" duration="30">
<Video codec="m4v" bitRate="256000" width="176" height="144" frameRate="15" />
<Audio codec="amrnb" bitRate="12200" sampleRate="8000" channels="1" />
</EncoderProfile>
<ImageEncoding quality="100" />
<ImageEncoding quality="90" />
<ImageEncoding quality="80" />
<ImageDecoding memCap="60000000" />
<Camera previewFrameRate="1" />
</CamcorderProfiles>
<EncoderOutputFileFormat name="3gp" />
<EncoderOutputFileFormat name="mp4" />
- <!--
If a codec is not enabled, it is invisible to the applications
In other words, the applications won't be able to use the codec
or query the capabilities of the codec at all if it is disabled
-->
<VideoEncoderCap name="h264" enabled="true" minBitRate="2000000" maxBitRate="3000000" minFrameWidth="800" maxFrameWidth="1280" minFrameHeight="480" maxFrameHeight="720" minFrameRate="24" maxFrameRate="30" />
<VideoEncoderCap name="h263" enabled="true" minBitRate="64000" maxBitRate="1000000" minFrameWidth="176" maxFrameWidth="800" minFrameHeight="144" maxFrameHeight="480" minFrameRate="15" maxFrameRate="24" />
<VideoEncoderCap name="m4v" enabled="true" minBitRate="1000000" maxBitRate="2000000" minFrameWidth="176" maxFrameWidth="800" minFrameHeight="144" maxFrameHeight="480" minFrameRate="15" maxFrameRate="24" />
<AudioEncoderCap name="amrnb" enabled="true" minBitRate="12200" maxBitRate="12200" minSampleRate="8000" maxSampleRate="8000" minChannels="1" maxChannels="1" />
- <!--
I would also like to add this, however, for the build.prop edits, in US, I got the idea from Paul's Desire build.prop, and after research on what it all meant and testing, I found the right categories (values) for me to be as follows:
(of course I'm in Madison, AL and we have awesome HSUDPA here so in other places you may need apply other values)(google gprs class; then google hsdpa category; then google hsupa category; then hsxpa category to see which category fits your signal best)
# bravo RF team request
ro.ril.enable.dtm = 1
ro.ril.gprsclass = 32
ro.ril.hsdpa.category = 8
ro.ril.hsupa.category = 6
ro.ril.hsxpa = 2
To Each His Own...I post every now and then with minor edits that work for me to give a little back..not saying anyoneelse is wrong so if you're that guy who's about to jump me, slow your role, Ya Douche... Here's your Sign.

oh yeah and also add
ro.ril.hsxpa=2 (1 if in US)
ro.ril.gprsclass=12 (11 if in US)
Shouldn't gprsclass=10 in US? Anyways, I added this stuff and flash video for example on network TV sites such as FOX playback beautifully. Just watched Fringe and the quality was close to FLO TV. PS....I completely updated my A22 setup using Pauls update-nexusone-FRF50-signed.zip file on my N1. So I assume that this is a good edit whether or not you stay with original ROM or reverted to original and kept the radio update.

So is this for Froyo or for those reverting back from Froyo to new Rom and not wanting to flash back their old radio?

Wow, tons of confusion going on with these roms and all the "fixes".

serialtoon said:
Wow, tons of confusion going on with these roms and all the "fixes".
Click to expand...
Click to collapse
yeah. and none of the suggestions in the thread worked for me.

This did not fix video playback or download speeds for me under Froyo with new radio.
My download speeds have dropped to 50KB/sec since updating, i used to get up to 400KB/sec
And video playback i can hear audio, but screen is blank, then it FC but even after killing it can still hear audio playing, only way to stop it is to reboot

dibdab214 said:
The new radio does break the video playback,
however I have found that if you add these entries:
ro.media.enc.file.format = 3gp,mp4
ro.media.enc.vid.codec = m4v,h263
ro.media.enc.vid.h263.width = 176,352
ro.media.enc.vid.h263.height = 144,288
ro.media.enc.vid.h263.bps = 64000,800000
ro.media.enc.vid.h263.fps = 1,30
ro.media.enc.vid.m4v.width = 176,352
ro.media.enc.vid.m4v.height = 144,288
ro.media.enc.vid.m4v.bps = 64000,800000
ro.media.enc.vid.m4v.fps = 1,30
into the build.prop file within the /system/ folder this allows all video playback to work properly again. This means that you can keep your new radio
oh yeah and also add
ro.ril.hsxpa=2 (1 if in US)
ro.ril.gprsclass=12 (11 if in US)
and this will increase your dl and ul speed
all you need is notepad++ to edit the build.prop and then use
adb remount
adb push (c:/location build.prop /system/
adb shell reboot
I have attached my own build.prop
Credit to Cyanogen, I researched his build.prop cheers dude
good luck
Dave
Click to expand...
Click to collapse
these properties seem not for a Nexus One, or am i incorrect?
values should be 800x480 instead of 352x288
anyway, i tried all this, and it didn't have any effect. video playback still doesn't work with the new radio

daedelus82 said:
This did not fix video playback or download speeds for me under Froyo with new radio.
My download speeds have dropped to 50KB/sec since updating, i used to get up to 400KB/sec
And video playback i can hear audio, but screen is blank, then it FC but even after killing it can still hear audio playing, only way to stop it is to reboot
Click to expand...
Click to collapse
Your sig shows the older 33.4 kernel from Raven. He has specific Froyo kernels that at least for me...work regarding watching flash stuff. Just watched NCIS on cbs.com and the video was as clear as FloTV was for me, on an LG Vue phone I used to have.

Can we get clarification as to what this is for?
I'm on Froyo right now after coming from Cyan, and personally after looking at many of my Speedtest app download and upload speeds, They seem to be a little lower. But not by a lot. but I'm having issues with speed.
Movies by Flickster is a great app for watching movie trailers and finding local theater's. It plays high quality preview trailers of movies and when I was on Cyan they would take a few seconds to load. And play very well and clear. Now they stutter and have to stop and load, then stop and load again.. Like it's not as stable of a connection. Same thing goes for downloading things in the market (but it could just be overloaded with froyo updaters getting all there apps) Also browsing seems a little slower also like pages loading.

Ok the deal with Froyo and the Radio is This:
The Froyo Radio handles Video encoding. There are dependencies in the Kernel. If you are using a custom kernel not designed for Froyo or you are using a radio other than the one that comes with Froyo, things are going to break. Especially video stuff.
IntersectRavens Kernel works for Video because he built it to, but a few other minor things don't work, like google goggles and there are problems with usb mounting and unmounting.
Anyway if you use stock radio and kernel everything in froyo works. Part of why there is so much confusion is that we have a test rom and no source code. So a lot of "Custom" stuff won't work because it is using Eclair code.
Got it?

Gr8gorilla said:
Ok the deal with Froyo and the Radio is This:
Anyway if you use stock radio and kernel everything in froyo works. Part of why there is so much confusion is that we have a test rom and no source code. So a lot of "Custom" stuff won't work because it is using Eclair code.
Got it?
Click to expand...
Click to collapse
I am using Paul's Froyo (which I assume has stock kernal and radio, does it not?) and have the exact same issues as xguntherc above.
YouTube is now practically useless unless i have wifi.

Gr8gorilla said:
Ok the deal with Froyo and the Radio is This:
The Froyo Radio handles Video encoding. There are dependencies in the Kernel. If you are using a custom kernel not designed for Froyo or you are using a radio other than the one that comes with Froyo, things are going to break. Especially video stuff.
IntersectRavens Kernel works for Video because he built it to, but a few other minor things don't work, like google goggles and there are problems with usb mounting and unmounting.
Anyway if you use stock radio and kernel everything in froyo works. Part of why there is so much confusion is that we have a test rom and no source code. So a lot of "Custom" stuff won't work because it is using Eclair code.
Got it?
Click to expand...
Click to collapse
MP4 do not play for me with Froyo no matter what configuration I use

The fix here does nothing but deteriorate the video encoding but switching it to h263. New radio has the firmware for h264 and h263 both. Froyo has both h263 and h264 and is doing h264 currently. With this it goes back to h263

Related

[Q] cm nightly 54 hw video decodeing??

I was reading the latest changelog for cm7 because the nightly went from 42 to 54 and found this! Is this hw video decoding??
Change-Id:
I987d1fd17462fd41655b193a8cb03709a7d85e8e
Owner
Project CyanogenMod/android_device_advent_vega
Branch gingerbread
Topic
Uploaded Apr 23, 2011 5:27 AM
Updated Apr 23, 2011 2:03 PM
Status Merged
Permalink
Vega : Enable HW Video Decoding
Enable OMX and Opencore prop pulls
Enable TARGET_OVERLAY_ALWAYS_DETERMINES_FORMAT
Enable TARGET_USE_SOFTWARE_AUDIO_AAC
Change-Id: I987d1fd17462fd41655b193a8cb03709a7d85e8e
Where are you seeing these changes ?
I can only see harmony related changes here:
http://cm-nightlies.appspot.com/?device=harmony
Code:
cm_harmony_full-54.zip
Revert "ignore sf error" (android_frameworks_base)
Correct changelog for bad English translation :( (android_vendor_cyanogen)
Changelog revision (android_vendor_cyanogen)
CHANGELOG (android_vendor_cyanogen)
Traditional Chinese: update translation (android_packages_apps_CMParts)
stagefright: Remove extra parenthesis in makefile (android_frameworks_base)
libutils: Fix an improper const-cast in RefBase (android_frameworks_base)
Updated Italian translations (android_packages_apps_CMParts)
Create tablet overlay and set encore to use it (android_vendor_cyanogen)
add csr_tegra support to bluetooth stack (android_external_bluetooth_bluez)
Revert "The ActivityThread will restart a stopped activity before sending onActivityResult" (android_frameworks_base)
harmony: set TARGET_USE_SOFTWARE_AUDIO_AAC in BoardConfig (android_device_harmony)
harmony: set TARGET_OVERLAY_ALWAYS_DETERMINES_FORMAT (android_device_harmony)
Fixes issue #3404 (http://code.google.com/p/cyanogenmod/issues/detail?id=3404) where many applications such as SMS, Contacts, etc would FC if the user changes their locale to Arabic (or any locale that doesn't use the English numeral system) (android_packages_apps_Email)
Convert bearing/heading from 10 bit value to degrees on locapi 20000 (android_hardware_qcom_gps)
Fix for issue 3551 (android_packages_inputmethods_LatinIME)
media: stagefright: Implement TARGET_USE_SOFTWARE_AUDIO_AAC in OMXCodec (android_frameworks_base)
harmony: update extract/setup for Stage Fright (android_device_harmony)
webkit: fix text wrapping (android_frameworks_base)
stagefright: allow targets to pass real dimensions to the decoder (android_frameworks_base)
Check BOARD_VOLD_EMMC_SHARES_DEV_MAJOR to share volumes to get the correct partition number for the volume. (android_system_vold)
Where did you find hw fixes? Its not in the changelog im seeing.
b3ltazar said:
I was reading the latest changelog for cm7 because the nightly went from 42 to 54 and found this! Is this hw video decoding??
Change-Id:
I987d1fd17462fd41655b193a8cb03709a7d85e8e
Owner
Project CyanogenMod/android_device_advent_vega
Branch gingerbread
Topic
Uploaded Apr 23, 2011 5:27 AM
Updated Apr 23, 2011 2:03 PM
Status Merged
Permalink
Vega : Enable HW Video Decoding
Enable OMX and Opencore prop pulls
Enable TARGET_OVERLAY_ALWAYS_DETERMINES_FORMAT
Enable TARGET_USE_SOFTWARE_AUDIO_AAC
Change-Id: I987d1fd17462fd41655b193a8cb03709a7d85e8e
Click to expand...
Click to collapse
Sent from my SPH-D700 using XDA Premium App
juanaraya92679 said:
Where did you find hw fixes? Its not in the changelog im seeing.
Click to expand...
Click to collapse
Here
Not sure how that relates to the latest nightly though.
It can be just one change from many step required to make this work.
Sent from my Nexus S using Tapatalk
All I know is that vids that didnt play before are playing now. A whole lot smoother too.
drx69 said:
All I know is that vids that didnt play before are playing now. A whole lot smoother too.
Click to expand...
Click to collapse
Can you take screenshots with this build? Either via ddms on the desktop, or screenshot ER?
Because not being able to take screenshots (as of the previous nightly) is what drove me to Vegantab (which I like, but I could go back )
drx69 said:
All I know is that vids that didnt play before are playing now. A whole lot smoother too.
Click to expand...
Click to collapse
How's youtube? Can it play HQ vids now?
I can confirm video playback from YouTube without stuttering. I played HD video from both the website (Dolphin and Stock Browser) and the YouTube App. I played the VEVO version of a few songs, and they all played flawlessly.
I am running Pershoot's Overclock Kernel, but all seems fine.
Here is a video link for documentation:
http://www.youtube.com/watch?v=iIk2WnS_lAk
This is indeed an incredible development! I can't wait for it to be refined and eventually baked into all the gingerbread roms. I know there are many of us holding off on jumping from froyo until hardware acceleration is enabled.
How about hardware decoding of local AVI's and wmv's? any tests?
thanks in advance.
pagantek said:
How about hardware decoding of local AVI's and wmv's? any tests?
thanks in advance.
Click to expand...
Click to collapse
no dice yet.
Observed speedups might be due to changes in the streaming libraries or flash handling or something.
Setting up hardware acceleration on video players (moboplayer and rockplayer) still fails.
Also graphics related benchmarks results didn't improve from the earlier rest of the CM7 releases.
video is better here... vplayer wouldnt play vids before, now after this update it plays all my movies perfectly!! i know for a fact they wouldnt play before the update, it was just freezing my gtab yesterday!
I just tried to move from Clem+Calkulin1.5 to the CM7 55 - Videos which works fine on Calkulin (h264 main @3.1 1024x600) plays much slower and sometimes hw decoder dies.
Well, from my personal experience.. this enables HW decoding got the default Android supported video formats... so no HD... only MP4...
crutzulee said:
This is indeed an incredible development! I can't wait for it to be refined and eventually baked into all the gingerbread roms. I know there are many of us holding off on jumping from froyo until hardware acceleration is enabled.
Click to expand...
Click to collapse
My thoughts exactly.
I threw on a Gingerbread rom just after I got my Gtab.
Then I tried a Froyo ROM just for the heck of it.
Until Nvidia drivers are a part of GB, I'll be sticking with Froyo.
strudel.chris said:
My thoughts exactly.
I threw on a Gingerbread rom just after I got my Gtab.
Then I tried a Froyo ROM just for the heck of it.
Until Nvidia drivers are a part of GB, I'll be sticking with Froyo.
Click to expand...
Click to collapse
+1
but in all honesty, CM 7.0.2 is MUCH better than the nightlies 54 and below. Its actually usable now. Coming from Vegan 5.1.1, I dont feel compelled to go back to froyo after flashing CM7 now. With pershoots OC kernel, this will definitely be my daily driver moving forward, and its only going to be get better over time! All of the tegra games run butter smooth, HQ (720p) flash works fine, and .3GP works with much more to follow.
How are videoconferencing apps? Camera and video? tempted t flash back to cm7 from vegan 5.1. 1. I love the cm7 honeycomb theme.
Sent from my SPH-D700 using XDA Premium App

Changing the camcorder frame rate

I saw on the forums a while ago (not that I can find it) that you can boost the recording frame rate as high as 120fps and now I can't find it no matter how many searches I do
If anyone knows maybe some shell commands or anything that would be great.
Also if you know how to use an external Mic for recording I will personally direct a yo mama joke at your fat ugly mother in my first episode
Sent from my MB860 using XDA App
Every post is worth thanking
It's in build.prop somewhere I believe.
posted in error... Apologies.
ertDeath said:
I saw on the forums a while ago (not that I can find it) that you can boost the recording frame rate as high as 120fps and now I can't find it no matter how many searches I do
If anyone knows maybe some shell commands or anything that would be great.
Also if you know how to use an external Mic for recording I will personally direct a yo mama joke at your fat ugly mother in my first episode
Sent from my MB860 using XDA App
Every post is worth thanking
Click to expand...
Click to collapse
here replace this in your build.prop save and reboot i use root explorer or adb shell
adb pull /system/ build.prop
ro.media.camcorder.1080p=mp4,h264,60,24000000,aac,128000,44100,2
ro.media.camcorder.720p=mp4,h264,30,10000000,aac,128000,44100,2
ro.media.camcorder.vga=mp4,h264,30,4000000,aac,128000,44100,2
ro.media.camcorder.cif=mp4,h264,30,1500000,aac,128000,44100,2
ro.media.camcorder.qvga=mp4,h264,15,500000,aac,64000,44100,2
ro.media.camcorder.mms=3gp,h264,15,128000,amrnb,12200,8000,1
ro.media.camcorder.mmsres=qvga
ro.camcorder.zoom=true
ro.media.capture.maxres=8m
ro.media.capture.shuttertone=1
ro.media.panorama.defres=3264x1840
ro.media.panorama.frameres=1280x720
ro.camcorder.videoModes=true
ro.media.capture.fast.fps=4
ro.media.capture.slow.fps=120
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-record=false
after making those changes, how am I supoosed to record videos with 120hz? from the stock camera app?
It should just record at a different frame rate. 120hz recording isn't a feature I was aware the phone had but these edits aren't to open new options they are to change preset ones.
Sent from my MB860 using XDA App
Ill be putting up a thank you soon but from what I can tell these edits may already be present in alien Tom's build.prop which is what I'm using
Sent from my MB860 using XDA App

[Q] Is it possible to record any video with CFR (Constant Frame Rate)?

Here's what I want to do: I'd like to be able to take multiple videos throughout the day and then at the end of the day join them together as one video to upload to YouTube.
Here's the problem: I can't join videos together that are VFR (variable framerate). They need to be converted to CFR first. However, no matter how I try converting them, I always end up with audio/video sync problems. I've spent days and done lots of research and tested several programs/methods to accomplish this. There's still more for me to try, but so far I've not been successful.
Which brings me back to: If I can just get the RAZR to record videos with a constant framerate, the above problem(s) should be eliminated.
My current favorite camcorder app is the LG Camera ("LG" having no relation to the electronics manufacturer). It has many options and blah blah blah. One of the options is to set the framerate. Offers selections as low as 2 FPS up to 60 FPS. Unfortunately (and I have emailed the dev about this), changing this setting doesn't seem to have any effect.
This could be because of a firmware limitation of the device itself, or it could simply be a bug with the app. I don't know yet. I'm trying to find out.
I did find another post around here about recording videos at 120 FPS or something like that. Seems that making some edits to the build.prop file made the phone think it was recording at that FPS but the resulting file showed otherwise. Well, I'm not looking for any real high FPS for my videos. I figure somewhere around 30 should be good enough. The only thing I really want to know is if there is any possible way I can force the camera to record at a constant framerate.
Perhaps the build.prop file can be edited to allow this. I'm not sure. I certainly hope this is possible one way or another, though.
Thanks for your time.
I was one of the people doing the 120fps experiments, and as you noted, nothing worked. I'm thinking the cpu is simply sending a stream of data that the phone must accept.
I'm pretty sure the phone records in a variant of motion jpeg, and simply takes up to 30 stills per second. I've edited these files myself, and it's a pain in the a**.
You need to find a setting in your video editing app that allows for variable framerate content. VFR for short.
Also, .avi containers doesn't support VFR content. You need to save to MKV, MP4, WMV or ASF. Probably more containers, but those are common.
Thanks for the response.
Well, bad news and good news.
Bad news is, I was never able to find any program that could properly convert and/or join the video files without blatant sync problems as a result.
The good news is that the above is not 100% true. After posting my question, I had received some help elsewhere and ended up using ffmpeg and MEncoder (both command line tools for video processing). ffmpeg converts the files to CFR and then MEncoder joins them together. These two utilities combined with the automation power of AutoHotkey allowed me to create an AHK script that will convert and join all the videos successfully simply by dropping the files in the folder and running the script.
In the rare case someone else comes here with the same problem, here's the video-help thread that brought me to this solution: ~~~ Okay, I can't post links. In that case, here's a sample command line for converting the file to CFR:
Code:
ffmpeg -i input01.mp4 -c:v mpeg4 -b:v 1800k -c:a copy -vsync 1 -r 25 temp_output01.mp4
You'll have to run ffmpeg separately on each file, I believe.
Here's a sample MEncoder command line for joining the converted files together:
Code:
mencoder input01.mp4 input02.mp4 input3.mp4 -vf harddup -ovc copy -oac mp3lame -lameopts cbr:br=128 -o joined_output.mp4
You can enter in as many input video filenames as you want to join together.
After I found a solution for converting and joining, I decided to leave this post up because I still wanted to find out if recording in CFR on the Droid was possible. I'm guessing it isn't. That's too bad.
I read about that actually, problem is that directly converting to CFR makes the video somewhat choppy. As you are either playing the same frame twice, or removing a frame to compensate for the fps you're using.
If I'm not too confused, you can interpolate the missing frames to make it appear smoother. At least in some video editors.
Yeah. Fortunately, so far I haven't noticed any obvious issues with the final video.

[Guide] How to Make Viper4Android work on Lollipop

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.

Some games don't detect the sensors

Here are the apps I'll be talking about:
*DroidShooting
*MyBoy - The Gameboy Advance Emulator
So here's the problem.
DroidShooting is an Augmented Reality game which uses the camera to render droids coming which you can shoot. So basically it uses the phone's sensor to calculate all of the movement.<br />
MyBoy, the GBA emulator has a sensor option by which you can tilt your phone to trigger left/right.<br />
So I remember both of these apps used to work perfectly on my old Android 2.2 phone. But now they don't work even on my Android 4.2 and 5.0 phones. It's like there's no sensor in the phone. Ok I understand DroidShooting is already old enough (maybe from 2012) but I'm using the latest release of MyBoy. I wonder why something that worked on my old A2.2 phone won't work now. I hope you guys here can help. Thanks. <br />
EDIT: Other common android apps requiring sensor like racing games work.
Sent from my MotoE2 using Tapatalk

Categories

Resources