Database Develop

[patch] hdmi multichannel

with this patch you can have multichannel output over hdmi, it is based on ffmpeg to decode the multichannel sound and send it as pcm. Also Apollo can bitstream the sound file (dts/ac3 wav files, maybe flac too as multichannel pcm).
on my AVR the center is swapped with LFE, please test and let me know if is working for you.
the sourcecode is on cyanogenmod gerrit but until now is no merged so I compiled the files, this patch also contains ffmpeg 2.2.2 vs 2.1.4
01.07.2014 - updated for cm nightlies 4.4.4, still LFE bug
Regards

Thanks lucize...amaizing!!! I'll try it this weekend!

Hello, I have a Motorola atrix 2 running an unofficial version of slimkat. based on android 4.4.3, and I have two questions
1. have you fixed the swapped center/lfe channels yet?
2. did you mean cyanogenmod that is 4.4.2 based or an older version.
I'm gonna test it now, I've got backups of my system already, gonna flash it seeing that the droid 4 is the same chipset and slightly faster. I'll report back whether or not multichannel partially works, if at all.

Gizoid1337 said:
Hello, I have a Motorola atrix 2 running an unofficial version of slimkat. based on android 4.4.3, and I have two questions
1. have you fixed the swapped center/lfe channels yet?
2. did you mean cyanogenmod that is 4.4.2 based or an older version.
I'm gonna test it now, I've got backups of my system already, gonna flash it seeing that the droid 4 is the same chipset and slightly faster. I'll report back whether or not multichannel partially works, if at all.
Click to expand...
Click to collapse
is for images that already have ffmpeg in them (i made the patch small, didn't include all the files so it would be functional for earlier versions), if hdmi is working the multichannel should work, didn't had the time to investigate further about center/LFE but I think ffmpeg extractor is the fault.
I'll make a 4.4.4 patch ASAP
Regards

lucize said:
is for images that already have ffmpeg in them (i made the patch small, didn't include all the files so it would be functional for earlier versions), if hdmi is working the multichannel should work, didn't had the time to investigate further about center/LFE but I think ffmpeg extractor is the fault.
I'll make a 4.4.4 patch ASAP
Regards
Click to expand...
Click to collapse
Thanks for great work

so based on this
http://www.spinics.net/lists/linux-omap/msg108750.html
quote: " Also there is still probably something wrong with
speaker mapping of multi-channel streams."
there is hope that channel mapping will be fixed sometime in the near future.
Regards

so will this patch let me use my hdmi cable from my droid 4 to my tv running a aosp rom?

the patch isnt required
edit: cm11 m12 has working hdmi already, didnt test cm12 but im assuming it does as well

Custom Bluetooth module for Nexus 5 (4.4.3) that works with BMW's ULF car kit

Apologies for the links: as I am a new user, I am not allowed to directly link to outside sources. Please replace _ with :// or . (Forum suggestion: use optional pre-publication review for posts from new users that depend strongly on external links.)
INTRODUCTION: My BMW 318 (E46, 2004) had a factory default BMW ULF bluetooth module (early generation) that worked fine with my BB Q10 and all phones up to Android 4.1. From 4.2 onwards, I and many others have been having problems with keeping the Bluetooth connection alive for more than a few seconds. This has been widely reported but never addressed in stock Android. As even the latest OTA upgrade to 4.4.3 didn't solve it, I decided to compile the required Bluetooth kernel module myself.
BACKGROUND: The change from the Bluez to Bluedroid system in Android 4.2 caused the compatibility issues. User 'wulu' at the forums of CyanogenMod reported on how he patched his CM10.2 (and later) to include a patch that solves the issue. I repeated his procedure for stock 4.4.3 for the Nexus 5.
Markus Schmidt's problem description & patch: https_github_com/Root-Box/external_bluetooth_bluedroid/commit/97d2f6346bad56299f60cfcd8c45ad893a0da78c
Wulu's specifics for Nexus 5 & BMW's ULF for CM: http_forum_cyanogenmod_com/topic/77834-bluetooth-connection-drops-car-kit-bmw/
METHODS:
The following procedure is specifically to compiled the Bluetooth kernel module for the Nexus 5 hardware and the 4.4.3_r1.1 (OTA) release. It should therefore only work for this specific combination. If you want to compile the module yourself, please read the linked pages with Google's excellent instructions: http_source_android_com/source/initializing.html
Here are a couple of notes I made that deal with some specifics for my Mac and the Nexus 5:
On Mountain Lion (Mac), I had to use Xcode 5.0.2 to get past a compile error. See instructions here on how to download and use the older 5.0.2 version of Xcode: https_groups_google_com/forum/#!topic/android-building/FPCSo1xKJ4U
Do not download the "master" source using the repo command, but download "android-4.4.3_r1.1". The master source has post-OTA changes that make a compiled module incompatible with the OTA release for the Nexus 5. "android-4.4.3_r1.1" was listed on those pages as specifically the version that was used for the OTA 4.4.3 upgrade for the Nexus 5.
Setup the environment as instructed and add the three proprietary driver sets listed for the Nexus 5 and 4.4.3 (see "Building for devices" on the Google pages).
There is no need to use the full patch. You can make the two small modifications to the bta_ag_sdp.c file using any text editor. Find the file first (find . -name "bta_ag_sdp.c") and commend out the two lines with the minus signs given in wulu's the first post (or Markus Schmidt's patch) by putting a # in front of both lines: #if (p_scb->peer_features == 0), #p_scb->peer_features = p_attr->attr_value.v.u16;.
Select the "aosp_hammerhead-userdebug" (=Nexus 5) option with the lunch command, and compile using the make command. I was able to follow the instructions pretty much to the letter without any problems.
After the compilation I had two version of the file, in four locations. They are easily found using the find command (find . -name "bluetooth.default.so" -exec ls -la {} \. The bigger one (in the symbols subdirectory) is for debugging. The smaller one is the one I used (and which is linked in this message). It was located at "./out/target/product/hammerhead/system/lib/hw/bluetooth.default.so" in my source tree.
After this, it was pretty straightforward. I rooted my Nexus 5, re-installed FX (with paid-for Root add-on, but the free ES File Explorer should also work), uploaded the file via Dropbox and its Save to SD, transferred it to the R/W mounted system directory to replace /system/lib/hw/bluetooth.default.so with it, and restarted my phone. I also modified the config file (/system/etc/bluetooth/auto_pair_devlist.conf) that blacklists BMW components by commenting out most lines, but I am not sure if this is helpful or not.
RESULTS: It seems a little bit less stable than the Bluetooth connection I had with my Blackberry, but it definitely works. I was able to transfer my contacts and to make and receive calls. For anybody with stock KitKat 4.4.3 on the Nexus 5, here is the bluetooth.default.so kernel module: http_s000_tinyupload_com/index.php?file_id=07750725920558658087
DISCUSSION: The compilation procedure can undoubtedly be optimized. I compiled the entire source tree over several hours, just to be sure I didn't miss out on things. Feel free to give tips, but I'm happy that it worked at all.
CONCLUSION: Thanks to wulu's advice in the CM forum thread I was able to compile a patched Bluetooth module for stock Android with KitKat 4.4.3 that works with my BMW 318 (E46, 2004) ULF car kit.

That´s great! :good:
Is it possible for you to provide the same for Nexus 5 - 4.4.4 OTA ?

mnasty said:
That´s great! :good:
Is it possible for you to provide the same for Nexus 5 - 4.4.4 OTA ?
Click to expand...
Click to collapse
Yes, great job!
Nobody have already done this for 4.4.4 ? I'll do this if I have time.

ZeroKcm said:
Yes, great job!
Nobody have already done this for 4.4.4 ? I'll do this if I have time.
Click to expand...
Click to collapse
4.4.4 from 4.4.3 is only security fixes, everything else is the same.

Does 5.0 Lollipop resolve the BMW ULF connection issue?
guys, do you think 5.0 Lollipop would resolve the current BMW ULF connection problem? Have anyone tried the 5.0 yet ?
I'm still in 4.4.3 working great on N5 paring ULF 8th Gen kit, thanks for S1010, wulu and Alpejohn guiding me the entire process.

REV HRD said:
guys, do you think 5.0 Lollipop would resolve the current BMW ULF connection problem? Have anyone tried the 5.0 yet ?
I'm still in 4.4.3 working great on N5 paring ULF 8th Gen kit, thanks for S1010, wulu and Alpejohn guiding me the entire process.
Click to expand...
Click to collapse
I have the same disconnect issue with my Seat, haven't tried the fix cause I was running 4.4.4 and there was no ready module for it, but lollipop didn't fixed it. I tried compilation without success. I followed all the instructions and compiled it successfully, but after replacing it, bluetooth fails to start. In the logcat logs I can see that it complains there is no bluetooth (something like that, don't have the exact logs to check it now), seems the compiled so file is not compatible.
If anyone can give a hand on this

Not sure if Seat using the same implementation as BMW ULF kit provides, my family also has a 06 Audi A4 with stock BT, I don't experience any connection issue from the stock 4.4.3 on N5. I would think Audi / Seat might use the same BT module as they share most of the VW parts.

I experience the same disconnects. I was experiencing it and with the old phone Galaxy Nexus, till one day I updated to cyanogenmod and the problem was gone. Then changed the phone with Nexus5 and again I have the same issues, tried everything with no luck. Changing the kernel, doing some stuff with paid bluetooth apps to manage the phonebook that the car is accessing. So I suspect the problem is the same
(Seems I'm still not able to post links, I just prepared one with the Blutooth device model number and year on it, if it mean anything to someone it is from 03.2007).

Don't work in lollipop, in your free time please compile a new file.
Thks.
S1010 said:
Apologies for the links: as I am a new user, I am not allowed to directly link to outside sources. Please replace _ with :// or . (Forum suggestion: use optional pre-publication review for posts from new users that depend strongly on external links.)
INTRODUCTION: My BMW 318 (E46, 2004) had a factory default BMW ULF bluetooth module (early generation) that worked fine with my BB Q10 and all phones up to Android 4.1. From 4.2 onwards, I and many others have been having problems with keeping the Bluetooth connection alive for more than a few seconds. This has been widely reported but never addressed in stock Android. As even the latest OTA upgrade to 4.4.3 didn't solve it, I decided to compile the required Bluetooth kernel module myself.
BACKGROUND: The change from the Bluez to Bluedroid system in Android 4.2 caused the compatibility issues. User 'wulu' at the forums of CyanogenMod reported on how he patched his CM10.2 (and later) to include a patch that solves the issue. I repeated his procedure for stock 4.4.3 for the Nexus 5.
Markus Schmidt's problem description & patch: https_github_com/Root-Box/external_bluetooth_bluedroid/commit/97d2f6346bad56299f60cfcd8c45ad893a0da78c
Wulu's specifics for Nexus 5 & BMW's ULF for CM: http_forum_cyanogenmod_com/topic/77834-bluetooth-connection-drops-car-kit-bmw/
METHODS:
The following procedure is specifically to compiled the Bluetooth kernel module for the Nexus 5 hardware and the 4.4.3_r1.1 (OTA) release. It should therefore only work for this specific combination. If you want to compile the module yourself, please read the linked pages with Google's excellent instructions: http_source_android_com/source/initializing.html
Here are a couple of notes I made that deal with some specifics for my Mac and the Nexus 5:
On Mountain Lion (Mac), I had to use Xcode 5.0.2 to get past a compile error. See instructions here on how to download and use the older 5.0.2 version of Xcode: https_groups_google_com/forum/#!topic/android-building/FPCSo1xKJ4U
Do not download the "master" source using the repo command, but download "android-4.4.3_r1.1". The master source has post-OTA changes that make a compiled module incompatible with the OTA release for the Nexus 5. "android-4.4.3_r1.1" was listed on those pages as specifically the version that was used for the OTA 4.4.3 upgrade for the Nexus 5.
Setup the environment as instructed and add the three proprietary driver sets listed for the Nexus 5 and 4.4.3 (see "Building for devices" on the Google pages).
There is no need to use the full patch. You can make the two small modifications to the bta_ag_sdp.c file using any text editor. Find the file first (find . -name "bta_ag_sdp.c") and commend out the two lines with the minus signs given in wulu's the first post (or Markus Schmidt's patch) by putting a # in front of both lines: #if (p_scb->peer_features == 0), #p_scb->peer_features = p_attr->attr_value.v.u16;.
Select the "aosp_hammerhead-userdebug" (=Nexus 5) option with the lunch command, and compile using the make command. I was able to follow the instructions pretty much to the letter without any problems.
After the compilation I had two version of the file, in four locations. They are easily found using the find command (find . -name "bluetooth.default.so" -exec ls -la {} \. The bigger one (in the symbols subdirectory) is for debugging. The smaller one is the one I used (and which is linked in this message). It was located at "./out/target/product/hammerhead/system/lib/hw/bluetooth.default.so" in my source tree.
After this, it was pretty straightforward. I rooted my Nexus 5, re-installed FX (with paid-for Root add-on, but the free ES File Explorer should also work), uploaded the file via Dropbox and its Save to SD, transferred it to the R/W mounted system directory to replace /system/lib/hw/bluetooth.default.so with it, and restarted my phone. I also modified the config file (/system/etc/bluetooth/auto_pair_devlist.conf) that blacklists BMW components by commenting out most lines, but I am not sure if this is helpful or not.
RESULTS: It seems a little bit less stable than the Bluetooth connection I had with my Blackberry, but it definitely works. I was able to transfer my contacts and to make and receive calls. For anybody with stock KitKat 4.4.3 on the Nexus 5, here is the bluetooth.default.so kernel module: http_s000_tinyupload_com/index.php?file_id=07750725920558658087
DISCUSSION: The compilation procedure can undoubtedly be optimized. I compiled the entire source tree over several hours, just to be sure I didn't miss out on things. Feel free to give tips, but I'm happy that it worked at all.
CONCLUSION: Thanks to wulu's advice in the CM forum thread I was able to compile a patched Bluetooth module for stock Android with KitKat 4.4.3 that works with my BMW 318 (E46, 2004) ULF car kit.
Click to expand...
Click to collapse

FYI, had similar issue with 2009 E61 5 series. Solution was third party app (Bluetooth Phone book) and a full software update for the car from the dealer. The app cost a few quid, the dealer software update much more!
That said, it works perfectly with stock Lollipop and I consider it money well spent.
---------- Post added at 09:15 PM ---------- Previous post was at 09:13 PM ----------
FYI, it was this app: https://play.google.com/store/apps/details?id=com.android_rsap.irmc

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.

[SOLVED] Porting Linage 17.1 - Modem problems

Hi,
I developed some apps and ported TWRP to some other devices already, therefore I have the feeling that this question is maybe a little bit silly
My current progress
I used the Lineage 17.1 source and the local manifests of MartinX3. Then I fixed the untracked_devices.xml, patched the TRINKET compile errors and finally patched the dialer crash in frameworks/opt/telephony/src/java/com/android/internal/telephony/uicc/UiccController.java:835 by merging the sanity check of the current AOSP upstream. Now the system is stable (as far I am concerned) and (hopefully) everything works - except the SIM card!
The problem
The logs indicate the driver successfully loads, modem starts and the TDC service registers a SIM. But then the RIL reports that no phone has been found an can therefore not use the sim card. For the full log: See attachment! Also Android registers my inserting / removal of the sim card, so... ?!
My question
I guess I have to modify one of the configs (xml) - but which one (as the local manifest I used are only lineagified automatically by GitHub actions and are currently untested with this device)? Where is a reference for the format? How can I diagnose that further? Do you know this problem or have similar experience - how did you solve it?
Greetings,
Simonmicro

Glad someone working on this! I'm looking for an alternative ROM, privacy oriented. I'd test it if it could dial, use SIM card.

Probably flashing Sony vendor image might help? They are based on Android 10 as well as LOS 17.1. https://developer.sony.com/file/download/software-binaries-for-aosp-android-11-0-kernel-4-14-seine/

Well, it works now - I just messed up to select the right configuration (and therefore triggered a ton of bugs inside the slightly dated AOSP source used by Lineage). I hope I can present my first builds in the next days. At least for me it seems stable and only the cams are stubbornly working (as also in AOSP). I'm currently working on OTA support, signing the build inside my CI (which I also plan to open source with the release) and then I must find time to write a guide (and cleanup my scripts) how to flash, as there is no TWRP right now...
EDIT: Btw I failed to use the DSDS build for the dual-sim variant (which I have), which caused the RIL to glitch out, trigger out_out_bounds exceptions inside the UiccController and so on... It was a mess.

Simonmicro said:
Well, it works now - I just messed up to select the right configuration (and therefore triggered a ton of bugs inside the slightly dated AOSP source used by Lineage). I hope I can present my first builds in the next days. At least for me it seems stable and only the cams are stubbornly working (as also in AOSP). I'm currently working on OTA support, signing the build inside my CI (which I also plan to open source with the release) and then I must find time to write a guide (and cleanup my scripts) how to flash, as there is no TWRP right now...
EDIT: Btw I failed to use the DSDS build for the dual-sim variant (which I have), which caused the RIL to glitch out, trigger out_out_bounds exceptions inside the UiccController and so on... It was a mess.
Click to expand...
Click to collapse
Well, there is a unofficial version right now https://forum.xda-developers.com/sony-xperia-10-ii/development/unofficial-twrp-xperia-10-ii-t4190089

Meloferz said:
Well, there is a unofficial version right now https://forum.xda-developers.com/sony-xperia-10-ii/development/unofficial-twrp-xperia-10-ii-t4190089
Click to expand...
Click to collapse
Hey - to be fair: It is brand new! But thanks for pointing that out. I'll may have to rethink my guide now.

[SOLVED] Battery drain on custom ROMs running on SO-02K(Japanese docomo model)

I'm using Xperia XZ1 Compact SO-02K (Japanese docomo model) unlocked bootloader via qUnlockTool.
I installed some custom ROMs like LineageOS 18.1, Havoc OS 4.8, 3.11.
Any ROMs doesn't go to deep sleep so the battery drain is so bad. I installed Android 11 ROMs and 10 ROMs, but both not working deep sleep.
Anyone know good solutions?

Hi,
great to see some other user from Japan with the SO-02K. I also recently installed a custom rom and had the same issues as you. The source is the NFC chip. Unfortunately the Japanese version have a different chip/driver because of the Felica services here (Felica was here in Japan well before Google was even thinking to integrate NFC in Android, so nobody to blame here, beside Google, not Sony.)
Anyway the fix is a bit ugly. However, there is help:
Download this image from here: https://forum.xda-developers.com/t/rom-lineageos-18-1-unofficial-2-0-update-2021-01-20.4047763/
Yes, this and only this. I know it has not been updated anymore, but the reason comes below.
Please check out this thread: https://forum.xda-developers.com/t/fixed-xz1-au-sov36-japan-deepsleep-on-g8341-custom-roms.4156209/
It is about the XZ1 AU version but it also applies to the compact. I summarize here to make the post complete:
Either you root the phone, which I did not do because I do not need root for anything and with root, some of my app do not work, like Spotify. So I recommend to do those steps in the TWRP. Simply mount all the partitions and go to the file manager under advanced options.
Go to folder: /vendor/lib/modules
and delete or rename file call pn553.ko
Restart your phone and it will go to deep sleep. Otsukaresama.
Now, why only this image. Because it uses the older NFC library. In all other images, this fix this not apply anymore, as the modules are not at that place. I really would appreciate if someone more experienced can point me to the nfc module drives in any newer LineageOS image.
PS: Of course NFC will never work with a custom rom (without trying yourself to find out how to make it work)
Best

mugenXperia said:
Hi,
great to see some other user from Japan with the SO-02K. I also recently installed a custom rom and had the same issues as you. The source is the NFC chip. Unfortunately the Japanese version have a different chip/driver because of the Felica services here (Felica was here in Japan well before Google was even thinking to integrate NFC in Android, so nobody to blame here, beside Google, not Sony.)
Anyway the fix is a bit ugly. However, there is help:
Download this image from here: https://forum.xda-developers.com/t/rom-lineageos-18-1-unofficial-2-0-update-2021-01-20.4047763/
Yes, this and only this. I know it has not been updated anymore, but the reason comes below.
Please check out this thread: https://forum.xda-developers.com/t/fixed-xz1-au-sov36-japan-deepsleep-on-g8341-custom-roms.4156209/
It is about the XZ1 AU version but it also applies to the compact. I summarize here to make the post complete:
Either you root the phone, which I did not do because I do not need root for anything and with root, some of my app do not work, like Spotify. So I recommend to do those steps in the TWRP. Simply mount all the partitions and go to the file manager under advanced options.
Go to folder: /vendor/lib/modules
and delete or rename file call pn553.ko
Restart your phone and it will go to deep sleep. Otsukaresama.
Now, why only this image. Because it uses the older NFC library. In all other images, this fix this not apply anymore, as the modules are not at that place. I really would appreciate if someone more experienced can point me to the nfc module drives in any newer LineageOS image.
PS: Of course NFC will never work with a custom rom (without trying yourself to find out how to make it work)
Best
Click to expand...
Click to collapse
Thanks for good solutions!
Actually, I couldn't find pn553.ko on the latest stock ROM(47.2.B.5.38), so I deleted all of NFC files in /Vendor (of cause I took /Vendor backup with TWRP.). The deepsleep little works (please check attached picture) but the battery drain is better than before.
Thanks anyway!

satokun2668 said:
Thanks for good solutions!
Actually, I couldn't find pn553.ko on the latest stock ROM(47.2.B.5.38), so I deleted all of NFC files in /Vendor (of cause I took /Vendor backup with TWRP.). The deepsleep little works (please check attached picture) but the battery drain is better than before.
Thanks anyway!
Click to expand...
Click to collapse
what files did you delete, can you help me to deep sleep?

mugenXperia said:
Hi,
great to see some other user from Japan with the SO-02K. I also recently installed a custom rom and had the same issues as you. The source is the NFC chip. Unfortunately the Japanese version have a different chip/driver because of the Felica services here (Felica was here in Japan well before Google was even thinking to integrate NFC in Android, so nobody to blame here, beside Google, not Sony.)
Anyway the fix is a bit ugly. However, there is help:
Download this image from here: https://forum.xda-developers.com/t/rom-lineageos-18-1-unofficial-2-0-update-2021-01-20.4047763/
Yes, this and only this. I know it has not been updated anymore, but the reason comes below.
Please check out this thread: https://forum.xda-developers.com/t/fixed-xz1-au-sov36-japan-deepsleep-on-g8341-custom-roms.4156209/
It is about the XZ1 AU version but it also applies to the compact. I summarize here to make the post complete:
Either you root the phone, which I did not do because I do not need root for anything and with root, some of my app do not work, like Spotify. So I recommend to do those steps in the TWRP. Simply mount all the partitions and go to the file manager under advanced options.
Go to folder: /vendor/lib/modules
and delete or rename file call pn553.ko
Restart your phone and it will go to deep sleep. Otsukaresama.
Now, why only this image. Because it uses the older NFC library. In all other images, this fix this not apply anymore, as the modules are not at that place. I really would appreciate if someone more experienced can point me to the nfc module drives in any newer LineageOS image.
PS: Of course NFC will never work with a custom rom (without trying yourself to find out how to make it work)
Best
Click to expand...
Click to collapse
hy bro, can you tell me list rom xz1 compact docomo that have pn553 ko?

bangsat69 said:
what files did you delete, can you help me to deep sleep?
Click to expand...
Click to collapse
See this:
[ROM] Havoc-OS 4.6 [OFFICIAL] [R]
Havoc-OS 4.x is based on AOSP, inspired by Google Pixel. Has a refined Material Design 2 UI crafted by @SKULSHADY. Many useful features that will blow your mind. All you can dream of and all you'll ever need. Just flash and enjoy... General...
forum.xda-developers.com