Database Info

[Q]Need Android Gurus - Issues

Hi to everybody, I come from the BADA subforum, and there is a new project trying to port Android to samsung Wave phone.
Devs have some issues, we are in the last steps and here is a summary
will want to note that the kernel has been confirmed as able to boot into android homescreen when flashed though JTAG
we're modifying the init scripts to boot it from sdcard
the device is accessible from adb how ever the Android system services such as zygote are restart looping
i *think* i managed to execute standard boot on init.rc with adb interface, zygote and android services appear to be stuck in a restart loop:
http://code.google.com/p/badadroid/source/detail?r=192
EDIT: would like to note that while "VIBETONZ" is appearing on the log, the phone is not vibrating, nothing is appearing on the display either. If possible i'd like a check on my kernel sources Oleg. EDIT AGAIN: the phone does actually vibrate, my bad
line 3150ish you can see the zygote service and various others getting killed and restarting.
EDIT2: another debug log extracted using "adb bugreport" (very large, will want to download in order to view)
http://code.google.com/p/badadroid/source/detail?r=193
http://badadroid.googlecode.com/svn/trunk/adb logs/bugreportnb190511.log
EDIT3: it's possible that the restart loop is caused by lack of memory, this could be caused by the memory mapping of the current bootloader we're using, will have to ask rebellos and srg about that.
added a log to googlecode for procedure to boot kernel using init.rc with adb interface working ( i'm not exactly sure why this works) i may upload the zImage i'm using for this, but it'll only work if you partition your memory card in the correct layout and format.
http://code.google.com/p/badadroid/source/detail?r=194
http://code.google.com/p/badadroid/d...511v2&can=2&q=
Click to expand...
Click to collapse
We need some ideas, or whatever you can provide with your knowledge to help us in this project.
more info: http://forum.xda-developers.com/showthread.php?t=1012856&page=100
Thanks to everybody.

hi to everybody

need help, please!

anybody?

I will take a look later on this evening and see if I can tell anything.

Your kernel seems to work, most of your issues in the log that was posted in my thread come from the ramdisk and system build. Until you work at those for a bit, I don't think you're going to know where to place the blame for issues until you're clean.
For the VM crash loop:
Take all of the non critical apps and gapps out of /system/apps (stuff like vending, maps, touchwiz and so on.)
And see what you get. If you can't solve it that way, then try to do:
adb pull /dbdata/databases/com.android.providers.settings/settings.db settings.db
And see what you get. If its there, it's corrupt. If it isn't, check to make sure the directory is getting created. You can also get someone to pull settings.db from a similar device (i9000?) and try to push it to yours.
But that's only the first of your problems. You have some bad lines in init.rc (your rild daemon isn't configured correctly amongst other things), and a few things missing in /system/bin and /system/lib (calls to missing things). If you aren't using an extract of system.img from the sdk, you probably should. Then you can load in libs one at a time in a clean and controlled environment.
BTW: What Android system are you using? What device did it come from? If you built it from source, seriously, try using an emulator image first.

spacemoose1 said:
Your kernel seems to work, most of your issues in the log that was posted in my thread come from the ramdisk and system build. Until you work at those for a bit, I don't think you're going to know where to place the blame for issues until you're clean.
For the VM crash loop:
Take all of the non critical apps and gapps out of /system/apps (stuff like vending, maps, touchwiz and so on.)
And see what you get. If you can't solve it that way, then try to do:
adb pull /dbdata/databases/com.android.providers.settings/settings.db settings.db
And see what you get. If its there, it's corrupt. If it isn't, check to make sure the directory is getting created. You can also get someone to pull settings.db from a similar device (i9000?) and try to push it to yours.
But that's only the first of your problems. You have some bad lines in init.rc (your rild daemon isn't configured correctly amongst other things), and a few things missing in /system/bin and /system/lib (calls to missing things). If you aren't using an extract of system.img from the sdk, you probably should. Then you can load in libs one at a time in a clean and controlled environment.
BTW: What Android system are you using? What device did it come from? If you built it from source, seriously, try using an emulator image first.
Click to expand...
Click to collapse
It is possible it was not made clear, its a 2.2 stock ROM being ported from the Samsung Galaxy S to the Samsung Wave (formerly a BadaOS device). It is also being booted off of SD as apposed to OneNand. It uses a patched version of the SBL from the galaxy S but when Android is flashed to Nand it can boot fine (although problems are had initializing the Modem).

