[ROM][6.0.1_r68][Official] Exodus Android 6 for Onyx - OnePlus X Original Android Development

{
"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"
}
ABOUT:
Team Exodus brings you EXODUS Rom, coded by professional level developers with additional support from the community, focusing on improved versions of common features and improvements found in the open-source community while bringing new, original improvements and coding with the highest standards.
INSTALLATION:
Take necessary backups
Be rooted w/ a custom recovery
Download EXODUS Rom & Gapps for your device and move them to your phone
Reboot to Recovery
Wipe (full wipe if coming from another Rom)**
Flash the Rom
Flash the Gapps**
Reboot to System
Setup and Reboot System
These directions are not necessary after the first install if you use the Exodus Updater, included in the ROM. It can notify you of updates, download, and install them for you automatically.
**This is automated if coming from a previous Exodus build (Dirty Flashing).
We recommend using our stock (preinstalled) kernel for best results and usage of all features!
SOURCES:
Exodus official build:
http://exodus-developers.net/exodus-6.0/onyx/
GApps:
Any 6.0.x GApps of your choice, we recommend opengapps.org
----- Advanced Developers/Users Section----
Rom source:
https://github.com/TeamExodus
Kernel source:
kernel_oneplus_onyx
Gerrit code review system:
http://review.exodus-developers.net
COMMUNITY
For additional support, info, and updates please join us in the official Google+ community:
https://plus.google.com/communities/106801227383087889476
Crowdin project:
Help us with translating to support your native language!
CREDITS:
Thank you to all the members, contributors, and maintainers on the Exodus Android team.
Please see our source for an unabridged list of contributions, authorship, and cherry-picks.
SUPPORT/DONATION:
If you would like to thank us for our work or help in support server costs you can do so here:
Primedirective (Team Leader / Project Owner / Server hosting)
MartinRo (Project Owner / Server hosting)
Raja. M (Senior Developer / Project Owner)
Alex (Kernel Developer / Project Owner)
Jorge (Developer / Overall Project )
Adrian (Developer / Overall Project )
&
TEAMExodus Team
XDA:DevDB Information
Exodus Android for Onyx, ROM for the OnePlus X
Contributors
Raja.M, TheCrazyLex, Martin_Ro, primedirective, Raja.M
Source Code: http://github.com/TeamExodus
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod, AOSP, CAF Mixed
Version Information
Status: Nightly
Created 2016-03-11
Last Updated 2016-09-24

Reserved

It gives error 07 installing ROM with twrp 3.0. Where I can find opx latest firmware?

Great, best room ever

Wow awesome! Thx for sharing
Am loving Exodus. Used it on many devices. Good feature set combined with great performance and of course layers:thumbup:
Flashed without issues. So far so good
Sent from my One X

mousse04 said:
Great, best room ever
Click to expand...
Click to collapse
Cris7ianO said:
Wow awesome! Thx for sharing
Am loving Exodus. Used it on many devices. Good feature set combined with great performance and of course layers:thumbup:
Flashed without issues. So far so good
Sent from my One X
Click to expand...
Click to collapse
Great to here enjoy exodus android experience !
Sent from my ONE A2003 using XDA Free mobile app

Can you add Screenshots to OP? And what about a bug list?

It's good to see Exodus on onyx. Thanks! Smooth rom so far, most stable layer rom in my opinion and I like it. haha. Only small issues with the model number being unknown and the user profile picture can't be changed.

Thanks for the ROM, very good work. Daily rom for me for sure.
Some questions, remarks however:
I enabled system ui tuner but can't find the menu ...
Would you plan to add network speed in status bar?
Updater doesn't seem to recognize this onyx version.
Keyboard gesture doesn't seem to work ...

Excellent ROM!! I really liked it, installed it as a daily driver.
One bug though... even though I did a clean flash, Uber app for some reason force closes on me... I'll do a logcat when I arrive home.
Sent from my unknown using Tapatalk

Installed it just now and it's running like a charm so no bugs encountered yet.

@Raja.M In the exopdus updater app, onyx is not included in the list. Thus giving message 'unsupported device found'.

This is the logcat of the Uber app crash, anyone can help me understand this error please? Thanks!
(I've tried cleaning cache, data, uninstalling and re-installing... the app opens, but after I log-in the app crashes before the map to order an uber appears).
03-11 23:10:52.964 30224 30224 E AndroidRuntime: FATAL EXCEPTION: main
03-11 23:10:52.964 30224 30224 E AndroidRuntime: Process: com.ubercab, PID: 30224
03-11 23:10:52.964 30224 30224 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'android.content.res.Configuration android.content.res.Resources.getConfiguration()' on a null object reference
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.util.ResolutionOverride.<init>(ResolutionOverride.java:56)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.view.SurfaceView.init(SurfaceView.java:207)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.view.SurfaceView.<init>(SurfaceView.java:187)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at maps.dz.aq.<init>(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at maps.dz.ao.<init>(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at maps.dg.u.<init>(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at maps.dg.u.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at maps.ei.ag.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at maps.ei.bu.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at maps.ei.r.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at com.google.android.gms.maps.internal.j$a.onTransactcom.google.android.gms.alldynamite:66)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.os.Binder.transact(Binder.java:387)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at bcq.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at bbs.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at adb$2.b(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at adb$1.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at bbt.f(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at bbt.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at adb.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at adb.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at com.google.android.gms.maps.MapView.a(Unknown Source)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at cry.a(SourceFile:115)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at com.ubercab.android.map.MapView.a(SourceFile:153)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at com.ubercab.client.feature.receipt.EnhancedReceiptDialogFragment.onViewCreated(SourceFile:415)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1086)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.moveToState(SourceFile:1248)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.support.v4.app.BackStackRecord.run(SourceFile:738)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl.execPendingActions(SourceFile:1613)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.support.v4.app.FragmentManagerImpl$1.run(SourceFile:517)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:739)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:95)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.os.Looper.loop(Looper.java:148)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:5445)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
03-11 23:10:52.964 30224 30224 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)

hey dev...
f*****g awsome rom.i have tried so many on my onyx till date.never have i found a rom which is this bug free at first go.
The only error i found is
"Invalid Number".
Fix that and i guess the rom will look perfect.Thanks a lot!!

Finally !! The wait is over. My favourite ROM has arrived. Thank you Raja for bringing exodus to onyx.?

Testing the rom for some hours now and looks very promising for the initial release. Only missing function to swap buttons before daily driver in my opinion.

laav said:
Testing the rom for some hours now and looks very promising for the initial release. Only missing function to swap buttons before daily driver in my opinion.
Click to expand...
Click to collapse
Do you speak about HW button?

mousse04 said:
Do you speak about HW button?
Click to expand...
Click to collapse
Yes, or do I miss something?

Could you link me to a list of features, guys?
I have searched in google and G+ and haven't found it...
Thanks!!

laav said:
Yes, or do I miss something?
Click to expand...
Click to collapse
Go into setting, hardware, define action or something like this.
Then, you can re define hardware button action

Related

[ROM][6.0][Read OP!]Official nightly Cyanogenmod 13 for Peregrine

