Database Develop

Help needed to make FidelityXAudio support

I'm building ultimate soundmod for Alsa devices. Right now I released for all Samsung devices using alsa with WM8994 chipset. I plan to extend support to Xperia Alsa-based devices in next release but require the following information below.
1. list of folders in /proc/asound
2. example of /system/etc/asound.conf file (and probably audio-policy.conf)
Please list folder names in 1) with attachments in 2). You can find my mod for other devices as example in http://forum.xda-developers.com/tags.php?tag=fidelityxaudio

1) Folders in proc/asound
card0
msm8960sndcard
2) there is no such file as system/etc/asound.conf file
audio_policy.conf is attached

Thanks. Right now I'm having little hard time differentiating between S4 Pro that uses APQ8064 and this ones. They all said msm8960 for board in build.prop and I'm thinking for additional properties to differentiate between these two.
Would be nice if you could suggest something to help identifying.

Try using model names, LT30p, LT30a, LT25i, LT29i. These are Xperia t, tl, v and tx
Sent from my phone using XDA Premium

Good news. I managed to improve configuration working for all devices. It won't work on devices without Alsa though

UPDATED ADRENO LIBS - how to use it ?

Hi
how to use updated adreno libs posted on official qualcomm site
here > http://forum.xda-developers.com/nexus-4/general/qualcomm-adreno-gpu-binaries-t2667759
i am on infected's CM11 tried replacing old file with new but didnt work because i have noted that there are some addtional libs which are not available on CM11
PLease help

Tap2Unlock source code

This feature would be amazing...It needs to be implemented into kernel.
http://forum.xda-developers.com/android/software-hacking/kernel-tap2unlock-tap2wake-feature-t2965344

@WhiteNeo @ElArchibald
Can you do something about this?

Aria.A97 said:
@WhiteNeo @ElArchibald
Can you do something about this?
Click to expand...
Click to collapse
Need some research. As i said, seems on SXV we have Synaptics ClearPad S3200 Series (RMI4 interface based on I2C bus) touch digitizer. Need update drivers in kernel, and add code for support Tap2Wake function, and touch firmware must support T2W.