sabianadmin said:
It is possible it was not made clear, its a 2.2 stock ROM being ported from the Samsung Galaxy S to the Samsung Wave (formerly a BadaOS device). It is also being booted off of SD as apposed to OneNand. It uses a patched version of the SBL from the galaxy S but when Android is flashed to Nand it can boot fine (although problems are had initializing the Modem).
Click to expand...
Click to collapse
You need to compare logs from system booted from nand and from sd. Whatever errors are the same don't matter. Its the different ones that will tell you more.
But you're crashing right now because some line of code somewhere in your build is looking for a database and can't find it. If it doesn't do that when installed to nand, then your problem is that directories that the system creates to host configs and module parts aren't getting created at boot.
The modem issue, (if the error in logcat is the same whether the system booted or not, haven't seen both) looks to be a radio interface layer problem, your rild daemon isn't loading (check /system/bin/ for "rild") and make sure the line in init rc that starts it is correct.

spacemoose1 said:
some line of code somewhere in your build is looking for a database and can't find it.
Click to expand...
Click to collapse
It's a strange problem, as using the extracted system.img from the Android emulator as filesystem the above error disappears - with the same kernel/initramfs/init.rc (obviously other errors appear but the services seems to be stable).
I think we can forget the ril related errors now (I commented out the service in my build together with the DR daemon) as we have no modem driver yet ...

[Q] Front camera in Snapchat broken CM11

Hello,
I have CM11 installed on my htc one s, but the front camera doesn't work in snapchat; It does work in other apps, so is this a problem related to cyanogenmod not having the htc drivers or is this snapchat's fault? More importantly, is there a fix or a snapchat replacement app of some sort which enables the front camera?

Maybe try a newer release of CM 11
Sent from my HTC One S using xda app-developers app

I'm on the latest nightly and it's still broken

Same issue
My camera is stretched and sometimes freezes but only in snapchat. Any ideas?

nikkarus said:
My camera is stretched and sometimes freezes but only in snapchat. Any ideas?
Click to expand...
Click to collapse
Bro same problem and it lags...I hope they can fix it!!!!!!

http://forum.xda-developers.com/showpost.php?p=50728759&postcount=1116
This is happening since 4.3.

phoenixita said:
http://forum.xda-developers.com/showpost.php?p=50728759&postcount=1116
This is happening since 4.3.
Click to expand...
Click to collapse
is there any fix available?

speedfreak007 said:
is there any fix available?
Click to expand...
Click to collapse
Unfortunately not yet.

phoenixita said:
Unfortunately not yet.
Click to expand...
Click to collapse
There is a temporary fix I have been doing since very early CM11 builds.
If you copy a "camera.msm8960.so" from another ROM (I took the one from a GUMMY ROM), and paste it into system/lib/hw (delete/overwrite the old one - may be in capitals "CAMERA.MSM8960.so and not overwrite so must be deleted manually) then the front camera works fine with CM11.
I have issue with my Galaxy S4 and have always done this after installing a new nightly and it has been fine. (Posting here as I was looking for a proper solution through Google searches and saw you are suffering with the same issue)

darrendm said:
There is a temporary fix I have been doing since very early CM11 builds.
If you copy a "camera.msm8960.so" from another ROM (I took the one from a GUMMY ROM), and paste it into system/lib/hw (delete/overwrite the old one - may be in capitals "CAMERA.MSM8960.so and not overwrite so must be deleted manually) then the front camera works fine with CM11.
I have issue with my Galaxy S4 and have always done this after installing a new nightly and it has been fine. (Posting here as I was looking for a proper solution through Google searches and saw you are suffering with the same issue)
Click to expand...
Click to collapse
Why don't they include this file in official cm11? is it HTC owned (not opensource) or something?

darrendm said:
There is a temporary fix I have been doing since very early CM11 builds.
If you copy a "camera.msm8960.so" from another ROM (I took the one from a GUMMY ROM), and paste it into system/lib/hw (delete/overwrite the old one - may be in capitals "CAMERA.MSM8960.so and not overwrite so must be deleted manually) then the front camera works fine with CM11.
I have issue with my Galaxy S4 and have always done this after installing a new nightly and it has been fine. (Posting here as I was looking for a proper solution through Google searches and saw you are suffering with the same issue)
Click to expand...
Click to collapse
Sorry @darrendm
what is a Gummy Rom ? (i'm french sorry)
And what about CM team ? Why don't solve this problem ?

darrendm said:
There is a temporary fix I have been doing since very early CM11 builds.
If you copy a "camera.msm8960.so" from another ROM (I took the one from a GUMMY ROM), and paste it into system/lib/hw (delete/overwrite the old one - may be in capitals "CAMERA.MSM8960.so and not overwrite so must be deleted manually) then the front camera works fine with CM11.
I have issue with my Galaxy S4 and have always done this after installing a new nightly and it has been fine. (Posting here as I was looking for a proper solution through Google searches and saw you are suffering with the same issue)
Click to expand...
Click to collapse
Not sure if this is still an issue for the One S, but it still is for the S4. I just did this and it worked, but I wanted to mention I had to use the camera file from a 4.1 ROM to do so. Hopefully that helps someone else.

spyder91 said:
Not sure if this is still an issue for the One S, but it still is for the S4. I just did this and it worked, but I wanted to mention I had to use the camera file from a 4.1 ROM to do so. Hopefully that helps someone else.
Click to expand...
Click to collapse
I am having this issue as well. Is there a way you could zip up the file as I don't know how to extract the file from a different ROM. Thanks
Edit: I think it may just be a Snapchat issue, as my front camera works for the regular camera app

th3pr1nc30f3gypt said:
I am having this issue as well. Is there a way you could zip up the file as I don't know how to extract the file from a different ROM. Thanks
Edit: I think it may just be a Snapchat issue, as my front camera works for the regular camera app
Click to expand...
Click to collapse
This is the file I use. Taken from an old nightly GUMMY ROM build for the Galaxy S4. It seems to work with every new CM11 nightly I install I so don't think it matters that the file is extracted from an older ROM.
EDIT: Can't seem to attach file so I have linked from my DropBox: https://www.dropbox.com/s/cnnx4gavx43e8v8/camera.msm8960.so

darrendm said:
This is the file I use. Taken from an old nightly GUMMY ROM build for the Galaxy S4. It seems to work with every new CM11 nightly I install I so don't think it matters that the file is extracted from an older ROM.
EDIT: Can't seem to attach file so I have linked from my DropBox: https://www.dropbox.com/s/cnnx4gavx43e8v8/camera.msm8960.so
Click to expand...
Click to collapse
I tried this, restarted my phone, and neither Snapchat or the regular camera app would work. I put the original backup file back in and my regular camera app works again, just not Snapchat front camera

darrendm said:
This is the file I use. Taken from an old nightly GUMMY ROM build for the Galaxy S4. It seems to work with every new CM11 nightly I install I so don't think it matters that the file is extracted from an older ROM.
EDIT: Can't seem to attach file so I have linked from my DropBox: https://www.dropbox.com/s/cnnx4gavx43e8v8/camera.msm8960.so
Click to expand...
Click to collapse
SERIOUSLY. WHAT. THANK YOU SO MUCH
I have been looking for a fix for sooooo long. And thank you for providing the file!
Worked like a charm
Galaxy S4 cm11 4.4.4
Snapchat 5.0.27.1
:good::good::good:

darrendm said:
This is the file I use. Taken from an old nightly GUMMY ROM build for the Galaxy S4. It seems to work with every new CM11 nightly I install I so don't think it matters that the file is extracted from an older ROM.
EDIT: Can't seem to attach file so I have linked from my DropBox: https://www.dropbox.com/s/cnnx4gavx43e8v8/camera.msm8960.so
Click to expand...
Click to collapse
Hey man. Any chance you could re-upload that file or provide intel on how/where to extract it myself?

Ojive said:
Hey man. Any chance you could re-upload that file or provide intel on how/where to extract it myself?
Click to expand...
Click to collapse
https://www.dropbox.com/s/cnnx4gavx43e8v8/camera.msm8960.so
This file works for me on my S4. I paste it into the /system/lib/hw directory after flashing the latest nightly. (you must DELETE the existing file manually as pasting this file into the directory DOES NOT delete the other file of the same name but in capital lettering)
Also, this does not a complete fix for the Snapchat camera issues. I am now able to record video with the front camera however a lot of the time it will still cause the app to freeze or camera to lock up - requiring a phone reboot. HOWEVER this is a lot better than not being able to record ANY videos at all (as it is normally with the CM11 ROMS)
EDIT: the file is extracted from an old GUMMY ROM nightly in the system/lib/hw directory. If this file doesn't work for you, you could try extract the file from other non CM based ROMS and see if if your problem is fixed.

darrendm said:
https://www.dropbox.com/s/cnnx4gavx43e8v8/camera.msm8960.so
This file works for me on my S4. I paste it into the /system/lib/hw directory after flashing the latest nightly. (you must DELETE the existing file manually as pasting this file into the directory DOES NOT delete the other file of the same name but in capital lettering)
Also, this does not a complete fix for the Snapchat camera issues. I am now able to record video with the front camera however a lot of the time it will still cause the app to freeze or camera to lock up - requiring a phone reboot. HOWEVER this is a lot better than not being able to record ANY videos at all (as it is normally with the CM11 ROMS)
EDIT: the file is extracted from an old GUMMY ROM nightly in the system/lib/hw directory. If this file doesn't work for you, you could try extract the file from other non CM based ROMS and see if if your problem is fixed.
Click to expand...
Click to collapse
Thanks <3

darrendm said:
There is a temporary fix I have been doing since very early CM11 builds.
If you copy a "camera.msm8960.so" from another ROM (I took the one from a GUMMY ROM), and paste it into system/lib/hw (delete/overwrite the old one - may be in capitals "CAMERA.MSM8960.so and not overwrite so must be deleted manually) then the front camera works fine with CM11.
I have issue with my Galaxy S4 and have always done this after installing a new nightly and it has been fine. (Posting here as I was looking for a proper solution through Google searches and saw you are suffering with the same issue)
Click to expand...
Click to collapse
Thanks man it really works for me after some tweaks :highfive:
I don't think you need the file "camera.msm8960.so" from another ROM :angel:.
Here is how I did it:
1) In the path system/lib/hw, there is two files "camera.MSM8960.so" (13KB) and "camera.vendor.msm8960.so" (210KB)
2) delete the file "camera.MSM8960.so", but copy its exact name with the capitals. This is important cuz I believe it is case sensitive.
3) rename "camera.vendor.msm8960.so" to "camera.MSM8960.so" which is the exact name of the deleted file
4) make sure the permissions are set as follows: "rw- r-- r--" which is short for read/write OWNER, read GROUP, read OTHER
5) open snapchat and go for video setting change qualiy to low. after that, record a video with front camera and send it to urself.
6) finally put the video quality back to standard and ENJOYYYY it should work for u.
:victory:

[LOS][RR][GZR] Bluetooth Fix for Existing ROMs

Code:
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
A lot.
ROMs with Bluetooth Fix!
For several years I have been frustrated with CM and LOS being unable to connect to my car. To compound this, most custom ROMs are based on these ROMs and use the same BT stack making it nearly impossible to find a custom ROM that works with my vehicle. I had assumed that it was hardware driver related until I found that it happened with the Oneplus 3T as well. I was beginning to lose hope.
But thankfully, it turns out that AOSPA uses a different BT stack that actually works with my car, so I spent several weeks researching ROM building and was finally able to build my favorite ROMs with AOSPA's BT stack! I have made a flashable zip using a bluetooth file found in the stock ROM to fix the issues I've been having. The zip is below. If you have a different device and would like this fix feel free to pm me to make a zip or just follow the instructions in post 2 for how to apply the fix in TWRP without a zip.
Disclaimers:
-I only have a Oneplus 3T, not a 3. This zip should work on both, but keep this in mind.
-This will only fix the issues you're having if the ROM you're taking the file from has Bluetooth that works.
BT Fix v1.2
XDA:DevDB Information
[LOS][RR][GZR] Bluetooth Fix for Existing ROMs, ROM for the OnePlus 3
Contributors
shadeau, TheCrazyLex, Thecrazyskull, arter97, xboxfanj, chrislahaye, carlosavignano, arzbhatia, scoobyjenkins, martinusbe, otisman, akhilnarang, varund7726, westcrip
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: OOS 4.1.6 or later
Based On: AOSP, LineageOS
Version Information
Status: Stable
Current Stable Version: 1.2
Stable Release Date: 2017-09-20
Created 2017-06-21
Last Updated 2017-11-21

Manual Bluetooth File Replacement Instructions
1) Install the ROM with working bluetooth on your device in TWRP
2) While in TWRP (no need to boot) mount the /system folder
3) Using the file manager navigate to /system/lib/hw, select the bluetooth.default.so file, and tap copy
4) Paste this file somewhere in the base /sdcard directory where it won't be deleted when you factory reset
5) Install your favorite ROM with everything like you normally would/restore it from a backup
6) Mount /system in TWRP again (if it became unchecked or you rebooted)
7) Use the file manager to locate the bluetooth.default.so file that you just placed in your internal memory
8) Copy the file and paste it in /system/lib/hw
9) Reboot and test by connecting to device
10) Enjoy!

