Related
Hi all,
I have visited this forum for some time and always found helpful information.
But this time I messed up this android phone and don't know how to fix it.
Late at night I was flashing custom roms to Motorola XT1032 and couple of other aps, I do it on CWM recovery using adb, so I where operating as root inside of device, had mounted all partition in Read and Write permissions.
Then when I finished applying custom stuff I wanted to delete not needed stuff what I put in /data/local/tmp. At this moment I thougt I am in this path, but I where in / and made "rm * " .
A second later I realized my mistake but that was to late.
Since that I tried to flash custom roms but that did not help to make wifi working again.
After flashing custom roms like ClockworkMod phone is working, mobile reception and bluetooth but no wifi.
I tried to insmod /system/lib/modules/wlan.ko but I got "insmod: init_module '/system/lib/modules/wlan.ko' failed (Operation not permitted)"
I think that need to flash rootfs but not 100% sure and I don't have copy of it.
Please help me.
Chris
I have the exact same problem and I have no idea how to fix it.
Chris.G said:
Hi all,
I have visited this forum for some time and always found helpful information.
But this time I messed up this android phone and don't know how to fix it.
Late at night I was flashing custom roms to Motorola XT1032 and couple of other aps, I do it on CWM recovery using adb, so I where operating as root inside of device, had mounted all partition in Read and Write permissions.
Then when I finished applying custom stuff I wanted to delete not needed stuff what I put in /data/local/tmp. At this moment I thougt I am in this path, but I where in / and made "rm * " .
A second later I realized my mistake but that was to late.
Since that I tried to flash custom roms but that did not help to make wifi working again.
After flashing custom roms like ClockworkMod phone is working, mobile reception and bluetooth but no wifi.
I tried to insmod /system/lib/modules/wlan.ko but I got "insmod: init_module '/system/lib/modules/wlan.ko' failed (Operation not permitted)"
I think that need to flash rootfs but not 100% sure and I don't have copy of it.
Please help me.
Chris
Click to expand...
Click to collapse
Same problem, wifi not active.
The PID are variable.
02-05 16:25:02.055 1049 1060 D WifiService: setWifiEnabled: true pid=9178, uid=1000
02-05 16:25:32.986 9178 9178 I ActivityManager: Timeline: Activity_launch_request id:com.android.settings time:3774476
02-05 16:25:32.987 1049 1061 I ActivityManager: START u0 {act=android.intent.action.MAIN cmp=com.android.settings/.SubSettings (has extras)} from pid 9178
02-05 16:25:33.023 9178 9178 D SubSettings: Launching fragment com.android.settings.wifi.WifiSettings
02-05 16:25:33.112 1049 1106 I ActivityManager: Displayed com.android.settings/.SubSettings: +115ms
02-05 16:25:33.155 9178 9178 I ActivityManager: Timeline: Activity_idle id: [email protected] time:3774645
02-05 16:25:33.457 1049 1106 I ActivityManager: Timeline: Activity_windows_visible id: ActivityRecord{41e2f0f8 u0 com.android.settings/.SubSettings t38} time:3774947
02-05 16:26:02.185 1049 1365 D WifiService: setWifiEnabled: true pid=9178, uid=1000
02-05 16:26:13.257 9178 9178 D BluetoothAdapter: 1115700712: getState() : mService = null. Returning STATE_OFF
02-05 16:26:13.309 9178 9178 D BluetoothAdapter: 1115700712: getState() : mService = null. Returning STATE_OFF
02-05 16:26:13.363 9178 9178 I ActivityManager: Timeline: Activity_idle id: [email protected] time:3814853
02-05 16:26:13.714 1049 1106 I ActivityManager: Timeline: Activity_windows_visible id: ActivityRecord{41dd1020 u0 com.android.settings/.Settings t38} time:3815204
02-05 16:26:14.317 1351 1351 I ActivityManager: Timeline: Activity_idle id: [email protected] time:3815806
02-05 16:26:14.688 1049 1106 I ActivityManager: Timeline: Activity_windows_visible id: ActivityRecord{4220d2b0 u0 com.mobint.hololauncher.hd/com.mobint.hololauncher.Launcher t1} time:3816177
02-05 16:26:15.802 1351 1351 I ActivityManager: Timeline: Activity_launch_request id:scd.lcex time:3817291
02-05 16:26:15.803 1049 1061 I ActivityManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=scd.lcex/.LogcatExtreme bnds=[257,680][371,878]} from pid 1351
02-05 16:26:16.060 1049 1334 W InputMethodManagerService: Starting input on non-focused client [email protected] (uid=10071 pid=1351)
02-05 16:26:16.094 9393 9393 I ActivityManager: Timeline: Activity_idle id: [email protected] time:3817583
02-05 16:26:16.353 1049 1106 I ActivityManager: Timeline: Activity_windows_visible id: ActivityRecord{41d267a0 u0 scd.lcex/.LogcatExtreme t37} time:3817843
---- 05/02/2014 16:27:23 ----
same probleme
please help us no wifi after unlock bootloader and format systeme, format data, format cache... . I tried rom paranoid, rom cyanogen 11 and rom GPE (google play edition) and same problem no wifi for all systemes. I wait a solution
Same problem
stylboss said:
please help us no wifi after unlock bootloader and format systeme, format data, format cache... . I tried rom paranoid, rom cyanogen 11 and rom GPE (google play edition) and same problem no wifi for all systemes. I wait a solution
Click to expand...
Click to collapse
I got the same problem today i try others roms and wifi is not working. Please some one help us!
Thank you.
SOLVED! SOLUTION WERE- http://forum.xda-developers.com/showthread.php?t=2619553
my moto g XT1033 in stock rom: wifi is not work fine, signal lost every 1 min
but in custom rom work fine!
please help me
Moto G XT1033 WiFi Problem,
hi everyone,
my moto g XT1033 WiFi have not problem with custom ROM but in stock rom WiFi connection lost signal!!!
please help me!
hello guys, can look here, good luck http://forum.xda-developers.com/showthread.php?t=2649763
Problem With WiFi in Stock rom
hello dear,
my moto g xt1033 in stock rom have problem with wifi,connect to wifi and after 5min connection lost< wifi signal is very low, but in custom rom work very good!
I converted my moto g xt1033 to xt1032 and now the wifi does not turn on
After converting, either the wifi does not turn on or after turning it does not display any network. Please help me.
Did you try converting back to xt1033 from xt1032?
I am trying to encrypt my rooted Nexus 5 (running CyanogenMod 13/Marshmallow).
Here is how I am doing:
1. With the phone running and connected to USB, make sure that /mnt/asec/ is empty
2. Long-press the power physical button, this makes the Power off dialog pop up
3. Long-press the "Power off" option of the pop up, confirm that you want to reboot in Safe Mode
4. Without starting any app, run adb shell on the computer then su to get root then pkill -KILL daemonsu to kill the SuperSU daemon
5. Settings > Security > Encrypt phone, confirm
6. The phone reboots, from the computer type adb logcat
Here is what I see:
Code:
I ServiceManager: service 'drm.drmManager' died
D libEGL : loaded /vendor/lib/egl/libEGL_adreno.so
D libEGL : loaded /vendor/lib/egl/libGLESv1_CM_adreno.so
D libEGL : loaded /vendor/lib/egl/libGLESv2_adreno.so
I Adreno-EGL: <qeglDrvAPI_eglInitialize:379>: QUALCOMM Build: 09/02/15, 76f806e, Ibddc658e36
E BootAnimation: couldn't find audio_conf.txt
W BootAnimation: Audio service is not initiated.
D BootAnimation: Use save memory method, maybe small fps in actual.
D BootAnimation: Use save memory method, maybe small fps in actual.
E Cryptfs : unmounting /data failed: Device or resource busy
E Cryptfs : Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/metadata
W vold : type=1400 audit(0.0:19): avc: granted { read } for name="mmcblk0p28" dev="tmpfs" ino=6735 scontext=u:r:vold:s0 tcontext=u:object_r:userdata_block_device:s0 tclass=blk_file
W vold : type=1400 audit(0.0:20): avc: granted { read open } for name="mmcblk0p28" dev="tmpfs" ino=6735 scontext=u:r:vold:s0 tcontext=u:object_r:userdata_block_device:s0 tclass=blk_file
W vold : type=1400 audit(0.0:21): avc: granted { ioctl } for path="/dev/block/mmcblk0p28" dev="tmpfs" ino=6735 ioctlcmd=1260 scontext=u:r:vold:s0 tcontext=u:object_r:userdata_block_device:s0 tclass=blk_file
D Cryptfs : Just asked init to shut down class main
W vold : emulated unmount requires state mounted
E Cryptfs : unmounting /data failed: Device or resource busy
W SocketClient: write error (Broken pipe)
W SocketClient: Unable to send msg '200 8 -
At that point the CyanogenMod loading screen keeps animating for 10+ hours and probably forever if I don't stop it. Pressing the Power physical button for 5 seconds makes it reboot and start normally this time. Obviously encryption has not been performed.
I tried the whole procedure twice.
What could be causing this Cryptfs : unmounting /data failed: Device or resource busy problem?
Android 11 here: Lineage 18.1 *UNOFFICIAL* for Sharp Aquos S2, S3 (SAT/SS2/HH1/HH6)
LEGAL
https://lineageos.org/legal/
You flash this ROM on own risk!
XDA:DevDB Information
Lineage 17 *UNOFFICIAL* for Sharp Aquos S2, S3 (SAT/SS2/HH1/HH6)
Multi ROM from sources supporting devices:
Sharp Aquos S2 4/64 -SS2/C10,
Sharp Aquos S2 6/128 -SAT,
Sharp Aquos S3 -sdm630 (HH1/HH6).
Sharp Aquos P6
Nokia x6 (DRG)
Contributors/Maintainers
heineken78
ROM OS Version: Android 10
ROM Kernel: CAF 4.4.205
ROM Firmware Required: Minimum update installed 2130WW/CN -for S2. For S3 - D350KR, Nokia DRG - Android 9-10.
Based On: Android 10- Lineage 17.1
Recovery: TWRP included.
Device sources: here
Gapps: Not included. Recommend to use only NANO version, because it includes necessary apps like Welbeing
Data Encryption: encrypted;
Do not: use boot(twrp) or vendor with other older/stock roms.
Version Information
Status: Beta
Created 2019-11-03
Last Updated LOS 17.1 2020-09-02
Sources: https://github.com/Eddie07
DOWNLOAD:
Gdrive folder
Changelog 02.09.2020:
Lineage OS 17.1 02/09/20 for SAT/SS2/HH6/HD1
-kernel: optimize power driver;
-kernel: fix mdsi panel on from suspend crushes;
-vendor/system:implement from sources Bluetooth QTI;
-vendor/System:implement from sources perf QTI;
-vendor/system:implement com.qualcomm.gps and drivers from sources;
-kernel/system/vendor: new touchscreen gestures;
-system: more options for Android 10 gestures;
-system: disable magnet sensor;
-system: implement new telecom framework from sources;
-system: sim toogle swithes;
-vendor/system: audio enhancements.
-selinux fixes;
-GSI:flash and go.
-other.
Changelog 07.08.2020:
-remove restrictions for audio records
-fixed auto recording option in Dialer
-icon packs support option for LA Trebuchet: nova, etc.
-long screenshot (Q from ASUS);
-enabled show mv of QC in lockscreen.
-fixes screen on bug after suspend
Changelog 02.08.2020:
Kernel:
-Livedisplay for S2 & S3 & NOkia DRG; -Fast charging S2;
System:
-ARcore support without Magisk;
-Dialer: autorecording;
-Quick internet change via QCTiles (multisim); -Imitation of wifi for android when using a mobile network: persist.force.unmetered = true: -Display Profiles (4) for S2 & S3
Vendor:
- updating halls; - selinux fixes; - fix for gsi boot; - other garbage to make everything work.
Changelog 13.05.2020:
-updated recovery 3.4.0: supports OTA updates, key decryption works;
-added custom face unlock: may need to assign camera perms manually;
-fixed sensors init issue;
-updated vendor.
Note: due to fixes in encryption this version needs fresh boot after format! Backup your data.
Use old backup, and apply gapps zip only after the first boot of system, dont boot to recovery after formatting.
LOS 17.1 beta 13b-04-2020
-fixed selinux denials: sensors issue, ril;
LOS 17.1 beta 13-04-2020
-LOS Android update android-10.0.0_r33 (05.04)
-added Nokia DRG (x6) support
-fixed configs media -front camera video fail fix in gcam.
-updated audio configs to Q.
-selinux still in testing.
LOS 17.1 beta 23-02-2020
-Able to disable sim card (if 2)- experimental;
-Lineage vendor implementations: Off screen gestures; Adjustable vibrations ( 3 levels);- More overlays.
- yuv support;
Also:
Kernel:
Power, sound, display changes, updated latest wifi driver. Also defined min brightness and tfa chip switching via nodes.
System:
Extra Minimum brightness option, reorganized, added settings, implementation of google personalisation (work but Screen Attention fails) no need gapps. 6x5 grid for launcher, option to add quick tile rows.
Vendor:
Made real blue accent color pickable, sound chip tweaking.
Still to do:virtual displays and wfd. (I think problem is hwc sources, need fix later)
LOS 17.1 daily 04-02-2020
-VENDOR: fixes wifi sharing (want working in last two builds), fixed diag_lsm error,
added support of external usb cameras.
LOS 17.1 daily 02-02-2020
-KERNEL: power drain fix to all previous kernels from 28.12 due hotplug conflict with PERF2.0 hal;
merged with LA.UM.8.2.r2-00700-sdm660.0;
updated qcacld (wifi);
not tested with s3.
-SYSTEM: Latest LOS updates, more telephony implementations from nokia stock Q;
-VENDOR: LOS updates, qcom caf updates, more display implementations.
LOS 17.1 test 08-01-2020
-New LOS Android;
-Kernel battery control changes (s2)
-gps enchantment, phone enchantments.
05-01-2020
-kernel: thermal related fixes.
-system: Snap camera replace by stock FIH cam, qcom ril framework blobs remade.
-vendor: manual network selection fix, new thermal impl.Fixed compatibility with GSI roms: camera and softkey navigation bar enabled.
25-12-2019
Kernel:
-merged 4.4.205;
-camera fix for gcam, dualcam; use this cam with dualcam enabled.
If gcam keeps crashing disable dualcam: persist.vendor.camera.expose.aux=0
-showing battery type (C10/S2);
System and Vendor:
-LOS up-to-date;
-implementation on new qcom encryption, booting faster;
-LOS beta circle battery icon ;
Note if you find that media folder is not getting encrypted with key/password - make full format from twrp and boot with current version.
14-12-2019
service pak N141219
28-11-2019
kernel: changes in kernel config
system: LOS 17.1 upd up 27.11
vendor: upd ril, qti, camera blobs, fixed PERF drain, fix bt lags, add APTX Bt codec.
-Rounded corners can be now disabled via vendor/build.prop.
-GUI of S3 of S2 can be chosen from developers settings (remain for GSI too)
17-11-2019
Update Android 10.0.0_r11
15-11-2019
-supports Sharp Aquos S3 models -HH1 and HH6!
-Los up-to-date
05-11-2019
-kernel updated to 4.4.194 (caf LA.UM.8.2.r1-04800-sdm660.0)
-CAMERA: latest camera vendor blobs Q from 2060 Nokia PL2 (test option prop persist.cam.dv=(PL2/B2N/C1N) for camera hal)
-PERFORMANCE: PERF 2.0 fixed
-LINEAGE: current Lineage updates from mainstream(not much)
-SOUND: revert to stock soundtrigger
-VNDK rebuild with Q rules
-added many enhancements in build.props
03-11-2019
First release
Installation
1. First time
Enter twrp or from fastboot and flash images: boot, system, vendor. Reboot back recovery and format data. Install Gapps same time (as option).Reboot to new system.
2. Next updates/upgrades
Enter twrp and flash new images. If you had installed Gapps, flash same zip file o gapps. Reboot to system.
Pls note: Due to changes in encryption, if your data is before July 2020, you will have to format data to be able to use newer roms.
Bugs:
-Minor LOS bugs.
-You will find may be
Please donate if you want to support my work.
I'm testing rom from yesterday. Updated from treble 3.4
Does't show % battery in status bar and the battery icon can't be changed.
There is a problem when I kill applications, it shows a problem with the launcher - operation stops and cant kill applikactions.
Some app from playstore like revolut isn't compatybile with 17.
Gcam working.
Thx for great work.
iiandrusii said:
I'm testing rom from yesterday. Updated from treble 3.4
Does't show % battery in status bar and the battery icon can't be changed.
There is a problem when I kill applications, it shows a problem with the launcher - operation stops and cant kill applikactions.
Some app from playstore like revolut isn't compatybile with 17.
Gcam working.
Thx for great work.
Click to expand...
Click to collapse
% of battery is still to do (Linage bug), there are others too..
About error, may be its because of current launcher problem. I don't have such.
I used vendor rom gsi I installed the camera and the flash didn't work
amiali said:
I used vendor rom gsi I installed the camera and the flash didn't work
Click to expand...
Click to collapse
I'm not able to test GSI's, pls bugs with LOS17 system/vendor. Try another GSI.
I tested three gsi models. The camera and the flash don't work
Hello heineken78. First of all thank you very much for all your work and help with this device.
I wanted to report 3 problems I saw with the ROM:
1) I cannot use NFC: when placing the NFC card near the phone NFC trigger reacts (it blocks, disables and enables) but it doesn't seem to work. The same works, for example, on 4.1. Is there something I could try?
2) I couldn't find a way to disable fingerprint actions on screen on when using gestures, which makes it trigger sometimes accidentally.
3) Data doesn't seem to be encrypted. When accessing TWRP it doesn't ask for a password and I can read sdcard without issues. Not sure if this is common with Android 10 as of yet.
Other than that, the ROM seems to be working perfectly, which is a lot since Android Q is really new.
Thanks!
jokolom said:
1) I cannot use NFC: when placing the NFC card near the phone NFC trigger reacts (it blocks, disables and enables) but it doesn't seem to
work. The same works, for example, on 4.1. Is there something I could try?
Click to expand...
Click to collapse
NFC works, people use safetynetfix and pay with gpay app
jokolom said:
2) I couldn't find a way to disable fingerprint actions on screen on when using gestures, which makes it trigger sometimes accidentally.
Click to expand...
Click to collapse
to do
jokolom said:
3) Data doesn't seem to be encrypted. When accessing TWRP it doesn't ask for a password and I can read sdcard without issues. Not sure if this is common with Android 10 as of yet.
Click to expand...
Click to collapse
encrypted, even password will not match in TWRP, cos TWRP uses old keymaster sources.
heineken78 said:
NFC works, people use safetynetfix and pay with gpay app
to do
encrypted, even password will not match in TWRP, cos TWRP uses old keymaster sources.
Click to expand...
Click to collapse
I have reinstalled LOS17 to retry these things on my phone, and this is the summary:
- Encryption: OK. I have now verified that after installing the ROM, wiping data and rebooting, data in TWRP shows as encrypted even though password will not match like you say (file names appear as garbled characters) so this seems to be working OK.
- NFC: I still cannot make NFC work. I have installed safetypatch on Magisk, CTS profile and basic integrity show as OK on Magisk. Not sure what makes NFC not work, maybe I'm missing something.
- Notification LED: I cannot see notification LED working after receiving a notification, such as Whatsapp.
- Warning message on boot: a warning message triggers on system reboot. This is a minor detail since it's just an informative message.
Other than that, everything seems to be working correctly. I will keep using this ROM as a daily driver and report any other problem I can see.
Thank you!
heineken78 said:
NFC works, people use safetynetfix and pay with gpay app
to do
encrypted, even password will not match in TWRP, cos TWRP uses old keymaster sources.
Click to expand...
Click to collapse
After installing latest version (0611) now NFC card makes sound when it's near the phone and opens NFC app. However, it seems to crash. I have taken a logcat regarding NFC problem. These are the following lines worthy of notice, please tell me if this helps:
Code:
11-06 12:35:07.189 11571 11618 E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'short android.os.Bundle.getShort(java.lang.String)' on a null object reference
11-06 12:35:07.189 11571 11618 E AndroidRuntime: at android.nfc.tech.NfcA.<init>(NfcA.java:76)
11-06 12:35:07.189 11571 11618 E AndroidRuntime: at android.nfc.tech.NfcA.get(NfcA.java:62)
Code:
11-06 12:35:07.853 3646 11670 E libnfc_nci: [ERROR:phNxpExtns.cpp(220)] Error Sending msg to Extension Thread
11-06 12:35:07.854 879 879 D NxpExtns: find found MIFARE_READER_ENABLE=(0x1)
11-06 12:35:07.854 879 879 D NfccPowerTracker: NfccPowerTracker::ProcessCmd: Enter,Recieved len :4
Code:
11-06 12:35:59.782 10874 10874 I RenderThread: type=1400 audit(0.0:846): avc: denied { execute } for path="/vendor/lib/hw/gralloc.sdm660.so" dev="mmcblk0p80" ino=776 scontext=u:r:untrusted_app_27:s0:c168,c256,c512,c768 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=1
According to logcat, even though it doesn't work, it seems to know the card type (mifare):
Code:
11-06 12:35:10.155 758 3327 D NxpHal : NxpNci: RF Interface = MIFARE
11-06 12:35:10.155 758 3327 D NxpHal : NxpNci: Protocol = MIFARE
Thank you!
amiali said:
I tested three gsi models. The camera and the flash don't work
Click to expand...
Click to collapse
release 06/11/19 fixes this issue.
jokolom said:
According to logcat, even though it doesn't work, it seems to know the card type (mifare):
Click to expand...
Click to collapse
config nfc-nxp.conf needs to be fixed to new drivers.
unfortunately im not able to use nfc at all on my SAT - antenna is broken.
so someone has to do it...
heineken78 said:
config nfc-nxp.conf needs to be fixed to new drivers.
unfortunately im not able to use nfc at all on my SAT - antenna is broken.
so someone has to do it...
Click to expand...
Click to collapse
I have found this file: /vendor/etc/libnfc-nxp.conf. Is that the file you reference to?
What can I do to help? I have no problem trying thing but I would need some pointers on what should be changed.
Thank you
Here's : /vendor/etc/libnfc-nxp.conf from 2080WW SAT (stock Oreo).
View attachment libnfc-nxp.zip
paulzie said:
Here's : /vendor/etc/libnfc-nxp.conf from 2080WW SAT (stock Oreo).
View attachment 4869289
Click to expand...
Click to collapse
I have just tried it. Instead of crashing, it will get stuck while trying to read the NFC card. Moreover, the NFC settings get stuck as well.
Thanks
Many GCam mod versions stop to get HDR+ shots at some point. Usually it start with exception in UI handler thread:
11-07 20:51:03.620 6899 7544 I CAM_PhotoCaptureSession: [409d074|IMG_20191107_205058] saveAndFinish
11-07 20:51:03.621 6899 7544 W System.err: java.util.concurrent.ExecutionException: java.lang.Exception
11-07 20:51:03.621 6899 7544 W System.err: at oxp.a(Unknown Source:20)
11-07 20:51:03.621 6899 7544 W System.err: at oxp.get(Unknown Source:475)
11-07 20:51:03.621 6899 7544 W System.err: at oxz.get(Unknown Source:0)
11-07 20:51:03.621 6899 7544 W System.err: at lqi.b(Unknown Source:6)
11-07 20:51:03.622 6899 7544 W System.err: at iqu.a(Unknown Source:46)
11-07 20:51:03.622 6899 7544 W System.err: at hfd.run(Unknown Source:44)
11-07 20:51:03.622 6899 7544 W System.err: at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:462)
11-07 20:51:03.622 6899 7544 W System.err: at java.util.concurrent.FutureTask.run(FutureTask.java:266)
11-07 20:51:03.622 6899 7544 W System.err: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
11-07 20:51:03.622 6899 7544 W System.err: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
11-07 20:51:03.622 6899 7544 W System.err: at java.lang.Thread.run(Thread.java:919)
11-07 20:51:03.622 6899 7544 W System.err: at loy.run(Unknown Source:5)
11-07 20:51:03.622 6899 7544 W System.err: Caused by: java.lang.Exception
11-07 20:51:03.622 6899 7544 W System.err: at lqi.a(Unknown Source:4)
11-07 20:51:03.622 6899 7544 W System.err: at frh.d(Unknown Source:35)
11-07 20:51:03.622 6899 7544 W System.err: at egc.a(Unknown Source:152)
11-07 20:51:03.622 6899 7544 W System.err: at eeg.y(Unknown Source:158)
11-07 20:51:03.622 6899 7544 W System.err: at eeg.o(Unknown Source:32)
11-07 20:51:03.622 6899 7544 W System.err: at efb.onShutterButtonClick(Unknown Source:44)
11-07 20:51:03.622 6899 7544 W System.err: at jyl.onShutterButtonClick(Unknown Source:25)
11-07 20:51:03.622 6899 7544 W System.err: at com.google.android.apps.camera.ui.shutterbutton.ShutterButton.performClick(Unknown Source:98)
11-07 20:51:03.622 6899 7544 W System.err: at android.view.View.performClickInternal(View.java:7117)
11-07 20:51:03.623 6899 7544 W System.err: at android.view.View.access$3500(View.java:801)
11-07 20:51:03.623 6899 7544 W System.err: at android.view.View$PerformClick.run(View.java:27351)
11-07 20:51:03.623 6899 7544 W System.err: at android.os.Handler.handleCallback(Handler.java:883)
11-07 20:51:03.623 6899 7544 W System.err: at android.os.Handler.dispatchMessage(Handler.java:100)
11-07 20:51:03.623 6899 7544 W System.err: at android.os.Looper.loop(Looper.java:214)
11-07 20:51:03.623 6899 7544 W System.err: at android.app.ActivityThread.main(ActivityThread.java:7356)
11-07 20:51:03.623 6899 7544 W System.err: at java.lang.reflect.Method.invoke(Native Method)
11-07 20:51:03.623 6899 7544 W System.err: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
11-07 20:51:03.623 6899 7544 W System.err: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:930)
And then no more shots could be taken until rebooted (probably camera left in illegal state after exception):
11-07 20:51:27.555 6899 7388 E CAM_HdrPBurstTkr: Failed to receive any frames. Aborting capture for shot 6
11-07 20:51:27.558 6899 7388 I CAM_HdrPShotParams: HDR+ pipeline reported shotId 6 was aborted.
11-07 20:51:27.559 6899 6899 I CAM_VirtualCameraManage: Disconnecting camera 0 asynchronously.
11-07 20:51:27.559 6899 6936 I CAM_CamDevLsnrShim: Camera device 1548342258(0) has been disconnected.
11-07 20:51:27.559 6899 7388 W libgcam : [pipeline_manager.cc:853]: AbortShot: Shot aborted by AbortShot() during capture.
11-07 20:51:27.559 6899 6936 I CAM_VirtualCameraManage: Camera device 0 was closed.
11-07 20:51:27.560 6899 6899 I CAM_CptrBtnReadiness: addCameraReadinessCallback: cameraReadiness=Obs.of{false}
11-07 20:51:27.563 6899 7388 I CAM_PictureTakerImpl: availability: get=true ret=filtered{DerefObs{filtered{TransformedObs{[email protected], [email protected]}}}} [email protected]
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: PictureTaker command failed: [email protected][status=SUCCESS, result=[[email protected]]]
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: mbl: HDR+ shot didn't succeed
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at den.a(Unknown Source:574)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at fan.a(Unknown Source:20)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at eyz.a(Unknown Source:39)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at fal.a(Unknown Source:7)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at hfu.a(Unknown Source:146)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at gnw.run(Unknown Source:42)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:462)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at pal.b(Unknown Source:2)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at ozq.run(Unknown Source:22)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at paj.run(Unknown Source:4)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at java.lang.Thread.run(Thread.java:919)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at loy.run(Unknown Source:5)
11-07 20:51:27.564 6899 7388 I CAM_PictureTakerImpl: PictureTakerCommand.run: success=false
jokolom said:
I have just tried it. Instead of crashing, it will get stuck while trying to read the NFC card. Moreover, the NFC settings get stuck as well.
Thanks
Click to expand...
Click to collapse
that what Im trying to tell you. Paul shared old config, I have put modified to work with new hals.
May be you can compare both and fix it.
My nfc is not working due antenna problems.
Thats it!
@heineken78 Sorry but I can't find link to download rom files in first post (update 2019-11-06 too) .
iiandrusii said:
@heineken78 Sorry but I can't find link to download rom files in first post (update 2019-11-06 too) .
Click to expand...
Click to collapse
This is question to XDA designer. Change XDA style page and find tabs, we are on "di-scussion" now, next is " downloads"...
I found ? thx
The Blackview BV9800 Pro is a relatively rare device, and has no support from LineageOS or any other popular ROM project I can find. This is kind of a shame, because it's a pretty cool device - in particular, it has an integrated thermal camera, and is also just a nice ruggedized phone at a surprisingly low price. The bootloader is unlockable out of the box without any need for an unlock code or other nonsense from the vendor, which is also a big bonus.
Being a Project Treble-compatible device, it's possible to run unofficial GSI builds of LineageOS on it, such as these, which are replacement images to flash over /system. These work well with the majority of the BV9800 Pro's functions (wireless, visible-light cameras, sensors, etc.), but getting the thermal camera to work requires a little bit more work. I have done this successfully, so I wanted to share what I did in case anyone else finds themselves in the same situation.
I have only tested these procedures on a BV9800 Pro (EEA version), running LineageOS 16 (Android 9) from the link above. Other versions of Android may work, but I do not know whether they do or not, and decided to stay with Android 9, since this is what the vendor ships on the device. Your results may vary if you decide to try a newer version.
The factory MyFLIR app for the device can be found at this location in the stock ROM:
Code:
/system/app/myflir-bv2.3.6-release-signed/myflir-bv2.3.6-release-signed.apk
However, if you try to just install it like a normal app package under LineageOS, it crashes on startup without providing any useful information. The system logs reveal that it crashes because it's trying to communicate with a system service that manages the thermal camera, but this service isn't installed. Fortunately, you can install it by just copying a few files from the factory ROM over to the LineageOS system. The files in question are located at these paths in the factory ROM:
Code:
/system/bin/leptonServer
/system/etc/init/LeptonCameraServer.rc
/system/lib64/libleptoncamera.so
If you copy these files to the same paths in the LineageOS /system tree, then the Lepton camera server backend, which is required for the MyFLIR app to function, will be installed and configured to start at boot.
SELinux seems to prevent the app from connecting to the Lepton server on my device, so I had to disable it by running
Code:
setenforce 0
in a root shell on the device. I didn't install it as a system app, though, which could be part of the problem. I don't know much about how SELinux actually works, but I feel comfortable enough disabling it. If you don't want to disable it, you can probably find information about how to make it allow the FLIR app to work, but I'm afraid I can't be of much help there.
You can find a copy of the stock BV9800 Pro ROM here on the Blackview forum.
If you want to root the stock ROM to allow you to inspect /system, this thread explains how. If you prefer, you can instead extract the ROM zip archive on a computer, decompress the included system.img with simg2img, and mount it to inspect the contents directly, which is what I did. Modifying /system on a running device can be difficult these days, so it will probably work best to mount up the GSI image the same way and copy the files into it, rather than try to edit it in-place on a running device.
I hope this information helps. The thermal camera is one of the most important (and expensive) features of the BV9800 Pro, and getting it working was pretty much the deciding factor for me as to whether I would keep the (kind of bad) factory ROM, or get to enjoy all the perks of LineageOS. I'm not really knowledgeable enough to write a complete and trustworthy guide to installing LineageOS, though, so if you're just getting started, you'll want to find a more detailed tutorial about how installing custom ROMs (especially GSI/Treble builds) works.
That's a cool rugged phone. Stock it's running on Pie... personally I leave it be and optimize it as best I could to get maximum battery life.
I was looking at these... FLIR, hell yes.
I was following your guide, I'm using my Blackview 9800pro without GApps (but with MicroG 0.2.18.204714) on LineageOS 17.1-20210321. When opening the MyFlir camera or gallery app, it asks me for all the relevant permissions on the first start and then promptly crashes every time I open it. I tried both as a system and a regular app, with and without selinux. In the error below, it complains about not finding the right function in libvndksupport.so. This library is much smaller in LineageOS than it is shipped in the Stock ROM from Blackview. Replacing the LineageOS shared object file with the one from Blackview causes my phone not to boot. Is there something I am missing that causes my instance of the app (I tried both 2.3.6 and 2.3.8) to crash?
Code:
04-28 00:27:34.047 1383 5788 I ActivityTaskManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.flir.tiger/com.flir.monarch.ui.MainActivity bnds=[27,996][232,1321]} from uid 10121
04-28 00:27:34.057 783 804 I [email protected]: powerHintAsync hint:8, data:1
04-28 00:27:34.061 783 803 I libPowerHal: 8: legacy set freq: 1989000 -1 2106000 -1
04-28 00:27:34.076 1383 1420 E system_server: Invalid ID 0x00000000.
04-28 00:27:34.077 1383 1419 W ActivityManager: Stopping service due to app idle: u0a216 -10s135ms com.flir.tiger/com.flir.monarch.media.MediaScanner
04-28 00:27:34.084 1008 1008 D Zygote : Forked child process 7648
04-28 00:27:34.087 1383 1426 I ActivityManager: Start proc 7648:com.flir.tiger/u0a216 for pre-top-activity {com.flir.tiger/com.flir.monarch.ui.MainActivity}
04-28 00:27:34.147 1579 1579 D ImageWallpaper: wallpaper visibility changes to: false
04-28 00:27:34.161 762 864 I hwcomposer: [DEV] 1024 0 0 0
04-28 00:27:34.162 762 864 I hwcomposer: [DEV] 0 741 0 0
04-28 00:27:34.162 762 864 I hwcomposer: [DEV] 0 0 470 0
04-28 00:27:34.162 762 864 I hwcomposer: [DEV] 0 0 0 1024
04-28 00:27:34.173 7648 7648 D FirebaseApp: com.google.firebase.auth.FirebaseAuth is not linked. Skipping initialization.
04-28 00:27:34.174 7648 7648 D FirebaseApp: com.google.firebase.crash.FirebaseCrash is not linked. Skipping initialization.
04-28 00:27:34.174 7648 7648 I FirebaseInitProvider: FirebaseApp initialization successful
04-28 00:27:34.177 762 864 I hwcomposer: [DEV] [DEV] (Send identity matrix)
04-28 00:27:34.187 7648 7673 I FA : App measurement is starting up, version: 15300
04-28 00:27:34.187 7648 7673 I FA : To enable debug logging run: adb shell setprop log.tag.FA VERBOSE
04-28 00:27:34.187 7648 7673 I FA : To enable faster debug mode event logging run:
04-28 00:27:34.187 7648 7673 I FA : adb shell setprop debug.firebase.analytics.app com.flir.tiger
04-28 00:27:34.196 762 864 I hwcomposer: [DEV] 1024 0 0 0
04-28 00:27:34.196 762 864 I hwcomposer: [DEV] 0 741 0 0
04-28 00:27:34.196 762 864 I hwcomposer: [DEV] 0 0 470 0
04-28 00:27:34.196 762 864 I hwcomposer: [DEV] 0 0 0 1024
04-28 00:27:34.200 7648 7648 I CrashlyticsCore: Initializing Crashlytics 2.6.8.32
04-28 00:27:34.207 7648 7686 W ContextImpl: Failed to ensure /data/user/0/com.google.android.gms/shared_prefs: mkdir failed: EACCES (Permission denied)
04-28 00:27:34.208 7648 7648 I CrashlyticsInitProvider: CrashlyticsInitProvider initialization successful
04-28 00:27:34.212 762 864 I hwcomposer: [DEV] [DEV] (Send identity matrix)
04-28 00:27:34.220 2428 2428 D GmsMeasureBrokerSvc: onBind: Intent { act=com.google.android.gms.measurement.START pkg=com.google.android.gms }
04-28 00:27:34.222 3179 3179 D GmsGcmRegister: onBind: Intent { act=com.google.android.c2dm.intent.REGISTER pkg=com.google.android.gms }
04-28 00:27:34.223 1024 1024 I netd : firewallSetUidRule(2, 10161, 1) <2.63ms>
04-28 00:27:34.227 1024 1024 I netd : firewallSetUidRule(2, 10160, 1) <1.74ms>
04-28 00:27:34.230 1024 1024 I netd : firewallSetUidRule(2, 10157, 1) <2.14ms>
04-28 00:27:34.233 1024 1024 I netd : firewallSetUidRule(2, 10151, 1) <1.85ms>
04-28 00:27:34.236 7648 7648 I ashmem : memfd: device VNDK version (28) is < Q so using ashmem.
04-28 00:27:34.277 7648 7648 D AndroidRuntime: Shutting down VM
04-28 00:27:34.277 7648 7648 E AndroidRuntime: FATAL EXCEPTION: main
04-28 00:27:34.277 7648 7648 E AndroidRuntime: Process: com.flir.tiger, PID: 7648
04-28 00:27:34.277 7648 7648 E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "android_get_exported_namespace" referenced by "/data/app/com.flir.tiger-EcVVz9vk2XWvVymOtKJxOQ==/lib/arm64/libvndksupport.so"...
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at java.lang.Runtime.loadLibrary0(Runtime.java:1071)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at java.lang.Runtime.loadLibrary0(Runtime.java:1007)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at java.lang.System.loadLibrary(System.java:1667)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at com.flir.flirone.sdk.FlirOne.<clinit>(FlirOne.java:59)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at com.flir.flirone.sdk.FlirOne.registerDeviceCallback(FlirOne.java:341)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at com.flir.monarch.app.ForegroundApplication.onActivityStarted(ForegroundApplication.java:88)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at android.app.Application.dispatchActivityStarted(Application.java:406)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at android.app.Activity.dispatchActivityStarted(Activity.java:1238)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at android.app.Activity.onStart(Activity.java:1723)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at android.support.v4.app.FragmentActivity.onStart(FragmentActivity.java:614)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at android.support.v7.app.AppCompatActivity.onStart(AppCompatActivity.java:178)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at com.flir.monarch.ui.MainActivity.onStart(MainActivity.java:79)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1432)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at android.app.Activity.performStart(Activity.java:7847)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at android.app.ActivityThread.handleStartActivity(ActivityThread.java:3294)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.performLifecycleSequence(TransactionExecutor.java:221)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.cycleToPath(TransactionExecutor.java:201)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:173)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2016)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:107)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at android.os.Looper.loop(Looper.java:214)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7356)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:491)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:940)
04-28 00:27:35.334 1383 5501 D AlarmManagerService: Kernel timezone updated to -120 minutes west of GMT
04-28 00:27:35.348 1383 6143 D AlarmManagerService: Kernel timezone updated to -120 minutes west of GMT
04-28 00:27:35.709 1090 1371 I 1090 1371 [sunwave-hal] : (711) 'healthMonitoringThread' enter.
04-28 00:27:35.710 1090 1371 I 1090 1371 [sunwave-client] : (90) ---8<---- TA LOG BEGINS ---------
04-28 00:27:35.710 1090 1371 I 1090 1371 [sunwave-ta-core] : (2869) 'sf_get_device_state' state:0008
04-28 00:27:35.710 1090 1371 I 1090 1371 [sunwave-client] : (107) --------- TA LOG FINISH ---->8---
Thanks for the info for the flir Camera,
It works fine with lineage OS 16 !
I want to add the info I got while doing it:
It does not work with all version of Andy Custom Lineage OS: I could not make it works with this one: lineage-16.0-20191017-UNOFFICIAL-treble_arm64_bvN.img.xz the lepton server had a seg fault.
I try with a lineage OS 18 , the lepton server worked but the application failed, I will look into it one day... maybe
I root my phone with magisk
I used a script to bypass SElinux and start the server when i want ( because i don't know if it wise to always have SElinux in permissive mode)
tylab said:
Thanks for the info for the flir Camera,
It works fine with lineage OS 16 !
I want to add the info I got while doing it:
It does not work with all version of Andy Custom Lineage OS: I could not make it works with this one: lineage-16.0-20191017-UNOFFICIAL-treble_arm64_bvN.img.xz the lepton server had a seg fault.
I try with a lineage OS 18 , the lepton server worked but the application failed, I will look into it one day... maybe
I root my phone with magisk
I used a script to bypass SElinux and start the server when i want ( because i don't know if it wise to always have SElinux in permissive mode)
Click to expand...
Click to collapse
thank u for the additional info!,so which version of lineage os 16 worked for u? iam on lineage-16.0-20191017-UNOFFICIAL-treble_arm64_bvN.img.xz and tried the author's steps but didn't work for me, also it'd be nice if u share with us the script u use to bybass selinux,thanks.
I want to report back some of my own success in regards to this thread. I have the camera working, but it's not a perfect solution and was wondering if you guys could assist me in checking what I could have possibly missed. I'm running it on the most current Lineage OS 18.1; I've compiled a version using the Treble ROM lineage-18.1-20210512-UNOFFICIAL-treble_arm64_bvS with Magisk as root (I also added MindTheGapps into it after some workarounds with the mounts, and had to register my device as an "unsupported device").
I followed the OP's guide to the T, and still couldn't get the app to even open. The logs revealed it was trying to call leptonServer, nulling out after five tries, and then crashing. Narrowed this down to being an issue with the /bin/leptonServer file itself being set as -rwx-r--r--, and changing it to -rwxr-x-r-x got the app to boot up. The only problem is, for the camera to actually start, I have to open a terminal session and start leptonServer from there, and I assume this has something to do with the SELinux policies in place. I've fought half the battle and got a version of sepolicy-inject set up to run (using the following policy: allow untrusted_app_27 default_android_service:service_manager { find }; (sepolicy-inject -s untrusted_app_27 -t default_android_service -c service_manager -p find (if this doesn't work for you, try doing logcat ServiceManager:V SELinux:V *:S to find the relevant SELinux policies that you need to apply, and follow the formulas))), but I figure this is still erroring out somewhere, since, after a restart, the only way I can get it working again is to go and disable SELinux using setenforce to 0 and then starting the server again using some sort of terminal. I also installed the MyFlir app as a system app.
I believe that part of the issue might be that I haven't properly added the SELinux policy, but I'm not entirely positive how I would go about testing this (I've more or less just gotten into the ROM building scene last week, but feel I have somewhat of an edge being a software developer for a living). I think if I boot into recovery I can grab the sepolicy file, but I'm not sure what else to do with it at this point.
The error I get when it's not running, aside from the PID is pretty consistent too:
05-31 19:19:06.814 372 372 E SELinux : avc: denied { find } for pid=20308 uid=10195 name=LeptonCameraService scontext=u:r:untrusted_app_27:s0:c195,c256,c512,c768 tcontext=ubject_r:default_android_service:s0 tclass=service_manager permissive=0
Hopefully, this helps someone to find the right answers before I can; I know I'll keep tinkering with it until I find the solution (I'm also attempting to overcome the CTSProfile/Basic failure in Magisk, which I plan to make a guide if I can find an answer).
I get the same error as @&00&V5yt$r2$E!n1IDUiJ9bF on Lineage18.1 - treble_arm64_bvS-userdebug
04-28 00:27:34.277 7648 7648 E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "android_get_exported_namespace" referenced by "/data/app/com.flir.tiger-EcVVz9vk2XWvVymOtKJxOQ==/lib/arm64/libvndksupport.so"...
My leptonServer is working correctly and service runs from the start so it I feel this is related to the /system/app/myflir-bv2.3.6-release-signed.
Are you guys using a different version of the app?
Flir said:
I get the same error as @&00&V5yt$r2$E!n1IDUiJ9bF on Lineage18.1 - treble_arm64_bvS-userdebug
04-28 00:27:34.277 7648 7648 E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "android_get_exported_namespace" referenced by "/data/app/com.flir.tiger-EcVVz9vk2XWvVymOtKJxOQ==/lib/arm64/libvndksupport.so"...
My leptonServer is working correctly and service runs from the start so it I feel this is related to the /system/app/myflir-bv2.3.6-release-signed.
Are you guys using a different version of the app?
Click to expand...
Click to collapse
I also used myflir-bv2.3.6-release-signed, pulled straight from the currently available 9.0 ROM.
For that specifically, if you are looking at the most recent ROM build available from Blackview, in the directory /system/system/app/myflir-bv2.3.6-release-signed, there is both the APK and a lib folder. I'd copy the lib folder over to your phone in that same directory; I think you're missing the dependencies from there.
If you already have those libaries in there, try the read/write settings on the folder too.
Hi bv9800 pro customers! Anyone tryed the magisk module in the thread https://forum.xda-developers.com/t/blackview-bv9900pro-magisk-modules.4331187/
to get flir worked on linage?
ilich79 said:
Hi bv9800 pro customers! Anyone tryed the magisk module in the thread https://forum.xda-developers.com/t/blackview-bv9900pro-magisk-modules.4331187/
to get flir worked on linage?
Click to expand...
Click to collapse
Hi ilich79
I tryed the magisk module for BV9900pro.
I have installed it manualy to improve my understanding.
First, selinux block as always :
E/SELinux ( 338): avc: denied { find } for pid=18411 uid=10175 name=LeptonCameraService scontext=u:r:priv_app:s0:c512,c768 tcontext=u:object_r:default_android_service:s0 tclass=service_manager permissive=0
After enforce selinux and relanch the leptonServer.
Application launch completly but the camera send only the first image and block after that
So, i replace the leptonServer by the old one and retry.
Finally it works fully.
I someone know how to correctly set the selinux policy for this app ? I will be graceful
May be this can help?
[MODULE] SELinux Mode Inverter (Advanced SELinux Mode Changer)
It Is Now A Part Of The Main Module Of MultiFunctions & Its Thread https://forum.xda-developers.com/apps/magisk/module-multifunctions-bootloop-t3933386. Introduction: Simple Module To Invert The Default Android SELinux Mode During Startup ([From...
forum.xda-developers.com
Flir said:
I get the same error as @&00&V5yt$r2$E!n1IDUiJ9bF on Lineage18.1 - treble_arm64_bvS-userdebug
04-28 00:27:34.277 7648 7648 E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "android_get_exported_namespace" referenced by "/data/app/com.flir.tiger-EcVVz9vk2XWvVymOtKJxOQ==/lib/arm64/libvndksupport.so"...
My leptonServer is working correctly and service runs from the start so it I feel this is related to the /system/app/myflir-bv2.3.6-release-signed.
Are you guys using a different version of the app?
Click to expand...
Click to collapse
I get the same error, @QuentinX5 : Did you use a different version? Would be nice to have a Lineage upgrade.
Regarding the problem with the MyFlir camera app: I had the same problem (unable to read camera files). I looked everywhere. I mean, everywhere trying to find an answer. There's also a video on youtube with comments suggesting flashing the APD.BIN file (I did not try). I even translated different language websites. Finally, I contacted the BV customer support and their reply was the classic (clear the app cache), which doesn't work at all and not just for me. I tried to get the APK file from the image and installing it which didn't work either.
Here's the simple magic solution that kept me trying for a week, and no one wrote it anywhere:
There's a folder named (com.flir.tiger) inside the Android folder in the phone storage with the contents:
com.flir.tiger\files\iron
com.flir.tiger\files\CameraFiles\system\calib.rsc
com.flir.tiger\files\CameraFiles\system\maps\ds_we_ap_fi_le_LCFMap.fff
Just copy the folder from another phone and paste it on your phone, and that's it!
thelaseman said:
Regarding the problem with the MyFlir camera app: I had the same problem (unable to read camera files). I looked everywhere. I mean, everywhere trying to find an answer. There's also a video on youtube with comments suggesting flashing the APD.BIN file (I did not try). I even translated different language websites. Finally, I contacted the BV customer support and their reply was the classic (clear the app cache), which doesn't work at all and not just for me. I tried to get the APK file from the image and installing it which didn't work either.
Here's the simple magic solution that kept me trying for a week, and no one wrote it anywhere:
There's a folder named (com.flir.tiger) inside the Android folder in the phone storage with the contents:
com.flir.tiger\files\iron
com.flir.tiger\files\CameraFiles\system\calib.rsc
com.flir.tiger\files\CameraFiles\system\maps\ds_we_ap_fi_le_LCFMap.fff
Just copy the folder from another phone and paste it on your phone, and that's it!
Click to expand...
Click to collapse
Hi do you think your solution works for all lineageos releases? If I change the stock rom I was thinking on putting release 19.1
thelaseman said:
Regarding the problem with the MyFlir camera app: I had the same problem (unable to read camera files). I looked everywhere. I mean, everywhere trying to find an answer. There's also a video on youtube with comments suggesting flashing the APD.BIN file (I did not try). I even translated different language websites. Finally, I contacted the BV customer support and their reply was the classic (clear the app cache), which doesn't work at all and not just for me. I tried to get the APK file from the image and installing it which didn't work either.
Here's the simple magic solution that kept me trying for a week, and no one wrote it anywhere:
There's a folder named (com.flir.tiger) inside the Android folder in the phone storage with the contents:
com.flir.tiger\files\iron
com.flir.tiger\files\CameraFiles\system\calib.rsc
com.flir.tiger\files\CameraFiles\system\maps\ds_we_ap_fi_le_LCFMap.fff
Just copy the folder from another phone and paste it on your phone, and that's it!
Click to expand...
Click to collapse
Hi, I'm trying to get the flir camera working on lineage 19.1 can @thelaseman gime me the file you write about? beacause I don't have another phone to copy from.
Thanks
Max
max74926 said:
Hi, I'm trying to get the flir camera working on lineage 19.1 can @thelaseman gime me the file you write about? beacause I don't have another phone to copy from.
Thanks
Max
Click to expand...
Click to collapse
If you are still looking for it I might be able to extract these files for you.
@thelaseman @QuentinX5
Is anyone still using a BV9800 Pro with a Lineage ROM? What version are you on, what specific build did you install, did you encounter any specific issues, were they fixable and how?
Not asking for a full guide (wouldn't mind of course ) but before I start messing with what is currently my daily driver I'd like to know if anyone else was successful with a certain version. Particularly interested if any newer versions have also ended up working with the FLIR-camera.
Hi @dj__jg,
I use the attached files for lineage 19.1 GSI (https://forum.xda-developers.com/t/gsi-12-lineageos-19-x-gsi-a64b-64b.4358041/).
My camera calib is wrong (the thermal camera is upside down.) so I don't push the calib file here, if you have a good one, i'm interested.
I don't have fixed the selinux error for the moment, so just disable it went you launch the '/system/bin/leptonServer'
I missnamed the attached file, it's for BV9800 pro
I suddenly feel very stupid, I just realised I've gotten confused about my phones model number
I actually have a Blackview ninethousandninehundred pro, not 9800. I either had a brainfart or made a typo as I was searching if anyone had managed to use a recent Lineage ROM on it and accidentally ended up on this thread and didn't notice.
Luckily I didn't upload my calib file etc here, or someone could have gotten very confused. I think I will try to run a GSI build at some point, but when I have some more spare time/don't need this phone every day. The information about the com.flir.tiger folder is still very handy because it is the same on my model, I hope the same tactics will work to get the FLIR working in a GSI build.
(Wrote out the model number in text so other people googling the model number won't end up confused on this thread without even making a typo)
It's my bad i missnamed my file, it's 9800 pro not 9800 (who don't have thermal camera)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Code:
#include
/*
* Your warranty is now void.
*
* 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.
*/
SUPPORTED DEVICES
- SONY XPERIA X Compact (kugo)
TODO:
Code:
- Nothing
Changelog:
Code:
29/03/2022:
- Initial build
3rd PARTY ADDONS/MODS
While we have no issues with people using supersu/magisk/xposed/custom kernels/etc, we can't provide support for users who have them installed.
This thread is not the right place to discuss about mods/addons.
HOW TO INSTALL LINEAGEOS
- Boot into TWRP.
- Format Data, Wipe System, Cache, Dalvick Cache
- Flash LineageOS.
- Optional: Install the Google Apps addon package. (see Downloads)
- Reboot
DOWNLOADS
Lineage 17.1 v1: https://androidfilehost.com/?fid=14655340768118443617
Google Apps: http://opengapps.org/
HOW TO CONTRIBUTE?
Send your patches up for review: https://review.lineageos.org/
SOURCES:
Common tree: https://github.com/sony-msm8956-dev/android_device_sony_loire-common
Device tree: https://github.com/sony-msm8956-dev/android_device_sony_kugo
Kernel source: https://github.com/sony-msm8956-dev/android_kernel_sony_msm8956
Vendor blobs: https://github.com/sony-msm8956-dev/proprietary_vendor_sony
Done by:
- @ud4
- @jmpf_bmx (me)
Thanks to:
- @TeamMex
- Panda
- @Chippa_a
- @tarkzim
SONY MSM8956 TG group:
https://t.me/sonyMSM8956
Donation:
https://www.paypal.com/paypalme/jmpfbmx
watching the github repo and wondered if you make it happen
contratulations!
Do you also plan to port 18.1 over (as I've seen the branch)?
And do you plan to support it with future security patches?
All the best and many thanks.
konstruktor said:
watching the github repo and wondered if you make it happen
contratulations!
Do you also plan to port 18.1 over (as I've seen the branch)?
And do you plan to support it with future security patches?
All the best and many thanks.
Click to expand...
Click to collapse
Hi konstruktor
Yes, we are working in 18.1 we booted it and we are testing it
And yeah we will support it with future security patches
Thanks
Regards Jose
Thank you very much for the fast response.
I just have a last question for now: Do I need the SW_binaries for Android 10 or 9 from the Sony website (10 does not seem to boot for me).
nvm - it worked with the ones for Android 10
I'm sorry - just forgot to wipe everything before
It's been some time I flashed custom roms
edit:
I'm impressed - it's really smooth.
Security patches seem to be from March - this really breathes new life into this device and one can use it again while feeling a bit more secure.
konstruktor said:
Thank you very much for the fast response.
I just have a last question for now: Do I need the SW_binaries for Android 10 or 9 from the Sony website (10 does not seem to boot for me).
nvm - it worked with the ones for Android 10
I'm sorry - just forgot to wipe everything before
It's been some time I flashed custom roms
edit:
I'm impressed - it's really smooth.
Security patches seem to be from March - this really breathes new life into this device and one can use it again while feeling a bit more secure.
Click to expand...
Click to collapse
You don't need SW Binaries as this ROM is based on stock rom (3.10 oreo stock kernel)
jmpf_bmx said:
You don't need SW Binaries as this ROM is based on stock rom (3.10 oreo stock kernel)
Click to expand...
Click to collapse
I don't start to ask how this is even possible But that explains the vendor security level of 2018 I guess.
Would it be possible to enable device encryption?
konstruktor said:
I don't start to ask how this is even possible But that explains the vendor security level of 2018 I guess.
Would it be possible to enable device encryption?
Click to expand...
Click to collapse
Yes, you can enable device encryption.
It was fixed in LOS v2 for suzi if u take a look into suzu post
Thank you for the support of the device, to be honest, I thought that everything, only Sailfish, turns out not, there are still in our ranks who do not want to give up the compact, it pleases. The firmware is quite stable, so far no bugs have come out. Thanks again.
Thanks for providing this LineageOS build.
Could you, please, help me to install it?
I managed using TRWP to wipe and flash the LineageOS image and the Google Apps addon package to the device. Then I rebooted and saw the moving circle of the LineageOS. I left the first boot do its work over night, but this morning I found a switched-off device. After restarting, LineageOS did not finish to boot for 5.5 hours, after which my Xperia X compact switched off again because of low power (despite being connected to the power plug).
I just read about LineagOS, rooting, TRWP and have no experience. I downloaded the ARM/10.0/pico variant of GApps, correct? What should I try next:
- when battery is reloaded, try a new boot (hoping that it continues from the last state)
- wipe and flash without the GoogleApps?
- wipe and flash but without the SD-Card or SIM card inserted?
- wait for the 18.x variant ?
- ?
tomaschwutz said:
Thanks for providing this LineageOS build.
Could you, please, help me to install it?
I managed using TRWP to wipe and flash the LineageOS image and the Google Apps addon package to the device. Then I rebooted and saw the moving circle of the LineageOS. I left the first boot do its work over night, but this morning I found a switched-off device. After restarting, LineageOS did not finish to boot for 5.5 hours, after which my Xperia X compact switched off again because of low power (despite being connected to the power plug).
I just read about LineagOS, rooting, TRWP and have no experience. I downloaded the ARM/10.0/pico variant of GApps, correct? What should I try next:
- when battery is reloaded, try a new boot (hoping that it continues from the last state)
- wipe and flash without the GoogleApps?
- wipe and flash but without the SD-Card or SIM card inserted?
- wait for the 18.x variant ?
- ?
Click to expand...
Click to collapse
Be sure you downloaded the ARM64 variant of Gapps
Also try to boot before you flash Gapps and see that the base image works. You can flash it afterwards.
tomaschwutz said:
Thanks for providing this LineageOS build.
Could you, please, help me to install it?
I managed using TRWP to wipe and flash the LineageOS image and the Google Apps addon package to the device. Then I rebooted and saw the moving circle of the LineageOS. I left the first boot do its work over night, but this morning I found a switched-off device. After restarting, LineageOS did not finish to boot for 5.5 hours, after which my Xperia X compact switched off again because of low power (despite being connected to the power plug).
I just read about LineagOS, rooting, TRWP and have no experience. I downloaded the ARM/10.0/pico variant of GApps, correct? What should I try next:
- when battery is reloaded, try a new boot (hoping that it continues from the last state)
- wipe and flash without the GoogleApps?
- wipe and flash but without the SD-Card or SIM card inserted?
- wait for the 18.x variant ?
- ?
Click to expand...
Click to collapse
Hey
You need to use ARM64/10.0/pico GAPPs
As this ROM is ARM64
Thanks
Regards Jose
I'm not able to load Tidal or Plex. Both just hang at the logo when it starts and I can't even get to the login screen. Does anyone have an idea what this is about?
Just went back to stock and reflashed everything cleanly.
konstruktor said:
I'm not able to load Tidal or Plex. Both just hang at the logo when it starts and I can't even get to the login screen. Does anyone have an idea what this is about?
Just went back to stock and reflashed everything cleanly.
Click to expand...
Click to collapse
Could you take some logs and send em here pls?
@jmpf_bmx
in generall I see a lot of this:
Code:
03-31 12:47:47.666 660 6001 I ServiceManagement: getService: Trying again for [email protected]::IDrmFactory/clearkey...
03-31 12:47:47.677 1 1 W libc : Unable to set property "ro.init.updatable_crashing_process_name" to "vendor.drm-clearkey-hal-1-2": error code: 0xb
03-31 12:47:47.678 1 1 W libc : Unable to set property "ro.init.updatable_crashing" to "1": error code: 0xb
03-31 12:47:47.776 660 4376 W ServiceManagement: Waited one second for [email protected]::IDrmFactory/clearkey
03-31 12:47:47.777 660 4376 I ServiceManagement: getService: Trying again for [email protected]::IDrmFactory/clearkey...
03-31 12:47:47.781 8807 8807 W init : type=1400 audit(0.0:806): avc: denied { execute_no_trans } for path="/system/vendor/bin/hw/[email protected]" dev="mmcblk0p52" ino=4081 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
03-31 12:47:47.788 428 428 I QNS : QNS: soc=94, v=4286, i=241, t=305
03-31 12:47:47.789 428 428 I QNS : QNS: requested charging current: 500
03-31 12:47:47.793 1 1 W libc : Unable to set property "ro.init.updatable_crashing_process_name" to "vendor.drm-clearkey-hal-1-2": error code: 0xb
03-31 12:47:47.794 1 1 W libc : Unable to set property "ro.init.updatable_crashing" to "1": error code: 0xb
03-31 12:47:47.891 660 660 W ServiceManagement: Waited one second for [email protected]::IDrmFactory/clearkey
03-31 12:47:47.892 660 660 I ServiceManagement: getService: Trying again for [email protected]::IDrmFactory/clearkey...
03-31 12:47:47.895 8809 8809 W init : type=1400 audit(0.0:807): avc: denied { execute_no_trans } for path="/system/vendor/bin/hw/[email protected]" dev="mmcblk0p52" ino=4081 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
03-31 12:47:47.904 1 1 W libc : Unable to set property "ro.init.updatable_crashing_process_name" to "vendor.drm-clearkey-hal-1-2": error code: 0xb
03-31 12:47:47.904 1 1 W libc : Unable to set property "ro.init.updatable_crashing" to "1": error code: 0xb
03-31 12:47:48.324 660 6002 W ServiceManagement: Waited one second for [email protected]::IDrmFactory/clearkey
03-31 12:47:48.326 660 6002 I ServiceManagement: getService: Trying again for [email protected]::IDrmFactory/clearkey...
03-31 12:47:48.328 8812 8812 W init : type=1400 audit(0.0:808): avc: denied { execute_no_trans } for path="/system/vendor/bin/hw/[email protected]" dev="mmcblk0p52" ino=4081 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
03-31 12:47:48.336 1 1 W libc : Unable to set property "ro.init.updatable_crashing_process_name" to "vendor.drm-clearkey-hal-1-2": error code: 0xb
03-31 12:47:48.337 1 1 W libc : Unable to set property "ro.init.updatable_crashing" to "1": error code: 0xb
03-31 12:47:48.489 660 4363 W ServiceManagement: Waited one second for [email protected]::IDrmFactory/clearkey
03-31 12:47:48.489 660 770 W ServiceManagement: Waited one second for [email protected]::IDrmFactory/clearkey
03-31 12:47:48.490 660 4363 I ServiceManagement: getService: Trying again for [email protected]::IDrmFactory/clearkey...
03-31 12:47:48.491 660 770 I ServiceManagement: getService: Trying again for [email protected]::IDrmFactory/clearkey...
03-31 12:47:48.495 8815 8815 W init : type=1400 audit(0.0:809): avc: denied { execute_no_trans } for path="/system/vendor/bin/hw/[email protected]" dev="mmcblk0p52" ino=4081 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
03-31 12:47:48.501 1 1 W libc : Unable to set property "ro.init.updatable_crashing_process_name" to "vendor.drm-clearkey-hal-1-2": error code: 0xb
03-31 12:47:48.502 1 1 W libc : Unable to set property "ro.init.updatable_crashing" to "1": error code: 0xb
03-31 12:47:48.666 660 6001 W ServiceManagement: Waited one second for [email protected]::IDrmFactory/clearkey
03-31 12:47:48.667 660 6001 I ServiceManagement: getService: Trying again for [email protected]::IDrmFactory/clearkey...
03-31 12:47:48.671 8817 8817 W init : type=1400 audit(0.0:810): avc: denied { execute_no_trans } for path="/system/vendor/bin/hw/[email protected]" dev="mmcblk0p52" ino=4081 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
03-31 12:47:48.681 1 1 W libc : Unable to set property "ro.init.updatable_crashing_process_name" to "vendor.drm-clearkey-hal-1-2": error code: 0xb
03-31 12:47:48.681 1 1 W libc : Unable to set property "ro.init.updatable_crashing" to "1": error code: 0xb
03-31 12:47:48.777 660 4376 W ServiceManagement: Waited one second for [email protected]::IDrmFactory/clearkey
03-31 12:47:48.779 660 4376 I ServiceManagement: getService: Trying again for [email protected]::IDrmFactory/clearkey...
03-31 12:47:48.786 1 1 W libc : Unable to set property "ro.init.updatable_crashing_process_name" to "vendor.drm-clearkey-hal-1-2": error code: 0xb
03-31 12:47:48.786 1 1 W libc : Unable to set property "ro.init.updatable_crashing" to "1": error code: 0xb
03-31 12:47:48.893 660 660 W ServiceManagement: Waited one second for [email protected]::IDrmFactory/clearkey
03-31 12:47:48.894 660 660 I ServiceManagement: getService: Trying again for [email protected]::IDrmFactory/clearkey...
03-31 12:47:48.898 8821 8821 W init : type=1400 audit(0.0:812): avc: denied { execute_no_trans } for path="/system/vendor/bin/hw/[email protected]" dev="mmcblk0p52" ino=4081 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
03-31 12:47:48.908 1 1 W libc : Unable to set property "ro.init.updatable_crashing_process_name" to "vendor.drm-clearkey-hal-1-2": error code: 0xb
03-31 12:47:48.908 1 1 W libc : Unable to set property "ro.init.updatable_crashing" to "1": error code: 0xb
03-31 12:47:49.326 660 6002 W ServiceManagement: Waited one second for [email protected]::IDrmFactory/clearkey
03-31 12:47:49.327 660 6002 I ServiceManagement: getService: Trying again for [email protected]::IDrmFactory/clearkey...
03-31 12:47:49.331 8823 8823 W init : type=1400 audit(0.0:813): avc: denied { execute_no_trans } for path="/system/vendor/bin/hw/[email protected]" dev="mmcblk0p52" ino=4081 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
03-31 12:47:49.340 1 1 W libc : Unable to set property "ro.init.updatable_crashing_process_name" to "vendor.drm-clearkey-hal-1-2": error code: 0xb
03-31 12:47:49.341 1 1 W libc : Unable to set property "ro.init.updatable_crashing" to "1": error code: 0xb
03-31 12:47:49.491 660 4363 W ServiceManagement: Waited one second for [email protected]::IDrmFactory/clearkey
03-31 12:47:49.491 660 770 W ServiceManagement: Waited one second for [email protected]::IDrmFactory/clearkey
03-31 12:47:49.492 660 770 I ServiceManagement: getService: Trying again for [email protected]::IDrmFactory/clearkey...
03-31 12:47:49.492 660 4363 I ServiceManagement: getService: Trying again for [email protected]::IDrmFactory/clearkey...
03-31 12:47:49.495 8826 8826 W init : type=1400 audit(0.0:814): avc: denied { execute_no_trans } for path="/system/vendor/bin/hw/[email protected]" dev="mmcblk0p52" ino=4081 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
03-31 12:47:49.503 1 1 W libc : Unable to set property "ro.init.updatable_crashing_process_name" to "vendor.drm-clearkey-hal-1-2": error code: 0xb
03-31 12:47:49.504 1 1 W libc : Unable to set property "ro.init.updatable_crashing" to "1": error code: 0xb
03-31 12:47:49.667 660 6001 W ServiceManagement: Waited one second for [email protected]::IDrmFactory/clearkey
03-31 12:47:49.668 660 6001 I ServiceManagement: getService: Trying again for [email protected]::IDrmFactory/clearkey...
03-31 12:47:49.671 8828 8828 W init : type=1400 audit(0.0:815): avc: denied { execute_no_trans } for path="/system/vendor/bin/hw/[email protected]" dev="mmcblk0p52" ino=4081 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
03-31 12:47:49.680 1 1 W libc : Unable to set property "ro.init.updatable_crashing_process_name" to "vendor.drm-clearkey-hal-1-2": error code: 0xb
03-31 12:47:49.680 1 1 W libc : Unable to set property "ro.init.updatable_crashing" to "1": error code: 0xb
03-31 12:47:49.779 660 4376 W ServiceManagement: Waited one second for [email protected]::IDrmFactory/clearkey
03-31 12:47:49.780 660 4376 I ServiceManagement: getService: Trying again for [email protected]::IDrmFactory/clearkey...
03-31 12:47:49.785 8830 8830 W init : type=1400 audit(0.0:816): avc: denied { execute_no_trans } for path="/system/vendor/bin/hw/[email protected]" dev="mmcblk0p52" ino=4081 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
03-31 12:47:49.792 1 1 W libc : Unable to set property "ro.init.updatable_crashing_process_name" to "vendor.drm-clearkey-hal-1-2": error code: 0xb
03-31 12:47:49.793 1 1 W libc : Unable to set property "ro.init.updatable_crashing" to "1": error code: 0xb
03-31 12:47:49.895 660 660 W ServiceManagement: Waited one second for [email protected]::IDrmFactory/clearkey
03-31 12:47:49.896 660 660 I ServiceManagement: getService: Trying again for [email protected]::IDrmFactory/clearkey...
03-31 12:47:49.907 1 1 W libc : Unable to set property "ro.init.updatable_crashing_process_name" to "vendor.drm-clearkey-hal-1-2": error code: 0xb
03-31 12:47:49.907 1 1 W libc : Unable to set property "ro.init.updatable_crashing" to "1": error code: 0xb
konstruktor said:
@jmpf_bmx
in generall I see a lot of this:
Code:
03-31 12:46:30.635 1 1 W libc : Unable to set property "ro.init.updatable_crashing_process_name" to "vendor.drm-clearkey-hal-1-2": error code: 0xb
03-31 12:46:30.636 1 1 W libc : Unable to set property "ro.init.updatable_crashing" to "1": error code: 0xb
03-31 12:46:30.751 660 660 W ServiceManagement: Waited one second for [email protected]::IDrmFactory/clearkey
03-31 12:46:30.752 660 660 I ServiceManagement: getService: Trying again for [email protected]::IDrmFactory/clearkey...
03-31 12:46:30.755 7777 7777 W init : type=1400 audit(0.0:482): avc: denied { execute_no_trans } for path="/system/vendor/bin/hw/[email protected]" dev="mmcblk0p52" ino=4081 scontext=u:r:init:s0 tcontext=ubject_r:vendor_file:s0 tclass=file permissive=0
03-31 12:46:30.764 1 1 W libc : Unable to set property "ro.init.updatable_crashing_process_name" to "vendor.drm-clearkey-hal-1-2": error code: 0xb
03-31 12:46:30.764 1 1 W libc : Unable to set property "ro.init.updatable_crashing" to "1": error code: 0xb
03-31 12:46:31.173 660 6002 W ServiceManagement: Waited one second for [email protected]::IDrmFactory/clearkey
03-31 12:46:31.175 660 6002 I ServiceManagement: getService: Trying again for [email protected]::IDrmFactory/clearkey...
03-31 12:46:31.178 7779 7779 W init : type=1400 audit(0.0:483): avc: denied { execute_no_trans } for path="/system/vendor/bin/hw/[email protected]" dev="mmcblk0p52" ino=4081 scontext=u:r:init:s0 tcontext=ubject_r:vendor_file:s0 tclass=file permissive=0
03-31 12:46:31.186 1 1 W libc : Unable to set property "ro.init.updatable_crashing_process_name" to "vendor.drm-clearkey-hal-1-2": error code: 0xb
03-31 12:46:31.187 1 1 W libc : Unable to set property "ro.init.updatable_crashing" to "1": error code: 0xb
03-31 12:46:31.326 660 4363 W ServiceManagement: Waited one second for [email protected]::IDrmFactory/clearkey
03-31 12:46:31.327 660 4363 I ServiceManagement: getService: Trying again for [email protected]::IDrmFactory/clearkey...
03-31 12:46:31.327 660 770 W ServiceManagement: Waited one second for [email protected]::IDrmFactory/clearkey
03-31 12:46:31.328 660 770 I ServiceManagement: getService: Trying again for [email protected]::IDrmFactory/clearkey...
03-31 12:46:31.328 7782 7782 W init : type=1400 audit(0.0:484): avc: denied { execute_no_trans } for path="/system/vendor/bin/hw/[email protected]" dev="mmcblk0p52" ino=4081 scontext=u:r:init:s0 tcontext=ubject_r:vendor_file:s0 tclass=file permissive=0
03-31 12:46:31.335 1 1 W libc : Unable to set property "ro.init.updatable_crashing_process_name" to "vendor.drm-clearkey-hal-1-2": error code: 0xb
03-31 12:46:31.335 1 1 W libc : Unable to set property "ro.init.updatable_crashing" to "1": error code: 0xb
03-31 12:46:31.628 660 4376 W ServiceManagement: Waited one second for [email protected]::IDrmFactory/clearkey
03-31 12:46:31.630 660 4376 I ServiceManagement: getService: Trying again for [email protected]::IDrmFactory/clearkey...
03-31 12:46:31.631 7784 7784 W init : type=1400 audit(0.0:485): avc: denied { execute_no_trans } for path="/system/vendor/bin/hw/[email protected]" dev="mmcblk0p52" ino=4081 scontext=u:r:init:s0 tcontext=ubject_r:vendor_file:s0 tclass=file permissive=0
03-31 12:46:31.641 1 1 W libc : Unable to set property "ro.init.updatable_crashing_process_name" to "vendor.drm-clearkey-hal-1-2": error code: 0xb
03-31 12:46:31.641 1 1 W libc : Unable to set property "ro.init.updatable_crashing" to "1": error code: 0xb
Click to expand...
Click to collapse
Weird
I will take a look asap
Thanks
Thanks for job. When i flash only lineage and reboot, i have a black screen and only i can see soft key and power menu if i push power button. Not homepage. While, if i flash gapps, boot until screen blu with linguages and after some second, start reboot without end. Any ideas for this problem?
decsimon said:
Thanks for job. When i flash only lineage and reboot, i have a black screen and only i can see soft key and power menu if i push power button. Not homepage. While, if i flash gapps, boot until screen blu with linguages and after some second, start reboot without end. Any ideas for this problem?
Click to expand...
Click to collapse
- flash newest stock, tprw, boot.img (inside lineageos .zip)
- boot into tprw and wipe everything incl data (seperate button)
- flash lineageos + gapps (if needed)
decsimon said:
Thanks for job. When i flash only lineage and reboot, i have a black screen and only i can see soft key and power menu if i push power button. Not homepage. While, if i flash gapps, boot until screen blu with linguages and after some second, start reboot without end. Any ideas for this problem?
Click to expand...
Click to collapse
I see that is sdcard the problem! It is a 64gb Kingston canvas select plus. I dont know why.....
Great to see some up to date open source contributions underway.
I try with magisk to hide My bank apk, and other apk as Google play film but without success. It is possible to have a lineage OS official so all work well?