[ROM]LineageOS 15.1 OFFICIAL [G2] d800/d801/d802/d803

[ROM]LineageOS 15.1 OFFICIAL [G2] d800/d801/d802/d803 - G2 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"
}
NOTE: PLEASE ALSO READ ALL OF THE FAQ IN THE SECOND POST. IT COVERS MANY OF THE COMMON PROBLEMS AND QUESTIONS!DONT FLASH SUPERSU OR ANY OTHER MOD THAT EDIT BOOT IMG
LineageOS 15.1 is a free, community built, aftermarket firmware distribution of Android 8.x (Oreo), 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.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
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.
The source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Changelog:
Latest commits for kernel, g2, and device d800 | d801 | d802 | d803 specific (based on date) [by review.lineageos.org]
Requirements:
Custom recovery (TWRP 3.2.2 or above)
KitKat (KK) bootloader (included in the lg-devs LP bootstack)
KitKat (KK) bootstack minimum; Please read the entire FAQ for important bootstack information. Installation of bootstacks is NOT recommended.
Clean flash if coming from another ROM or CM 13/14 (no dirty flash, wipe system too check you bootstack (needen bump support)
Recommended install method
Start from stock Lollipop Rom (flashing using KDZ method)
Root with One click root (other methods are not recommended, Link)
Install TWRP with Autorec for Lollipop (Search in apkpure or apkmirrordownload)
Update TWRP to 3.2.3 (Link)
Flash the Rom and Gapps
Works:
Audio
Bluetooth
Camera
GPS
Headphones
NFC
SIM
User storage
UI
Wi-Fi
FAQ, other information:
Please read on to the second post in this thread for more information and answers to some frequently asked questions. Please read through it as I will absolutely, positively, and unequivocably NOT offer any help or answers that are already provided in that post.
Changelog:
Code:
[B]08/03/2019[/B]
* Fixed not showing charging message during USB charging (Cosmetic)
* Fixed dmesg logging function which was broken long ago
[B]22/10/2018[/B]
* Fixed OTA Updates
[B]15/10/2018[/B]
* Enabled ambient display
[B]24/09/2018[/B]
* Official builds start
[B]09/09/2018:[/B]
* Updated to android 8.1.0_r46
* Changed Audio/Video OMX to non Treble
[B]31/08/2018:[/B]
* Fixed audio distortion and stuttering issues
* New vibration HAL (New Tick effect)
Download:
D800 - download.lineageos.org/d800
D801 - download.lineageos.org/d801
D802 - download.lineageos.org/d802
D803 - download.lineageos.org/d803
SU - https://download.lineageos.org/extras
Last LOS 15.1 Official build Download: (use when 15.1 roms disappear from official site)
d800/d801/d802/d803
Note to users: I'm not responsible if you brick your phone. See the disclaimer above.
If this thread is inappropriate, please move/delete it.
Thanks to These People:
@Kapricornus
@qwertyu123
@YoDevil
Everyone of LineageOS Devs
LG Devs
@dr4stic for thread(copied from him)
XDA:DevDB Information
LineageOS, ROM for the LG G2
Contributors
Kapricornus, qwertyu123, Yodevil
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Kitkat bootloader (bump)
Version Information
Status: Nightly
Created 2017-11-19
Last Updated 2019-03-26

For those, who want to test it out. If you have noticed that something doesn't work and it is not mentioned in the first post, grab a logcat and send a message in this thread!

This is great news.

Ohh! I lovu.

Any chance you could compile a build for d800? Thanks for the hard work you and qwertyu have been putting in.

Music player doesn't work:
11-19 17:03:14.111 1272 1295 E AndroidRuntime: FATAL EXCEPTION: MusicPlayerHandler
11-19 17:03:14.111 1272 1295 E AndroidRuntime: Process: com.cyanogenmod.eleven:main, PID: 1272
11-19 17:03:14.111 1272 1295 E AndroidRuntime: java.lang.IllegalStateException
11-19 17:03:14.111 1272 1295 E AndroidRuntime: at android.media.MediaPlayer.getCurrentPosition(Native Method)
11-19 17:03:14.111 1272 1295 E AndroidRuntime: at com.cyanogenmod.eleven.MusicPlaybackService$MultiPlayer.position(MusicPlaybackService.java:3394)
11-19 17:03:14.111 1272 1295 E AndroidRuntime: at com.cyanogenmod.eleven.MusicPlaybackService.saveQueue(MusicPlaybackService.java:1704)
11-19 17:03:14.111 1272 1295 E AndroidRuntime: at com.cyanogenmod.eleven.MusicPlaybackService.notifyChange(MusicPlaybackService.java:1554)
11-19 17:03:14.111 1272 1295 E AndroidRuntime: at com.cyanogenmod.eleven.MusicPlaybackService.-wrap3(Unknown Source:0)
11-19 17:03:14.111 1272 1295 E AndroidRuntime: at com.cyanogenmod.eleven.MusicPlaybackService$MusicPlayerHandler.handleMessage(MusicPlaybackService.java:3062)
11-19 17:03:14.111 1272 1295 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:105)
11-19 17:03:14.111 1272 1295 E AndroidRuntime: at android.os.Looper.loop(Looper.java:164)
11-19 17:03:14.111 1272 1295 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:65)
11-19 17:03:14.116 1272 1272 W MediaPlayer: mediaplayer went away with unhandled events
11-19 17:03:14.116 1272 1272 W MediaPlayer: mediaplayer went away with unhandled events