Troubleshooting
The flashable zip basically does three things:
1) mounts system partition
2) copies modified bluetooth file to system partition
3) unmounts system partition
4) performs update script like all zips
The zip assumes that your system partition is in the normal location (for a 3T) and formatted in ext4 for my script to work. If you have issues then try manually mounting the system partition with TWRP before flashing the zip.

Reserved2

Thank you!!! I can't wait to try this! I've had this exact issue! Should the Validus version work with all CAF based ROMs?
Edit: Nevermind. I misunderstood what this was. Still, thank you very much! I cannot wait to try it still!

jbw716 said:
Thank you!!! I can't wait to try this! I've had this exact issue! Should the Validus version work with all CAF based ROMs?
Click to expand...
Click to collapse
I've built full ROM zips, so you'll need to do a clean install of the ROM that you prefer and you should be good to go. Hope that helps.

Superbbbbbb Thanks, waiting for this fixing for a long time. BT with gear s.3 WORK. Please be keep update.
BTW RR Roms from your file why option in notification slider in additional buttons are difference from the link thread

Hey this sounds pretty interesting. Bluetooth with my car has been hit or miss since and throughout Android 5, 6 and 7!! They fix, they break, they fix and break it again. I have an OP3.
Understanding that it different in everyone's case on device, car and OS's, but this Bluetooth issue seems to be a pain in *** fors some and that includes me.
So I'm now on OOS 4.0.3, Android 7.0.0 and it works, partially. I can't update to any OOS as I lose metadata, AVRCP and additional BT features connections with my vehicle (Lexus IS 250 F Sport 2015).
I had BJRR, Android 6 on my device and it was all working with no issue. If I was on Stock OS, it connect and plays the sound, but no meta or AVRCP no matter what I tried.
I'm rooted, running TWRP and wondering how this will work out. Sounds very promising and looking forward to hearing some feedback from others it is works.
I am wondering if this will work with GZR's Tesla as well.
Cheers!

