Related
Introduction:-
Hello Friends!!Here I present to you Another Awesome Port...Z3 SystemUI For Stock JB 4.2.2...Hope you like it...
Disclaimer:-
* 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 make nandroid backup before flashing it as a precaution!
*Try this MOD at your own risk!
Click to expand...
Click to collapse
Features:-
Added Quick Settings Flash Light Toggle
Drag And Drop To Add Or Remove Quick Settings
Added New Animations
Launch What's New Along With Google Now
Improved SuperStamina With New Widget
Added Two Different Versions Of SystemUI
NOTE- DO NOT USE ANY PART OF MY WORK IN ANY ROM OR ANY MOD WITHOUT MY PERMISSION!! IF YOU WANT TO USE, JUST WRITE ME A P.M...
Bugs:-
Flash Light toggle is not switching Off flashlight.
Download Link And Instructions:-
On next Post..
Credits:-
@serajr for precious help...
@kongaz2 for Original Z3 SystemUI...
DON'T FORGET TO HIT THANKS BUTTON!!
Downloads And Instructions
I have Included Two Different Versions of Z3 SystemUI...Both are Flashable Zips..Download Whichever you want...
Downloads:-
Z3 SystemUI Stock Version
Z3 SystemUI Theme Accent Version
For only those who are getting force close when charger is connected...Download this SystemUI - LINK
Instructions:-
Make Sure You're On Deodexed Stock ROM And Superuser MOD Installed.
Download Z3 SystemUI.
Go into CWM Recovery.
Flash Z3 SystemUI Zip.
Wipe Cache and Dalvik-Cache.
Reboot...Done!!:good:
DON'T FORGET TO HIT THANKS BUTTON!!:good::good:
Screenshots
Screenshots:-
STOCK VERSION-
{
"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"
}
THEME ACCENT VERSION-
DON'T FORGET TO HIT THANKS BUTTON!!:good::good:
Xperia C
Hey bro,,,,can you please port the same z3 system ui for xperia c....
Please bro i need it badly
Samuel Wankhede said:
Hey bro,,,,can you please port the same z3 system ui for xperia c....
Please bro i need it badly
Click to expand...
Click to collapse
Sorry friend..I can't help you..I don't have the device.. And its dual sim phone so it requires lots of changes in SystemUI..
support on xperia m?
Newbie_ID said:
support on xperia m?
Click to expand...
Click to collapse
Try it.. I don't think it'll work coz I specially made it for 4.2.2..But give it a try..
thanks bro,great job.Finally waited.
Superb work dude
Dude, after a few hours of flash it the systemui has stopped, any fix?
SmokinSickStyle said:
Dude, after a few hours of flash it the systemui has stopped, any fix?
Click to expand...
Click to collapse
Please post logcat of the force close..
Same here, system ui has stopped when i connected the charger to the phone
I don't know if this is what you request about the logcat but this is what logcat show me when systemUI Force close
//sorry for my english :silly:
Code:
12-09 21:59:40.744 D/StatusBar.NetworkController(6137): In updateSimIcon simState= READY
12-09 21:59:40.754 D/StatusBar.NetworkController(6137): In updateSimIcon simState= UNKNOWN
12-09 21:59:40.774 D/PhoneStatusBarPolicy(6137): updateSimState for subscription :0
12-09 21:59:43.347 W/InputDispatcher(789): channel '41ca7ca0 StatusBar (server)' ~ Consumer closed input channel or an error occurred. events=0x9
12-09 21:59:43.347 E/InputDispatcher(789): channel '41ca7ca0 StatusBar (server)' ~ Channel is unrecoverably broken and will be disposed!
12-09 21:59:43.357 W/InputDispatcher(789): Attempted to unregister already unregistered input channel '41ca7ca0 StatusBar (server)'
12-09 21:59:43.357 I/WindowState(789): WIN DEATH: Window{41ca7ca0 u0 StatusBar}
12-09 21:59:43.497 D/SystemUIService(6180): loading: class com.android.systemui.statusbar.phone.PhoneStatusBar
12-09 21:59:43.507 D/SystemUIService(6180): running: [email protected]
12-09 21:59:43.527 I/StatusBarManagerService(789): registerStatusBar [email protected]8
12-09 21:59:43.577 D/PhoneStatusBar(6180): mSettingsPanelGravity = 55
12-09 21:59:43.807 D/dalvikvm(6180): DexOpt: couldn't find field Lcom/android/systemui/statusbar/NotificationData$Entry;.row
12-09 21:59:43.807 D/dalvikvm(6180): DexOpt: couldn't find field Lcom/android/systemui/statusbar/NotificationData$Entry;.row
12-09 21:59:43.807 I/dalvikvm(6180): Could not find method com.android.systemui.statusbar.BaseStatusBar.onHeadsUpDismissed, referenced from method com.android.systemui.statusbar.policy.HeadsUpNotificationView.onChildDismissed
12-09 21:59:43.807 W/dalvikvm(6180): VFY: unable to resolve virtual method 2448: Lcom/android/systemui/statusbar/BaseStatusBar;.onHeadsUpDismissed ()V
12-09 21:59:43.807 I/dalvikvm(6180): Could not find method com.android.systemui.statusbar.BaseStatusBar.resetHeadsUpDecayTimer, referenced from method com.android.systemui.statusbar.policy.HeadsUpNotificationView.onTouchEvent
12-09 21:59:43.807 W/dalvikvm(6180): VFY: unable to resolve virtual method 2454: Lcom/android/systemui/statusbar/BaseStatusBar;.resetHeadsUpDecayTimer ()V
12-09 21:59:43.807 D/dalvikvm(6180): DexOpt: couldn't find field Lcom/android/systemui/statusbar/NotificationData$Entry;.row
12-09 21:59:43.807 D/dalvikvm(6180): DexOpt: couldn't find field Lcom/android/systemui/statusbar/NotificationData$Entry;.row
12-09 21:59:43.807 D/dalvikvm(6180): DexOpt: couldn't find field Lcom/android/systemui/statusbar/NotificationData$Entry;.row
12-09 21:59:43.807 D/dalvikvm(6180): DexOpt: couldn't find field Lcom/android/systemui/statusbar/NotificationData$Entry;.row
12-09 21:59:43.807 I/dalvikvm(6180): DexOpt: unable to optimize instance field ref 0x030b at 0x0c in Lcom/android/systemui/statusbar/policy/HeadsUpNotificationView;.canChildBeExpanded
12-09 21:59:43.807 D/dalvikvm(6180): DexOpt: couldn't find field Lcom/android/systemui/statusbar/NotificationData$Entry;.row
12-09 21:59:43.807 I/dalvikvm(6180): DexOpt: unable to optimize instance field ref 0x030b at 0x2a in Lcom/android/systemui/statusbar/policy/HeadsUpNotificationView;.setNotification
12-09 21:59:43.807 D/dalvikvm(6180): DexOpt: couldn't find field Lcom/android/systemui/statusbar/NotificationData$Entry;.row
12-09 21:59:43.807 I/dalvikvm(6180): DexOpt: unable to optimize instance field ref 0x030b at 0x0c in Lcom/android/systemui/statusbar/policy/HeadsUpNotificationView;.setUserExpandedChild
12-09 21:59:43.807 D/dalvikvm(6180): DexOpt: couldn't find field Lcom/android/systemui/statusbar/NotificationData$Entry;.row
12-09 21:59:43.807 I/dalvikvm(6180): DexOpt: unable to optimize instance field ref 0x030b at 0x0c in Lcom/android/systemui/statusbar/policy/HeadsUpNotificationView;.setUserLockedChild
12-09 21:59:44.067 I/dalvikvm(6180): Could not find method com.android.internal.telephony.ITelephony.setPreferredNetworkType, referenced from method com.sonymobile.systemui.statusbar.tools.LteService.changeTo
12-09 21:59:44.127 D/PhoneStatusBar(6180): disable: < expand icons alerts ticker system_info back home recent clock search >
12-09 21:59:44.127 V/PhoneStatusBar(6180): setLightsOn(true)
12-09 21:59:45.429 D/StatusBar.NetworkController(6180): In updateSimIcon simState= READY
12-09 21:59:45.449 D/StatusBar.NetworkController(6180): In updateSimIcon simState= UNKNOWN
12-09 21:59:45.459 D/PhoneStatusBarPolicy(6180): updateSimState for subscription :0
Dominator_666 said:
Same here, system ui has stopped when i connected the charger to the phone
Click to expand...
Click to collapse
Alright.. I'll upload fixed SystemUI today.. Stay tuned..
josu2016 said:
I don't know if this is what you request about the logcat but this is what logcat show me when systemUI Force close
//sorry for my english :silly:
Code:
12-09 21:59:40.744 D/StatusBar.NetworkController(6137): In updateSimIcon simState= READY
12-09 21:59:40.754 D/StatusBar.NetworkController(6137): In updateSimIcon simState= UNKNOWN
12-09 21:59:40.774 D/PhoneStatusBarPolicy(6137): updateSimState for subscription :0
12-09 21:59:43.347 W/InputDispatcher(789): channel '41ca7ca0 StatusBar (server)' ~ Consumer closed input channel or an error occurred. events=0x9
12-09 21:59:43.347 E/InputDispatcher(789): channel '41ca7ca0 StatusBar (server)' ~ Channel is unrecoverably broken and will be disposed!
12-09 21:59:43.357 W/InputDispatcher(789): Attempted to unregister already unregistered input channel '41ca7ca0 StatusBar (server)'
12-09 21:59:43.357 I/WindowState(789): WIN DEATH: Window{41ca7ca0 u0 StatusBar}
12-09 21:59:43.497 D/SystemUIService(6180): loading: class com.android.systemui.statusbar.phone.PhoneStatusBar
12-09 21:59:43.507 D/SystemUIService(6180): running: com.androi[email protected]
12-09 21:59:43.527 I/StatusBarManagerService(789): registerStatusBar [email protected]8
12-09 21:59:43.577 D/PhoneStatusBar(6180): mSettingsPanelGravity = 55
12-09 21:59:43.807 D/dalvikvm(6180): DexOpt: couldn't find field Lcom/android/systemui/statusbar/NotificationData$Entry;.row
12-09 21:59:43.807 D/dalvikvm(6180): DexOpt: couldn't find field Lcom/android/systemui/statusbar/NotificationData$Entry;.row
12-09 21:59:43.807 I/dalvikvm(6180): Could not find method com.android.systemui.statusbar.BaseStatusBar.onHeadsUpDismissed, referenced from method com.android.systemui.statusbar.policy.HeadsUpNotificationView.onChildDismissed
12-09 21:59:43.807 W/dalvikvm(6180): VFY: unable to resolve virtual method 2448: Lcom/android/systemui/statusbar/BaseStatusBar;.onHeadsUpDismissed ()V
12-09 21:59:43.807 I/dalvikvm(6180): Could not find method com.android.systemui.statusbar.BaseStatusBar.resetHeadsUpDecayTimer, referenced from method com.android.systemui.statusbar.policy.HeadsUpNotificationView.onTouchEvent
12-09 21:59:43.807 W/dalvikvm(6180): VFY: unable to resolve virtual method 2454: Lcom/android/systemui/statusbar/BaseStatusBar;.resetHeadsUpDecayTimer ()V
12-09 21:59:43.807 D/dalvikvm(6180): DexOpt: couldn't find field Lcom/android/systemui/statusbar/NotificationData$Entry;.row
12-09 21:59:43.807 D/dalvikvm(6180): DexOpt: couldn't find field Lcom/android/systemui/statusbar/NotificationData$Entry;.row
12-09 21:59:43.807 D/dalvikvm(6180): DexOpt: couldn't find field Lcom/android/systemui/statusbar/NotificationData$Entry;.row
12-09 21:59:43.807 D/dalvikvm(6180): DexOpt: couldn't find field Lcom/android/systemui/statusbar/NotificationData$Entry;.row
12-09 21:59:43.807 I/dalvikvm(6180): DexOpt: unable to optimize instance field ref 0x030b at 0x0c in Lcom/android/systemui/statusbar/policy/HeadsUpNotificationView;.canChildBeExpanded
12-09 21:59:43.807 D/dalvikvm(6180): DexOpt: couldn't find field Lcom/android/systemui/statusbar/NotificationData$Entry;.row
12-09 21:59:43.807 I/dalvikvm(6180): DexOpt: unable to optimize instance field ref 0x030b at 0x2a in Lcom/android/systemui/statusbar/policy/HeadsUpNotificationView;.setNotification
12-09 21:59:43.807 D/dalvikvm(6180): DexOpt: couldn't find field Lcom/android/systemui/statusbar/NotificationData$Entry;.row
12-09 21:59:43.807 I/dalvikvm(6180): DexOpt: unable to optimize instance field ref 0x030b at 0x0c in Lcom/android/systemui/statusbar/policy/HeadsUpNotificationView;.setUserExpandedChild
12-09 21:59:43.807 D/dalvikvm(6180): DexOpt: couldn't find field Lcom/android/systemui/statusbar/NotificationData$Entry;.row
12-09 21:59:43.807 I/dalvikvm(6180): DexOpt: unable to optimize instance field ref 0x030b at 0x0c in Lcom/android/systemui/statusbar/policy/HeadsUpNotificationView;.setUserLockedChild
12-09 21:59:44.067 I/dalvikvm(6180): Could not find method com.android.internal.telephony.ITelephony.setPreferredNetworkType, referenced from method com.sonymobile.systemui.statusbar.tools.LteService.changeTo
12-09 21:59:44.127 D/PhoneStatusBar(6180): disable: < expand icons alerts ticker system_info back home recent clock search >
12-09 21:59:44.127 V/PhoneStatusBar(6180): setLightsOn(true)
12-09 21:59:45.429 D/StatusBar.NetworkController(6180): In updateSimIcon simState= READY
12-09 21:59:45.449 D/StatusBar.NetworkController(6180): In updateSimIcon simState= UNKNOWN
12-09 21:59:45.459 D/PhoneStatusBarPolicy(6180): updateSimState for subscription :0
Click to expand...
Click to collapse
Well friend...You took logcat but it is not showing the error.. The error in logcat usually starts with E/FATAL EXCEPTION: or E/FATAL MAIN: ... It's okay by the way.. I'll upload fixed SystemUI today...
Strange,I have no such problems.Perhaps the problem is not in fashion.
FC Fixed SystemUI
For Those Who are getting force close when charger connected to phone...Flash the SystemUI through recovery or extract from zip and manually replace the SystemUI from the Attachment...
Don't forget to hit THANKS button if you liked my work...
Amirxon said:
Strange,I have no such problems.Perhaps the problem is not in fashion.
Click to expand...
Click to collapse
Neither do I...Just few people are reporting this problem...Maybe the problem is in their charger...It might not be original...
Anyways I've uploaded Fixed SystemUI for them but they'll not get the Vibration and Charger Connected tone I've added when the cable is connected...Really Sorry for that Friends...
Okay bro,good luck.
STRYDER~007 said:
For Those Who are getting force close when charger connected to phone...Flash the SystemUI through recovery or extract from zip and manually replace the SystemUI from the Attachment...
Don't forget to hit THANKS button if you liked my work...
Click to expand...
Click to collapse
Thanks now works perfect
Hi everyone,
I tried some Pie port ROMS and I found none has support for the S View Cover (no sleep, no cover screen). Lastly I settled on BlackDiamond NFE port v4.0, and so I'm trying to add support for the S View Cover which I own.
Long story short: I'm trying to make this work by modifying some system apks but it still doesn't work.
So I was investigating the S View Cover not supported on S7E BlackDiamond Pie Roms and here are my findings:
- To enable the S View Cover support, all there is to do is to put the following file into /system/etc/permissions/com.sec.feature.cover.sviewcover_level4.xml
Code:
<?xml version="1.0" encoding="utf-8"?>
<!-- Copyright (C) 2009 The Android Open Source Project
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<permissions>
<feature name="com.sec.feature.cover.sviewcover" level="4"/>
</permissions>
- Then the cover is recognized and all BUT SystemUI does not like it and continuously crashes until reboot, or until you remove the cover. The crash is as follows:
Code:
E AndroidRuntime: FATAL EXCEPTION: main
E AndroidRuntime: Process: com.android.systemui, PID: 4764
E AndroidRuntime: android.view.InflateException: Binary XML file line #1: Binary XML file line #2: Attempt to invoke virtual method 'void android.widget.FrameLayout.addView(android.view.View)' on a null object reference
E AndroidRuntime: Caused by: android.view.InflateException: Binary XML file line #2: Attempt to invoke virtual method 'void android.widget.FrameLayout.addView(android.view.View)' on a null object reference
E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'void android.widget.FrameLayout.addView(android.view.View)' on a null object reference
E AndroidRuntime: at com.samsung.android.app.cover.ui.CoverServiceBoxContainer.onFinishInflate(CoverServiceBoxContainer.java:467)
E AndroidRuntime: at android.view.LayoutInflater.rInflate(LayoutInflater.java:915)
E AndroidRuntime: at android.view.LayoutInflater.rInflateChildren(LayoutInflater.java:863)
E AndroidRuntime: at android.view.LayoutInflater.inflate(LayoutInflater.java:554)
E AndroidRuntime: at android.view.LayoutInflater.inflate(LayoutInflater.java:461)
E AndroidRuntime: at android.view.LayoutInflater.inflate(LayoutInflater.java:383)
E AndroidRuntime: at com.samsung.android.app.cover.ui.sviewcover.SViewCoverView.onFinishInflate(SViewCoverView.java:78)
E AndroidRuntime: at android.view.LayoutInflater.rInflate(LayoutInflater.java:915)
E AndroidRuntime: at android.view.LayoutInflater.rInflateChildren(LayoutInflater.java:863)
E AndroidRuntime: at android.view.LayoutInflater.inflate(LayoutInflater.java:554)
E AndroidRuntime: at android.view.LayoutInflater.inflate(LayoutInflater.java:461)
E AndroidRuntime: at android.view.LayoutInflater.inflate(LayoutInflater.java:383)
E AndroidRuntime: at android.view.View.inflate(View.java:26197)
E AndroidRuntime: at com.samsung.android.app.cover.CoverViewFactory.makeCoverView(CoverViewFactory.java:20)
E AndroidRuntime: at com.samsung.android.app.cover.CoverEx.reloadCoverView(CoverEx.java:284)
E AndroidRuntime: at com.samsung.android.app.cover.CoverEx.onCoverAttached(CoverEx.java:168)
E AndroidRuntime: at com.samsung.android.app.cover.plugin.PluginViewCoverImpl.onCoverAttached(PluginViewCoverImpl.java:38)
E AndroidRuntime: at com.android.systemui.cover.SysUICoverService.startCover(Unknown Source:33)
E AndroidRuntime: at com.android.systemui.cover.SysUICoverService.onPluginConnected(Unknown Source:24)
E AndroidRuntime: at com.android.systemui.cover.SysUICoverService.onPluginConnected(Unknown Source:2)
E AndroidRuntime: at com.android.systemui.splugins.SPluginInstanceManager$MainHandler.handleMessage(Unknown Source:183)
E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
E AndroidRuntime: at android.os.Looper.loop(Looper.java:214)
E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7045)
E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:964)
- From what I understand, there are some missing resources in SystemUI to handle the S View Cover display, which makes sense.
- And that's where my understanding in Android stops, so if someone have any idea/advice to give me in order to fix this issue, I'd be glad to help make it work. I can do testings on my phone as needed.
Okay for the crash it says there is missing Method.
About the recompile i suggest to use BatchApktool and ofc set api to PIE. And disable sign output apks then recompile the apk when it's done recompiling.
Open the stock UI(the one comes with the rom)let's BD V4. Using Winrar and open your recently compiled apk too.
From your compiled apk copy the following
Resources.arsc
Classes1.dex
Classes2.dex
Res
And paste them in the stock apk. And choose "store" as compression method. Then push the apk to system
Hard
hello can you put the apk on the forum because it's too hard for me I can not do it:angel:
Alexandre05YTB said:
hello can you put the apk on the forum because it's too hard for me I can not do it:angel:
Click to expand...
Click to collapse
This is a WIP, it's not ready yet, but when this is done I'll make it available (but it'll be embedded in a ROM, not as a simple flashable zip, because the SystemUI varies for every ROM)
Mwyann said:
This is a WIP, it's not ready yet, but when this is done I'll make it available (but it'll be embedded in a ROM, not as a simple flashable zip, because the SystemUI varies for every ROM)
Click to expand...
Click to collapse
Thank you very much :good: have a nice day
So I got a working patched SystemUI APK this time - that is, it installs and boots correctly again. BUT, it gives me the same error when I try to use the sview cover. So now I have to figure out what exactly is missing, maybe it's not even inside systemui, IDK...
does it work now?
No it still doesn't, and I personally bought a Clear Case on a discount which works fine with my ROM so I kind of left this topic behind for someone else to look at it, sorry.
I was searching full screen caller but there is non for black diamond s73
The All-In-One thread for Ground Zero ROMs - GZOSP 10.0 and Validus 10.0
{
"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"
}
@sparx: Bullhead Maintainer
@Char_G: Public Relations and Thread Maintainer
@scoobyjenkins: Graphics and Thread Maintainer
About the ROMs :
Validus is GZOSP based with a Clown theme and has a lot of features.
GZR Tapatalk Group
here
TBO apps
here
GZR Custom Mods & Extras
here
Installation Instructions
ALWAYS MAKE A NANDROID BACKUP FIRST!
Coming from another rom/clean install:
Reboot to recovery, flash required firmware
Wipe system, cache,, data
Flash rom zip and gapps
Reboot
Updating from a previous build/dirty flash:
Wipe system, cache in recovery
Flash rom zip, gapps and any other zips you may use
Reboot
Never dirty flash from one rom to another
Builds are rootless, so to be rooted, flash your SU of choice
If you have any issues, grab a log after a clean flash, upload and link here please. Add steps to reproduce the issue in your post.
Do not report issues dirty flashing this over some unofficial build or with some kernel flashed.
Logcat Extreme app is great as you can choose to start recording a log just before reproducing an error and stop recording just after so you log just the part you need.
Xposed is not supported here, if you want to run it and have issues, try an Xposed thread for support and bug reports here only welcome with a clean install with no Xposed present.
Make sure to state which rom you are running when asking for support
Open Gapps
here
GZOSP AIO Thread
here
Downloads
GZOSP :
Build 03/15 (10.0) (Stable)
--> Get GZOSP here
Validus :
Build 08/23 (10.0) (Stable)
--> Get Validus here
GZR Telegram Updates Channel
here
Source Code:
https://github.com/ValidusOs
https://github.com/ValidusOs-devices
https://github.com/GZR-Kernels
https://github.com/BigTopKrazies
XDA:DevDB Information
Ground Zero Roms, ROM for the LG Nexus 5X
Contributors
scoobyjenkins, sparx, Char_G
Source Code: https://github.com/GZOSP
ROM OS Version: Android 10
ROM Kernel: Linux 3.10.x
Based On: GZOSP
Version Information
Status: Stable
Created 2020-01-02
Last Updated 2020-08-24
Reserved
Reserved #2
We're back!! Nice job @scoobyjenkins!!
Hi, thx for your hard working, the ROM is good.
I found some minor issues:
- System time does not synchronized with the internet.
- First time opening the wifi preferences page leads an ANR of system, please see the attachment.
imknown said:
Hi, thx for your hard working, the ROM is good.
I found some minor issues:
- System time does not synchronized with the internet.
- First time opening the wifi preferences page leads an ANR of system, please see the attachment.
Click to expand...
Click to collapse
Thanks for the info, I'm not suffering from either of those issues and can't recreate...I'll keep trying :good:
sparx said:
Thanks for the info, I'm not suffering from either of those issues and can't recreate...I'll keep trying :good:
Click to expand...
Click to collapse
Yes, strange. I met the second issue only once when first time booting up.
The first issue about datetime I can reproduct it here. Here is the logcat.
Code:
--------- beginning of main
01-03 15:49:43.433 892 1260 D SntpClient: request time failed: java.net.SocketTimeoutException: Poll timed out
--------- beginning of system
01-03 15:49:45.624 892 910 W LocalDisplayAdapter: Unable to find color mode 0, ignoring request.
01-03 15:49:45.661 12195 12195 D DashboardFragment: Cannot find preference with key system_update_settings in Controller SystemUpdatePreferenceController
01-03 15:49:45.669 12195 21224 W TileUtils: Found com.android.settings.Settings$DataUsageSummaryActivity for intent Intent { act=com.android.settings.action.SETTINGS pkg=com.android.settings } missing metadata com.android.settings.category
01-03 15:49:45.696 12195 22101 D SettingsActivity: No enabled state changed, skipping updateCategory call
01-03 15:49:45.729 12195 22102 D SummaryLoader: No fragment specified for ComponentInfo{com.android.settings/com.android.settings.backup.UserBackupSettingsActivity}
01-03 15:49:45.778 1157 1170 I ndroid.systemu: NativeAlloc concurrent copying GC freed 8212(493KB) AllocSpace objects, 0(0B) LOS objects, 49% free, 14MB/28MB, paused 163us total 146.403ms
01-03 15:49:45.953 892 892 V SettingsProvider: Notifying for 0: content://settings/system/screen_brightness
01-03 15:49:45.975 335 335 I hwservicemanager: getTransport: Cannot find entry [email protected]::ILight/default in either framework or device manifest.
01-03 15:49:46.174 335 335 I chatty : uid=1000(system) hwservicemanage identical 12 lines
01-03 15:49:46.190 335 335 I hwservicemanager: getTransport: Cannot find entry [email protected]::ILight/default in either framework or device manifest.
01-03 15:49:46.202 1354 21936 D DhcpClient: Received packet: 1c:1b:0d:6d:db:1a ACK: your new IP /0.0.0.0, netmask /255.255.248.0, gateways [/10.20.0.1] DNS servers: /10.20.0.152 /10.20.0.144 , lease time null
01-03 15:49:46.206 335 335 I hwservicemanager: getTransport: Cannot find entry [email protected]::ILight/default in either framework or device manifest.
01-03 15:49:49.202 892 3895 E TaskPersister: File error accessing recents directory (directory doesn't exist?).
01-03 15:49:49.237 892 909 I ActivityTaskManager: START u0 {act=android.intent.action.MAIN cmp=com.android.settings/.SubSettings (has extras)} from uid 1000
01-03 15:49:46.521 335 335 I chatty : uid=1000(system) hwservicemanage identical 19 lines
01-03 15:49:46.538 335 335 I hwservicemanager: getTransport: Cannot find entry [email protected]::ILight/default in either framework or device manifest.
01-03 15:49:49.266 12195 12195 W ActivityThread: handleWindowVisibility: no activity for token [email protected]
01-03 15:49:49.283 12195 12195 D SettingsActivity: Starting onCreate
01-03 15:49:49.319 12195 12195 D SettingsActivity: Starting to set activity title
01-03 15:49:49.320 12195 12195 D SettingsActivity: Done setting title
01-03 15:49:49.320 12195 12195 D SettingsActivity: Switching to fragment com.android.settings.DateTimeSettings
01-03 15:49:49.320 12195 12195 D SubSettings: Launching fragment com.android.settings.DateTimeSettings
01-03 15:49:49.330 12195 12195 D DateTimeSettings: NO dashboard tiles for DateTimeSettings
01-03 15:49:49.330 12195 12195 D DateTimeSettings: All preferences added, reporting fully drawn
01-03 15:49:49.332 12195 12195 D SettingsActivity: Executed frag manager pendingTransactions
01-03 15:49:49.349 12195 21224 W TileUtils: Found com.android.settings.Settings$DataUsageSummaryActivity for intent Intent { act=com.android.settings.action.SETTINGS pkg=com.android.settings } missing metadata com.android.settings.category
01-03 15:49:49.362 12195 22113 D SettingsActivity: No enabled state changed, skipping updateCategory call
01-03 15:49:50.311 892 892 V SettingsProvider: Notifying for 0: content://settings/global/auto_time
01-03 15:49:50.315 538 22121 E ResolverController: No valid NAT64 prefix (109, <unspecified>/0)
01-03 15:49:52.041 559 559 W wificond: Failed to get NL80211_ATTR_EXT_FEATURES
01-03 15:49:52.046 559 559 I chatty : uid=1010(wifi) /system/bin/wificond identical 1 line
01-03 15:49:52.049 559 559 W wificond: Failed to get NL80211_ATTR_EXT_FEATURES
01-03 15:49:52.853 892 3895 E TaskPersister: File error accessing recents directory (directory doesn't exist?).
01-03 15:49:55.329 892 1260 D SntpClient: request time failed: java.net.SocketTimeoutException: Poll timed out
imknown said:
Yes, strange. I met the second issue only once when first time booting up.
The first issue about datetime I can reproduct it here. Here is the logcat.
Code:
--------- beginning of main
01-03 15:49:43.433 892 1260 D SntpClient: request time failed: java.net.SocketTimeoutException: Poll timed out
--------- beginning of system
01-03 15:49:45.624 892 910 W LocalDisplayAdapter: Unable to find color mode 0, ignoring request.
01-03 15:49:45.661 12195 12195 D DashboardFragment: Cannot find preference with key system_update_settings in Controller SystemUpdatePreferenceController
01-03 15:49:45.669 12195 21224 W TileUtils: Found com.android.settings.Settings$DataUsageSummaryActivity for intent Intent { act=com.android.settings.action.SETTINGS pkg=com.android.settings } missing metadata com.android.settings.category
01-03 15:49:45.696 12195 22101 D SettingsActivity: No enabled state changed, skipping updateCategory call
01-03 15:49:45.729 12195 22102 D SummaryLoader: No fragment specified for ComponentInfo{com.android.settings/com.android.settings.backup.UserBackupSettingsActivity}
01-03 15:49:45.778 1157 1170 I ndroid.systemu: NativeAlloc concurrent copying GC freed 8212(493KB) AllocSpace objects, 0(0B) LOS objects, 49% free, 14MB/28MB, paused 163us total 146.403ms
01-03 15:49:45.953 892 892 V SettingsProvider: Notifying for 0: content://settings/system/screen_brightness
01-03 15:49:45.975 335 335 I hwservicemanager: getTransport: Cannot find entry [email protected]::ILight/default in either framework or device manifest.
01-03 15:49:46.174 335 335 I chatty : uid=1000(system) hwservicemanage identical 12 lines
01-03 15:49:46.190 335 335 I hwservicemanager: getTransport: Cannot find entry [email protected]::ILight/default in either framework or device manifest.
01-03 15:49:46.202 1354 21936 D DhcpClient: Received packet: 1c:1b:0d:6d:db:1a ACK: your new IP /0.0.0.0, netmask /255.255.248.0, gateways [/10.20.0.1] DNS servers: /10.20.0.152 /10.20.0.144 , lease time null
01-03 15:49:46.206 335 335 I hwservicemanager: getTransport: Cannot find entry [email protected]::ILight/default in either framework or device manifest.
01-03 15:49:49.202 892 3895 E TaskPersister: File error accessing recents directory (directory doesn't exist?).
01-03 15:49:49.237 892 909 I ActivityTaskManager: START u0 {act=android.intent.action.MAIN cmp=com.android.settings/.SubSettings (has extras)} from uid 1000
01-03 15:49:46.521 335 335 I chatty : uid=1000(system) hwservicemanage identical 19 lines
01-03 15:49:46.538 335 335 I hwservicemanager: getTransport: Cannot find entry [email protected]::ILight/default in either framework or device manifest.
01-03 15:49:49.266 12195 12195 W ActivityThread: handleWindowVisibility: no activity for token [email protected]
01-03 15:49:49.283 12195 12195 D SettingsActivity: Starting onCreate
01-03 15:49:49.319 12195 12195 D SettingsActivity: Starting to set activity title
01-03 15:49:49.320 12195 12195 D SettingsActivity: Done setting title
01-03 15:49:49.320 12195 12195 D SettingsActivity: Switching to fragment com.android.settings.DateTimeSettings
01-03 15:49:49.320 12195 12195 D SubSettings: Launching fragment com.android.settings.DateTimeSettings
01-03 15:49:49.330 12195 12195 D DateTimeSettings: NO dashboard tiles for DateTimeSettings
01-03 15:49:49.330 12195 12195 D DateTimeSettings: All preferences added, reporting fully drawn
01-03 15:49:49.332 12195 12195 D SettingsActivity: Executed frag manager pendingTransactions
01-03 15:49:49.349 12195 21224 W TileUtils: Found com.android.settings.Settings$DataUsageSummaryActivity for intent Intent { act=com.android.settings.action.SETTINGS pkg=com.android.settings } missing metadata com.android.settings.category
01-03 15:49:49.362 12195 22113 D SettingsActivity: No enabled state changed, skipping updateCategory call
01-03 15:49:50.311 892 892 V SettingsProvider: Notifying for 0: content://settings/global/auto_time
01-03 15:49:50.315 538 22121 E ResolverController: No valid NAT64 prefix (109, <unspecified>/0)
01-03 15:49:52.041 559 559 W wificond: Failed to get NL80211_ATTR_EXT_FEATURES
01-03 15:49:52.046 559 559 I chatty : uid=1010(wifi) /system/bin/wificond identical 1 line
01-03 15:49:52.049 559 559 W wificond: Failed to get NL80211_ATTR_EXT_FEATURES
01-03 15:49:52.853 892 3895 E TaskPersister: File error accessing recents directory (directory doesn't exist?).
01-03 15:49:55.329 892 1260 D SntpClient: request time failed: java.net.SocketTimeoutException: Poll timed out
Click to expand...
Click to collapse
Thanks dude - been a while since I've seen a properly reported issue
I don’t have sound in wired headphones when talking on the phone (aosp dialer, google dialer)
pincher65 said:
I don’t have sound in wired headphones when talking on the phone (aosp dialer, google dialer)
Click to expand...
Click to collapse
I'll check it out
---------- Post added at 02:39 PM ---------- Previous post was at 01:47 PM ----------
pincher65 said:
I don’t have sound in wired headphones when talking on the phone (aosp dialer, google dialer)
Click to expand...
Click to collapse
Plugged in my wired headphones - works perfectly!
sparx said:
I'll check it out
---------- Post added at 02:39 PM ---------- Previous post was at 01:47 PM ----------
Plugged in my wired headphones - works perfectly!
Click to expand...
Click to collapse
the music works, the sound of pressing the buttons is there, but the voices are not heard.
only possible with me. flash clean
pincher65 said:
the music works, the sound of pressing the buttons is there, but the voices are not heard.
only possible with me. flash clean
Click to expand...
Click to collapse
Do you mean headphones or a proper hands free head set with built-in microphone?
Headphones worked perfectly for me during a call, I don't own a head set...
GZOSP & Validus 10.0 builds in the OP,
GZOSP: Fixed hotspot, raised volumes, other fixes/stuffses
Validus: Initial release, all gzosp fixes plus extra stuffses
scoobyjenkins said:
GZOSP & Validus 10.0 builds in the OP,
GZOSP: Fixed hotspot, raised volumes, other fixes/stuffses
Validus: Initial release, all gzosp fixes plus extra stuffses
Click to expand...
Click to collapse
Thanks Scoobs
Encryption and SELinux
Thanks for creating this ROM. Does this ROM support device encryption? Is SElinux enforcing?
Rahulmsinghvi said:
Thanks for creating this ROM. Does this ROM support device encryption? Is SElinux enforcing?
Click to expand...
Click to collapse
No encryption and not enforcing...
scoobyjenkins said:
GZOSP & Validus 10.0 builds in the OP,
GZOSP: Fixed hotspot, raised volumes, other fixes/stuffses
Validus: Initial release, all gzosp fixes plus extra stuffses
Click to expand...
Click to collapse
the sound of a voice in a wired headset appeared in both ROMs.
Validus (clean installation):
If you flash openengapps immediately (with a reboot in recovery), then it is impossible to connect to Wifi. First installed ROM, booted into the system, turned on Wifi, then flashed the gapps. When installing apps from the market, only 9 was downloaded and then froze. When you press the power button and try to boot from its menu in recovery, the phone also freezes.
A clean flash of GCOSP did not cause problems, while everything is working. I'll try all day tomorrow.
for some reason I can’t install the Pixel Launcher 10, only 7.1 works.
Thank you your work.
the test failed. Chrome does not work, applications constantly freeze, even a gps test.
as a daily rum I do not advise
pincher65 said:
the sound of a voice in a wired headset appeared in both ROMs.
Validus (clean installation):
If you flash openengapps immediately (with a reboot in recovery), then it is impossible to connect to Wifi. First installed ROM, booted into the system, turned on Wifi, then flashed the gapps. When installing apps from the market, only 9 was downloaded and then froze. When you press the power button and try to boot from its menu in recovery, the phone also freezes.
A clean flash of GCOSP did not cause problems, while everything is working. I'll try all day tomorrow.
for some reason I can’t install the Pixel Launcher 10, only 7.1 works.
Thank you your work.
the test failed. Chrome does not work, applications constantly freeze, even a gps test.
as a daily rum I do not advise
Click to expand...
Click to collapse
Would be good if you logged all that and posted...
It does sound like a gaps issue though
sparx said:
Would be good if you logged all that and posted...
It does sound like a gaps issue though
Click to expand...
Click to collapse
no, it's not gapps, on another ROM everything works after they are installed
opengapps nano 20191209 beta
pincher65 said:
no, it's not gapps, on another ROM everything works after they are installed
opengapps nano 20191209 beta
Click to expand...
Click to collapse
Please link me the gapps and supply some logs, I need to examine this...also, did you restore any backups before?
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)
Hey!
Due to some reason which is unknown to me my phone restarts after I swap WhatsApp application. Left or right it doesn't matter. This happens only with whatsapp. I'm providing logs.
02-16 11:11:01.419 1473 1473 E AndroidRuntime: at com.android.server.notification.Notifi cation RecordLogger$NotificationCanc elledEvent.fromCancel Reason(Notific ation RecordLogger.java:226)
02-16 11:11:01.419 1473 1473 E
AndroidRuntime: at
E com.android.server.notification.Notifi cation RecordLogger.log NotificationCa ncelled(Notification RecordLogger.jav a:86)
What could be the solution to this problem?
Thank you!