Please search the thread and read the OP before postings to reduce the numbers of unneeded reposting by everyone.
{
"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"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0(MM), which is designed to increase performance and reliability over stock Android for your device.
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.
*/
CyanogenMod 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. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Tips and notes:
When choosing a Gapps package ensure it can fit into /system when flashed. Micro gapps is recommend as it fits and provides everything in a base package you will need for gapps support you can install the other google apps from the store as want later on.
Remember nightly builds are experimental they can and will be broken from time to time. Always have a backup at hand.
Storage in Marshmallow is dynamically mounted. That means you will get a prompt at boot to mount as either portable storage or internal storage. Use portable storage to continue using it as like in previous versions of android.
To transfer file to PC when plugged in you will get the charging mode prompt status in the status bar click it to change from charging mode to transfer files.
TWRP cannot read internal formatted sdcards at the moment in order to flash a new nightly try one of these suggestions -
Adb sideloading - http://forum.xda-developers.com/showpost.php?p=64194455&postcount=398
USB OTG - http://forum.xda-developers.com/showpost.php?p=64194957&postcount=401
Using PC file manager to place the file where TWRP can see it - http://forum.xda-developers.com/showpost.php?p=64194157&postcount=397
TWRP 3 now supports internal formatted sdcards - http://forum.xda-developers.com/moto-g/4g-development/unofficial-twrp-3-0-0-0-moto-g-lte-t3310450
If you want to use Supersu see here for non-systemless root. For systemless root use a zip from the SuperSu page othwerwise inbuilt superuser from development settings works fine.
Having issues with Titanium Backup? This should help - https://www.youtube.com/watch?v=DrOuUtlqz9w&ab_channel=AbhinavSrivastava
Want to mount system as read write for apps like Adaway use this(For builds before 29 Nov 2015)
Builds 29Nov 2015+ from a terminal app use
Code:
su
mount -o rw,remount /system
then after changes use
Code:
mount -o ro,remount /system
to mount it back as read-only or reboot.
what doesn't work:
-You tell me as am not sure atm [emoji14]
Downloads:
Older Unofficial builds
Official builds nightly builds
Install instructions:
IMPORTANT! When coming from older builds to CM13 24 Nov+ builds if you have FCs with phone
LuK1337 said:
From now after flashing 20151121 build you will have to remove /data/data/com.android.providers.telephony/databases/telephony.db file due to db scheme updates. Otherwise com.android.phone crash will happen.
You can use TWRP file manager to do it.
Click to expand...
Click to collapse
Contrary to popular belief(me included) wiping between versions is not needed - https://plus.google.com/u/0/+DanPasanen/posts/GKnirTFjojg
Coming from an official CM12.1 rom
Reboot to recovery
Install Rom
Optional Gapps, Kernel, etc
Reboot
Make sure to install Gapps before booting are you will have FCs with Setup wizard.
Coming from a different rom or stock
Wipe data and cache
Flash the CM13zip
Install opengapps or any other perffered gapps if you want
Reboot
Profit
Changelog - http://www.cmxlog.com/13/peregrine/
Source:
base: https://github.com/CyanogenMod
kernel: https://github.com/CyanogenMod/android_kernel_motorola_msm8226/tree/cm-13.0
Device: https://github.com/CyanogenMod/android_device_motorola_msm8226-common/tree/cm-13.0, https://github.com/CyanogenMod/android_device_motorola_peregrine/tree/cm-13.0
Vendor: https://github.com/TheMuppets/proprietary_vendor_motorola/tree/cm-13.0
Rest of the stuff is all unmerged stuff from gerrit
Credits:- (not in a order)
AOSParadox team @h2o64
@luca020400 @LuK1337
@srisurya95 for helping me spot my error with compiling.
CM Team
Google
Motorola
And any one else that I forgot to mention [emoji14]
Thanks a lot for this, I'll test on weekend
Enviado desde mi XT1040 mediante Tapatalk
keep up the good work
Whoa, thank you! <3
First of all, thanks! Just installed it.
In the first boot, when cm confugration wizard started, I tried to change language, and system soft rebooted, never to boot up again. Tried it a couple of times with same result. Wiping data/cache solves the issue. So using it in english for now. I will report if more things come up!
Edit: After installing cm, installed gapps, and upon booting the "setup wizard had to close" (or similar xD) message appeared once and again. This happened the 2 times I tried.
gartzen said:
First of all, thanks! Just installed it.
In the first boot, when cm confugration wizard started, I tried to change language, and system soft rebooted, never to boot up again. Tried it a couple of times with same result. Wiping data/cache solves the issue. So using it in english for now. I will report if more things come up!
Edit: After installing cm, installed gapps, and upon booting the "setup wizard had to close" (or similar xD) message appeared once and again. This happened the 2 times I tried.
Click to expand...
Click to collapse
Same here
I have the same problem when i try to change language. Is someone also having a problem of fc with titanium backup ?
Nice work, the only issue i have ran into at the moment is when you go Under More in settings and go into Mobile networks you get an FC on com.android.phone posted the logcat below for you
Code:
10-22 20:06:34.340 646 656 I art : Background partial concurrent mark sweep GC freed 22291(1385KB) AllocSpace objects, 6(120KB) LOS objects, 33% free, 23MB/35MB, paused 2.507ms total 133.930ms
10-22 20:06:34.341 31441 31441 D AndroidRuntime: Shutting down VM
10-22 20:06:34.350 31441 31441 E AndroidRuntime: FATAL EXCEPTION: main
10-22 20:06:34.350 31441 31441 E AndroidRuntime: Process: com.android.phone, PID: 31441
10-22 20:06:34.350 31441 31441 E AndroidRuntime: java.lang.ArrayIndexOutOfBoundsException: length=13; index=13
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.preference.ListPreference.getEntry(ListPreference.java:220)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.preference.ListPreference.getSummary(ListPreference.java:165)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.preference.Preference.onBindView(Preference.java:558)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.preference.Preference.getView(Preference.java:495)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.preference.PreferenceGroupAdapter.getView(PreferenceGroupAdapter.java:246)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.AbsListView.obtainView(AbsListView.java:2346)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.ListView.makeAndAddView(ListView.java:1875)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.ListView.fillDown(ListView.java:702)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.ListView.fillFromTop(ListView.java:763)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.ListView.layoutChildren(ListView.java:1684)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.AbsListView.onLayout(AbsListView.java:2148)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.View.layout(View.java:16633)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.ViewGroup.layout(ViewGroup.java:5437)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1743)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1586)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.LinearLayout.onLayout(LinearLayout.java:1495)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.View.layout(View.java:16633)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.ViewGroup.layout(ViewGroup.java:5437)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1743)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.LinearLayout.layoutHorizontal(LinearLayout.java:1732)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.LinearLayout.onLayout(LinearLayout.java:1497)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.View.layout(View.java:16633)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.ViewGroup.layout(ViewGroup.java:5437)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1743)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1586)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.LinearLayout.onLayout(LinearLayout.java:1495)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.View.layout(View.java:16633)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.ViewGroup.layout(ViewGroup.java:5437)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.FrameLayout.layoutChildren(FrameLayout.java:336)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.FrameLayout.onLayout(FrameLayout.java:273)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.View.layout(View.java:16633)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.ViewGroup.layout(ViewGroup.java:5437)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at com.android.internal.widget.ActionBarOverlayLayout.onLayout(ActionBarOverlayLayout.java:493)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.View.layout(View.java:16633)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.ViewGroup.layout(ViewGroup.java:5437)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.FrameLayout.layoutChildren(FrameLayout.java:336)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.widget.FrameLayout.onLayout(FrameLayout.java:273)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at com.android.internal.policy.PhoneWindow$DecorView.onLayout(PhoneWindow.java:2678)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.View.layout(View.java:16633)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.ViewGroup.layout(ViewGroup.java:5437)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.ViewRootImpl.performLayout(ViewRootImpl.java:2171)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1931)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1107)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:6013)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.Choreographer$CallbackRecord.run(Choreographer.java:858)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.Choreographer.doCallbacks(Choreographer.java:670)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.Choreographer.doFrame(Choreographer.java:606)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:844)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:739)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:95)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.os.Looper.loop(Looper.java:148)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:5417)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
10-22 20:06:34.350 31441 31441 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
10-22 20:06:34.356 646 1619 W ActivityManager: Force finishing activity com.android.phone/.MobileNetworkSettings
10-22 20:06:34.359 646 1619 W ActivityManager: Force finishing activity com.android.settings/.SubSettings
10-22 20:06:34.365 8632 8632 I art : Starting a blocking GC Explicit
10-22 20:06:34.407 8632 8632 I art : Explicit concurrent mark sweep GC freed 2328(136KB) AllocSpace objects, 0(0B) LOS objects, 40% free, 13MB/22MB, paused 708us total 41.399ms
10-22 20:06:34.414 646 882 I OpenGLRenderer: Initialized EGL, version 1.4
10-22 20:06:34.431 8632 8632 I art : Starting a blocking GC Explicit
10-22 20:06:34.466 8632 8632 I art : Explicit concurrent mark sweep GC freed 584(33KB) AllocSpace objects, 0(0B) LOS objects, 39% free, 13MB/22MB, paused 594us total 34.252ms
10-22 20:06:34.466 8632 8632 I art : Starting a blocking GC Explicit
10-22 20:06:34.499 8632 8632 I art : Explicit concurrent mark sweep GC freed 5(160B) AllocSpace objects, 0(0B) LOS objects, 40% free, 13MB/22MB, paused 555us total 32.508ms
10-22 20:06:34.537 8632 8706 E Surface : getSlotFromBufferLocked: unknown buffer: 0xb90366d0
10-22 20:06:34.538 8632 8706 D OpenGLRenderer: endAllStagingAnimators on 0xb9328d68 (ListView) with handle 0xb90440e0
10-22 20:06:34.860 646 663 W ActivityManager: Activity pause timeout for ActivityRecord{b1c66fa u0 com.android.phone/.MobileNetworkSettings t133 f}
10-22 20:06:35.004 8632 8632 D DashboardSummary: rebuildUI took: 88 ms
10-22 20:06:37.131 6307 6434 D audio_hw_primary: out_standby: enter: stream (0xb8446ac0) usecase(1: low-latency-playback)
10-22 20:06:37.182 6307 6434 D hardware_info: hw_info_append_hw_type : device_name = speaker-lite
10-22 20:06:38.408 253 367 I ThermalEngine: Sensor:xo_therm_pu2:25000 mC
• Camera crashes (Cannot connect to the camera error) right after you take a picture
• Facebook crashes as soon as you start to write your username on the login screen
• File Manager crashes (some kind of "no privileges" error)
I also don't have the option to set Google Now launcher as default launcher, like if it wasn't installed, but it works with Nova Launcher.
edit : problem solve after rebooting sorry
Camera has already been fixed on Falcon's build... so it's just a mater of time @Kayant merges it!
I have also seen the issues with camera, file manager, TB. Can't really say too much because my limited knowledge doesn't give me too much insight into what exactly is going on but am going through some logs and will see what I can understand from them. @ebol94 I already had the camera fix merged in but maybe is because I don't have an updated lib which is why it's not completed fixed? Will test that in a build later.
Kayant said:
I have also seen the issues with camera, file manager, TB. Can't really say too much because my limited knowledge doesn't give me too much insight into what exactly is going on but am going through some logs and will see what I can understand from them. @ebol94 I already had the camera fix merged in but maybe is because I don't have an updated lib which is why it's not completed fixed? Will test that in a build later.
Click to expand...
Click to collapse
You need to add this branch to your repo in order to use the new libs
Code:
<project path="external/sony/boringssl-compat" name="CyanogenMod/android_external_sony_boringssl-compat" revision="cm-13.0" />
By the way, I managed to get working data but not LTE on my build, but I'm not quite sure the state of yours since I haven't flashed it. Could anybody tell me? :silly:
Nevermind, LTE is working good here too . So far there's pretty much everything working, the only thing left is that I'm not having my sdcard partition mounted (at least on my build). Maybe it can be forced through terminal, I'll try later. How about on this build?
Regards!
beeeto said:
You need to add this branch to your repo in order to use the new libs
Code:
<project path="external/sony/boringssl-compat" name="CyanogenMod/android_external_sony_boringssl-compat" revision="cm-13.0" />
By the way, I managed to get working data but not LTE on my build, but I'm not quite sure the state of yours since I haven't flashed it. Could anybody tell me? :silly:
Nevermind, LTE is working good here too . So far there's pretty much everything working, the only thing left is that I'm not having my sdcard partition mounted (at least on my build). Maybe it can be forced through terminal, I'll try later. How about on this build?
Regards!
Click to expand...
Click to collapse
I already have the necessary things. The only thing that may have changed is h2o64's lib being newer than luk1337's one
There's how SDcard works in MM now because you can choose to use it as internal storage so how it mounts at boot has changed - http://source.android.com/devices/storage/config.html
You need to click the notification and choose which option you want.
Kayant said:
I already have the necessary things. The only thing that may have changed is h2o64's lib being newer than luk1337's one
There's how SDcard works in MM now because you can choose to use it as internal storage so how it mounts at boot has changed - http://source.android.com/devices/storage/config.html
You need to click the notification and choose which option you want.
Click to expand...
Click to collapse
My lib is based o, the 5.1 blobs, and Luk's one is based off 5.0.2.
So if you wanna use mine, you must have all the other libs from 5.1
PS : I like the "not in order" xD :justkidding:
h2o64 said:
My lib is based o, the 5.1 blobs, and Luk's one is based off 5.0.2.
So if you wanna use mine, you must have all the other libs from 5.1
PS : I like the "not in order" xD :justkidding:
Click to expand...
Click to collapse
Hey you should hunt srisurya95 down for that
Thanks for the heads up.
Great work guys! I love it
One quick question: is the mobile radio active bug still present? On Lollipop, Chrome and Google Play Services are killing my battery for no apparent reason.
I have a question, if I install this Alpha build on my Motorola Moto G when the nightly builds start would it be a case of simply upgrading to this from the device via Cyanogenmod updates?
also, what recovery did you guys use? I am currently running CM recovery but its very basic and no options for nandroid backup so looking to do this before trying out CM13
ceanth said:
also, what recovery did you guys use? I am currently running CM recovery but its very basic and no options for nandroid backup so looking to do this before trying out CM13
Click to expand...
Click to collapse
I am using the TWRP-v2.8.7.0 from here - http://forum.xda-developers.com/mot...ection-somcom3xs-experimental-corner-t2996266