plepew said:
Hey this sounds pretty interesting. Bluetooth with my car has been hit or miss since and throughout Android 5, 6 and 7!! They fix, they break, they fix and break it again. I have an OP3.
Understanding that it different in everyone's case on device, car and OS's, but this Bluetooth issue seems to be a pain in *** fors some and that includes me.
So I'm now on OOS 4.0.3, Android 7.0.0 and it works, partially. I can't update to any OOS as I lose metadata, AVRCP and additional BT features connections with my vehicle (Lexus IS 250 F Sport 2015).
I had BJRR, Android 6 on my device and it was all working with no issue. If I was on Stock OS, it connect and plays the sound, but no meta or AVRCP no matter what I tried.
I'm rooted, running TWRP and wondering how this will work out. Sounds very promising and looking forward to hearing some feedback from others it is works.
I am wondering if this will work with GZR's Tesla as well.
Cheers!
Click to expand...
Click to collapse
I wish you luck in testing it on your car, and as far as GZR's Tesla is concerned: I'd have to build the whole ROM with the BT fix as a separate ROM (these are all full ROM zips) and I probably won't get around to that for a while. I'm sure the fix will work though. I just need to figure out if this is something that can be converted to a flashable zip instead of needing to build the ROM.

shadeau said:
I wish you luck in testing it on your car, and as far as GZR's Tesla is concerned: I'd have to build the whole ROM with the BT fix as a separate ROM (these are all full ROM zips) and I probably won't get around to that for a while. I'm sure the fix will work though. I just need to figure out if this is something that can be converted to a flashable zip instead of needing to build the ROM.
Click to expand...
Click to collapse
Yes, a flashable zip would be the way to go if possible.
I will try Validus on the weekend and report back if I have success... I've installed in in the past and it's nice. But prefer Tesla due to some features.
Thanks for the quick response!
Cheers!!

