I have seen a multitude of websites and audio mods which provide mixed opinions on the following line found in build.prop:
af.resampler.quality=X
And also adding a line to build.prop called:
af.resample=X
Do either of these actually make a difference to the processing of Audio in Android (note: I am using a Nexus 4, if that makes any difference)? And because "af.resampler.quality=4" was already part of build.prop (I'm running stock Android 4.3), does anyone know for fact what the parameters for this option are?
Thanks to all replies in advance!
UPDATE: If there's another forum where there's a better chance of me getting a reply, please do move it. Thank You.
Sorry, had to bump to keep the thread up.
Sorry, had to bump yet again. Would really like answers to this Q. Isn't there anyone with experience on this topic?
i would like to know and i notice that this isn't on my HP Touchpad by default.
Related
What kind of user-specific info is there in the build.prop file?
I'm having weird crackling on my view when I try to use bluetooth for voice, and it sucks. I figure there is something in my build.prop file that isn't quite done right... I followed the instructions for the flyer, and I know other people have this part working on their views, so I just figured having a post with people's EXACT build.prop might help everyone.
Instead of editing the build file and finding all the right parts in it, we should be able to simply just download the file and replace the old one...
UNLESS of course, there is a lot of personal information that can be gleened from it and should not be shared.
Whachall think?
Hi Everyone,
Has anyone changed the NT build.prop to have it being recognized as a different tablet? Like say a Samsung Galaxy Tab?
Care to share your settings? Please?
The reason I ask is that a lot of the Market apps are not availble for our NT,and so by changing it, it should give us more option and openess to download and install those apps.
Thanks in advance.
Wickster said:
Hi Everyone,
Has anyone changed the NT build.prop to have it being recognized as a different tablet? Like say a Samsung Galaxy Tab?
Care to share your settings? Please?
The reason I ask is that a lot of the Market apps are not availble for our NT,and so by changing it, it should give us more option and openess to download and install those apps.
Thanks in advance.
Click to expand...
Click to collapse
This has been a very well covered topic.
http://forum.xda-developers.com/showthread.php?t=1398310&highlight=build+prop
A little bit of advice, try doing searches before posting asking about something that has been widely discussed. This item was pretty easily found and there are certain people that get mad when new users ask old questions. I am not one of those people, but it will save you some grief. Then if you have questions regarding something you don't understand people will be more likely to help you out. Good Luck....
Hey guys, I have a few questions. I looked around a bit before posting this, but I may have missed some stuff so if I need to remove this thread just let me know that I should have looked harder(and kindly provide a link please).
First I would like to know how to get into "Themeing". I want to know how to change the colors mostly. I can usually find the file I need to edit in order to change the icon shape, but If I'm not mistaken, the colors are probably controlled in an xml file. They may all look for a "central file" that contains the colors, or I may need to change each one individually. If there is a central file could someone help me find out what it is.
I have only found how to edit apps, so here's where I get a major case of the noobs. Are the system colors controlled by the launcher or the theme or is there a UI that can be edited what do I need to do. I want to be able to change the number styles, the fonts of the keyboard, and all that jazz. The most important thing, though; is that I need to be able to change the colors. I really don't have an issue with the current fonts and don't have a good idea what to replace them with anyway.
---------------------------------------------------------------------------------------------
Now that the above train wreck is over I have some harder questions.
I also want to get into developing. I will probably start by modifying someone else's. (side question, could I re-release theirs with my changes just so that people could test it provided I ask and give them credit. I know this depends on the person, but is it taboo, or just a no for some people) I already read through and followed shrike1978's. It was possibly the best thing that could have happened to me. It showed me that it was actually possible to do for someone with less android experience. (link)
But after I have built it what do I need to do to get started modifying it? I'm not even sure what all I want to do, but is there any suggestions of a starter project, as well as a how to do it?(maybe changing the launcher, or something like that)
Also I have been using xfce linux mint on a second hard drive of 75 gigs. Will this be an ok setup? Should I switch to ubuntu although I don't really like it as much?
Should I be s-off or on (maybe on so that I know that they will be supported)? Also is there any good vm's that run in linux and will run android?
I probably missed a few questions that I intended to ask, so I will edit them in when needed.
I plan to make a how to thread on my findings(hopefully good enough shrike gives me a :highfive: for doing a good job) so everyone who helps (provided I actually learn how and am capable of making the how to) will be thanked in my future famous thread
Also I apologize for any miss-types. I will do my best to correct them, but my keyboard is pretty broken (it took a tumble when I moved home for winter break)
I figured out the fonts(at least for the few roms I checked). They are easy to change and add. They are controlled in a system_fonts.xml in the "\system\etc" folder of the rom. The files that they represent are in the "\system\fonts" folder of the rom. The xml file has a pretty good explanation of how it is read, so adding your own should be pretty easy.
If anyone here has any suggestions even if you dont know for sure let me know please.;
Here's some threads I had bookmarked that may help:
http://forum.xda-developers.com/showthread.php?p=16459009
http://forum.xda-developers.com/showthread.php?t=916814
I had another one that I can't find the bookmark for.
feralicious said:
Here's some threads I had bookmarked that may help:
http://forum.xda-developers.com/showthread.php?p=16459009
http://forum.xda-developers.com/showthread.php?t=916814
I had another one that I can't find the bookmark for.
Click to expand...
Click to collapse
You are my hero.
NOTE: A lot of this info is duplicated from a post i had made on droidrzr a while ago. I'm adding it here because i'm actively looking into getting this working once again and I would love any input/thoughts that other devs have on this topic.
Ok, so i've been poking around trying to get HDMI support working in non moto-based ROMs (basically anything that would be using kexec or an AOSP base like CM). It's not complete but i figure it's better to have more eyes on this than just mine. Apologies ahead of time if this post turns into a big info-dump, but here's what i have so far. Also, this is HDMI only, not webtop related.
Initial research:
My previous phone was a Droid X and there were similar issues relating to HDMI on non-stock roms. So my first inclination was to look into how that was fixed.
Here's the post in question: http://rootzwiki.com...m-audio-solved/
Basically, there are some required framework files that are needed for detecting an HDMI cable, notifying the system that it exists and enabling the output. There were also some permissions files and an APK that needed to be copied as well. The big issue with this is that the APK needed to be signed with a signature that matched the one that the ROM was built with (and since a lot of devs use the default android test/build keys, this wasn't all that difficult).
Now, keep in mind that the HDMI on the droid X wasn't mirror mode and operated VERY differently. However, it gave me a good place to start looking on the razr.
Some digging:
First, after looking through system/app i found this apk: ExtDispService.apk. As with the DX, this file is definitely going to be needed. This was where i started digging. I re-signed it and added it to the CM install zip, and put it on my phone. Now, of course it immediately crashed, but at least i had some logs to help me determine why.
Tools:
As a small note, I was using Virtuous Ten Studio to do a lot of this editing. I can't stress enough how awesome this program is for things like this. I had been doing it all manually at the start and making ONE change to that APK would take me close to 15 minutes. With VTS, i could do it in 5 or less. So from here on out, if you're following along, be sure to have the APK and JAR files mentioned added to a project in VTS and de-compiled so that you can see the smali code.
The roadblocks:
So once i had the logs, i was able to see where the APK was crashing. I knew that I would need to include some items from the framework, but i just wasn't sure what yet.
The first hiccup was in ExtDispService$HandleInitAutoDetectSetting.
Code:
const-string v3, "hdmi_autodetection"
invoke-static {v1, v3}, Lcom/motorola/android/provider/MotorolaSettings;->getInt(Landroid/content/ContentResolver;Ljava/lang/String;)I
So, from looking at this, you can see that it's trying to access a Moto utility that allows programs access to information from the settings menu. In this particular instance, it's the on/off switch for HDMI autodetect. This opened up a whole new can of worms. How would we add these items back to the settings menu? How would we fake the overscan setting?
My first inclination was to look for the MotorolaSettings class and include that into the package. However, this could potentially lead us down a very dark path of dependency hell. Worst case scenario: we have to include a lot of moto's framework to get this working (and isn't the whole point of this to get away from moto's code?!). I attempted to remove the references to the settings menu in the smali code and replace them with hardcoded values. This was EXTREMELY hackey but it was more of a proof of concept at this point anyway. I was able to get the phone to boot and not have ExtDispService crash on me, however there was also no response when I plugged in the HDMI cable (nothing at all in the logs).
List of files needed:
Here are a list of some files that i know are required to get this working:
system/app/ExtDispService.apk
system/framework/framework-ext.jar
system/lib/libextdispjni.so
system/lib/libhdmi.so
system/lib/libhdcp.so
Some final thoughts:
I realize that there isn't too much concrete info here, but I wanted to share what progress I had made so that maybe someone else could either pick up from where i've left off, or make some suggestions on how to proceed.
EDIT: I wasn't sure if this belonged in the Android Development sub-forum or not, but i put it here just to be safe. If a mod sees this and think's thats a better place, please feel free to move it.
HDMI is mostly related to the kernel (for kexec at least). But currently there is a new kernel and a workaround for kexec in development, 3.0.31 / 3.0.88 Kernel. Two of the main goals are Full HD video recoding and HDMI.
The apks only will not work as there are complete different drivers in the kexec kernel. I guess we would have it working already if this could have been fixed by app side.
However, maybe I'm wrong
Hash told me about the current development, you can see it in their repo of course. Maybe we should wait a little more..
Gesendet von meinem XT910 mit Tapatalk 4
Ah, wonderful! I just read through your thread. Thanks for posting here about it. I'll be keeping an eye on the new kernel. If there's anything i can do to help out, be sure to let me know.
djuniah said:
Ah, wonderful! I just read through your thread. Thanks for posting here about it. I'll be keeping an eye on the new kernel. If there's anything i can do to help out, be sure to let me know.
Click to expand...
Click to collapse
Help is always appreciated! Are you familiar with C coding?
Gesendet von meinem XT910 mit Tapatalk 4
Yup, I am quite familiar with C.
djuniah said:
Yup, I am quite familiar with C.
Click to expand...
Click to collapse
Nice! If you would like to join kernel development, let me kow.
This had been one of the first things that never worked with our custom roms. Your reasearch and approach for solving this damned bug make good sense. I hope you can succeed for all of us and solve the DROID RAZR HDMI MYTH. Thank you.
What do I want to achieve?
I want to play music/prerecorded audio into a ongoing phone call and the other should hear the audio also.
What did I do so far?
I have searched a lot on Google, Stack Overflow, and XDA forum but didn't find a working solution yet. Some engineers claim that it is possible with modifying AOSP code, specially in Framework and Linux kernel Layers. But they didn't provide any resource or doc on how to achieve this or exactly which files need to be edited and where. FYI, I am quite aware that it is not possible normally as Android OS does not allow for security reasons.
What did I find till now?
I have gone through every possible links and found that this question has been asked several times but nobody couldn't provide a solution with proper guidelines. :crying:
Did anyone achieve this recently or is there any way? Thanks in advance.