Restore incoming call swipe directions

On stock ROM, noticed after the OTA update before last that the direction to swipe the icon to answer an incoming call changed from left (reject)/right (answer) to up(reject)/down(answer). I really dislike this change, and would like to know if anyone has a way to change it back.
Thanks in advance
Have you got unlocked bootloader?
knw257 said:
On stock ROM, noticed after the OTA update before last that the direction to swipe the icon to answer an incoming call changed from left (reject)/right (answer) to up(reject)/down(answer). I really dislike this change, and would like to know if anyone has a way to change it back.
Thanks in advance
Click to expand...
Click to collapse
I really love to change slide up to answer and slide down to reject incoming call
przemcio510 said:
Have you got unlocked bootloader?
Click to expand...
Click to collapse
Yes, and installed Magisk for root
knw257 said:
Yes, and installed Magisk for root
Click to expand...
Click to collapse
You may try to install previous version of OOS dialer (you'd have to extract the ROM zip) or switch to an old version of Google Dialer (e.g. 4.2)
przemcio510 said:
You may try to install previous version of OOS dialer (you'd have to extract the ROM zip) or switch to an old version of Google Dialer (e.g. 4.2)
Click to expand...
Click to collapse
I tried this, and managed to extract the dialer.apk from the 4.1.7 OOS image, but upon trying to install, I get a message:
{
"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"
}
knw257 said:
I tried this, and managed to extract the dialer.apk from the 4.1.7 OOS image, but upon trying to install, I get a message:
Click to expand...
Click to collapse
You have to copy the apk to /system/priv-app/OPDialer (I thnk that this is correct path, but please check) and reboot. You can't install it like a normal app
przemcio510 said:
You have to copy the apk to /system/priv-app/OPDialer (I thnk that this is correct path, but please check) and reboot. You can't install it like a normal app
Click to expand...
Click to collapse
I attempted this, but found after reboot that trying to open the dialer resulted in the app immediately crashing. I'm guessing I also need the .odex files that go along with the APK from the image.
Also, the path is /system/priv-app/dialer, just for reference.
One question: does dialer.apk rely on other apps, such as OPInCallUI, TelephonyProvider, Telcom, TeleService, etc?
knw257 said:
I attempted this, but found after reboot that trying to open the dialer resulted in the app immediately crashing. I'm guessing I also need the .odex files that go along with the APK from the image.
Click to expand...
Click to collapse
Did you clear data and set 755 for folder and 644 for file permissions?
Odex files aren't needed.
It wolud be easier to debug, if you could grab the logcat from crash.
knw257 said:
Also, the path is /system/priv-app/dialer, just for reference.
Click to expand...
Click to collapse
Ok, thanks.
knw257 said:
One question: does dialer.apk rely on other apps, such as OPInCallUI, TelephonyProvider, Telcom, TeleService, etc?
Click to expand...
Click to collapse
OPInCallUI is not needed. The rest should stay.
przemcio510 said:
OPInCallUI is not needed. The rest should stay.
Click to expand...
Click to collapse
Just to clarify, I wanted to make sure those items are not also requirements to pull from the previous OOS ROM image. I.E. do I need the older versions of those as well in addition to the dialer.apk that I pulled out?
przemcio510 said:
It wolud be easier to debug, if you could grab the logcat from crash.
Click to expand...
Click to collapse
I'll see about getting that data tonight.
There are flashable zips for Google Dialer too, if I'm not wrong. Try getting that and flash it.
knw257 said:
Just to clarify, I wanted to make sure those items are not also requirements to pull from the previous OOS ROM image. I.E. do I need the older versions of those as well in addition to the dialer.apk that I pulled out.
Click to expand...
Click to collapse
I think no, but if it won't work, you may try to pull these too.
I hope you find the fix.
May be you can create a ZIP to flash it.
Thanks
przemcio510 said:
It wolud be easier to debug, if you could grab the logcat from crash.
Click to expand...
Click to collapse
I pulled a logcat from the phone just after trying open the dialer app, and found this:
Code:
10-24 22:30:51.937 4091 4091 D AndroidRuntime: Shutting down VM
10-24 22:30:51.938 4091 4091 E AndroidRuntime: FATAL EXCEPTION: main
10-24 22:30:51.938 4091 4091 E AndroidRuntime: Process: com.android.dialer, PID: 4091
10-24 22:30:51.938 4091 4091 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.dialer/com.oneplus.contacts.activities.OPDialtactsActivity}: java.lang.RuntimeException: Unknown animation name: selector
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2733)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2819)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at android.app.ActivityThread.-wrap12(ActivityThread.java)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1532)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6321)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: Caused by: java.lang.RuntimeException: Unknown animation name: selector
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at android.view.animation.AnimationUtils.createAnimationFromXml(AnimationUtils.java:160)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at android.view.animation.AnimationUtils.createAnimationFromXml(AnimationUtils.java:127)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at android.view.animation.AnimationUtils.loadAnimation(AnimationUtils.java:108)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at com.oneplus.contacts.activities.OPDialtactsActivity.createViewsAndFragments(OPDialtactsActivity.java:541)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at com.oneplus.contacts.activities.OPDialtactsActivity.onCreate(OPDialtactsActivity.java:423)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at android.app.Activity.performCreate(Activity.java:6760)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1134)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2686)
10-24 22:30:51.938 4091 4091 E AndroidRuntime: ... 9 more
10-24 22:30:51.938 4091 4091 D AppTracker: App Event: crash
I'm guessing this means I also need to replace the Contacts app with the old version, but I'm not certain. If you have any input, I'd certainly appreciate it.

[MOD] Camera supporting 60FPS 120FPS