shadeau said:
I just need to figure out if this is something that can be converted to a flashable zip instead of needing to build the ROM.
Click to expand...
Click to collapse
Should be doable unless framework is involved.

silentvisitor said:
Should be doable unless framework is involved.
Click to expand...
Click to collapse
I need to change out files in the system/bt folder and the vendor/qcom/bluetooth folder (edit: both of these are in the working directory before building in case that wasn't clear). Are those framework files? I'm kind of new at this and would appreciate help learning how to create a flashable zip if you have some article/forums I can read. Thanks!

Would you be open to posting your sources for these builds?

Strange. It seems that with your version of LOS, the bug is now reversed for me. I get Phone audio through my car now, but not media audio. The radio acts as though it is getting sound, showing the playback time and track name, but the audio comes out of the phone speaker. I'm not sure if a log would help with this sort of thing, but I can try to get one later if it would be helpful.

Excellent job brother! I too have the same issue with my 2015 Nissan Altima. I honestly have no idea why the makers of these roms don't just use this BT stack...... OOS has no issues with my car, so why don't they all use OOS BT? Just makes no sense to me lol

jbw716 said:
Would you be open to posting your sources for these builds?
Click to expand...
Click to collapse
I'm totally open to that. But I need to figure it how to post to git first .
jbw716 said:
Strange. It seems that with your version of LOS, the bug is now reversed for me. I get Phone audio through my car now, but not media audio. The radio acts as though it is getting sound, showing the playback time and track name, but the audio comes out of the phone speaker. I'm not sure if a log would help with this sort of thing, but I can try to get one later if it would be helpful.
Click to expand...
Click to collapse
It might be helpful so post it here and I can look at it. I'll see if I have the same issues in my car and report back.

shadeau said:
I need to change out files in the system/bt folder and the vendor/qcom/bluetooth folder (edit: both of these are in the working directory before building in case that wasn't clear). Are those framework files? I'm kind of new at this and would appreciate help learning how to create a flashable zip if you have some article/forums I can read. Thanks!
Click to expand...
Click to collapse
No framework seemingly.
Which files you're changing (names)?
In most probabilities they're residing in /system/lib and/or /system/bin folder. If so, than you could just make a simple flashable zip or a Magisk module (that'll be a better learning experience).

shadeau said:
I'm totally open to that. But I need to figure it how to post to git first .
It might be helpful so post it here and I can look at it. I'll see if I have the same issues in my car and report back.
Click to expand...
Click to collapse
Here you go. I hope it helps!
https://drive.google.com/file/d/0B22KzlQ3gJRaMHhNbGVDd29JMXM/view?usp=drivesdk

silentvisitor said:
No framework seemingly.
Which files you're changing (names)?
In most probabilities they're residing in /system/lib and/or /system/bin folder. If so, than you could just make a simple flashable zip or a Magisk module (that'll be a better learning experience).
Click to expand...
Click to collapse
Honestly, I swapped the entire folder for each of the two I mentioned. I wanted to get something that worked first and then figure I could sort out the exact file to blame later. I also need to look into the media audio problem since I have the same issue. Thanks for the suggestion, I'll look into building a module for the required files. That should be less time between iterations as well.