I think that a lot of things won't work until later builds.

Romflasher69 said:
Any chance you could compile a build for d800? Thanks for the hard work you and qwertyu have been putting in.
Click to expand...
Click to collapse
Yeah, OK. I'll make a build by the end of the week
If there is any interest in any other G2 device, feel free to ping me

good news

It finally booted?! Awesome!!
Would have flashed and helped testing if I had a backup phone but I can't go without calls working.
Keep it up, your work is much appreciated!

Seems like this phone will never end to get support

Can you do a build for D801/T-Mobile?

Awesome work !
I would have helped in testing if G2 is not my daily driver .
Thanks for the quick support and efforts .
KEEP IT UP !!
You made my day !

Сan i get firmware for vs 980?
Thank you very much for your efforts.

Kapricornus said:
any interest in any other G2 device, feel free to ping me
Click to expand...
Click to collapse
f320 build is always desirable
just in case, if suddenly it will be possible to support it

This is going to be nice christmas gift for all G2 community. Thank you all involved people for bringing this oreo rom to us
EDIT: My G2 is no longer my daily driver i can help with testing the rom if you guys need any help. Is a D802 mine

Thank you so much! This amazing phone deserves work on it! Im still using it and not a single problem 3,5 years.
Looking forward to this.

Kapricornus said:
If there is any interest in any other G2 device, feel free to ping me
Click to expand...
Click to collapse
F320 support? There NEVER has been any support for the F320, neither CM13 nor LOS14.1... I guess it's time now?
I know F320 is different from others, would be very very difficult but a man can only wish, please! :fingers-crossed:
please do try, u are a great great developer!

I want to try the rom but i need working wifi . Ill wait this to be fixed and will give it try . Thank you for the rom !

I will try rom but i need working sim and wifi becouse g2 is my only phone.

Related

[ROM][7.1.2] SLIM ROM 7 Stable v1.4 [UNOFFICIAL] [RA Kernel] For Zuk Z1 [20170802]