I've tried adding basic DT2W feature. It worked as expected for several minutes and then the touch panel start to malfunction (some point is constantly detected as "touched", and thus the system won't respond to any other touch).
Kernel source is here: https://github.com/updateing/android_kernel_sony_msm8960/commits/dt2w (I don't know how to use git then so there's squashed commit for new touch driver and DT2W support)
The driver is taken from Xperia Z kernel source (latest at commit time) and DT2W code from XDA (can't remember It should be initially for HTC Sensation).
And as for the digitalizer firmware, I don't think Sony will provide us with updates for these things... Firmwares in stock 4.1 and 4.3 are the same.
Finally, the digitalizer on Xperia TX may be Synaptics S3000, instead of S3200. I checked this by adding a pr_info in init function of driver (half a year ago). Don't know if the other two phones are using the same..

Is there any progress with Tap2Unlock? I have been revisiting this thread for some time now and and nothing new..

Can the CM12 theme engine be ported to stock firmware alone?

Guys,
Recently, I am struggling between using cm12.1 and stock .222 firmware foe my Z because they both have something I desire ( system ui and camera for .222 and cm theme engine for cm12 ). My question is can they exist on my phone at the same time? If so, what ROMs or addons should I apply to my phone?
Many thanks!
(Sorry for my poor English)

I think you should try xposed + addon Xtheme engine or HKThemeManager.

well83 said:
I think you should try xposed + addon Xtheme engine or HKThemeManager.
Click to expand...
Click to collapse
I have tried those but none of them works om my device…

Try RRO layers
Some apps can be themed,status bar and navigation bar on stock deodexed rooted

No, it cannot. And neither can RRO Layers (fully). Both theme engines depend on native code changes, not just Java/Smali changes, which means an .so file must be modified at source, which means Xposed (or any stock mod method) will not work - firmware needs to be modified at AOSP level and compiled from scratch. And since we don't get full Sony source code, it's practically impossible. Not feasible is more accurate.
Source: My own research.
[/thread]
Sent from Xperia Z via Tapatalk

CosmicDan said:
No, it cannot. And neither can RRO Layers (fully). Both theme engines depend on native code changes, not just Java/Smali changes, which means an .so file must be modified at source, which means Xposed (or any stock mod method) will not work - firmware needs to be modified at AOSP level and compiled from scratch. And since we don't get full Sony source code, it's practically impossible. Not feasible is more accurate.
Source: My own research.
[/thread]
Sent from Xperia Z via Tapatalk
Click to expand...
Click to collapse
Ok. Thanks!

iSaidyiu said:
Ok. Thanks!
Click to expand...
Click to collapse
Or u can use Multirom.
I had installed stock fw as primary rom with kexec enabled kernel like Zombie kernel and used Multirom for installing secondary roms like cm12.1 and DU.

langeveld024 said:
Or u can use Multirom.
I had installed stock fw as primary rom with kexec enabled kernel like Zombie kernel and used Multirom for installing secondary roms like cm12.1 and DU.
Click to expand...
Click to collapse
True that.
Another tip if you do this is to use Link2SD (might need Pro, I do but I'm unsure if what I'm about to say is possible in Free version). You can link apps to ext# partition on microSD, and also data for those apps (I think that's the pro feature) - which means you can share user apps between both ROM's with data shared across both.
Keep in mind though that both ROM's need to have same format of apps for this to work. For example its impossible to share between 5.0 and 5.1 apps because 5.1 has a changed file structure for apk's (all their libs and the apk itself goes into a subfolder under apps in 5.1, unlike 5.0) and Link2SD can't handle that (yet, if ever).
I'm guessing CM12.1 and all other 5.1 AOSP Rom's use the same structure as stock 5.1 though, just thought I'd point this out in case you want to use a 5.0 ROM one day.
Sent from Xperia Z via Tapatalk

ZTE Nubia Z9 Mini (NX511j) - Cam driver for international Version

Hey all,
the problme is that the international version has another cam module (13mp) than the chinese version (18mp).
Therefore the custom roms , which are always based on the chinese version and cant use the camera.
Now I need some help on how to implement the driver from the original firmware:
http://rom.download.nubia.com/Germany/Z9mini/NX511J-update.zip
Into this custom rom from mokee:
http://download.mokeedev.com/?device=nx511j
My phone is already rooted and has a custom reovery. I already tried to "zip-edit" the mokee rom and copied/replaced files from the stock rom into the mokee rom , base on this info from here and here e.g.:
Libcamalgo.so
Libcameracustom.so
Libcameraclient.so
Libcameraservice.so
Libcamerametadata.so​
and
system/lib/ libcamdrv.so
system/lib/libcamalgo.so
system/lib/libcameracustom.so
system/lib/libdpframework.so
system\etc\permissions\android.hardware.camera.xml​
and then rezipped the rom and signed the zip with the autosign tool.
This "custom" rom than could even be successfuly installed with twrp without an problem, but then didnt
get beyond the mokee boot logo.
Now my question is:
Can this be due to the fact that the stock rom is 5.02 and the custom rom/mokee is 6.01 and the drivers simply cant work due to another android version?
Am I thinking way to easy with this simple "copy/paste zip editing" and something more complex like editing the kernel has to be done?
Any tip for what to do is very appreciated, as I think I have to solve it by myself due to a lack of mass-interest in this device.

Does it support Indian version?
Sent from my NX511J using XDA-Developers mobile app

Sorry for my late reply, I've been on vacation.
I dont know if it supports the indian version. My device is the EU version I guess...
It has a different camera module whith only 13mp-

Hi!
Just replacing those files can't work. The drivers for the t4k37 camera sensor aren't built in in the mokee release.
When it boots, it only polls those Sony IMX sensors. Furthermore the librarys for the t4k37 sensor arent't in the rom.
I'vre tried to build my own mokee rom, but with no luck, got only to boot animation. The device isn't supported officialy by
Mokee any longer. As I didn't build android before, my knowledge is obviously too little for this kind of task... perhaps some
more experienced guys could help...
Also it's hard to understand what is the exact difference in the chinese, indian , international an german modells of the phone, there are little informations.

Just flashed Mokee MK51.1-nx511j-160420-HISTORY.zip and moved the appropriate libraries to the flash, it seems, that the t4k37 sensor initializes and works. Sadly there's no camera app preinstalled.
Tested with Open Camera App from Playstore. I'll now try to get the original camera app.
Libraries where taken from germans stock rom in vendor folder.

kai4065 said:
Just flashed Mokee MK51.1-nx511j-160420-HISTORY.zip and moved the appropriate libraries to the flash, it seems, that the t4k37 sensor initializes and works. Sadly there's no camera app preinstalled.
Tested with Open Camera App from Playstore. I'll now try to get the original camera app.
Libraries where taken from germans stock rom in vendor folder.
Click to expand...
Click to collapse
Hi kai4065!
Can you give me more info please. Which file list I need to replace. I need to create patch for one of localized firmware. Also may be you know where I can get last de firmware? My device was flashed with NX511J_DECommon_V1.01 now but buyed with 1.02.
Thx for any help.

falkolab said:
Hi kai4065!
Can you give me more info please. Which file list I need to replace. I need to create patch for one of localized firmware. Also may be you know where I can get last de firmware? My device was flashed with NX511J_DECommon_V1.01 now but buyed with 1.02.
Thx for any help.
Click to expand...
Click to collapse
Here's the list:
# Camera
etc/firmware/cpp_firmware_v1_4_0.fw
etc/firmware/cpp_firmware_v1_2_0.fw
etc/firmware/cpp_firmware_v1_1_6.fw
etc/firmware/cpp_firmware_v1_1_1.fw
-lib/libmm-qcamera.so
-lib/libmorpho_jpeg_io.so
-lib/libmmjpeg_interface.so
-lib/libqomx_core.so
-lib/libmorpho_memory_allocator.so
-lib/libmmcamera_interface.so
-lib/libmorpho_strobe_photo_jni.so
-lib/libmorpho_image_converter.so
-lib64/libmorpho_jpeg_io.so
-lib64/libmorpho_memory_allocator.so
-lib64/libmorpho_image_converter.so
lib/hw/camera.msm8916.so
bin/mm-qcamera-daemon
bin/mm-qcamera-app
vendor/lib/libmmcamera_faceproc.so
vendor/lib/libchromatix_ov5648_p5v18g_common.so
vendor/lib/libchromatix_skuf_ov5648_p5v23c_snapshot.so
vendor/lib/libactuator_rohm_bu64297gwz.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_preview.so
vendor/lib/libmmcamera_t4k35.so
vendor/lib/libmmcamera2_stats_modules.so
vendor/lib/libactuator_bu64291gwz.so
vendor/lib/libmmcamera2_stats_algorithm.so
vendor/lib/libjpegdhw.so
vendor/lib/libmmcamera_t4k37_qtech_f4k37ab.so
vendor/lib/libmmcamera2_c2d_module.so
vendor/lib/libmmcamera2_cpp_module.so
vendor/lib/libmmcamera2_vpe_module.so
vendor/lib/libmmcamera_ov2720.so
vendor/lib/libmmcamera_S5K4E1_13P1BA.so
vendor/lib/libchromatix_t4k35_nightmode_1.so
vendor/lib/libmmipl.so
vendor/lib/libchromatix_t4k35_common.so
vendor/lib/libchromatix_ov2720_preview.so
vendor/lib/libmmcamera_sunny_q5v22e_eeprom.so
vendor/lib/libjpegehw.so
vendor/lib/libmmcamera2_sensor_modules.so
vendor/lib/libchromatix_ov5648_q5v22e_zsl.so
vendor/lib/libchromatix_ov5648_oty5f03_common.so
vendor/lib/libmmcamera_sp1628.so
vendor/lib/libmmcamera_skuf_ov5648_p5v23c.so
vendor/lib/libmmQSM.so
vendor/lib/libactuator_bu64291gwz_t4k35.so
vendor/lib/libmmcamera_wavelet_lib.so
vendor/lib/libchromatix_t4k35_preview.so
vendor/lib/libchromatix_t4k35_hfr_120.so
vendor/lib/libmmcamera2_pproc_modules.so
vendor/lib/libmmcamera_imx132.so
vendor/lib/libmmjpeg.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_snapshot.so
vendor/lib/libchromatix_ov5648_oty5f03_default_video.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_nightmode.so
vendor/lib/libactuator_bu64291gwz_camcorder.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_common.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_default_video.so
vendor/lib/libmmcamera_tintless_algo.so
vendor/lib/libmmcamera_ov5648_oty5f03.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_video_hd.so
vendor/lib/libactuator_bu64291gwz_camera.so
vendor/lib/libchromatix_t4k35_default_video.so
vendor/lib/libmmcamera2_wnr_module.so
vendor/lib/liboemcamera.so
vendor/lib/libactuator_bu64291gwz_t4k35_camcorder.so
vendor/lib/libchromatix_ov5648_preview.so
vendor/lib/libmmcamera_ov5648.so
vendor/lib/libmmcamera_ov5648_p5v18g.so
vendor/lib/libchromatix_ov5648_q5v22e_preview.so
vendor/lib/libchromatix_t4k35_snapshot.so
vendor/lib/libchromatix_ov5648_p5v18g_preview.so
vendor/lib/libmmcamera2_isp_modules.so
vendor/lib/libchromatix_ov5648_q5v22e_snapshot.so
vendor/lib/libmm-qdcm.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_hfr_120.so
vendor/lib/libchromatix_t4k35_nightmode.so
vendor/lib/libmmqjpeg_codec.so
vendor/lib/libchromatix_ov5648_q5v22e_common.so
vendor/lib/libmmcamera2_imglib_modules.so
vendor/lib/libmmcamera_tintless_bg_pca_algo.so
vendor/lib/libchromatix_ov5648_p5v18g_default_video.so
vendor/lib/libchromatix_ov5648_q5v22e_default_video_hd.so
vendor/lib/libchromatix_ov5648_common.so
vendor/lib/libchromatix_ov5648_oty5f03_snapshot.so
vendor/lib/libmmcamera_imglib.so
vendor/lib/libmmcamera_hdr_gb_lib.so
vendor/lib/libchromatix_ov5648_p5v18g_default_video_hd.so
vendor/lib/libmmcamera2_frame_algorithm.so
vendor/lib/libmmcamera_hi256.so
vendor/lib/libmmcamera2_iface_modules.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_liveshot.so
vendor/lib/libchromatix_skuf_ov5648_p5v23c_common.so
vendor/lib/libchromatix_ov5648_default_video.so
vendor/lib/libchromatix_skuf_ov5648_p5v23c_default_video.so
vendor/lib/libchromatix_ov5648_p5v18g_zsl.so
vendor/lib/libqomx_jpegdec.so
vendor/lib/libchromatix_ov5648_snapshot.so
vendor/lib/libchromatix_ov5648_oty5f03_preview.so
vendor/lib/libmmcamera_hdr_lib.so
vendor/lib/libmmcamera_ov5648_q5v22e.so
vendor/lib/libactuator_bu64291gwz_t4k35_camera.so
vendor/lib/libchromatix_ov5648_oty5f03_zsl.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_pre4zsl.so
vendor/lib/libchromatix_ov5648_zsl.so
vendor/lib/libqomx_jpegenc.so
vendor/lib/libchromatix_ov5648_q5v22e_default_video.so
vendor/lib/libmmcamera_ov5645.so
vendor/lib/libchromatix_t4k37_qtech_f4k37ab_nightmode_1.so
vendor/lib/libmmcamera2_is.so
vendor/lib64/libmmcamera2_stats_algorithm.so
vendor/lib64/libchromatix_imx214_hfr_60fps.so
vendor/lib64/libchromatix_imx219_q8n13a_common.so
vendor/lib64/libactuator_rohm_bu64297gwz_camcorder.so
vendor/lib64/libchromatix_imx214_default_video_4k.so
vendor/lib64/libchromatix_imx214_nightmode_1.so
vendor/lib64/libchromatix_imx219_q8n13a_default_video.so
vendor/lib64/libchromatix_imx219_q8n13a_liveshot.so
vendor/lib64/libchromatix_ov8858_q8v19w_common.so
vendor/lib64/libchromatix_imx234_liveshot.so
vendor/lib64/libchromatix_imx219_q8n13a_snapshot.so
vendor/lib64/libchromatix_imx234_hfr_120.so
vendor/lib64/libchromatix_ov16825_common.so
vendor/lib64/libchromatix_imx214_snapshot.so
vendor/lib64/libchromatix_imx234_snapshot_nightmode_1.so
vendor/lib64/libchromatix_imx214_liveshot.so
vendor/lib64/libchromatix_ov8858_snapshot.so
vendor/lib64/libchromatix_imx234_snapshot_nightmode.so
vendor/lib64/libchromatix_ov8858_liveshot.so
vendor/lib64/libchromatix_imx179_preview.so
vendor/lib64/libchromatix_ov8858_hfr_60fps.so
vendor/lib64/libchromatix_imx234_common.so
vendor/lib64/libchromatix_ov8858_q8v19w_snapshot.so
vendor/lib64/libchromatix_ov13850_default_video.so
vendor/lib64/libchromatix_imx219_q8n13a_preview.so
vendor/lib64/libchromatix_imx234_default_video.so
vendor/lib64/libmmcamera2_frame_algorithm.so
Probably not all files are necessary, but i was too lazy to test it out one by one. I just replaced all of them. The libs for the imx sensor probably aren't needed.
Latest german rom is V1.01, as far as I know. Never ever seen a german localized V1.02. Files above were taken from 1.01.
Just works for 5.1, as in Mokee 60.1 there's some sort of timeout when it tries to initialize the driver. Some patching would be needed, but trying to build Mokee myself
didn't resume a working ROM.

kai4065 said:
Here's the list
Click to expand...
Click to collapse
Thank you! I'll try. :good:

Just wanted to let you know,that I was sick of copying the files in every new release, so I just swapped the main camera sensor with the Sony sensor found in the Chinese model. Works like a charm.