shadeau said:
Honestly, I swapped the entire folder for each of the two I mentioned. I wanted to get something that worked first and then figure I could sort out the exact file to blame later. I also need to look into the media audio problem since I have the same issue. Thanks for the suggestion, I'll look into building a module for the required files. That should be less time between iterations as well.
Click to expand...
Click to collapse
Search for "bt" and "bluetooth" in both folders and you'll get list of files. Now extract those files, make a flashable zip and test with some other ROM

Blackview BV9900Pro Magisk Modules

I have installed Caos 11 on my Blackview BV9900Pro. The strange thing is I have to use the a/b version to make it work while it's an a-only device. I got Magisk and exposed to work.
To get the Flir camera to work I installed the MyFlir APK from the original Android 10 ROM from Blackview and I created a Magisk module that 'installs' the libraries and leptonserver bin file. It also starts the leptonserver at boot.
To get the heart rate sensor working I did the same but then for healthcare.
When I have time I will create a manual on how to install Caos 11 on the Blackview 9900(Pro). The only things I noticed up to now is that Volte doesn't work, the Flir camera doesn't work and the heart rate sensor doesn't work. O yeah, after first boot I had to factory reset to make it see/use all storage. Without factory reset Android storage shows just 2GB while it has 128GB.
Attached you find the Magisk Modules and the APK's. Let me know if it works for you on any custom ROM.
Edit 10-09-21:
I changed the MyFlir module. Now it wil also install the MyFlir app. No manual installation of the app anymore. I will do the same for HealthCare later.
edit 11-09-21:
Did the same with HealthCare. No manual installation of the app anymore.

[email protected] said:
I have installed Caos 11 on my Blackview BV9900Pro. The strange thing is I have to use the a/b version to make it work while it's an a-only device. I got Magisk and exposed to work.
To get the Flir camera to work I installed the MyFlir APK from the original Android 10 ROM from Blackview and I created a Magisk module that 'installs' the libraries and leptonserver bin file. It also starts the leptonserver at boot.
To get the heart rate sensor working I did the same but then for healthcare.
When I have time I will create a manual on how to install Caos 11 on the Blackview 9900(Pro). The only things I noticed up to now is that Volte doesn't work, the Flir camera doesn't work and the heart rate sensor doesn't work. O yeah, after first boot I had to factory reset to make it see/use all storage. Without factory reset Android storage shows just 2GB while it has 128GB.
Attached you find the Magisk Modules and the APK's. Let me know if it works for you on any custom ROM.
Edit 10-09-21:
I changed the MyFlir module. Now it wil also install the MyFlir app. No manual installation of the app anymore. I will do the same for HealthCare later.
edit 11-09-21:
Did the same with HealthCare. No manual installation of the app anymore.
Click to expand...
Click to collapse
Thanks for this! MyFlir works now on my BV9900pro with LineageOS 18 GSI. Only issue: App is closing just after pressing the shoot button. No images stored in the gallery. Happy anyway as I can now use at least the Flir thermal camera with my custom rom!

backtoroot said:
Thanks for this! MyFlir works now on my BV9900pro with LineageOS 18 GSI. Only issue: App is closing just after pressing the shoot button. No images stored in the gallery. Happy anyway as I can now use at least the Flir thermal camera with my custom rom!
Click to expand...
Click to collapse
Healthcare App works, too - without any issue. Thanks again! If I ever get TWRP installed on this device but that's another story...

backtoroot said:
Thanks for this! MyFlir works now on my BV9900pro with LineageOS 18 GSI. Only issue: App is closing just after pressing the shoot button. No images stored in the gallery. Happy anyway as I can now use at least the Flir thermal camera with my custom rom!
Click to expand...
Click to collapse
Thank @backroot,
backtoroot said:
Thanks for this! MyFlir works now on my BV9900pro with LineageOS 18 GSI. Only issue: App is closing just after pressing the shoot button. No images stored in the gallery. Happy anyway as I can now use at least the Flir thermal camera with my custom rom!
Click to expand...
Click to collapse
Great it works for you 2. Concerning saving I noticed I had the same issue. I almost never take pictures myself is why I haven't noticed myself. I got this resolved by installing myflir.apk again, without removing myflir app, from the following location:
/system/app/myflir
or
/system/priv-app/myflir
Hope this works 4u2.