About:
This is a modification of the LineageOS camera wrapper, Snapdragon Camera app, libstagefright, and media profiles to allow recording video at 60FPS and 120FPS with stereo audio at 256kbps, also allows recording files over 4GB (the selected storage filesystem must support files larger than 4GB), and the ability to change AV bitrates/codecs on the fly. Album preference has been added in 1.3.
Q Users: Backup before install!
/system/lib/libstagefright.so
/system/product/priv-app/Snap/Snap.apk
/system/product/priv-app/Snap/oat/arm/Snap.odex
/system/product/priv-app/Snap/oat/arm/Snap.vdex
/system/vendor/etc/media_profiles_V1_0.xml
/system/vendor/lib/hw/camera.msm8974.so
P/O Users: Backup before install!
/system/lib/libstagefright.so
/system/priv-app/Snap/Snap.apk
/system/priv-app/Snap/oat/arm/Snap.odex
/system/priv-app/Snap/oat/arm/Snap.vdex
/system/vendor/etc/media_profiles_V1_0.xml (or /system/etc/media_profiles.xml)
/system/vendor/lib/hw/camera.msm8974.so
N Users: Backup before install!
/system/etc/media_profiles.xml
/system/lib/libstagefright.so
/system/lib/hw/camera.msm8974.so
/system/priv-app/Snap/Snap.apk
Download ZIP:
If you experience bugs or crashes please attach the adb log file, also include your mod version, OS, and device model in the post!
Q v1.3, TWRP 3.3.1: https://drive.google.com/file/d/1T3d6tIj_aM_zcfS7Q-RNNrT2IkvMwwvf/view?usp=sharing
P v1.3, TWRP 3.3.1: https://drive.google.com/file/d/1MPOfu7UXV-1RfWbW4EBJfSwmbVSnPXkC/view?usp=sharing
----------------
Q v1.2: https://drive.google.com/file/d/1wL5QeTFPaBGhbT3l3x4J52Q6f-fF9w8-/view?usp=sharing
P v1.2: https://drive.google.com/file/d/1Pjzu_Y5L0H8qqszYzwHJptD3uESvFKkB/view?usp=sharing
----------------
O v0.6: https://drive.google.com/open?id=1fM-SMDZT2iYxaX3AoYWCRegu918PqRFp
N v0.6: https://drive.google.com/open?id=1t2HalWYSObez0Xar0MOfk7opcLaSf0AD
----------------
Old versions: https://drive.google.com/drive/folders/1oFLPaoDmfDJlD8FAoRVhAk2haETI_dH6
v1.3 Changelog:
snap: Album preference: This will store media into subdirectories: Default, Date, Custom, Hidden.
snap: Media is now stored using the MediaStore API for Android 10 / LOS 17.1 builds.
Past Changelogs:
v1.2 Changelog:
snap: Merge upstream
snap: PiP and Multi-Window Removed (Bugs)
stagefright: Merge upstream
v1.1 Changelog:
snap: Added Picture-in-Picture support
snap: Fixed Multi-Window handling
profiles: Updated to proper location (again)
v0.9 Changelog:
snap: Merge upstream
stagefright: Merge upstream
profiles: Set all audio channels to stereo
v0.8-2 Changelog:
profiles: Updated path from upstream change, moved from /system/etc/media_profiles.xml to /system/vendor/etc/media_profiles_V1_0.xml
v0.8 Changelog:
snap: Upstream change now saves files in /Android/data/org.lineageos.snap/files instead of /DCIM/Camera
v0.7 Changelog:
snap: Fix compilation for Pie
v0.6 Changelog:
snap: Added new advanced video preferences: Video bitrate, Audio bitrate
To access these preferences, tap the "Bright screen" preference until it enables advanced camera preferences
Auto: Run the original code.
Profile: Use bitrate found in media profile, no scaling.
Manual: Set custom bitrate with slider dialog, based on the minimum and maximum bitrate caps, saving the preference for each codec.
Max: Set maximum bitrate from the encoder cap.
snap: Disabled 4GB file size limit
snap: Separate video denoise and photo denoise preferences
stagefright: Disabled 4GB file size limit
profiles: Cleanup
v0.5-3 Changelog:
wrapper: Fix quick settings flash
wrapper: Fix flash "On" photo mode
v0.5 Changelog:
wrapper: Fix hang during selfie shot
profiles: Increase audio bitrates in media_profiles.xml
v0.4 Changelog:
snap: Added "Denoise" setting to Video menu
wrapper: Restart flash during preview changes
wrapper: Removed focus modes from previous versions
wrapper: Code optimizations
profiles: Cleanup
v0.3 Changelog:
snap: Handle resource error
wrapper: Fix flash mode "On" in photo mode
v0.2 Changelog:
snap: Enabled advanced settings by default
wrapper: If torch is set, turn back on once recording in 60FPS
Known Bugs:
Camera name becomes assigned to a different resource ID on Android 9 and below. Android 10 does not have this issue.
On certain devices, front camera does not load or fails to save pictures.
1.2 Q is not parsing Snaps external storage, the files exist but they will not appear in the Gallery. In 1.3 this is fixed.
Android 9 still has the sdcard deletion bug.. if you do your own builds you can fix it with the commits below:
https://github.com/tomm1e/android_vendor_lineage/commit/6ad07dee60e26bdf88d9ac07face4d7a0fbe5610
https://github.com/tomm1e/android_p...mmit/7cad0838a254f6422343d17d5a578d2e09382359
https://github.com/LineageOS/android_frameworks_base/commit/c3f4b30d8e15228a12ca6bd1f4037d5c69dda6ea
Notes:
To access the Advanced camera preferences in Snap, tap the "Bright screen" preference until it enables.
Bitrates can be changed in media_profiles.xml. To reload them, clear the camera out of recent apps.
O+ users should force rebuild of dalvik cache after installing or upgrading: adb shell cmd package compile -m speed -f org.lineageos.snap
P and below should clear Data after upgrading so the Camera name does not get reassigned.
Source Code:
All of my changes can be found at Github:
https://github.com/tomm1e/android_device_samsung_klte-common
https://github.com/tomm1e/android_packages_apps_Snap
https://github.com/tomm1e/android_frameworks_av
Thanks to everyone at LOS and XDA! :good:
-Tom
Why to buy a new phone when we have a huge ,great support for our old S5 ,with Dev's like you ?
S5 Resurrected!
This is great! Im gonna test it
Does it works with Klte?
razor17 said:
Does it works with Klte?
Click to expand...
Click to collapse
Duh.. Read the op.
Sent from my SM-G900V using XDA Labs
Tested on klte + dotOS 2.3, does not work:
06-26 22:14:06.422 470 3336 I ActivityManager: Start proc 17888rg.lineageos.snap/u0a26 for activity org.lineageos.snap/com.android.camera.CameraActivity
06-26 22:14:06.406 1430 1566 W OpenGLRenderer: Incorrectly called buildLayer on View: ShortcutAndWidgetContainer, destroying layer...
06-26 22:14:06.473 470 8663 I OpenGLRenderer: Initialized EGL, version 1.4
06-26 22:14:06.473 470 8663 D OpenGLRenderer: Swap behavior 1
06-26 22:14:06.487 470 8663 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
06-26 22:14:06.530 470 707 W AppOps : Finishing op nesting under-run: uid 1000 pkg android code 24 time=0 duration=0 nesting=0
06-26 22:14:06.563 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile field:QUALITY_VGA
06-26 22:14:06.563 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile QUALITY_VGA
06-26 22:14:06.565 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile field:QUALITY_4KDCI
06-26 22:14:06.565 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile QUALITY_4KDCI
06-26 22:14:06.565 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile field:QUALITY_TIME_LAPSE_VGA
06-26 22:14:06.565 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile QUALITY_TIME_LAPSE_VGA
06-26 22:14:06.565 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile field:QUALITY_TIME_LAPSE_4KDCI
06-26 22:14:06.565 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile QUALITY_TIME_LAPSE_4KDCI
06-26 22:14:06.565 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile field:QUALITY_HIGH_SPEED_CIF
06-26 22:14:06.565 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile QUALITY_HIGH_SPEED_CIF
06-26 22:14:06.565 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile field:QUALITY_HIGH_SPEED_VGA
06-26 22:14:06.565 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile QUALITY_HIGH_SPEED_VGA
06-26 22:14:06.565 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile field:QUALITY_HIGH_SPEED_4KDCI
06-26 22:14:06.565 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile QUALITY_HIGH_SPEED_4KDCI
06-26 22:14:06.566 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile field:QUALITY_QHD
06-26 22:14:06.566 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile QUALITY_QHD
06-26 22:14:06.566 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile field:QUALITY_2k
06-26 22:14:06.566 17888 17888 D Wrapper : getField:class android.media.CamcorderProfile QUALITY_2k
06-26 22:14:06.569 377 822 W QCamera2Factory: getCameraInfo: E, camera_id = 0
06-26 22:14:06.569 377 822 W QCamera2HWI: __dbg: info->orientation : 90 rc = 0
06-26 22:14:06.569 377 822 W QCamera2Factory: getCameraInfo: X
06-26 22:14:06.570 377 5565 W QCamera2Factory: getCameraInfo: E, camera_id = 1
06-26 22:14:06.570 377 5565 W QCamera2HWI: __dbg: info->orientation : 90 rc = 0
06-26 22:14:06.570 377 5565 W QCamera2HWI: __dbg: info->orientation : 270 rc = 0
06-26 22:14:06.570 377 5565 W QCamera2Factory: getCameraInfo: X
06-26 22:14:06.571 17888 17888 I CameraManagerGlobal: Connecting to camera service
06-26 22:14:06.574 377 822 W QCamera2Factory: getCameraInfo: E, camera_id = 0
06-26 22:14:06.574 377 822 W QCamera2HWI: __dbg: info->orientation : 90 rc = 0
06-26 22:14:06.574 377 822 W QCamera2Factory: getCameraInfo: X
06-26 22:14:06.594 17888 17888 D SnapCam_SettingsManager: cameraIdList size =2
06-26 22:14:06.601 377 377 W QCamera2Factory: getCameraInfo: E, camera_id = 1
06-26 22:14:06.601 377 377 W QCamera2HWI: __dbg: info->orientation : 90 rc = 0
06-26 22:14:06.601 377 377 W QCamera2HWI: __dbg: info->orientation : 270 rc = 0
06-26 22:14:06.601 377 377 W QCamera2Factory: getCameraInfo: X
06-26 22:14:06.608 17888 17888 D SnapCam_SettingsManager: cameraIdList size =2
06-26 22:14:06.613 17888 17888 W ResourceType: No known package when getting value for resource number 0x3f080009
06-26 22:14:06.614 17888 17888 D AndroidRuntime: Shutting down VM
06-26 22:14:06.614 17888 17888 E AndroidRuntime: FATAL EXCEPTION: main
06-26 22:14:06.614 17888 17888 E AndroidRuntime: Process: org.lineageos.snap, PID: 17888
06-26 22:14:06.614 17888 17888 E AndroidRuntime: java.lang.RuntimeException: Unable to create application com.android.camera.app.CameraApp: android.content.res.Resources$NotFoundException: Resource ID #0x3f080009
06-26 22:14:06.614 17888 17888 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5774)
06-26 22:14:06.614 17888 17888 E AndroidRuntime: at android.app.ActivityThread.-wrap1(Unknown Source:0)
06-26 22:14:06.614 17888 17888 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1673)
06-26 22:14:06.614 17888 17888 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
06-26 22:14:06.614 17888 17888 E AndroidRuntime: at android.os.Looper.loop(Looper.java:164)
06-26 22:14:06.614 17888 17888 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6525)
06-26 22:14:06.614 17888 17888 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
06-26 22:14:06.614 17888 17888 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:440)
06-26 22:14:06.614 17888 17888 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
06-26 22:14:06.614 17888 17888 E AndroidRuntime: Caused by: android.content.res.Resources$NotFoundException: Resource ID #0x3f080009
06-26 22:14:06.614 17888 17888 E AndroidRuntime: at android.content.res.ResourcesImpl.getValue(ResourcesImpl.java:215)
06-26 22:14:06.614 17888 17888 E AndroidRuntime: at android.content.res.Resources.getInteger(Resources.java:1083)
06-26 22:14:06.614 17888 17888 E AndroidRuntime: at com.android.camera.util.CameraUtil.initialize(CameraUtil.java:247)
06-26 22:14:06.614 17888 17888 E AndroidRuntime: at com.android.camera.app.CameraApp.onCreate(CameraApp.java:47)
06-26 22:14:06.614 17888 17888 E AndroidRuntime: at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1119)
06-26 22:14:06.614 17888 17888 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5771)
06-26 22:14:06.614 17888 17888 E AndroidRuntime: ... 8 more
06-26 22:14:06.616 470 2724 W ActivityManager: Force finishing activity org.lineageos.snap/com.android.camera.CameraActivity
06-26 22:14:06.622 470 486 I ActivityManager: Showing crash dialog for package org.lineageos.snap u0
06-26 22:14:06.656 470 8663 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
06-26 22:14:06.661 470 8663 D vndksupport: Loading /vendor/lib/hw/gralloc.msm8974.so from current namespace instead of sphal namespace.
06-26 22:14:07.119 470 485 W ActivityManager: Activity pause timeout for ActivityRecord{3c30b0 u0 org.lineageos.snap/com.android.camera.CameraActivity t5012 f}
06-26 22:14:07.155 1519 8622 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
06-26 22:14:07.170 1519 8622 D vndksupport: Loading /vendor/lib/hw/gralloc.msm8974.so from current namespace instead of sphal namespace.
06-26 22:14:07.173 1430 1566 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
06-26 22:14:07.186 1430 1566 D vndksupport: Loading /vendor/lib/hw/gralloc.msm8974.so from current namespace instead of sphal namespace.
06-26 22:14:07.203 1430 1566 W OpenGLRenderer: Incorrectly called buildLayer on View: ShortcutAndWidgetContainer, destroying layer...
06-26 22:14:07.203 1430 1566 W OpenGLRenderer: Incorrectly called buildLayer on View: ShortcutAndWidgetContainer, destroying layer...
06-26 22:14:07.210 1519 1519 W StaticLayout: maxLineHeight should not be -1. maxLines:2 lineCount:2
06-26 22:14:07.237 470 2724 W ActivityManager: Force finishing activity org.lineageos.snap/com.android.camera.CameraActivity
06-26 22:14:07.227 1519 1519 I chatty : uid=10040 com.google.android.googlequicksearchbox:search identical 6 lines
Inviato dal mio SM-G900F utilizzando Tapatalk
cinghio71 said:
Tested on klte + dotOS 2.3, does not work
No known package when getting value for resource number 0x3f080009
Click to expand...
Click to collapse
Ok, that error comes from a request to LineageOS 15.1 resources, I removed that request and recompiled it, try this version:
https://drive.google.com/file/d/1VVColk1q8D7_bM48QXo7hjDrB12pDolr/view?usp=sharing
Let me know if it works
socialentry said:
Ok, that error comes from a request to LineageOS 15.1 resources, I removed that request and recompiled it, try this version:
https://drive.google.com/file/d/1VVColk1q8D7_bM48QXo7hjDrB12pDolr/view?usp=sharing
Let me know if it works
Click to expand...
Click to collapse
G900F AEX v5.6 works like a charm ,test video record 720p/120fps slow motion ,perfect .
The Camera name changed to "enable" ,can you change to default name "Camera".
Thanks ! :good:
Edit :screenshot is set to 1080p ,just to show the active slow motion FPS .
Bosket said:
G900F AEX v5.6 works like a charm ,test video record 720p/120fps slow motion ,perfect .
The Camera name changed to "enable" ,can you change to default name "Camera".
Thanks ! :good:
Edit :screenshot is set to 1080p ,just to show the active slow motion FPS .
Click to expand...
Click to collapse
Awesome, does the High Speed work as well?
I'll look into that app name problem
Tested on lineage 15.1 klte build (SM-G900P model)
Everything works well, one bug i noticed was it doesn't work without flash, its not concerning but I'd like to point it out as a bug.
But I'd like to personally thank you so much for working on this mod as 60fps recording was one of the reasons I switched back and forth from AOSP to stock as I use this feature alot, I'm happy to know awesome devs like you are finally working on this, I wish you all the best with this project and I will keep testing and report back accordingly
rulex231 said:
Tested on lineage 15.1 klte build (SM-G900P model)
Everything works well, one bug i noticed was it doesn't work without flash, its not concerning but I'd like to point it out as a bug.
But I'd like to personally thank you so much for working on this mod as 60fps recording was one of the reasons I switched back and forth from AOSP to stock as I use this feature alot, I'm happy to know awesome devs like you are finally working on this, I wish you all the best with this project and I will keep testing and report back accordingly
Click to expand...
Click to collapse
Thank you!
With flash or without? I noticed it turned the torch off once recording starts, for now I made it so torch turns back on if it was set. New links in the OP. More changes are needed to properly switch into 60FPS after selecting it from the menu, that way the torch won't turn off.
socialentry said:
Awesome, does the High Speed work as well?
I'll look into that app name problem
Click to expand...
Click to collapse
Yes ,high speed work as well.
Camera name is not a problem ,just a suggestion.
socialentry said:
Ok, that error comes from a request to LineageOS 15.1 resources, I removed that request and recompiled it, try this version:
https://drive.google.com/file/d/1VVColk1q8D7_bM48QXo7hjDrB12pDolr/view?usp=sharing
Let me know if it works
Click to expand...
Click to collapse
Tested, works perfectly. Thanks.
Inviato dal mio SM-G900F utilizzando Tapatalk
Thanks, big biproject.
Does the front camera work?
I have not worked in my klte.
Using a KTLE S5. The front camera doesn't work instead the camera app crashes. Highspeed and Slow-mo both seemed to working great. Would love to see the front camera get fixed. Thanks
Delete
tomm1e said:
Thank you!
With flash or without? I noticed it turned the torch off once recording starts, for now I made it so torch turns back on if it was set. New links in the OP. More changes are needed to properly switch into 60FPS after selecting it from the menu, that way the torch won't turn off.
Click to expand...
Click to collapse
Installed it this morning, works great now thank you, even the front camera works regardless as well.
So, whats the difference between the LOS and Others?? What am asking is, which one should i install in example, Resurrection Remix?? Sorry if its a dumb question, i just thought since RR is based on LOS......
Also, what are the exact bugs?
Ano01 said:
So, whats the difference between the LOS and Others?? What am asking is, which one should i install in example, Resurrection Remix?? Sorry if its a dumb question, i just thought since RR is based on LOS......
Also, what are the exact bugs?
Click to expand...
Click to collapse
I'm not sure if RR uses lineageos resource names, if LOS doesn't work the Others one should work. Only difference in those LOS versions is that Snap requests a resource from LOS configuration during startup, specifically which hardware keys are present for the camera, like home/back/menu, those will crash if you are not on lineageos. Others just keep a default hardware key set so no crash should happen in any android. Future versions will just handle the error, it will go back to one release if it still works across all android builds.
Bugs? Nothing major, currently the flash/torch has to restart when switching into 60fps. Maybe there should be a preference to keep the camera displaying 60fps while recording or not, to save battery. Trying to rewrite the wrapper to do this currently. Some say their front camera isn't working but I think that is only for certain variants, I need their logs to see what's going on.
On my S5 G9008W (kltechnduo), with LOS 15.1, this just makes snap crash.