{
"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"
}
SlimRom
SLIM ROM Community on G+
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices,
* 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.
*
*/
UPDATED To Stable 1.4 on 02-08-2017
Changes in 1.0 Build
- fw/base: PowerProfile: allow overriding default power profile
- hw/qcom/fm: Update colors and translations (LineageOS)
- apps/Bluetooth: Translation updates (LineageOS)
- apps/Settings: MSIM: Fix user set DDS sub in hotswap cases.
- apps/Snap: Translation updates (LineageOS)
- resources/devicesettings: Translations update (LineageOS)
- vendor/qcom/opensource/dataservice : datatop: Fix out_dir array empty content verification. datatop: Remove unused
variables from datatop_ip_table_poll.c
- vendor/slim: Updates to APNs, sensitive phone numbers, offline charging graphics and build configs
- Full changelog can be found Here or as always on SlimROMS website
Note
Slim launcher was still broken in this build. I have removed it and replaced it with Nova Launcher. (fixed)
This is SlimROM 7 for the Lenovo Zuk Z1 (ham)
SlimRoms is a custom operating system. Our main goal is to offer users a slimmed down yet feature rich alternative to other operating systems. The entire SlimTeam work together to bring you this tailor-made beauty straight from Open Source Project (AOSP) source code. All of the sources can be publicly viewed through GitHub and you can stop by our public Gerrit to submit patches of any type.
Known Issues
- Let me know and I'll try to fix. ( PM me)
I highly recommend a full backup before flashing this ROM.Again,I am not responsible if you lose any or all of your data!
Installation
- Install TWRP version of your choice
- Download the zip file
- Copy to your phone
- Reboot into recovery mode (Volume-Up + Volume-Down + Power button)
- Wipe Dalvik/art Cache, Cache, System and Data (inside Wipe -> Advanced Wipe)
- Install
- Install GApps of your choice
- Reboot
Click to expand...
Click to collapse
Downloads
* Slim ROM 7 Stable v1.4 - Here
* SuperSU- Here
* OpenGApps - Here
* TWRP (latest) - Here
Click to expand...
Click to collapse
Sources
ROM - https://github.com/SlimRoms
Device - https://github.com/forkking/forkking-device-tree
Click to expand...
Click to collapse
Credits & Thanks To :
@OrdenKrieger for setting up the base ie. device tree, kernel and vendor.
@acuicultor for his RA Kernel
@SlimRom Team
Lineage OS , SlimRoms , OmniRoms , TeslaROM , and all the rest who make their source open
@MZO , @tech mashido , @Anush12133 , @shubhambhise , for helping me alot
Many others... (if you're feeling upset being out of the thanks list just send a PM )
BECAUSE LESS IS MORE !
XDA:DevDB Information
Slim 7, ROM for the Lenovo Zuk Z1
Contributors
jyothish1231
Source Code: https://github.com/SlimRoms
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: UNLOCKED BOOTLOADER
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 1.4
Stable Release Date: 2017-07-04
Current Beta Version: 0.26
Beta Release Date: 2017-05-28
Created 2017-05-29
Last Updated 2017-08-02

Reserved
Updated to beta 0.26 With june security patches
Updated to STABLE v 1.4

Where SMS? Where is the browser? Where's the calendar? Where is file manager? Developer mode is not enabled. In the furnace

Syn Drome said:
Where SMS? Where is the browser? Where's the calendar? Where is file manager? Developer mode is not enabled. In the furnace
Click to expand...
Click to collapse
Too bold! Don't like it? Exit is there ---->

Syn Drome said:
Where SMS? Where is the browser? Where's the calendar? Where is file manager? Developer mode is not enabled. In the furnace
Click to expand...
Click to collapse
That's SLIM for u. Stripped down version of AOSP. Just download apps that you like from play store. No extra ****.

adanoss said:
Too bold! Don't like it? Exit is there ---->
Click to expand...
Click to collapse
You forgot to ask, sorry!!

Syn Drome said:
Where SMS? Where is the browser? Where's the calendar? Where is file manager? Developer mode is not enabled. In the furnace
Click to expand...
Click to collapse
Slim rom is a feature less rom & Wont come with much apps. u con download from PS.
SlimRom Mainly looks on batterybackup & Performance.
U can enable developer options by tapping build number in about phone

Hello everyone, i have a question regarding this rom and also any other nougat rom...
Does vulkan api included on this rom or any of nougat rom available for this device??
I'm asking for Galaxy Guardian 3 manticore...

How is battery??
Sent from my ZUK Z1 using Tapatalk

jerriel.reyes24 said:
How is battery??
Sent from my ZUK Z1 using Tapatalk
Click to expand...
Click to collapse
Battery is perfect in slim7 . Im getting 6-7hrs sot

Nice. Always wanted slim for the zuk z1.
Thanks OP.
Is there any chance we can get official support?
Also, I guess Paranoid Android is back after a long while. Can we expect anything for the zuk z1?
Will let you know if i face any bugs. Thanks again.
Edit- Developer options isn't working.. It causes the whole settings app to freeze.

Shreyas.FrEaK said:
Nice. Always wanted slim for the zuk z1.
Thanks OP.
Is there any chance we can get official support?
Also, I guess Paranoid Android is back after a long while. Can we expect anything for the zuk z1?
Will let you know if i face any bugs. Thanks again.
Edit- Developer options isn't working.. It causes the whole settings app to freeze.
Click to expand...
Click to collapse
chance for official support will be after 2-3 months. paranoid is little bitter to compile. let it first stuck on bacon, then ham will get support

Can u guys use substratum in this rom
Sent from my LG-H860 using Tapatalk

jerriel.reyes24 said:
Can u guys use substratum in this rom
Sent from my LG-H860 using Tapatalk
Click to expand...
Click to collapse
supported

UPDATED !!!

06-09 10:35:38.646 4580 4733 W ActivityManager: Activity pause timeout for Act
ivityRecord{96eb0be u0 com.android.settings/.Settings$DevelopmentSettingsActivit
y t312}
06-09 10:35:38.962 329 548 I qdhwcomposer: handle_blank_event: dpy:0 panel p
ower state: 0
06-09 10:35:39.028 329 329 D qdhwcomposer: hwc_setPowerMode: Done setting mo
de 0 on display 0
06-09 10:35:39.029 4580 4733 W art : Long monitor contention with owner an
droid.display (4743) at void com.android.server.wm.WindowManagerService$H.handle
Message(android.os.Message)(WindowManagerService.java:8368) waiters=0 in void co
m.android.server.wm.WindowManagerService.stopAppFreezingScreen(android.os.IBinde
r, boolean) for 383ms
06-09 10:35:39.031 4580 14790 D SurfaceControl: Excessive delay in setPowerMode
(): 392ms
06-09 10:35:39.031 4580 14790 E QCOM PowerHAL: Invalid hint ID.
06-09 10:35:39.031 4580 14790 I QCOM PowerHAL: Got set_interactive hint
06-09 10:35:39.031 4580 14790 E QCOM PowerHAL: Failed to acquire lock.
06-09 10:35:39.062 365 365 D audio_hw_primary: adev_set_parameters: enter: s
creen_state=off
06-09 10:35:39.086 17388 17635 D WhatsApp: LL_D W [183:ReaderThread] RECV <messa
ge from='[email protected]' type='media' id='95519DB2315D67BFAA6E0A3
ADB log extracted while trying to access development settings , might help to resolve , cannot understand it but there is something wrong with power hal

Muhammad Faraz said:
06-09 10:35:38.646 4580 4733 W ActivityManager: Activity pause timeout for Act
ivityRecord{96eb0be u0 com.android.settings/.Settings$DevelopmentSettingsActivit
y t312}
06-09 10:35:38.962 329 548 I qdhwcomposer: handle_blank_event: dpy:0 panel p
ower state: 0
06-09 10:35:39.028 329 329 D qdhwcomposer: hwc_setPowerMode: Done setting mo
de 0 on display 0
06-09 10:35:39.029 4580 4733 W art : Long monitor contention with owner an
droid.display (4743) at void com.android.server.wm.WindowManagerService$H.handle
Message(android.os.Message)(WindowManagerService.java:8368) waiters=0 in void co
m.android.server.wm.WindowManagerService.stopAppFreezingScreen(android.os.IBinde
r, boolean) for 383ms
06-09 10:35:39.031 4580 14790 D SurfaceControl: Excessive delay in setPowerMode
(): 392ms
06-09 10:35:39.031 4580 14790 E QCOM PowerHAL: Invalid hint ID.
06-09 10:35:39.031 4580 14790 I QCOM PowerHAL: Got set_interactive hint
06-09 10:35:39.031 4580 14790 E QCOM PowerHAL: Failed to acquire lock.
06-09 10:35:39.062 365 365 D audio_hw_primary: adev_set_parameters: enter: s
creen_state=off
06-09 10:35:39.086 17388 17635 D WhatsApp: LL_D W [183:ReaderThread] RECV <messa
ge from='[email protected]' type='media' id='95519DB2315D67BFAA6E0A3
ADB log extracted while trying to access development settings , might help to resolve , cannot understand it but there is something wrong with power hal
Click to expand...
Click to collapse
Developer settings is fixed in latest build. Check if u r using build 0.26 !

I am using .26 but the issue might still be there for me because I did dirty flash over .25 .overall nice rom so far.

Muhammad Faraz said:
I am using .26 but the issue might still be there for me because I did dirty flash over .25 .overall nice rom so far.
Click to expand...
Click to collapse
Developer options not opening ?

Yes development options are not working for me but USB debugging is on by default so doesn't hurt , I normally don't play with more settings than that

[TREBLE][10.0][arm64] H-VENDOR V1.0

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DISCLAIMER
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
Since I dont have EVERY 7870, this project is open to contributions, so feel free to suggest fixes, improvements or any other thing that could be helpful.
FEATURES
Arm64 vendor ported from J6, A7 2018 and S20
A320X, G610X, J530X, J600X, J701X, J710X, J730X are supported
Android 10 A/B ARM64 supported. Android 11 ready.
H-KERNEL included (3.18.140 kernel compiled from A600FNXXU5CTB9 sources. Built permissive and overclocked. F2fs supported)
AresKernel by @SPARTANICUS supported and recommended
And many more!
KNOWN BUGS
Remember that some bugs could come from GSI side and not from vendor
We haven't tested EVERY 7870 out there, so could be possible that some variants has specific and unknown bugs, or even not booting
Always provide logs and dmesg if you want to report bugs
Common bugs: offlice charging, screen unlock takes a while after a reboot, camera preview streched for some variants or apps. BT calls is a common bug too for some devices. Stock camera flash can be unstable, use footej
A320X: echo in calls
G610X: sometimes, screen delay when coming on, camera flash?
J530X: ?
J600X: NFC could be broken for some variants
J701X: front camera flash
J710X: NFC could be broken for some variants. Audio has a delay for the NM
J730X: ?
You tell me
DOWNLOAD
Current version: 1.0 (16/06/2020)
GoogleDrive folder
Mega folder
md5: 30620c555e13eaecca42ddda56ddec58
INSTALLATION
Vendor partition is required
HIGHLY RECOMMENDED TO USE AN UPDATED RECOVERY. Check my OrangeFox or SHRP builds.
Wipe system, data (clean install mandatory), vendor, dalvik&cache and cache
Flash an Android 10 A/B ARM64 system GSI image
Flash H-VENDOR zip
Reboot
WALLPAPERS
https://imgur.com/a/El75gHV. Thanks to @SaiFurR
ROOT
Flash stable Magisk
SUPPORT
Telegram group
CREDITS
Me, for infinite hours spent with this project
Special thanks to @ananjaser1211, @SPARTANICUS and @Valera1978, and everyone that has contributed to the 7870 development
Huge thanks also to my testers, without them this coundn't have been possible
Thanks to @Kique119, because he pushed me to start this project
And finally thanks to @SaiFurR for the banner and supporting me in every project
DONATIONS
I don't need them, I don't need coffees or beers. I really hate see here people with high end devices asking for donations, but you can still donate money to charity. Donate money or simply help people that is really needed. If you like this project you can make me very happy just pushing THANKS
XDA:DevDB Information
H-VENDOR, ROM for the Samsung Galaxy J5
Contributors
Astrako
Source Code: https://gitlab.com/android_samsung_universal7870/common/android_kernel_samsung_exynos7870/-/tree/oneui_q
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
Version Information
Status: Stable
Current Stable Version: 1.0
Created 2020-06-16
Last Updated 2020-10-06

Reserved

Thanks Sir!

Thanks
Thanks Astrako for giving 7870 a breath of fresh air and for making me a part of this project

Thanks for this !
What is the benefit compared to previeous vendors ?

Hi, thank you for your work, it's great to be able to try out many different GSIs on this device
It's not listed in known bugs, but can anyone confirm if they were able to encrypt their device ? I've made several attempts with several different GSIs, but without success so far ... Could it be something disabled in the kernel ?
Behaviour :
I go to the usual 'settings > security > encryption & credentials > encrypt phone' then I follow the instructions. The android mascot shows up, then the device soft-reboots (I am not asked the PIN for my sim card) and I'm back at the welcome screen in a matter of seconds, the device is not encrypted.
phone : J530F
data partition : ext4 (edit : tried also with f2fs, still the same issue)
Treble : same behavior with "spaget_X" (https://forum.xda-developers.com/ga...t/treble-projecttreble-v1-0-jxy17lte-t3929286)
GSIs I tried out so far (all taken from there https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list) :
Android 10
- AOSP
- CAOS
- Havoc
Android 9 (with spagetX)
- /e/
Log with keyword "crypt" :
Code:
06-30 21:55:17.141 2870 10864 W vold : Found map /proc/10839/maps referencing /data/dalvik-cache/arm64/[email protected]@boot-conscrypt.art
06-30 21:55:17.176 2870 10864 E Cryptfs : Unexpected value for crypto key location
06-30 21:55:17.176 2870 10864 E Cryptfs : Cannot open block device
06-30 21:55:23.838 2870 2932 D vold : e4crypt_unlock_user_key 0 serial=0 token_present=0
06-30 21:55:24.490 11002 11002 D AccessibilityManagerService: Ignoring non-encryption-aware service ComponentInfo{com.footej.camera/com.footej.services.FingerPrint.FJFingerprintGesturesService}
06-30 21:55:26.285 2870 2932 D vold : e4crypt_prepare_user_storage for volume null, user 0, serial 0, flags 2
06-30 21:55:28.971 12143 12143 E bootstat: Failed to read /data/misc/bootstat/post_decrypt_time_elapsed: No such file or directory
06-30 21:55:28.972 12143 12143 E bootstat: Failed to parse boot time record: /data/misc/bootstat/post_decrypt_time_elapsed
06-30 21:55:35.905 12710 12710 V NativeCrypto: Registering org/conscrypt/NativeCrypto's 286 native methods...
Any idea ?
Have a nice day

[KERNEL][AOSP/MIUI][12/13] IMMENSITY - X [UMI][25-09-2022]

reserved

You have done my journey ! Just what's we need ! Thx you

Great Work Sir ,
Everything working great in Miui Eu Rom except all sensors of mobile has stopped working like gyroscope , magnetic sensor , accelerometer senser and every other sensors , i also flashed Dtbo image but still sensors are not working ,

Flashed it over Xiaomi EU rom. Damn better response now plus no more screen flickering (seconds before screen goes out it used to flicker, very annoying).
You're the best!

Hussain_97 said:
Great Work Sir ,
Everything working great in Miui Eu Rom except all sensors of mobile has stopped working like gyroscope , magnetic sensor , accelerometer senser and every other sensors , i also flashed Dtbo image but still sensors are not working ,
Click to expand...
Click to collapse
How do u check sensors ?

by going into settings and tapping kernal 5 times it will go into CIT where you can check sensors working , or you can also check by rotating the phone ,if auto rotate works then sensor are working ok .
And Did you flash this kernal over Xiaomi Eu Stable Rom or weekly rom ??
fuadhdmini said:
How do u check sensors ?
Click to expand...
Click to collapse

mee too, flashed on OneOs weekly, sensors not working

Fabiosx21m said:
mee too, flashed on OneOs weekly, sensors not working
Click to expand...
Click to collapse
yes there is issue with this kernal , sensors not working ..

For all people above. This kernel is for AOSP/CAF based rom's, dont report bugs on Miui.

New I M M E N S I T Y - X Update!
C H A N G E L O G
- Kernel synced with android kernel common at Linux version 4.19.203 with August CVE patches merged ASB-2021-08-05_4.19-stable
- Merged Latest QCOM tags for 4.19 mobile platform `LA.UM.9.12.r1-12500-SMxx50.0`, `LA.UM.9.15.1.r1-04000-KAMORTA.0`
- F2FS drivers updated to latest from jaeguek/f2fs-stable
- Fixed a critical bug which caused device to freeze in suspend and unable to wake from it
- Fixed a critical bug on `apollo` which caused display glitches
- Fixed Inline building of kernel for devs interested in using this as base
- Added LineageOS FOD support for cmi, umi
- Aligned GPU Frequency table of SM8250 devices with SM8250-AB
Click to expand...
Click to collapse
D O N A T E
If you found my work useful and want to continue supporting development contribute by becoming
- A Patron for early releases and better support.
- You can also provide a small donation through PayPal
- Indian users can support through UPI: [email protected]
Please consider a donation for IMMENSITY because it will help me offer support in the long term.
Its fine even if you can't afford it alternatively consider providing a thanks on XDA thread.
N O T E S
If you encounter issues with gestures not working or facing wrong display scaling on Apps
then flash the provided dtbo
- Umi
D O W N L O A D

Any rom you would recommend to use with this kernel ?

UtsavTheGreat said:
A B O U T - I M M E N S I T Y
IMMENSITY is a unique custom kernel project that focuses on optimizing UX and fine tuning the OEM modifications to provide the best of your device.
Downloads and Changelogs can be found here
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead batteries
* 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 KERNEL
* 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. Hard & a lot.
*
*/
F E A T U R E S
Check out features here
I N S T A L L A T I O N
Download the latest build on your device
Reboot into TWRP
Select the kernel zip file and flash
Or
Flash from FKM Must be rooted
R E P O R T I N G - I S S U E S
Before reporting an issue please check that it only occurs when having this kernel installed. Otherwise it may be an issue with the ROM.
The above also applies the other way around; i.e Don't report issues to the maintainer of a ROM unless they also occur without this kernel.
Be aware that battery issues are very likely related to your personal settings. Don't blame me for your modifications.
Always use the latest Kernel release with the latest build of your ROM of choice. If the kernel is much newer than the ROM or the other way around weird issues may arise.
LIKE MY WORK ?
Leave a Thanks
XDA:DevDB Information
IMMENSITY-X Kernel for the Xiaomi MI 10
Contributors
UtsavTheGreat
Version Information
Status: Stable
Stable Release Date: 2021-08-02
Click to expand...
Click to collapse
Im currently on 12.5.7.0 stable eu, will this work?

JustNabus said:
Any rom you would recommend to use with this kernel ?
Click to expand...
Click to collapse
PE, Evo or p404

Would it be possible to offer this kernel for MIUI Weekly?

dontobi said:
Would it be possible to offer this kernel for MIUI Weekly?
Click to expand...
Click to collapse
You can try and use its but best compatible for aosp/CAF ROMs

I use with PE last version, it is greet! Thanks!!
But I flashed kernel and dtbo, without dtbo no worked fingerprints!

Hi!
Using this with Evolution X (2021-09-21 release), the fingerprint sensor does not work anymore due to screen brightness issue: the finger area is not brighter than the rest of the screen, so that means you can only unlock when the screen is at full brightness. Reflashing Evolution X immediately solved the problem, the fingerprint area is much brighter even at low screen brightness levels.
Thanks!

Would this kernel by any chance be compatible with Mi 10 Ultra? (naturally, my first thought is no, just looking to confirm that)

New I M M E N S I T Y - X Update!
C H A N G E L O G
- Kernel synced with android kernel common at Linux version 4.19.259.
- Merged the latest CLO tag `LA.UM.9.12.r1-14700-SMxx50.0` in kernel and kernel subtrees.
- Merged latest AOSP security patches in kernel added in tag `ASB-2022-09-05_13-4.19`.
- Added support for Xiaomi Redmi K40S / POCO F4 (munch).
- Added support for android 13 ROMs.
- Upgraded F2FS drivers from jaegeuk/f2fs-stable [Linux kernel 6.0.0-rc3].
- Kernel compiled using latest AOSP clang v15.0.2 with Full LTO support.
- Fixed a critical TCP issue due to a broken congestion algorithm.
- Upgraded exfat drivers from namjaejeon/exfat-linux [Linux kernel 6.0.0].
- Fixed memory reclaim issue on Android.
- Removed proximity blocking feature for telegram from the kernel.
- Increased swappiness to 160.
- Fixed issue with game mode on MIUI.
- Imported the new xiaomi MIUI experience modifications for MIUI builds.
- Optimized charging control for all xiaomi sm8250 devices.
- Removed display panel power state modifications.
- Enabled F2FS compression support.
- Upgraded lrng driver from Linux kernel 5.15.
- Fixed unusual power consumption issue on UMI / THYME.
- Updated kernel devicetree to LA.UM.9.12.r1-14400-SMxx50.0.
- Backported fortify source patches from mainline kernel.
- Enabled back support for ARM64 compiler optimizations.
- Fixed async binder buffer running out and save unnecessary binder read workloads.
Click to expand...
Click to collapse
D O N A T E
If you found my work useful and want to continue supporting development, contribute by becoming
- A Patron for early releases and better support.
- You can also provide a small donation through PayPal
- Indian users can support through UPI:
[email protected]
Please consider a donation for IMMENSITY because it will help me offer support in the long term.
Its fine even if you can't afford it alternatively, consider providing a thanks on XDA thread.
N O T E S
Do NOT flash on hentaiOS or hentaiOS based ROMs.
D O W N L O A D

[KERNEL][AOSP/MIUI][12/13] IMMENSITY - X [CMI][25-09-2022]

Reserved

Not Support for MIUI ?

New I M M E N S I T Y - X Update!
C H A N G E L O G
- Kernel synced with android kernel common at Linux version 4.19.203 with August CVE patches merged ASB-2021-08-05_4.19-stable
- Merged Latest QCOM tags for 4.19 mobile platform `LA.UM.9.12.r1-12500-SMxx50.0`, `LA.UM.9.15.1.r1-04000-KAMORTA.0`
- F2FS drivers updated to latest from jaeguek/f2fs-stable
- Fixed a critical bug which caused device to freeze in suspend and unable to wake from it
- Fixed a critical bug on `apollo` which caused display glitches
- Fixed Inline building of kernel for devs interested in using this as base
- Added LineageOS FOD support for cmi, umi
- Aligned GPU Frequency table of SM8250 devices with SM8250-AB
Click to expand...
Click to collapse
D O N A T E
If you found my work useful and want to continue supporting development contribute by becoming
- A Patron for early releases and better support.
- You can also provide a small donation through PayPal
- Indian users can support through UPI: [email protected]
Please consider a donation for IMMENSITY because it will help me offer support in the long term.
Its fine even if you can't afford it alternatively consider providing a thanks on XDA thread.
N O T E S
If you encounter issues with gestures not working or facing wrong display scaling on Apps
then flash the provided dtbo
- Cmi
D O W N L O A D

Hello, thanks dev very much, but I have a question, ANX camera work?

@UtsavTheGreat hey there. Great Kernel, however I found an issue. when pressing the fingerprint sensor, the screen dims and the white light coming out of the sensor is weak, thus the finger is not recognized. If I set the screen brightness at 100% it works, but it doesn't in any lower setting. This can also be seen in dark environments and auto brightness

meneses.leonardo said:
@UtsavTheGreat hey there. Great Kernel, however I found an issue. when pressing the fingerprint sensor, the screen dims and the white light coming out of the sensor is weak, thus the finger is not recognized. If I set the screen brightness at 100% it works, but it doesn't in any lower setting. This can also be seen in dark environments and auto brightness
Click to expand...
Click to collapse
If your AOSP ROM is based on the stock kernel, you can try to restore these and recompile the kernel to solve this problem because they do not use LineageOS FOD

Thank you for the kernel made by the author. He is very good. I also used the redmi k20 pro kernel you made before. Thank you for meeting again, but I found an error. This problem is a change after msm4.19:
Image.gz-dtb is no longer applicable to msm4.19 because it is invalid. After flashing, the modified dtb will not be loaded directly. This causes the Aligned GPU Frequency table of SM8250 devices with SM8250-AB to fail to take effect.
To replace dtb normally, you need to rename the corresponding dtb to "dtb" and put it into the root directory of Anykernel (for example, rename kona-v2.1.dtb to dtb and put it into the root directory of Anykernel)

Um it should work needlessly even if it is appended dtb.
AK3 splits the image any way and flashes the splits accordingly

EDIT: wrong thread sorry

Can you add support for Kali NetHunter?
I always fail to compile by myself.

yfjy said:
Can you add support for Kali NetHunter?
I always fail to compile by myself.
Click to expand...
Click to collapse
@UtsavTheGreat

Hello, I get bootloop when installing on the latest version of Xiaomi.eu for mi 10 pro.
Doesn't support xiaomi.eu?
The latest version is android 12 miui13.
Thanks.

[ROM][OFFICIAL][fajita][13] LineageOS 20

Not sure to understand how to upgrade from lineage os 19:
reading here https://wiki.lineageos.org/devices/fajita/upgrade
I understand I have to revert to stock firmware before upgrading.
Doing this I lose all data isn't it?
Thanks!

dav01it said:
Not sure to understand how to upgrade from lineage os 19:
reading here https://wiki.lineageos.org/devices/fajita/upgrade
I understand I have to revert to stock firmware before upgrading.
Doing this I lose all data isn't it?
Thanks!
Click to expand...
Click to collapse
It doesn't tell you to go back to stock, just that you need Android 11 firmware, which you likely already have if you're on 19.1.

EdwinMoq said:
It doesn't tell you to go back to stock, just that you need Android 11 firmware, which you likely already have if you're on 19.1.
Click to expand...
Click to collapse
My 19.1 says it's Android 12..
I'm confused, pls explain!
See attachment.

dav01it said:
My 19.1 says it's Android 12..
I'm confused, pls explain!
See attachment.
View attachment 5798931
Click to expand...
Click to collapse
Firmware is not the same as the ROM.
Like I said, you're probably already on Android 11 firmware, so you can go ahead and upgrade.

Smooth update from LineageOS 19. Good performance and no problems encountered so far. Thanks for the great efforts of maintaining the software update to the Oneplus 6t device. Much appreciated.

Smooth update here from Lineage-19.1 (MindTheGapps + TWRP + Magisk) to Lineage-20 (MindTheGapps + TWRP + Magisk) using TWRP_3.7.0_12.
Thanks to the devs !

dwardo said:
Smooth update here from Lineage-19.1 (MindTheGapps + TWRP + Magisk) to Lineage-20 (MindTheGapps + TWRP + Magisk) using TWRP_3.7.0_12.
Thanks to the devs !
Click to expand...
Click to collapse
Is TWRP_3.7.0_12 fully functional with decryption and such?
Are you using the official release or a another modded fork? Care to share the link?
I just upgraded to LOS 20, but would like to go back using TWRP again.

yoruuba2 said:
Is TWRP_3.7.0_12 fully functional with decryption and such?
Are you using the official release or a another modded fork? Care to share the link?
I just upgraded to LOS 20, but would like to go back using TWRP again.
Click to expand...
Click to collapse
Using siddk's specific version with A12 base (hence the _12 in the version name) and decryption was fully functional in LineageOS 19.1 and is also in LineageOS 20 (I upgraded using install from internal storage i.e. without using adb sideload)

Thanks to support the 6T!!!
edit: I found the issue. I used an old LOS 19.1 boot image to patch magisk and then flashed the LOS 19.1 to my device running LOS 20. Using the correct LOS 20 boot.img in magisk is fine. No isues so far.
I cannot scan for wifi networks and can't connect to known wifi networks. Does anybody has the same issue on LOS 20? I can provide logcat.
LineageOS version: 20
LineageOS Download url: https://download.lineageos.org/fajita
Gapps version: MindTheGapps-13.0.0-arm64-20221025_100653
Did you--
wipe: no
restore with titanium backup: no
reboot after having the issue: yes
Are you using--
a task killer: no
a non-stock kernel: no
other modifications: magisk and MindTheGApps
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
It worked on latest LOS19.1
logcat snippet from startup filtering for error messages and wifi. I can provide more on request:
01-02 13:43:21.262 1049 1049 E [EMAIL][email protected][/EMAIL]: Failed to access driver state control param No such file or directory, 2: No such file or directory
01-02 13:43:21.263 1049 1049 E [EMAIL][email protected][/EMAIL]: Failed to load WiFi driver
01-02 13:43:21.263 1049 1049 E [EMAIL][email protected][/EMAIL]: Failed to initialize firmware mode controller
01-02 13:43:21.263 1049 1049 E [EMAIL][email protected][/EMAIL]: Wifi HAL start failed
01-02 13:43:21.263 1251 1988 E HalDevMgr: Cannot start IWifi: 9 ()
01-02 13:43:21.263 1251 1988 E WifiVendorHal: Failed to start vendor HAL
01-02 13:43:21.263 1251 1988 E WifiNative: Failed to start vendor HAL
01-02 13:43:21.263 1251 1988 E WifiNative: Failed to start Hal
01-02 13:43:21.263 1251 1988 E WifiClientModeManager[unknown]: Failed to create ClientInterface. Sit in Idle
01-02 13:43:21.263 1251 1988 E WifiActiveModeWarden: ClientModeManager start failed!ConcreteClientModeManager{id=52658 iface=null role=null}
01-02 13:43:21.264 1251 1988 D WifiScanRequestProxy: Sending scan available broadcast: false
01-02 13:43:21.264 1251 1988 I WifiScanRequestProxy: Scanning is disabled
01-02 13:43:21.264 1251 2001 I WifiScanningService: Received a request to disable scanning, UID = 1000
01-02 13:43:21.265 1251 2001 I WifiScanningService: wifi driver unloaded
01-02 13:43:21.265 1251 1988 I WifiCountryCode: No active mode, call onDriverCountryCodeChanged with Null
01-02 13:43:21.265 1251 1988 D WifiService: locale changed
01-02 13:43:21.265 1251 1988 E HalDevMgr: IWifiEventCallback.onFailure: 9 ()
01-02 13:43:21.265 1251 1988 I WifiNative: Vendor HAL died. Cleaning up internal state.
01-02 13:43:21.266 1251 1251 V ProfileTriggerHelper: Enabling
01-02 13:43:21.266 1251 1988 D WifiController: STA disabled, return to DisabledState.
01-02 13:43:21.266 1251 1988 D WifiController: EnabledState.exit()
01-02 13:43:21.266 1251 1988 D WifiController: DisabledState.enter()
01-02 13:43:21.266 1251 1988 E WifiActiveModeWarden: One of the native daemons died. Triggering recovery
01-02 13:43:21.266 1251 1988 E WifiSelfRecovery: Triggering recovery for reason: WifiNative Failure
01-02 13:43:21.266 1251 1988 E WifiSelfRecovery: Restarting wifi for reason: WifiNative Failure
01-02 13:43:21.266 1251 1988 D WifiController: Recovery triggered, already in disabled state
In addition I cannot hear anything on the phone speaker. Microphone does not work. I just did an update via sideload from LOS 12.

Awesome to see this. I recently upgraded to Pixel 6A but kept my OP 6T as a backup phone. Nice to have it relatively up to date still! Update very easy using adb sideload per instructions.

dwardo said:
Using siddk's specific version with A12 base (hence the _12 in the version name)
Click to expand...
Click to collapse
Thanks

Congrats on the quick release! Haven't had a single issue since installing LineageOS 20; everything just works. Haven't had issue with MindtheGApps or Magisk either (although I know the latter is out-of-scope). Thank you again for providing a consistently stable and updated ROM.

Smooth update here as well to LOS 20+MTGapps+Magisk.
The only issue that I've experienced so far is the Music app force closing.
I had the same issue on LOS 19.1. I'm thinking it's not a ROM issue but rather something on my side causing it.
I'm running Viper4Android repackaged and I think that's causing the force close.
Great experience so far. Thanks to the devs/maintainers

Hi, Im on Pixel Experience 12L. Can i upgrade to LineageOS 20 without going back to Stock OOS?

I'm using Lineage 19.1 with nikgapps, I guess the instructions work the same to upgrade to 20, right?
any ideas on if I can use local update instead of sideloading.

Upgrade to Lineageos 20 was smooth indeed. Some struggle to get Magisk working. But now everythings works, it seems to be far better with the battery. In the last releases of Lineageos 19 the screen won't go black after two minutes like it should have >> Battery drain.
Now it works again.
Regards

Upgrade from newest 19.1 to 20 went smooth. Just the LOS20 pack + MindTheGapps.
Already loving a few new features, like the new player, or being able to edit recently copied text. Especially when copying link by share-button.
One minor downside I noticed however was when using the keyboard: The buttons to hide keyboard and choosing input method have been swapped. The hide-button was on the right side, and input method on left, now they're swapped. Is there a method to swap them again?
Another thing I've noticed is, when unlocking the phone with fingerprint. There was a vibration first when placing the finger on the scanner, then a vibration when it proceeds (unlock or error). Now it only vibrates when proceeding. Was it on purpose? I don't mind it, but don't know if it's a bug.
Last but not least: Thank you for the big support for 6T! Like the phone quite a lot, and it's great to see it being supported still!
ugugx said:
I'm using Lineage 19.1 with nikgapps, I guess the instructions work the same to upgrade to 20, right?
any ideas on if I can use local update instead of sideloading.
Click to expand...
Click to collapse
If you open the updater, you'll see an information-button instead of download/install, which tells you that it won't install with the local updater. You also need your gapps-package for Android 13.

Awesome work! Successfully upgraded to LOS20 from 19.1.
Is it possible to enable digital wellbeing app for LOS20 + MindtheGapps?
Currently, it says "This app isn't compatible with your device anymore".
I already tried APK as well. Not sure if there's anything I can sideload just for this.

mahashakti89 said:
Upgrade to Lineageos 20 was smooth indeed. Some struggle to get Magisk working. But now everythings works, it seems to be far better with the battery. In the last releases of Lineageos 19 the screen won't go black after two minutes like it should have >> Battery drain.
Now it works again.
Regards
Click to expand...
Click to collapse
What's the issue with Magisk with this release?

Database Develop

welcome