Yeaahhhh! To re-install the APP over the old one did the trick! No issue with the save function anymore! Thanks again for your help!
Last issue I discovered with myFlir:
the calibration tool (the last point at settings - not the one on top with the flower/MSX) to adjust the real and thermal camera to be on same focus doesn't work at all. Nothing happens if I try to choose that function. As it's called something like "Picture Adjusting-Tool" it sounds too me like a separate APP or so which is probably missing in my installation.
I can't really tell if it ever worked as this was never an issue with the stock rom but since it works with my custom rom the position of the two pictures is quite different which makes the overlay of the thermal image a bit useless.
Any advice on this?

backtoroot said:
Yeaahhhh! To re-install the APP over the old one did the trick! No issue with the save function anymore! Thanks again for your help!
Last issue I discovered with myFlir:
the calibration tool (the last point at settings - not the one on top with the flower/MSX) to adjust the real and thermal camera to be on same focus doesn't work at all. Nothing happens if I try to choose that function. As it's called something like "Picture Adjusting-Tool" it sounds too me like a separate APP or so which is probably missing in my installation.
I can't really tell if it ever worked as this was never an issue with the stock rom but since it works with my custom rom the position of the two pictures is quite different which makes the overlay of the thermal image a bit useless.
Any advice on this?
Click to expand...
Click to collapse
I've noticed that too and have been searching how to resolve this but haven't been able to find a solution. I know it works on the original rom from Blackview.

How to install twrp?

1x23 said:
How to install twrp?
Click to expand...
Click to collapse
i got TWRP to install by treating the phone as if it had ramdisk.
fastboot devices
fastboot flash boot boot.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash recovery recovery.img
fastboot reboot recovery

TWRP is installed, but read-only. And I couldn't connect an sd card. Thank you for your help.

1x23 said:
TWRP is installed, but read-only. And I couldn't connect an sd card. Thank you for your help.
Click to expand...
Click to collapse
Hey, I'm running an eBay business, had a request to work on the BV9900Pro. I have ported a twrp build from the BV9900, but cannot test because I am not currently in possession of the device. Could you maybe test it for me?

1x23 said:
TWRP is installed, but read-only. And I couldn't connect an sd card. Thank you for your help.
Click to expand...
Click to collapse
If you are trying to flash a GSI, you don't need it. You can do fastboot flash system GSI.img in the bootloader and it will flash. I have booted CAOS and LineageOS. Make sure you download the ab versions because the a only versions do not work for some reason. You could possibly do adb sideload in twrp afterwards for root.

[email protected] said:
I have installed Caos 11 on my Blackview BV9900Pro. The strange thing is I have to use the a/b version to make it work while it's an a-only device. I got Magisk and exposed to work.
To get the Flir camera to work I installed the MyFlir APK from the original Android 10 ROM from Blackview and I created a Magisk module that 'installs' the libraries and leptonserver bin file. It also starts the leptonserver at boot.
To get the heart rate sensor working I did the same but then for healthcare.
When I have time I will create a manual on how to install Caos 11 on the Blackview 9900(Pro). The only things I noticed up to now is that Volte doesn't work, the Flir camera doesn't work and the heart rate sensor doesn't work. O yeah, after first boot I had to factory reset to make it see/use all storage. Without factory reset Android storage shows just 2GB while it has 128GB.
Attached you find the Magisk Modules and the APK's. Let me know if it works for you on any custom ROM.
Edit 10-09-21:
I changed the MyFlir module. Now it wil also install the MyFlir app. No manual installation of the app anymore. I will do the same for HealthCare later.
edit 11-09-21:
Did the same with HealthCare. No manual installation of the app anymore.
Click to expand...
Click to collapse
Good afternoon and what a good afternoon that is.
I have accidentality formatted and downloaded stock ROM by SF Format tool on my BV9800pro phone. I was looking for ways to fix it, even instaled a custom rom.
I'm quoting this user because his file saved me. "MM-Myflir.zip" - so to anyone please make a copy and don't let it get lost.
Now I have again a working phone with thermal cam, that isn't crushing when taking a picture or anything.
Did any of You did it on a stock ROM after crushing it? I don't have much time to explain how I did it (and it took many approaches to do so). So I'll write what I did. I don't know it was the right way to approach it but it works and it's all that matters.
Thanks again
I'm a bit sad. That TWRP on my BV9800pro works only before booting for the first time to the system. I can't decrypt it even if I know the pin that I used.
So I made the stupid mistake of formatting and flashing stock ROM on my phone. Who knew, before having this problem that it will mess up my thermal camera.
Anyway what I did was, unlocking bootloader. Installed TWRP.IMG.
Before first boot to system I went to recovery mode. On my SD card I had my copy of MM-Myflir.zip, and it was decompressed to a folder in Windows.
All I did was transfer files from "lib64", "bin" and "app" folders to those on /system/app/Myflir /system/bin and /system/lib64.
I did not coppy those .sh files.
Now I didn't change any chmod on files, I also didn't use any "getenforce" on those files to make them enforced or permissive.
So here what happened. I didn't check if those files got replaced or not, but the one thing I wanted to replace was the Myflir.apk. I have forgotten to name it properly so it was like in the zip folder Myflir.apk and not Myflir-2.3.8.... (can't remember it whole, because I'm writing this on a bus).
After reboot there was no Myflir apk. That was the moment I understood my mistake. Installed es manager. Went to /system/app/bin directory and installed the app (no root). The app came up on desktop of phone, now it can be uninstalled. But the most important thing is that it WORKS!!!
I wonder if the only step that I could have made was add an app in the same location and to the above, or copying those files was necessary.
Maybe I'll check it out. But I think I'll leve it like this since all works.
Please report on your successes. I would like to know what it took for You.
I did test the phone. On newest stock rom. All above for me is not needed. I don't need to copy all those files. Only thing to copy is the Myflir.app.
But my phone is not formatted again. I lef the recovery partition for TWRP.
Again after booting first time and going trough all those windows. I didn't have my stock Myflir apk installed. So I installed after going to /system/app/Myflir-bv2.3.8...
That did the trick.
I won't go trough format restoring the Tee and google services by sw write tool again just to check if we all could do what I wrote in all my posts....
I hope it is a solution for all people that would like to stay by the stock rom.