[T710/T715] LineageOS 15.1 (Experimental stuff)

These are my experimental builds. They are not pretend to be stable and have a lot of issues. Flash it if you know how to restore your tablet from brick. This stuff is not for daily usage. Just for testing and helping me to find bugs.
Feel free to write your feedback about builds.
I will upload roms for t710 and t715 only. Don't ask about t81x roms here please.
if you don't know how to flash recovery or flash rom, this topic is not for you.
compatible twrp:
T710: https://drive.google.com/open?id=1F-RA6OEXpWSJx2LgxsRKum2KoROGrIhd
T715: https://drive.google.com/open?id=1Icux5fPJqxDveYAjvMWASnfUpfWzO4xj
rom:
t710 only: https://drive.google.com/open?id=1-abtJDh5CbnC2ijCoAL8AdVHzP47hfCe
I'm trying to make compatibility with phh gsi builds., but for now I have error with composer. To run his builds is dirty hack: replace /system/lib/libsurcafeflinger*.so two libs from my working build.
sources:
http://github.com/bonuzzz
one more build for today
https://drive.google.com/open?id=1cIV5WN-VZUngamcNCQCNZfHS_BDIMO_W
this universal build for both models (t710 and t715)
modem stuff doesn't work here. I haven't included in config yet, but all sensors should work.
bonuzzz said:
one more build for today
https://drive.google.com/open?id=1cIV5WN-VZUngamcNCQCNZfHS_BDIMO_W
this universal build for both models (t710 and t715)
modem stuff doesn't work here. I haven't included in config yet, but all sensors should work.
Click to expand...
Click to collapse
Hello, thanks for those builds! I've been trying your lineage 15.1 ROM and I think everything is working there already. So I'll start testing these ones now... Is there something in particular you want me to logcat?
Sent from my Aquaris M5 using Tapatalk
So like these build are treble enabled? @ripee and @bonuzzz
mtnez.david said:
Hello, thanks for those builds! I've been trying your lineage 15.1 ROM and I think everything is working there already. So I'll start testing these ones now... Is there something in particular you want me to logcat?
Sent from my Aquaris M5 using Tapatalk
Click to expand...
Click to collapse
if you want something to test, there is new build https://drive.google.com/open?id=1Mu-XjXbskSXzft11onGL3mrY_I1llVKX
bonuzzz said:
if you want something to test, there is new build https://drive.google.com/open?id=1Mu-XjXbskSXzft11onGL3mrY_I1llVKX
Click to expand...
Click to collapse
Downloading again then
Sent from my Aquaris M5 using Tapatalk
mtnez.david said:
Downloading again then
Sent from my Aquaris M5 using Tapatalk
Click to expand...
Click to collapse
Hi, I am getting an error while trying to flash this rom... what does the script /tmp/install/bin/custom_t710.sh test?
mtnez.david said:
Hi, I am getting an error while trying to flash this rom... what does the script /tmp/install/bin/custom_t710.sh test?
Click to expand...
Click to collapse
no. it replaces some parameters in build.prop
will check later
bonuzzz said:
no. it replaces some parameters in build.prop
will check later
Click to expand...
Click to collapse
ok, so you are writing into the /system/build.prop my device atributes (model, device name, stuff ...). I guess you do that there in order to have same build for both t710 and t715, am i right?
---------- Post added at 01:10 PM ---------- Previous post was at 12:51 PM ----------
bonuzzz said:
no. it replaces some parameters in build.prop
will check later
Click to expand...
Click to collapse
So in this line:
sed -i 's/.*ro.build.fingerprint.*/ro.build.fingerprint=samsung/gts28wifixx/gts28wifi:7.0/NRD90M/T710XXU2DRB1:user/release-keys/' /system/build.prop
I suppose you're trying to replace the "ro.build.fingerprint=samsung/lineage ... " with "ro.build.fingerprint=samsung/gts28wifixx/gts28wifi:7.0/NRD90M/T710XXU2DRB1:user/release-keys" but I think sed can not understand that ... don't you have to scape the "/" stuff on your string there?
---------- Post added at 01:21 PM ---------- Previous post was at 01:10 PM ----------
in any case the '/' in the substituting expression crashes, I just tested it
Sent from my Aquaris M5 using Tapatalk
---------- Post added at 01:41 PM ---------- Previous post was at 01:21 PM ----------
mtnez.david said:
ok, so you are writing into the /system/build.prop my device atributes (model, device name, stuff ...). I guess you do that there in order to have same build for both t710 and t715, am i right?
---------- Post added at 01:10 PM ---------- Previous post was at 12:51 PM ----------
So in this line:
sed -i 's/.*ro.build.fingerprint.*/ro.build.fingerprint=samsung/gts28wifixx/gts28wifi:7.0/NRD90M/T710XXU2DRB1:user/release-keys/' /system/build.prop
I suppose you're trying to replace the "ro.build.fingerprint=samsung/lineage ... " with "ro.build.fingerprint=samsung/gts28wifixx/gts28wifi:7.0/NRD90M/T710XXU2DRB1:user/release-keys" but I think sed can not understand that ... don't you have to scape the "/" stuff on your string there?
---------- Post added at 01:21 PM ---------- Previous post was at 01:10 PM ----------
in any case the '/' in the substituting expression crashes, I just tested it
Sent from my Aquaris M5 using Tapatalk
Click to expand...
Click to collapse
So this works:
sed -i 's/.*ro.build.fingerprint.*/ro.build.fingerprint=samsung\/gts28wifixx\/gts28wifi:7.0\/NRD90M\/T710XXU2DRB1:user\/release-keys/' /system/build.prop
sed -i 's/.*ro.vendor.build.fingerprint.*/ro.build.fingerprint=samsung\/gts28wifixx\/gts28wifi:7.0\/NRD90M\/T710XXU2DRB1:user\/release-keys/' /system/vendor/build.prop
mtnez.david said:
ok, so you are writing into the /system/build.prop my device atributes (model, device name, stuff ...). I guess you do that there in order to have same build for both t710 and t715, am i right?
Yes. You're right.
---------- Post added at 01:10 PM ---------- Previous post was at 12:51 PM ----------
So in this line:
sed -i 's/.*ro.build.fingerprint.*/ro.build.fingerprint=samsung/gts28wifixx/gts28wifi:7.0/NRD90M/T710XXU2DRB1:user/release-keys/' /system/build.prop
I suppose you're trying to replace the "ro.build.fingerprint=samsung/lineage ... " with "ro.build.fingerprint=samsung/gts28wifixx/gts28wifi:7.0/NRD90M/T710XXU2DRB1:user/release-keys" but I think sed can not understand that ... don't you have to scape the "/" stuff on your string there?
---------- Post added at 01:21 PM ---------- Previous post was at 01:10 PM ----------
in any case the '/' in the substituting expression crashes, I just tested it
Sent from my Aquaris M5 using Tapatalk
---------- Post added at 01:41 PM ---------- Previous post was at 01:21 PM ----------
So this works:
sed -i 's/.*ro.build.fingerprint.*/ro.build.fingerprint=samsung\/gts28wifixx\/gts28wifi:7.0\/NRD90M\/T710XXU2DRB1:user\/release-keys/' /system/build.prop
sed -i 's/.*ro.vendor.build.fingerprint.*/ro.build.fingerprint=samsung\/gts28wifixx\/gts28wifi:7.0\/NRD90M\/T710XXU2DRB1:user\/release-keys/' /system/vendor/build.prop
Click to expand...
Click to collapse
I haven't checked this script on t710 yet. Working mostly on t715 tablet. Thanks for fix.
bonuzzz said:
I haven't checked this script on t710 yet. Working mostly on t715 tablet. Thanks for fix.
Click to expand...
Click to collapse
You're welcome, that's what this thread is about ... :good:
new build with fixed install script for t710 and some more things. one issue with lock screen (mobicore/keystore stuff) left. at least what I know
https://drive.google.com/open?id=1Uk3YISTssJ9h2-C8-K-XwlpGP3tpyMnk
Ok, im installing it real quick
bonuzzz said:
new build with fixed install script for t710 and some more things. one issue with lock screen (mobicore/keystore stuff) left. at least what I know
https://drive.google.com/open?id=1Uk3YISTssJ9h2-C8-K-XwlpGP3tpyMnk
Click to expand...
Click to collapse
Enviado desde mi Aquaris M5 mediante Tapatalk
---------- Post added at 10:46 PM ---------- Previous post was at 10:02 PM ----------
fingerprint settings is crashing:
Code:
08-04 00:50:45.441 7591 7591 E AndroidRuntime: FATAL EXCEPTION: main
08-04 00:50:45.441 7591 7591 E AndroidRuntime: Process: com.android.settings, PID: 7591
08-04 00:50:45.441 7591 7591 E AndroidRuntime: java.lang.RuntimeException: Failure delivering result ResultInfo{who=android:fragment:0, request=100, result=-1, data=null} to activity {com.android.settings/com.android.settings.password.ChooseLockGeneric}: java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String android.content.Intent.getStringExtra(java.lang.String)' on a null object reference
08-04 00:50:45.441 7591 7591 E AndroidRuntime: at android.app.ActivityThread.deliverResults(ActivityThread.java:4268)
08-04 00:50:45.441 7591 7591 E AndroidRuntime: at android.app.ActivityThread.handleSendResult(ActivityThread.java:4312)
08-04 00:50:45.441 7591 7591 E AndroidRuntime: at android.app.ActivityThread.-wrap19(Unknown Source:0)
08-04 00:50:45.441 7591 7591 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1644)
08-04 00:50:45.441 7591 7591 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
08-04 00:50:45.441 7591 7591 E AndroidRuntime: at android.os.Looper.loop(Looper.java:164)
08-04 00:50:45.441 7591 7591 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6494)
08-04 00:50:45.441 7591 7591 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
08-04 00:50:45.441 7591 7591 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:440)
08-04 00:50:45.441 7591 7591 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
08-04 00:50:45.441 7591 7591 E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String android.content.Intent.getStringExtra(java.lang.String)' on a null object reference
08-04 00:50:45.441 7591 7591 E AndroidRuntime: at com.android.settings.password.ChooseLockGeneric$ChooseLockGenericFragment.onActivityResult(ChooseLockGeneric.java:344)
08-04 00:50:45.441 7591 7591 E AndroidRuntime: at android.app.Activity.dispatchActivityResult(Activity.java:7303)
08-04 00:50:45.441 7591 7591 E AndroidRuntime: at android.app.ActivityThread.deliverResults(ActivityThread.java:4264)
08-04 00:50:45.441 7591 7591 E AndroidRuntime: ... 9 more
08-04 00:50:45.448 3604 4687 W ActivityManager: Force finishing activity com.android.settings/.password.ChooseLockGeneric
08-04 00:50:45.458 3604 4687 W ActivityManager: Force finishing activity com.android.settings/.fingerprint.FingerprintEnrollIntroduction
08-04 00:50:45.466 3604 3620 I ActivityManager: Showing crash dialog for package com.android.settings u0
---------- Post added at 10:59 PM ---------- Previous post was at 10:46 PM ----------
screen lock as well:
Code:
08-04 00:57:44.415 4955 4955 D SubSettings: Launching fragment com.android.settings.password.ChooseLockGeneric$ChooseLockGenericFragment
08-04 00:57:44.423 3594 3786 I ActivityManager: START u0 {cmp=com.android.settings/.password.ConfirmLockPattern$InternalActivity (has extras)} from uid 1000
08-04 00:57:44.457 4955 5043 W TileUtils: Found com.android.settings.backup.BackupSettingsActivity for intent Intent { act=com.android.settings.action.SETTINGS pkg=com.android.settings } missing metadata com.android.settings.category
08-04 00:57:44.460 4955 5043 W TileUtils: Found org.lineageos.lineageparts.trust.TrustPreferences for intent Intent { act=org.lineageos.lineageparts.action.SETTINGS pkg=org.lineageos.lineageparts } missing metadata
08-04 00:57:44.474 4955 4979 D mali_winsys: EGLint new_window_surface(egl_winsys_display*, void*, EGLSurface, EGLConfig, egl_winsys_surface**, egl_color_buffer_format*, EGLBoolean) returns 0x3000, [1536x2048]-format:1
08-04 00:57:44.474 4955 4955 E RecyclerView: No adapter attached; skipping layout
08-04 00:57:44.476 4955 5044 D Settings: No enabled state changed, skipping updateCategory call
08-04 00:57:44.643 4955 4955 D AndroidRuntime: Shutting down VM
--------- beginning of crash
08-04 00:57:44.643 4955 4955 E AndroidRuntime: FATAL EXCEPTION: main
08-04 00:57:44.643 4955 4955 E AndroidRuntime: Process: com.android.settings, PID: 4955
08-04 00:57:44.643 4955 4955 E AndroidRuntime: java.lang.RuntimeException: Failure delivering result ResultInfo{who=android:fragment:0, request=100, result=-1, data=null} to activity {com.android.settings/com.android.settings.SubSettings}: java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String android.content.Intent.getStringExtra(java.lang.String)' on a null object reference
08-04 00:57:44.643 4955 4955 E AndroidRuntime: at android.app.ActivityThread.deliverResults(ActivityThread.java:4268)
08-04 00:57:44.643 4955 4955 E AndroidRuntime: at android.app.ActivityThread.handleSendResult(ActivityThread.java:4312)
08-04 00:57:44.643 4955 4955 E AndroidRuntime: at android.app.ActivityThread.-wrap19(Unknown Source:0)
08-04 00:57:44.643 4955 4955 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1644)
08-04 00:57:44.643 4955 4955 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
08-04 00:57:44.643 4955 4955 E AndroidRuntime: at android.os.Looper.loop(Looper.java:164)
08-04 00:57:44.643 4955 4955 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6494)
08-04 00:57:44.643 4955 4955 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
08-04 00:57:44.643 4955 4955 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:440)
08-04 00:57:44.643 4955 4955 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
08-04 00:57:44.643 4955 4955 E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String android.content.Intent.getStringExtra(java.lang.String)' on a null object reference
08-04 00:57:44.643 4955 4955 E AndroidRuntime: at com.android.settings.password.ChooseLockGeneric$ChooseLockGenericFragment.onActivityResult(ChooseLockGeneric.java:344)
08-04 00:57:44.643 4955 4955 E AndroidRuntime: at android.app.Activity.dispatchActivityResult(Activity.java:7303)
08-04 00:57:44.643 4955 4955 E AndroidRuntime: at android.app.ActivityThread.deliverResults(ActivityThread.java:4264)
08-04 00:57:44.643 4955 4955 E AndroidRuntime: ... 9 more
08-04 00:57:44.647 3594 3786 W ActivityManager: Force finishing activity com.android.settings/.SubSettings
08-04 00:57:44.651 3594 3786 W ActivityManager: Force finishing activity com.android.settings/.Settings$SecuritySettingsActivity
08-04 00:57:44.661 3594 3610 I ActivityManager: Showing crash dialog for package com.android.settings u0
@mtnez.david I said about it in previous message
I confirm it then. I'll see if I find something else
Enviado desde mi Aquaris M5 mediante Tapatalk
today's build
https://drive.google.com/open?id=1yJQ8Pu1VnZddFr7YMeX9n7NQ_M5DkBE6
I haven't got any crash today in today's build, I've been installing apps, not games, all seem to work properly. I could install nexflix from play store but I got the apk and it works fine.
Is there something specific that is supposed not to work?
Sent from my Aquaris M5 using Tapatalk
@mtnez.david no. everything should work
Is it supposed to be treble enabled?
Sent from my SM-T710 using Tapatalk
@mtnez.david no, only build in first post was treble enabled. I have broken camera and I don't want to upload new builds until I fix it. But I'm not even sure I will fix it.

Development [ROM][UNOFFICIAL][13][RMX3085/nashc] LineageOS 20 for Realme 8

{
"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 a free, community built, aftermarket firmware distribution of Android 13, which is designed to increase performance and reliability over stock Android for your device.
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 the Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Code:
/*
* Your warranty is 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 the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
Instructions:
Unlock the bootloader with the guide mentioned later in this post
Ensure the device is running the RealmeUI 3 C.17 Firmware
Flash the included LineageOS recovery using fastboot
Reboot to recovery mode
Wipe system, data and cache
Flash the ROM and the Gapps
Reboot and enjoy!
Downloads:
Builds: ROM/Recovery
GApps: MindTheGapps (Lineage 20 ARM64)
Reporting Bugs:
DO NOT Report bugs if you're running a custom kernel, flashed the ROM without using Lineage Recovery or you installed Xposed/Zygisk modules
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Known issues:
Auto Brightness can be a bit buggy.
You tell me.
Notes:
RealmeUI 3 C.17 firmware is required.
The ROM supports all regional variants of the Realme 8 (RMX3085)
Do not ask for ETAs
How do i...
Unlock?
Follow the instructions of the unlock thread
Reporting Bugs
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with any backup apps:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
magisk modules (list them here):
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Contributors
@TheMalachite, @Rortiz2, @TechyMinati
Source Code
Device Tree: Here
Kernel Tree: Here
Previous Builds
Spoiler: Previous Builds
Build 1
- Initial stable build
Download
Current Build (Build 2)
Code:
- Updated and synced with latest Lineage 20 sources
- Update Android Security Patch to 5 May 2023
- Update Vendor Security Patch to 5 April 2023 (C.17 blobs)
- Merge latest android-4.14-stable into kernel (4.14.317)
- Add WireGuard support
- Implement ALS compensation algorithm (should help with auto brightness stability but no guarantees)
- Massive kernel debloat, removed a bunch of useless oplus features and code
- Fix fingerprint for some Goodix sensors
- Switch to OSS Memtrack HAL
- Switch to OSS GNSS service
- Switch to OSS USB HAL
- Switch to OSS Wi-Fi HAL
- Rework brightness implementation
- Rework screen-off gesture handling
- LiveDisplay HBM improvements (brightness cannot be adjusted until HBM is turned off)
- Cleaned up init scripts
- Disable/Remove useless MTK debugging tools
- Drop unneeded Dirac blobs
- Drop uneeded ADSP/CDSP blobs
- Switch to backported exFAT driver from Linux 6.0
- Switch to stock ext4 driver from ALPS 12 kernel-4.14
- Switch to skiaglthreaded rendering backend
- Resolve some more IMS crashes
- Support blur rendering in UI
- Add boosts for blur rendering in UI
- Intensify app launching boosts
- Improve PowerHAL hint handling
- Fix random PowerHAL crashes (observed as random 2-4 second hangs in UI)
- Enable Wi-Fi dual interface (Wi-Fi and Hotspot at the same time)
- Change reserved partition sizes for GApps install.
- Fix USB OTG
- Apply patch for Mali exploit CVE-2022-20186
- Fix GPS crashes
- Implement Lineage charging control
Download
Notes
- Recommended firmware has changed to C.17, please flash C.17 before updating!
- Please make sure you reflash the GApps package BEFORE YOU REBOOT INTO SYSTEM.
Reserved #3
Fingerprint is not working.
What should i do ?
kdwivedi said:
Fingerprint is not working.
What should i do ?
Click to expand...
Click to collapse
It doesn't work for me either
The custom rom is really amazing, thank you for your job. I wonder if the fingerprint sensor could be fixed.
kdwivedi said:
Fingerprint is not working.
What should i do ?
Click to expand...
Click to collapse
Medzik said:
It doesn't work for me either
Click to expand...
Click to collapse
Kilo_Eurocorp said:
The custom rom is really amazing, thank you for your job. I wonder if the fingerprint sensor could be fixed.
Click to expand...
Click to collapse
Hey, it's kind of weird that you all seem to be having issues with the fingerprint reader. First of all, avoid using the "Extra Dim" feature as that does stop the fingerprint reader from working. If that doesn't resolve it, can you please install "Device Info HW" app from the play store and check what fingerprint sensor you have? It should either be "goodix_fp" or "anc_mtk". If you have the "goodix_fp" please also attach a logcat from when the device is booting up to when you try to enrol the fingerprint.
bengris32 said:
Hey, it's kind of weird that you all seem to be having issues with the fingerprint reader. First of all, avoid using the "Extra Dim" feature as that does stop the fingerprint reader from working. If that doesn't resolve it, can you please install "Device Info HW" app from the play store and check what fingerprint sensor you have? It should either be "goodix_fp" or "anc_mtk". If you have the "goodix_fp" please also attach a logcat from when the device is booting up to when you try to enrol the fingerprint.
Click to expand...
Click to collapse
I have goodix_fp
my logcat: https://pastebin.com/raw/7TqxX82y (sorry for such a one but I did it with termux, then I can do it from the computer because I currently do not have access)
bengris32 said:
Hey, it's kind of weird that you all seem to be having issues with the fingerprint reader. First of all, avoid using the "Extra Dim" feature as that does stop the fingerprint reader from working. If that doesn't resolve it, can you please install "Device Info HW" app from the play store and check what fingerprint sensor you have? It should either be "goodix_fp" or "anc_mtk". If you have the "goodix_fp" please also attach a logcat from when the device is booting up to when you try to enrol the fingerprint.
Click to expand...
Click to collapse
Device info HW indeed report goofix_fp as the sensor on my device. I don't have extra fim feature active. Here are the logcat files, the first one is for boot and the second one is for the registration of the fingerprint ( I opened settings, security and tried to register my fingerprint). The log files I think are filled with junk from other things running but I don't know how to filter them out.
Kilo_Eurocorp said:
Device info HW indeed report goofix_fp as the sensor on my device. I don't have extra fim feature active. Here are the logcat files, the first one is for boot and the second one is for the registration of the fingerprint ( I opened settings, security and tried to register my fingerprint). The log files I think are filled with junk from other things running but I don't know how to filter them out.
Click to expand...
Click to collapse
Here is a more stripped down log of what is happepening during the registration process of the fingerprint:
01-23 16:34:55.345 1411 1611 I ActivityTaskManager: START u0 {cmp=com.android.settings/.biometrics.fingerprint.FingerprintEnrollEnrolling (has extras)} from uid 1000
01-23 16:34:55.348 27492 27510 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:55.352 1411 7393 W ActivityTaskManager: Tried to set launchTime (0) < mLastActivityLaunchTime (8155215)
01-23 16:34:55.360 27492 27492 I SetupLibrary: [ThemeHelper] Return SudFullDynamicColorTheme_DayNight
01-23 16:34:55.362 27492 27510 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:55.363 27492 29205 D libMEOW : meow new tls: 0xb400007a3b7bc220
01-23 16:34:55.363 27492 29205 D libMEOW : applied 1 plugins for [com.android.settings]:
01-23 16:34:55.363 27492 29205 D libMEOW : plugin 1: [libMEOW_gift.so]: 0xb4000079fb5b9840
01-23 16:34:55.363 27492 29205 D libMEOW : rebuild call chain: 0xb400007a3b94c3b0
01-23 16:34:55.363 27492 29205 D libMEOW : meow delete tls: 0xb400007a3b7bc220
01-23 16:34:55.365 810 810 I Accelerometer: batch: handle:0, flag:0,samplingPeriodNs:80000000 maxBatchReportLatencyNs:0
01-23 16:34:55.366 810 810 I Accelerometer: flush, flushCnt:1
01-23 16:34:55.377 27492 27510 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:55.379 27492 27492 D FingerprintEnrollEnrolling: Enrollment not started yet
01-23 16:34:55.380 810 887 I Accelerometer: flush complete, flushCnt:0
01-23 16:34:55.385 1411 1611 D CoreBackPreview: Window{6a80f8e u0 com.android.settings/com.android.settings.biometrics.fingerprint.FingerprintEnrollEnrolling}: Setting back callback OnBackInvokedCallbackInfo{[email protected]bc, mPriority=-1}
01-23 16:34:55.396 27492 27510 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:55.396 27492 27510 E OpenGLRenderer: Unable to match the desired swap behavior.
01-23 16:34:55.400 27492 27510 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:55.401 27492 27510 W Parcel : Expecting binder but got null!
01-23 16:34:55.406 1411 1515 I ActivityTaskManager: Displayed com.android.settings/.biometrics.fingerprint.FingerprintEnrollEnrolling: +60ms
01-23 16:34:55.409 27492 27510 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:55.411 27492 27510 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:55.426 27492 27510 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:55.428 27492 27510 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:55.429 2531 2531 I GoogleInputMethodService: GoogleInputMethodService.onFinishInput():3227
01-23 16:34:55.430 2531 2531 I GoogleInputMethodService: GoogleInputMethodService.updateDeviceLockedStatus():2087 repeatCheckTimes = 0, unlocked = true
01-23 16:34:55.431 2531 2531 I GoogleInputMethodService: GoogleInputMethodService.onStartInput():1877 onStartInput(EditorInfo{inputType=0x0(NULL) imeOptions=0x0 privateImeOptions=null actionName=UNSPECIFIED actionLabel=null actionId=0 initialSelStart=-1 initialSelEnd=-1 initialCapsMode=0x0 hintText=null label=null packageName=com.android.settings fieldId=-1 fieldName=null extras=null}, false)
01-23 16:34:55.431 2531 2531 I GoogleInputMethodService: GoogleInputMethodService.shouldHideHeaderOnInitialState():4008 ShouldHideHeaderOnInitialState = false
01-23 16:34:55.432 2531 2531 I GoogleInputMethodService: GoogleInputMethodService.updateDeviceLockedStatus():2087 repeatCheckTimes = 2, unlocked = true
01-23 16:34:55.440 27492 27510 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:55.446 27492 27510 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:55.455 27492 27510 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:55.461 27492 27510 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:55.475 27492 27510 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:55.476 27492 27510 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:55.492 27492 27510 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:55.494 27492 27510 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:55.510 27492 27510 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:55.512 27492 27510 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:55.526 27492 27510 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:55.543 27492 27510 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:55.559 27492 27510 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:55.576 27492 27510 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:55.591 27492 27510 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:55.609 27492 27510 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:55.628 27492 27510 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:55.635 27492 27510 D OpenGLRenderer: endAllActiveAnimators on 0xb40000794b614fe0 (InsetDrawable) with handle 0xb40000785b6579a0
01-23 16:34:55.648 1411 1411 D BiometricScheduler/Fingerprint21: [Added] {[31] com.android.server.biometrics.sensors.fingerprint.hidl.FingerprintUpdateActiveUserClient, proto=1, owner=android, cookie=0, requestId=-1, userId=0}, new queue size: 1
01-23 16:34:55.648 1411 1411 D BiometricScheduler/Fingerprint21: [Polled] {[31] com.android.server.biometrics.sensors.fingerprint.hidl.FingerprintUpdateActiveUserClient, proto=1, owner=android, cookie=0, requestId=-1, userId=0}, State: 0
01-23 16:34:55.648 1411 1411 D BiometricScheduler/Fingerprint21: [Started] {[31] com.android.server.biometrics.sensors.fingerprint.hidl.FingerprintUpdateActiveUserClient, proto=1, owner=android, cookie=0, requestId=-1, userId=0}
01-23 16:34:55.648 1411 1411 D FingerprintUpdateActiveUserClient: Already user: com.android.server.biometrics.s[email protected]ece22d8, returning
01-23 16:34:55.648 1411 1411 D BiometricSchedulerOperation: [Finished / destroy]: {[31] com.android.server.biometrics.sensors.fingerprint.hidl.FingerprintUpdateActiveUserClient, proto=1, owner=android, cookie=0, requestId=-1, userId=0}
01-23 16:34:55.648 1411 1411 V BiometricSchedulerOperation: started: {[31] com.android.server.biometrics.sensors.fingerprint.hidl.FingerprintUpdateActiveUserClient, proto=1, owner=android, cookie=0, requestId=-1, userId=0}, State: 5
01-23 16:34:55.648 1411 1411 D BiometricScheduler/Fingerprint21: [Added] {[32] com.android.server.biometrics.sensors.fingerprint.hidl.FingerprintEnrollClient, proto=2, owner=com.android.settings, cookie=0, requestId=10, userId=0}, new queue size: 1
01-23 16:34:55.648 1411 1411 V BiometricScheduler/Fingerprint21: Not idle, current operation: {[31] com.android.server.biometrics.sensors.fingerprint.hidl.FingerprintUpdateActiveUserClient, proto=1, owner=android, cookie=0, requestId=-1, userId=0}, State: 5
01-23 16:34:55.648 1411 1411 D BiometricScheduler/Fingerprint21: [Finishing] {[31] com.android.server.biometrics.sensors.fingerprint.hidl.FingerprintUpdateActiveUserClient, proto=1, owner=android, cookie=0, requestId=-1, userId=0}, success: true
01-23 16:34:55.648 1411 1411 D BiometricScheduler/Fingerprint21: [Polled] {[32] com.android.server.biometrics.sensors.fingerprint.hidl.FingerprintEnrollClient, proto=2, owner=com.android.settings, cookie=0, requestId=10, userId=0}, State: 0
01-23 16:34:55.649 1411 1411 D GestureAvailabilityTracker: Notifying gesture availability, active=false
01-23 16:34:55.649 810 810 I WiseLight: batch: handle:90, flag:0,samplingPeriodNs:200000000 maxBatchReportLatencyNs:0
01-23 16:34:55.651 1411 1411 V ALSProbe: Enable ALS: 68047126
01-23 16:34:55.651 1411 1411 D BiometricScheduler/Fingerprint21: [Started] {[32] com.android.server.biometrics.sensors.fingerprint.hidl.FingerprintEnrollClient, proto=2, owner=com.android.settings, cookie=0, requestId=10, userId=0}
01-23 16:34:55.651 1411 1411 D BiometricStateCallback: State updated from 0 to 1, client {[32] com.android.server.biometrics.sensors.fingerprint.hidl.FingerprintEnrollClient, proto=2, owner=com.android.settings, cookie=0, requestId=10, userId=0}
01-23 16:34:55.653 1157 1157 D [email protected]: OpticalFingerprint enroll
01-23 16:34:55.653 1157 1157 E [GF_HAL][FingerprintCore]: [enroll] gid : 0.
01-23 16:34:55.653 1157 1157 E [GF_HAL][SZFingerprintCore]: [prepareEnrollRequest] spmt is not pass, please to do the process of spmt
01-23 16:34:55.653 1157 1157 E [GF_HAL][FingerprintCore]: [enroll] exit. err=GF_ERROR_CANCELED, errno=1008
01-23 16:34:55.653 1157 1157 E [email protected]: An unknown error returned from fingerprint vendor library: 1008
01-23 16:34:55.653 1411 1411 V BiometricSchedulerOperation: started: {[32] com.android.server.biometrics.sensors.fingerprint.hidl.FingerprintEnrollClient, proto=2, owner=com.android.settings, cookie=0, requestId=10, userId=0}, State: 2
01-23 16:34:55.654 1721 1721 V UdfpsEnrollHelper: Using old coordinates
01-23 16:34:55.665 1411 7393 D CoreBackPreview: Window{1668a2 u0 UdfpsControllerOverlay}: Setting back callback OnBackInvokedCallbackInfo{[email protected]f0, mPriority=0}
01-23 16:34:55.667 1721 1721 V UdfpsController: showUdfpsOverlay | adding window reason=2
01-23 16:34:55.668 1721 1721 V UdfpsView: onAttachedToWindow
01-23 16:34:55.675 1721 1920 E OpenGLRenderer: Unable to match the desired swap behavior.
01-23 16:34:55.681 1721 1920 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:55.682 1721 1920 W Parcel : Expecting binder but got null!
01-23 16:34:56.008 805 1002 I hwcomposer: [HWC] (0)fire a callback of refresh to SF[4]
01-23 16:34:56.033 872 872 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:56.176 1411 1411 W AccessibilityManagerService: wait for adding window timeout: 246
01-23 16:34:56.188 1721 1721 V UdfpsController: onTouch | action down
01-23 16:34:56.255 1157 1157 D [email protected]: onFingerDown
01-23 16:34:56.255 1157 1157 E [GF_HAL][FingerprintCore]: [touchdown]in
01-23 16:34:56.255 1157 1157 E [GF_HAL][FingerprintCore]: [set_hypnus] entry, action_type is 12, action_timeout is 500
01-23 16:34:56.255 1157 1157 D [email protected]: hypnusdSetAction(type=12, timeout=500)
01-23 16:34:56.255 1157 1157 I [email protected]: fingerprint try to acquire orms hal client !!!
01-23 16:34:56.256 542 542 I hwservicemanager: getTransport: Cannot find entry [email protected]::IOrmsHalProxy/ORMS_HAL_PROXY in either framework or device VINTF manifest.
01-23 16:34:56.256 1157 1157 D OrmsHalClient: Unable to get Orms Hal Service!
01-23 16:34:56.256 1157 1157 D OrmsHalClient: OrmsHalClient connect Orms_Hal_Proxy failed!
01-23 16:34:56.256 542 542 I hwservicemanager: getTransport: Cannot find entry [email protected]::IOrmsHalProxy/ORMS_HAL_PROXY in either framework or device VINTF manifest.
01-23 16:34:56.256 1157 1157 D OrmsHalClient: Unable to get Orms Hal Service!
01-23 16:34:56.256 1157 1157 D OrmsHalClient: OrmsHalClient check access permission failed!
01-23 16:34:56.256 1157 1157 D OrmsHalClient: get orms hal client instance failed
01-23 16:34:56.256 1157 1157 W RefBase : RefBase: Explicit destruction, weak count = 0 (in 0xb400007d708c3450). Use sp<> to manage this object.
01-23 16:34:56.257 1157 1157 W RefBase : CallStack::getCurrentInternal not linked, returning null
01-23 16:34:56.257 1157 1157 W RefBase : CallStack::logStackInternal not linked
01-23 16:34:56.257 1157 1157 E [email protected]: fingerprint orms setAction fail
01-23 16:34:56.263 1721 1721 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:56.263 1721 1721 V UdfpsController: onTouch | finger down: minor: 12,0, major: 12,0, v: 0,0, exceedsVelocityThreshold: false
01-23 16:34:56.271 1721 1920 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:56.274 1721 1920 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:56.283 872 872 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:56.303 872 872 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:56.320 872 872 E gralloc4: Empty SMPTE 2094-40 data
01-23 16:34:56.417 1721 1721 V UdfpsController: onTouch | finger move: minor: 13,0, major: 13,0, v: 0,0, exceedsVelocityThreshold: false
01-23 16:34:56.463 1721 1721 V UdfpsController: onTouch | finger up
01-23 16:34:56.465 1721 1721 E BufferQueueProducer: [SurfaceView[UdfpsControllerOverlay]#164(BLAST Consumer)164](id:6b9000000a4,api:0,p:-1,c:1721) disconnect: not connected (req=2)
01-23 16:34:56.465 1157 1157 D [email protected]: onFingerUp
01-23 16:34:56.465 1157 1157 E [GF_HAL][FingerprintCore]: [touchup] in
Hey all, I have found the issues which are causing fingerprint to not work, and a new build with the fix will be released in the near future.
Good afternoon!
Thank you for the great development work!
I want to clarify the approximate timing of the new assembly with the correction of the print?
New build available!
I'm excited to announce the release of the second stable unofficial build of LineageOS 20 for the Realme 8. This release contains multiple bug fixes and stability improvements over the previous build.
Code:
- Updated and synced with latest Lineage 20 sources
- Update Android Security Patch to 5 May 2023
- Update Vendor Security Patch to 5 April 2023 (C.17 blobs)
- Merge latest android-4.14-stable into kernel (4.14.317)
- Add WireGuard support
- Implement ALS compensation algorithm (should help with auto brightness stability but no guarantees)
- Massive kernel debloat, removed a bunch of useless oplus features and code
- Fix fingerprint for some Goodix sensors
- Switch to OSS Memtrack HAL
- Switch to OSS GNSS service
- Switch to OSS USB HAL
- Switch to OSS Wi-Fi HAL
- Rework brightness implementation
- Rework screen-off gesture handling
- LiveDisplay HBM improvements (brightness cannot be adjusted until HBM is turned off)
- Cleaned up init scripts
- Disable/Remove useless MTK debugging tools
- Drop unneeded Dirac blobs
- Drop uneeded ADSP/CDSP blobs
- Switch to backported exFAT driver from Linux 6.0
- Switch to stock ext4 driver from ALPS 12 kernel-4.14
- Switch to skiaglthreaded rendering backend
- Resolve some more IMS crashes
- Support blur rendering in UI
- Add boosts for blur rendering in UI
- Intensify app launching boosts
- Improve PowerHAL hint handling
- Fix random PowerHAL crashes (observed as random 2-4 second hangs in UI)
- Enable Wi-Fi dual interface (Wi-Fi and Hotspot at the same time)
- Change reserved partition sizes for GApps install.
- Fix USB OTG
- Apply patch for Mali exploit CVE-2022-20186
- Fix GPS crashes
- Implement Lineage charging control
Download
Notes
- Recommended firmware has changed to C.17, please flash C.17 before updating!
- Please make sure you reflash the GApps package BEFORE YOU REBOOT INTO SYSTEM.
How are we supposed to get C.17, i had a hard time getting C.14 last time.
I really like your work, i managed to root and hide the root too.

Categories

Resources