app installed via apk keeps crashing

Hello. I'm "slightly" out of my depth here, unfortunately. The aforementioned app (Chess Tactics Pro) suddenly became "incompatible with my device" and so unavailable in play store, I therefore had to extract the apk file from another phone. In fact, I tried 3 different versions of this app. It installs alright and works to some extent, only when I want to use computer analysis function, it crashes. The crash report reads:
java.lang.UnsatisfiedLinkError: dlopen failed: library "liblrengine.so" not found
at java.lang.Runtime.loadLibrary0(Runtime.java:1087)
at java.lang.Runtime.loadLibrary0(Runtime.java:1008)
at java.lang.System.loadLibrary(System.java:1664)
at net.lrstudios.android.chess_problems.chess.engines.LREngine.<clinit>(SourceFile:1)
at h.a.a.a.g.c.T(SourceFile:2)
at h.a.a.a.g.c.W(SourceFile:1)
at h.a.a.a.g.c.onOptionsItemSelected(SourceFile:8)
at androidx.fragment.app.Fragment.performOptionsItemSelected(SourceFile:3)
at c.j.d.k.A(SourceFile:3)
at c.j.d.f.k(SourceFile:1)
at c.j.d.c.onMenuItemSelected(SourceFile:3)
at c.b.k.c.onMenuItemSelected(SourceFile:1)
at c.b.p.i.onMenuItemSelected(SourceFile:1)
at c.b.p.i.onMenuItemSelected(SourceFile:1)
at c.b.k.j$b.onMenuItemClick(SourceFile:1)
at androidx.appcompat.widget.Toolbar$a.onMenuItemClick(SourceFile:2)
at androidx.appcompat.widget.ActionMenuView$d.a(SourceFile:2)
at c.b.p.j.g.h(SourceFile:1)
at c.b.p.j.i.k(SourceFile:2)
at c.b.p.j.g.O(SourceFile:3)
at c.b.p.j.g.N(SourceFile:1)
at androidx.appcompat.widget.ActionMenuView.a(SourceFile:1)
at androidx.appcompat.view.menu.ActionMenuItemView.onClick(SourceFile:2)
at android.view.View.performClick(View.java:7509)
at android.view.View.performClickInternal(View.java:7486)
at android.view.View.access$3600(View.java:841)
at android.view.View$PerformClick.run(View.java:28720)
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:236)
at android.app.ActivityThread.main(ActivityThread.java:8056)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:656)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:967)
Click to expand...
Click to collapse
The phone: vayu (Poco X3 Pro), stock rom, rooted with magisk. On another vayu with the same system (MIUI 11.5), unrooted, it works fine, as it does on 2 other phones with lineageos, both rooted, Android 10 and 11 respectively, and still available in play store. What am I missing? Do you have any ideas what I can try? What does the crash report say? Let me add that the app folder contains like 5 .apk files out of which I only installed base.apk . What are the other apks for? I hope someone can help me with this.

IMO the correct method to get the very reason why an app crashes is to do a LOGCAT.

Thanks. I'll look into it but for now I'm rather busy so it'll have to wait a bit.

It seems that a shared library file, liblrengine.so, is missing.

I appreciate your input but can't check if it works right now as in the meantime I've switched to LineageOS, used SAI to move the whole split package from another phone, but it doesn't work either, complaining that google play store might not be installed or sth to this effect. Anyway, I must install Android Studio and learn how to use logcat, cause other apps also give me problems.

Solved for now. Back to MIUI as LineageOS+MindTheGapps combo misses some dependencies apparently, so the app backed up by SAI wouldn't work there but it works fine in MIUI.