[ROM][testing][suez] Lineage-16.0 [05 JULY 2022] - Fire HD 8 and HD 10 Original Android Development

Disclaimer
Code:
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* in the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
- EVEN MORE IMPORTANT: This ROM only works on devices using the bootloader hack. See <<< HERE >>> to unlock your devices.
- IMPORTANT: Do not update Magisk via the Magisk Manager App, your device will enter a bootloop if you do. Instead update Magisk via TWRP only. If you do this by accident then it is recoverable by just flashing the latest version of the ROM again (with gapps etc as required). This will be fixed in a later update.
Rules
- Please search the thread before asking questions
- Please try to stay on topic, I know it's not always possible
- When reporting bugs please post a logcat and/or dmesg where possible
Lastest TWRP version
- 3.6.1-9.2
Downloads
- Google Drive
Source Code
GitHub - lineage16-suez/kernel_amazon_suez
Contribute to lineage16-suez/kernel_amazon_suez development by creating an account on GitHub.
github.com
GitHub - lineage16-suez/device_amazon_suez
Contribute to lineage16-suez/device_amazon_suez development by creating an account on GitHub.
github.com
GitHub - android-extra/twrp_device_amazon_suez: TWRP device tree for Amazon Fire HD10 (2017)
TWRP device tree for Amazon Fire HD10 (2017). Contribute to android-extra/twrp_device_amazon_suez development by creating an account on GitHub.
github.com
Thanks
- @k4y0z and @xyz` for the bootloader hack
- @k4y0z for the initial kernel
- LineageOS

⏱ Change log / Release Notes
05 July 2022
- [fixed] Backlight HAL Errors
- [fixed] LiveDisplay not working
06 May 2022
- [fixed] Voice assist MIC not working
- [fixed] USB-OTG Ethernet
- [fixed] TWRP: MTP access
- [fixed] TWRP: Fixed USB-OTG
- [info] Added android.hardware.opengles.aep.xml permissions
13 April 2022
- [fixed] Terminal input via apps and adb shell
12 April 2022
- [kernel] Up-streamed to 3.18.140
- [kernel] Enable per user storage quota
- [kernel] Optimized build flags for Cortex-a53
- [kernel] Boeffla Wakelock Blocker Driver v1.1.0
- [kernel] Enable some TCP congestion algorithms
- [kernel] Westwood Default TCP congestion algorithm
- [kernel] Sdcardfs v2.0
- [info] Remove aptX bluetooth libraries for now
- [info] Mount /system partition early-mount style
- [info] Add vendor security patch
06 April 2022
- [fixed] Fix KernelUidCpuTimeReader errors
- [info] Revert audio HIDL from 2.0 to 4.0 back to 2.0 - our drivers aren't ready for this
- [info] Put storage permissions force close on the todo list
- [info] Chrome browser works
- [info] Jelly browser works
- [info] WeDo lego app works
Show Further History
03 April 2022
- [fixed] Magisk update by app
- [fixed] Storage permission issues (cause of some apps crashing)
- [fixed] Lego app not working (more info here)
- [fixed] Cannot switch wifi on after storage encryption enabled
- [info] Update suez defconfig in kernel to be more inline with aosp
- [info] TWRP 3.6.1-9.0 available from Google Drive (no encryption support)
- [info] Up-rev audio HIDL from 2.0 to 4.0
- [info] Disabled amazon logging functions in kernel
- [info] Disabled unused squashfs in kernel
- [info] Conditionally compile MTK_M4U in the ion kernel driver as our device doesn't use it
27 March 2022
- [reverted] WiFi changes from previous build
- [removed] 26 March Build
26 March 2022
- [fixed] Speakers continuing to play while headphones are plugged in
- [fixed] Disney+ crashing
- [didn't work for everyone] Slow WiFi throughtput
- [didn't work for everyone] 5GHz connectivity to AX-88U router and in general
- [didn't work for everyone] 5GHz connectivity to across all channels
- [info] Include Bromite Webview
- [request] WiFi: Can someone test connecting to hidden SSID's and report back?
- [request] Magisk: Can someone test whether updating through the application works and report back?
16 March 2022
- [fixed] MtkOmxCore crash
- [fixed] Better auto adjust on backlight
- [fixed] SIM card prompt
- [fixed] Changed battery capacity to 6300mAh
- [fixed] sdcard access for chrome and other apps
- [fixed] "There's an internal problem with your device." dialog
- [info] Explicitly enable sdcardfs
- [info] Refactor root init scripts
- [info] Remove deprecated storage_list.xml
- [info] Clean-up build.prop
01 March 2022
- [info] Re-build of 28 February version
28 February 2022
- [fixed] DRM Widevine L3 support
- [new] Signature spoofing (enable and disable via developer options)
- [fixed] Wired headphones not working
- [fixed] Backlight HAL crashing
- [fixed] Hardware OMX (MTK codecs now been used)
- [info] Disable camera completely until fully investigated to stop logcat spam
- [info] Enable OTG for ethernet in kernel
07 February 2022
- [fixed] OMX regression was breaking NewPipe and local video file playback
- [info] Clean-up amazon binaries - media playback should be better - config file mess
05 February 2022
- [fixed] Navbar icon corruption
- [fixed] Wallpaper corruption
- [fixed] Laggy graphics
- [fixed] High idle cpu usage
- [info] Updated amazon binaries to fireos 5.6.9.0
12 February 2021
- Initial Release

🛠 Worklist / Tasks
- [fixed] Bluetooth works
- [fixed] Audio works
- [fixed] Internal storage isn't accessible from any app
- [done] Sensors working
- [fixed] Touch sounds are working
- [done] Test audio format playback - mp3 working
- [done] Tested video playback with NewPipe which is working
- [fixed] WiFi signal strength not working
- [done] Support aptX-HD encoder for bluetooth
- [fixed] No adb during boot
- [fixed] WiFi working
- [fixed] Navbar icon corruption
- [fixed] Wallpaper corruption
- [fixed] Laggy graphics
- [fixed] High cpu usage
- [fixed] DRM not working
- [fixed] Hardware OMX (for the most part)
- [fixed] Wired headphones not working
- [done] Enable OTG USB for ethernet
- [fixed] Youtube black screen with audio
- [fixed] MtkOmxCore crash
- [fixed] Battery showing wrong capacity - reported here
- [fixed] "There's an internal problem with your device." dialog
- [fixed] SIM card prompt
- [fixed] Chrome cannot access internal storage
- [fixed] Poor WiFi throughput (potential cause of choppy video playback)
- [fixed] Disney app crashing (more info here)
- [fixed] Speakers continuing to play while headphones are plugged in
- [fixed] Cannot switch wifi on after storage encryption enabled
- [hold] Bluetooth not working properly - can't see issue here
- [fixed] Magisk update by app
- [fixed] Storage permission issues (cause of some apps crashing)
- [done] Upstreamed kernel
- [todo] TWRP: USB-OTG not working
- [fixed] USB-OTG Ethernet
- [fixed] TWRP: MTP access
- [todo] Voice assist MIC not working
- [done] Added android.hardware.opengles.aep.xml permissions
- [fixed] LiveDisplay not working
- [fixed] Backlight HAL Errors
- [todo] Shutdown after entering sleep mode (suspect cpu/gpu coming up in the wrong state -> overheating)
- [todo] Gapps > pico causing not enough space error
- [todo] Youtube black screen with audio
- [todo] Mirrorcast not working
- [todo] Multi-user not working
- [todo] Navbar problem when keyboard is in horizontal mode
- [todo] Playing videos over SMB failure after 30 min (more info here)
- [todo] Can't connect to hidden WiFi networks
- [todo] Lego app not working (more info here)
- [todo] Cameras not working (more info here)
- [todo] SELinux
- [todo] Intermittent high idle cpu usage
- [todo] Investigate L1 widevine support (L3 currently)
- [todo] Pass safetynet
- [todo] Device build fingerprinting
- [todo] Enable zram?
- [todo] Device encryption (TWRP)
- [todo] Battery idle mode
- [todo] Offline charging mode
- [todo] Low speaker volume
- [todo] Thermal Shutoff, overheating
- [todo] System partition needs to be increased in size to accomodate gapps

New Build is up
12 February 2021
- Initial Release
- Post #2 contains change log
- Post #3 contains task list
- Clean installation is required

Thank you for your great work! Can´t wait to try the new rom!
Just a few questions on build 12.february.2021:
DRM not working -> So netflix, amazon prime etc. isn´t working yet?
clean install required -> coming from lineage 12, factory reset and flashing afterwards will work? Or do i have to wipe anything specific?
Cameras not working -> both of them ? Or maybe just camcorder like in the early versions of your Los12?
Wired headphones not working -> i guess the headphone fix from previous versions (Los-12,Los-14) does +not+ work on Lineage 16?

cochonez1312 said:
Thank you for your great work! Can´t wait to try the new rom!
Just a few questions on build 12.february.2021:
DRM not working -> So netflix, amazon prime etc. isn´t working yet?
clean install required -> coming from lineage 12, factory reset and flashing afterwards will work? Or do i have to wipe anything specific?
Cameras not working -> both of them ? Or maybe just camcorder like in the early versions of your Los12?
Wired headphones not working -> i guess the headphone fix from previous versions (Los-12,Los-14) does +not+ work on Lineage 16?
Click to expand...
Click to collapse
Try netflix and amazon and let me know if anything needs looking into, I have started a tasklist so we can add items there.
Factory reset should suffice for clean installation.
Cameras not working at all, more to come on this. I understand why they are not working and it's not great news I know. I'll do a more detailed post on this.
The headphone fix from cm-14.1 might work or be adaptable to work on this rom. I am looking into a permanent solution for this.

I have faced these issues so far
1) Directly after first boot, i get the error message "Your device encountered a problem. Please contact the manufacturer". Anyways, I can proceed after tapping on OK.
2) I can only flash pico Gapps, any package larger than that throw error 70 (Insufficient system space). In older builds, i was able to flash the nano package. The system partition (1.5 GB) should be large enough to fit Gapps packages larger than pico.
3) The start assistant prompts me to insert a SIM card, although this device does not have a SIM card slot.
4) The three softbuttons are broken, as shown in the picture

BeniS98 said:
I have faced these issues so far
1) Directly after first boot, i get the error message "Your device encountered a problem. Please contact the manufacturer". Anyways, I can proceed after tapping on OK.
2) I can only flash pico Gapps, any package larger than that throw error 70 (Insufficient system space). In older builds, i was able to flash the nano package. The system partition (1.5 GB) should be large enough to fit Gapps packages larger than pico.
3) The start assistant prompts me to insert a SIM card, although this device does not have a SIM card slot.
4) The three softbuttons are broken, as shown in the picture
Click to expand...
Click to collapse
Point 1: I forgot to mention this initial message after boot. This is due to fixing the persistent and repeated camera hal crash and the way in which I had to stop that from happening, hopefully as a temporary measure. I'll add this to the OP so everyone is aware.
Point 2 and 3: I'll add to the list
Point 4: already on the list todo

A few more issues:
1) HD videos in Youtube app are not working. The video either stops or i'm just getting a blackscreen. 480p works.
2) The graphics is not very fluent and a bit laggy, especially when opening apps and scrolling within them. It seems that there's no graphics acceleration.

@ggow is playready crashing (DRM)? If so try to debug the crash with https://github.com/douglas-developm...987d31da8cda42c03b53fb988c18d77f3e297fffd16c4
As for the graphic glitches try adding:
Code:
PRODUCT_PROPERTY_OVERRIDES += \
debug.hwui.renderer=opengl \
debug.hwui.use_partial_updates=false \
debug.sf.disable_backpressure=1 \
debug.sf.latch_unsignaled=1 \
persist.sys.display.clearMotion=1
That fixed Graphic Glitches in 16.0 for my MT8163 tablet.

*****in danks ggow

Lineage 16 = Android 9 !!
OMG, never ever expected to see this on a 7th Gen HD10
Big thanks to ggow for bringing new life to our old "crap". The tablet isn't bad at all, so definitely worth to receive an update. Have to have a drink first to celebrate this, maybe will try the update next week. (I'm still on Amazon stock version, so I'll have to unlock first)

@ggow I may have found some useful information regarding the camera. While exploring why SuperSU wasn't working, I unexpectedly came across some logs. I did not save them, but I'm still trying to fix supersu and will grab them the next time I'm attempting a fix. It might be the smoking gun I'm not sure though.
In regards to supersu, I have figured out why it will not hold root access. For some reason it fails to obtain a root user account.
Code:
Error stderr: null, stdout: null, exit_value: 1
according to root checker, that is the only issue now. I have managed, I think, to rewrite or remove the scripts or lines of script in the files that lineage superuser uses. I'm not sure why it's doing this though. Flashing in twrp just causes a neverending boot animation. @ggow that's where I came across the camera logs, because after rebooting from flashing, I still get an adb connection so I ran a logcat, but aside from the camera, I didn't find anything useful. I made sure the files have owner root:root. I do know KingoRoot doesn't have an issue rooting. So the investigation continues.

Why are we pushing SuperSU? That's been deprecated and I've used Magisk on 12.1 and 14.1 successfully.

for the 11 thousandth time dragon supersu is DEAD stop using it use magisk in core only mode if you need minimal root handling stop pinging ggow because you refuse to join us in the year 2021 and use magisk like everybody else on xda

DragonFire1024 said:
I think the lack of space for gapps has to do with mounts. It sems things are confused to an extent because technically nothing is where it should be. For example, on the lin14 rom, SuperSU won't work and that's because it can't find the boot.img (it's looking in the spot where the img was prior to the unlock hack). I don't know why it won't work as a system install though.
I got init.d to finally work (lineage uses their own so you have to write a script in /system/etc/init and modify a line in init.cm.rc (in root directory) because lineage disables androids init.d I think that's where some of the issues are and part of why SuperSU doesn't work (superuser.rc).
Click to expand...
Click to collapse
the issue for gapps is the system partition size after installing los 16, is set incorrectly, not a mounting issue. supersu dont work because its not compatible and wont be, use magisk. the camera dont work due to a lack of proper drivers not to mention the coding is completly missing from 14.1 and 16 so dont bother trying to fix it yourself unless your compiling a new rom. this is just the first release and will get better in time. it boots and thats a start.

Understanding the Camera Issue:
@daniel_hk made a good post on understanding this:
REF: https://forum.xda-developers.com/t/rom-7-1-2_r36-27jan2018-lineageos-14-1-custom-roms.3513466/
Relevant Extract of the information
III. The Camera
After my first ROM was out, the most eye catching in the log would be the stack corruption in libcam.halsensor.so.
Code:
11-24 21:53:55.967 490 490 F DEBUG : #08 pc 00017459 /system/lib/libcam.halsensor.so (_ZN12ImgSensorDrv13getResolutionEPP34ACDK_SENSOR_RESOLUTION_INFO_STRUCT+60)
After study the source for mt6735, I found it was called within the blob libcam.halsensor.so. In the function ImgSensorDrv::getResolution(), an ioctl() call was passed to the kernel. I was thinking it was caused by user space data handling in the kernel. After a series of trials and dumping, I remarked that part of code from the kernel. The crash persisted. That means it was from the blob itself. I tried a shim library to replace the function ImgSensorDrv::getResolution() but the result is the same. That means the callee was responsible.
After some digging, I was pretty sure it was caused by the alignment (address sanitize) of struct addresses. The latest blob from Lenovo dev.1631 (also the latest for mt6752 devices) were built with gcc 4.9 Clang 3.6. Nougat now use Clang 3.8 by default. Those blob already have alignment support in Clang 3.6 might have issues with the new Clang 3.8.
What is address alignment? In short, a 32 bit processor can handle 32 bit at a time. It would be a easier for the register to locate memories in 32 bits (4 bytes) cells (aligned). If the head or tail for a block of memory is not aligned, extra code would required to separately handle those loose ends. The new clang compiler would fill leading bytes with its own algorithm to make the pointer or variable aligned. Why is ImgSensorDrv::getResolution() being "affected"? The argument of it is a pointer to ACDK_SENSOR_RESOLUTION_INFO_STRUCT. Its definition can be found in the kernel. It is a struct of an array of pointers to another struct. The source from Mediatek use direct reference to the address of struct variables all the time. This is inappropriate in sense of address alignment. Early compilers didn't handle alignments and won't have problem with that. Newer compiler would use its own algorithm to align the structs and pointers. I guess Clang 3.6 didn't handle the above complex struct as argument well. Nougat linker and loader are all built with Clang 3.8. Local variables are allocated at load time which might be handled differently. Thus a call to ImgSensorDrv::getResolution() would cause the stack corruption.
** Those interested may read this article for detail. **
1. Work around
Using older blobs built by gcc 4.8 or earlier might work. Jiayu S3's AOSP were using those old blobs. I'm new to K3-note. I don't think I have the patience and experience to test all the existing blobs. That's the main reason I uploaded the last two test ROM. Trying blobs and hoping some combination would work is passive. Stlport is also obsolete for some time now. I rather deal with the problem directly.
2. The solution
Without the source, building the whole blob is impossible. Even if we have the source from other devices, those custom parameters are unique to each image sensor. It's impossible to guess or back engineer...
If we can change the way ImgSensorDrv::getResolution() is being called or didn't touch the argument within the function. It would avoid the crash. Unfortunately, the function need to fill a local struct within the ImgSensorDrv class. That means it is not seen outside ImgSensorDrv. The only way is to replace the whole ImgSensorDrv class. Fortunately, it is self contained. We can write a wrapper to replace the ImgSensorDrv class only. The source from mt6735 or mt6595 are a bit different and obviously can't be used directly. Most of the struct can be cross referenced to the kernel source. There are two local sturct left unknown. One is for the commands sent to the kernel. The other is some info. collected from the kernel.
With the wrapper, the crash was gone but still no preview. I wrote a test HAL to dump the values in stock ROM. Guessing the values against the names was not a decent job. Fortunately, there were only a few differences. After nights of trial and error, I finally pulled everything together. Camera is working now! Video recording is still not working. Seems codec related. Some say it's not a problem "again". Hoping there will be some real solutions and helps soon...

ggow said:
Understanding the Camera Issue:
@daniel_hk made a good post on understanding this:
REF: https://forum.xda-developers.com/t/rom-7-1-2_r36-27jan2018-lineageos-14-1-custom-roms.3513466/
Relevant Extract of the information
III. The Camera
After my first ROM was out, the most eye catching in the log would be the stack corruption in libcam.halsensor.so.
Code:
11-24 21:53:55.967 490 490 F DEBUG : #08 pc 00017459 /system/lib/libcam.halsensor.so (_ZN12ImgSensorDrv13getResolutionEPP34ACDK_SENSOR_RESOLUTION_INFO_STRUCT+60)
After study the source for mt6735, I found it was called within the blob libcam.halsensor.so. In the function ImgSensorDrv::getResolution(), an ioctl() call was passed to the kernel. I was thinking it was caused by user space data handling in the kernel. After a series of trials and dumping, I remarked that part of code from the kernel. The crash persisted. That means it was from the blob itself. I tried a shim library to replace the function ImgSensorDrv::getResolution() but the result is the same. That means the callee was responsible.
After some digging, I was pretty sure it was caused by the alignment (address sanitize) of struct addresses. The latest blob from Lenovo dev.1631 (also the latest for mt6752 devices) were built with gcc 4.9 Clang 3.6. Nougat now use Clang 3.8 by default. Those blob already have alignment support in Clang 3.6 might have issues with the new Clang 3.8.
What is address alignment? In short, a 32 bit processor can handle 32 bit at a time. It would be a easier for the register to locate memories in 32 bits (4 bytes) cells (aligned). If the head or tail for a block of memory is not aligned, extra code would required to separately handle those loose ends. The new clang compiler would fill leading bytes with its own algorithm to make the pointer or variable aligned. Why is ImgSensorDrv::getResolution() being "affected"? The argument of it is a pointer to ACDK_SENSOR_RESOLUTION_INFO_STRUCT. Its definition can be found in the kernel. It is a struct of an array of pointers to another struct. The source from Mediatek use direct reference to the address of struct variables all the time. This is inappropriate in sense of address alignment. Early compilers didn't handle alignments and won't have problem with that. Newer compiler would use its own algorithm to align the structs and pointers. I guess Clang 3.6 didn't handle the above complex struct as argument well. Nougat linker and loader are all built with Clang 3.8. Local variables are allocated at load time which might be handled differently. Thus a call to ImgSensorDrv::getResolution() would cause the stack corruption.
** Those interested may read this article for detail. **
1. Work around
Using older blobs built by gcc 4.8 or earlier might work. Jiayu S3's AOSP were using those old blobs. I'm new to K3-note. I don't think I have the patience and experience to test all the existing blobs. That's the main reason I uploaded the last two test ROM. Trying blobs and hoping some combination would work is passive. Stlport is also obsolete for some time now. I rather deal with the problem directly.
2. The solution
Without the source, building the whole blob is impossible. Even if we have the source from other devices, those custom parameters are unique to each image sensor. It's impossible to guess or back engineer...
If we can change the way ImgSensorDrv::getResolution() is being called or didn't touch the argument within the function. It would avoid the crash. Unfortunately, the function need to fill a local struct within the ImgSensorDrv class. That means it is not seen outside ImgSensorDrv. The only way is to replace the whole ImgSensorDrv class. Fortunately, it is self contained. We can write a wrapper to replace the ImgSensorDrv class only. The source from mt6735 or mt6595 are a bit different and obviously can't be used directly. Most of the struct can be cross referenced to the kernel source. There are two local sturct left unknown. One is for the commands sent to the kernel. The other is some info. collected from the kernel.
With the wrapper, the crash was gone but still no preview. I wrote a test HAL to dump the values in stock ROM. Guessing the values against the names was not a decent job. Fortunately, there were only a few differences. After nights of trial and error, I finally pulled everything together. Camera is working now! Video recording is still not working. Seems codec related. Some say it's not a problem "again". Hoping there will be some real solutions and helps soon...
Click to expand...
Click to collapse
Yeah after you fix that you'll get mediaserver libc fatal crashes as I do in douglas.

MOD ACTION:
Thread cleaned.
Friends, please do not lose the focus of the thread. Discussions about other issues and multiple persons posting multiple ways of solving such issues etc make the thread cluttered.
The OP is there and answering queries.
Thank you for understanding!

ggow said:
🛠 Worklist / Tasks
...
- [todo] Wired headphones not working
Click to expand...
Click to collapse
thank you, @ggow, for coming back to Fire HD 10!!! ur recent works on HDX makes me thinking about it but its still >5yo tab.
for the wired headset, there is a fix available already: https://forum.xda-developers.com/t/...4-1-26-sep-2019.3973703/page-29#post-81763775
i have used it on both HD8 and HD10. hope it saves u some work!

Related

[native] [ubuntu] [rom] [kernel] Native Ubuntu Linux for T-Mobile LG V10

Hello everybody,
I have developed a working, native booting Ubuntu MATE 18.04 system for the T-Mobile LG V10. This device has not received enough attention in the development community, so I decided I'd go all out and get a fully open source Linux distribution to boot and run on this underestimated device. I have gotten most of the basic features working, except for Wi-Fi and audio output. I think this could be a great foundation for developing a fully functional GNU/Linux based operating system that can harness the true functionality and power the LG V10 offers.
As of now, this is what works:
- Display (fbdev , no hardware acceleration)
- Touch (Xorg natively supports it)
- Modem/ADSP/Venus subsystems brought up
- Microphones (using Alsa usecase files from LG G4)
- USB OTG ethernet
- rt2800usb wireless driver backported (connect with NetworkManager)
- Stable systemd support
- Udev detects charging/battery percentage
To do:
- Enable hardware acceleration with freedreno DRM/KMS
- WiFi working
- Get HDMI slimport output working with Xorg and freedreno
- Get audio output working
- Offset the second screen in Xorg
- Make ADSP sensors accessible to userspace
- Screen rotation
- Camera blob bringup with libhybris
- Mainline kernel support
For more information, read the README.md on my GitHub repository
If you want to contribute, or have a look at what I have done, here are the links to my GitHub repositories, and the rootfs:
Boot Images: github.com/doitaljosh/native-ubuntu-mate-pplus
Ubuntu MATE 18.04 rootfs archive: drive.google.com/open?id=1AjhBs_9HLO0KC3bFpka2ewpuJTmigimK
Kernel Source: github.com/doitaljosh/android_kernel_lge_msm8992
hey what does this do. that stock kernel don't do?
If you want an extra tester, I have another v10 laying around that could be used for stuff.
great effort. thanks for your time and contribution. i am waiting for my v10 to arrive from ebay. will test.
I'm getting an issue where when the tar is extracting it'll stop and say it was killed. I know that I didn't kill it, as I left it alone while it was extracting. Or is it just it's say of showing that it's done?

[TREBLE][addison][OFICIAL][PIE][9.0.0_r38]XPerience 13.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"
}
XPerience is a free, community built distribution of Android 9.0.0 (pie) which greatly extends the capabilities of your phone.
This project are based on CAF
The XPerience Project since 2011
MOTO MODS AREN'T COMPLETELY SUPPORTED AT THIS MOMENT​
Code:
#include <std_disclaimer.h>
/*
* 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.
*/
NOTE: READ this PLS
Please don't ask for etas
[*] Please don't report same bugs all time
Report with logcat and dmesg
Screenshots representative only
Click to expand...
Click to collapse
Features:
Custom tiles (Caffeine, HeadsUP,Usb tether)
Power menu customizations (reboot to recovery one touch in advanced reboot, for bootloader do a long touch)
Quick Unlock
FaceUnlock (need support from google apps)
Disabled Power menu in lockscreen
Alessa kernel tweaker
weather in lockscreen
SmartPixels (Oled display only)
Custom fonts Manager
Theme appart of white,dark, black (added LUNAR and AITA)
Bionic optimizations
NightFall Launcher our fork of Launcher3
Per-App Thermal control
3 fingers swipe take screenshot
OneHand Mode
Allow to use 4g icon instead of LTE
Show Auto-BT while driving setting
Configurable 0, 90, 180 and 270 degree rotation
Disable Quick Settings on secure lockscreen
//Devices with HW buttons
Disable Home key when calling
HW Keys customization (remap your hardware buttons)
Disable Hardware keys
Hardware key ilumination timeout
Accidental Touch
// Motorola z play
Moto Mods support (not complete )
WORKING:
Boot
Rild
LTE/3G/2G
bluetooth
Camera
camcorder
MTP
Sensors
Led
Wi-Fi
MUSIC
sounds
Videos
Moto mods ( battery, all mods without audio routing)
sepolicy enforced
not Working
VoLTE Sh!t
HostingSharedBox
Source forge
Basketbuild
Or the web
http://thexperienceproject.com​
GAPPS:
from
Opengapps.org
OUR CUSTOM TWRP TREBLE needed
twrp-3.3.1-0
old
TWRP-3.2.3-addison-Unnoficial.img
Changes in second post
Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
XPerience version:
Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
If you like my work, you can buy me a coffee , coke or any drink all donations are appreciated.
Ór
https://www.paypal.me/TheXPerienceProject ​
XDA:DevDB Information
The XPerience project, ROM for the Moto Z Play
Contributors
TeamMex
Source Code: https://github.com/TheXPerienceProject/android_kernel_motorola_msm8953
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: unlocked bootloader, oreo bootloadeer
Based On: AOSP
Version Information
Status: Testing
Created 2018-08-21
Last Updated 2019-06-23
Reserved
XX means no date yet
13/05/2020
Merge tag 'LA.UM.7.1.r1-17400-sm8150.0 '
Added rotation degrees (that functionality was added in the beginning and i forget to add the option in menu)
Merge kernel tag 'LA.UM.7.6.r1-07400-89xx.0'-->
msm: camera: jpegdma: Fix uninitialized variable
Merge "msm: camerav2: isp: Removed closing of isp node"
Merge "net: sit: fix memory leak in sit_init_net()"
Merge "asoc: msm-compress: Replace goto with return in case of invalid value"
Merge "asoc: msm-compress: Add missing mutex initialization for pdata"
Merge "msm: vidc: avoid OOB write while accessing memory"
msm: camerav2: isp: Removed closing of isp node
Merge "net-sysfs: Fix mem leak in netdev_register_kobject"
Merge "msm: vidc: remove additional checks in response_handler"
msm: vidc: remove additional checks in response_handler
msm: vidc: avoid OOB write while accessing memory
asoc: msm-compress: Replace goto with return in case of invalid value
asoc: msm-compress: Add missing mutex initialization for pdata
net: sit: fix memory leak in sit_init_net()
xfrm: policy: Fix out-of-bound array accesses in __xfrm_policy_unlink
net-sysfs: Fix mem leak in netdev_register_kobject
asoc: msm-compress: Add lock in controls _put() and _get() callback
msm: pcie: Use local variable for manipulation
11/01/2020
Kernel updates
* tag 'LA.UM.7.6.r1-06700-89xx.0':
rmnet: Add support for bridging rmnet_data
dsp: avtimer: validate payload size before memory copy
msm: ipa: add additional checks to prevent use-after free errors
fbdev: msm: Avoid UAF in mdss_dsi_cmd_write
soc: msm-pcm: fix missing mutex unlock while exit
msm: adm: Add error check to avoid memory overread
qseecom : Clear client handle after unmap the resources
PM / devfreq: gpubw_mon: Add null check for governor private data
asoc: msm-routing: Fix array out of bounds issue
ASoC: Fix possible overflow in routing driver
msm: adm: Fix memory overread in adm callback
drm/msm/hdmi-staging: Fix Buffer Overflow
soc: msm-pcm: Add mutex lock to protect prvt data
soc: msm-pcm: Added lock in controls _put() and _get() callback
diag: Validate msg source length to prevent out of bound access
qseecom: check invalid handle for app loaded query request
drm/msm/dsi-staging: Add length check before copying to user space
* tag 'LA.UM.7.6.r1-06400-89xx.0':
msm: kgsl: Make the "scratch" global buffer use a random GPU address
msm: kgsl: Use a bitmap allocator for global addressing
msm: kgsl: Execute user profiling commands in an IB
netlabel: check for IPV4MASK in addrinfo_get
defconfig: msm: Disable EXT2 and EXT3 FS configs for MSM8937/53
msm: kgsl: Verify the offset of the profiling buffer
icnss: Add check on msa region
msm: kgsl: Change data type for GPU ib vote
--Rom changes--
do a vndk-sp copy of libandroid this should fix the camera on android 10 GSI
Add extra vndk v27
03/09/2019
Kernel updates
Merged LA.UM.7.6.r1-05900-89xx.0
Some parts of LA.UM.8.6.r1-01900-89xx.0 (Android Q changes)
Preparations for Q
Rom side
LA.UM.7.1.r1-16900-sm8150.0
15/08/2019
Rebased branch over LA.UM.7.1.r1-15800-sm8150.0
overlay: CarrierConfig: Enable IMS services in Brazil from alberto97
Merged all changes in kernel from alberto 97
the last build until Q arrives (i will try to bring Q)
02/08/2019
add camera firmware from PPK29 deen
update adreno firmware from deen PPKS29.68-16-34-5
Widevine - DRM from deen PPKS29.68-16-34-5
update PERF and iop from deen PPKS29.68-16-34-5
fix moto actions
ship Qcom AT from deen PPKS29.68-16-34-5
: drop whitelisted games
FEATURE_OPENGLES_EXTENSION_PACK support string config file
Fixed Google Drive issue
26/07/2019
MErge tag 'LA.UM.7.6.r1-05500-89xx.0' in to kernel xpe-13.0
wifi: Update WPA3 support overlay config for legacy devices
-- Set WPA3 support overlay config to false for unsupported legacy chipsets.
Migrate to androidx LineageActions
surface hang up when screen on and screen off
frameworks: Add unlinked ringtone and notification volumes
Prevent surfaceflinger gets swapped to zram
Expanded volume bar
Moved to VNDK 28 (Tested some GSI like oxygenOS and works fine without issues )
copy libbinder under VNDK and libcutil under VNDK-sp to satisfy oreo camera blobs
Move some hidl under vendor
Kernel compressed in LZ4 + LZMA ramdisk
xx/07/2019
Merge tag 'LA.UM.7.3.r1-07900-sdm845.0' into xpe-13.0-caf (Jun security patch)
Removed prebuild busybox please install busybox for ndk from Magisk
Merged ASB-2019-06-05_3.18 in kernel
03/07/2019
Implement Yunikon our webview based browser (take as basis Jelly)
Conditionally disable unencrypt for OTA
Add more missing permissions for Google apps :/ again
Created overlay for managed profiles this should fix Android for Work
-- The ManagedProvisioning xml's were moved in Pie.
Also added missing managed_device and managed_user xml's.
This fixes 'Android for Work'.
01/07/2019
Removed libbinder from vndk this make camera crash
Conditionally disable uncrypt for ota
in last build from today i removed a lot of sepolicy cuz that was marked as neverallow but make a lot of issues so i added it again
fixed some services
28-29/06/2019
Tethering issue fixed (AGAIN)
Set HAL3 disabled if you want it enable it using magisk module
Some booting issues
Fixes in black theme
24/06/2019
Add vibration motorola hal to silence MdFmwk crash
add more sepolicy to allow health and others services to rw
A lot of sepolicy remove neverallows
Return Pocket Judge
update sdm and adreno from LA.UM.7.5.r1-03700-8x96.0
addison: move permission set to early-boot
vibrator hal service launched in rootdir/init.rc boot trigger will fail if
given permission have not been set correctly. This CL is to fix such
racing conditions.
addison: set on fs persist/battery permission to give time to read/write the information and not
failed to open
add libc copy to vndk it should help to boot in some GSI's (Please test )
Fix WFD (Wifi display Qcom implementation)
Fixed night light
18/06/2019
Merge "LA.UM.7.6.r1-05300-89xx.0" tag in to kernel/motorola/msm8953
Updated Versioned VNDK
Add libbinder to VNDK-SP-$(BOARD_VNDK_VERSION)
Add libcutils to vndk-sp to silence some warnings in sockets
Per-App Thermal controller configurable from app info
Fixed Backup tool (was broken in the last changes for System as root commits needed by lavender)
Disable Quick Settings on secure lockscreen
Per-APP ThermalControl
One Hand mode
Add three-fingers-swipe to screenshot
Add Flashlight blink on incoming calls (like iOS)
Allow to use 4G icon instead of LTE
Fixed backup tools
VoLTE icon toggle
Import DIRAC framework from MIUI
Added Battery mod reader apk (To read battery mod stats Still working to make it enable the function to activate or deactivate mod like eficiency mode)
add some props for moto mods (Still no lucky xD)
Implement Pixel 3a fingerprint to bypass CTS due to our addison fingerprint is rejected
Extra copy of [email protected] to vendor to fix wifidisplay in AOSP roms
Add extra copy of [email protected] to vndk to fix Wifi issues in AOSP gsi
Add extra copy of [email protected]
13/06/2019
SchedAlessa: Fix CPU overheatting
SchedAlessa: Use idle_calls counter of the remote CPU
For single policies however, the current
code uses the local CPU when trying to determine if the remote sg_cpu entered
idle or is busy. This is incorrect. To remedy this, compare with the nohz tick
idle_calls counter of the remote CPU.
SchedAlessa:Reduce Frequencies Slower
Disable SPI: CRC errors on SPI bus usually means there is something wrong with the
hardware(unstable voltage, wiring, etc).
Disable SPI CRC in favor of improving performance as the cost of
detecting hardware errors are too high, and not all that useful.
Fix Wifi in some GSI's (Like MIUI , AOSP, etc)
Fixed Camera in GSI's now you only need to flash miui fix to get booting the miui GSI
Vibration and sensors hals changes from alberto97
08/06/2019
Fixed Charge_only_mode
updated some blobs for rild
removed qcrild
added android Q battery style
update GPS stack and blobs from LA.UM.7.6.r1-04300-89xx.0
enable some UX optimizations
Updated apn's and sensitive apn
Updated display audio and media hal to LA.UM.7.6.r1-04800-89xx.0
Fix User cannot listen to a VVM that has been saved onto the device via quickoffice
Fix Libcore CTS fail
This CTS issue was introduced by (CR). I inserted 'audio/mp3'
before "audio/mpeg" according to the alphabetical order, but CTS has the hardcode
test that need "audio/mpeg" to be the default mime type of '.mp3' extension.
Solution: Adjust the position of 'audio/mp3' to avoid the CTS issue.
Add a sanity check against the file name because Android hardcoded the file.encoding to UTF-8, thus for any filename other
than that, we have to ignored it since we will have no idea on what the encoding it would be.
Added lockscreen charging animation.
lmkd: ignore the pressure if we still have enough file cache
storaged: ignore the SIGPIPE, or storaged will be crash.
don't kill b-service too early under medium pressure
25/04/2019
Returned to old rild, CNE , GPS
23/04/2019
CPU Overclock 2.2ghz (it can be overclocked to 2.4 ghz but 2.2 is ok)
Gpu overclock to 700mhz
Upstreamed to 3.18.140 [EOL]
increase usleep_range in camera actuator to give more time to power up
Revert some adsp changes some of them are not compatible with ADSP blobs we use (Oreo blobs)
--Revert "ASoC: msm: add support for AVS version check"
--ASoC: revert P qcom changes to keep O ADSP compatibility
--Revert "ASoC: msm: qdsp6v2: add 32bit capture support in dai driver"
--Revert "ASoc: msm: Enable support for 32 bit format and 384Khz"
--Revert "ASoC: msm: qdsp6v2: add support for latest version of media format command"
msm: camera: isp: Fix drop frame due to reg update miss
arm64:check valid low & highmem addr before saving cpu_suspend context.
Merge prima wlan LA.UM.7.6.r1-04800-89xx.0
--ROM
Merge branch LA.UM.7.3.r1-07800-sdm845.0
26/04/2019
Fixed boot (forget to add sensors source my bad)
merged security patch of feb 05 aka LA.UM.7.3.r1-07400-sdm845.0
some fixes
Hotspot fixed
Updated thermal from deen PPK29.68-16-21 (and use prebuilt thermal.msm8953)
Updated ATFWD from deen PPK29.68-16-21
Updated perf from deen PPK29.68-16-21 and OP3 PKQ1.181203.001
Fixed some permissions to qcrild (please test with the new rild again and take some logs with
Code:
adb shell logcat -b radio > radio.txt
Build Services-ext
Added support to change font from settings->Display->font
I added some fonts i will add more soon
Adjust some perf changes
Download will be pushed tomorrow I hope
FROM now user build are really different from my personal builds
12/04/2019
--- Kernel side ---
SchedAlessa 2.1.4 updatesBackporting changes from SchedUtil from 4.9 kernel instead of modify SchedUtil I preffer to update SchedAlessa)
* - Use >= when aggregating CPU loads in a policy
* - Switch from sprintf to scnprintf
* - Add trace point for get_next_freq
* - Avoid processing certain notifications
* - Return to FIFO
* - track hi_speed and pl from upstream
* - schedalessa:Change to use WALT Load based
* - Add hispeed load tunable
* - cpufreq: Return 0 from ->fast_switch() on errors
* - Hard-code rate-limit thresholds
Merge kernel 3.18 tag LA.UM.7.6.r1-04500-89xx.0
Merge prima wlan LA.UM.7.6.r1-04500-89xx.0
Upstream kernel to 3.18.138
Fix ANDROID: qpnp: fg+smbcharger: implement Linux cycle count we use QPNP_SMBCHARGER_MMI and not QPNP_SMBCHARGER
msm_thermal: ignore sensor 19
--- Rom Side ---
Return battery learned
Reverted to old RIL and GPS (if not works dont ask for Fixes)
Implemented core source from motorola for mods (?)
03/04/2019
add exfat lib
vold: add support for more filesystems for public storage
* Add exfat and ntfs support based off f2fs and ported to use
fuse
* Add support for both along with f2fs and ext4 to PublicVolume
* Also attempt to mount any volume if it's been determined that the kernel supports it
vold: ntfs: Use strlcat
vold: Fix fsck on public volumes
vold: Support internal storage partitions
vold: Honor mount options for ext4/f2fs partitions
vold: Mount ext4/f2fs portable storage with sdcard_posix
vold ext4/f2fs: do not use dirsync if we're mounting adopted storage
Fix the group permissions of the sdcard root.
healthd: make periodic battery status a debug message
Kernel optimizations(big changelog so i will write it later or read it here https://privatebin.net/?8a926e288ddb4507#xLieO9avhqWhjLllpneJh/RW2DM+8gbuxEiVSN7DIzE=).
Update wlan to LA.UM.7.6.2.r1-07400-89xx.0
ipv6: add option to drop unsolicited neighbor advertisements
ipv4: add option to drop gratuitous ARP packets
testing radio props (posted in #761 comment)
addison: performance_profiles: set conservative in power saving profile
addison: add ipa data/vendor permissions
addison: add system property to set AudioFlinger client heap size
Addison: more sepolicy
addison: set battery capacity to the correct value 3510mha (this will fix some issues about battery recognized as 4800mha 4000mha etc)
Backport z3fold from Sony devices (4.4 kernel)
-z3fold, a special purpose allocator for storing
compressed pages. It is designed to store up to three compressed pages
per physical page. It is a ZBUD derivative which allows for higher
compression ratio keeping the simplicity and determinism of its
predecessor.
This patch comes as a follow-up to the discussions at the Embedded Linux
Conference in San-Diego related to the talk [1]. The outcome of these
discussions was that it would be good to have a compressed page
allocator as stable and deterministic as zbud with with higher
compression ratio.
To keep the determinism and simplicity, z3fold, just like zbud, always
stores an integral number of compressed pages per page, but it can store
up to 3 pages unlike zbud which can store at most 2. Therefore the
compression ratio goes to around 2.6x while zbud's one is around 1.7x.
wlan_hdd_cfg80211:use active scan
20/03/2019
Track IPACM LA.UM.7.6.2.r1-07300-89xx.0 (this will help us with tethering still dead)
update ramdisk (ims related services from LA.UM.7.6.2.r1-07300-89xx.0)
addison: Update privapp-permissions-qti from LA.UM.7.6.2.r1-07300-89xx.0
addison: update qti_whitelist from caf tag LA.UM.7.6.2.r1-07300-89xx.0
addison: add some ims props (TESTING)
Update thermal config
updated sepolicy
rever: "addison: force HAL1 for motorola camera"
merge LA.UM.7.6.2.r1-07300-89xx.0 tag in kernel
Motorola HEALTH from BECKHAM_PPW29.131_27_1 (removed)
A lot of sepolicy related to motomods
Regenerate Manifest,xml
Moto mod tile
Updated Mod Manager and ModFmwkProxyService
Set the correct mod platform version
Moto mods are now placed in connected devices
13/03/2019
--Kernel--
ipv6: add option to drop unicast encapsulated in L2 multicast
ipv4: add option to drop unicast encapsulated in L2 multicast
(fix wpa_supplicant: nl80211: Failed to open /proc/sys/net/ipv4/conf/wlan0/drop_unicast_in_l2_multicast: No such file or directory)
Re-Enable RFKILL_INPUT (this fix multiexistence of BT + wifi in the new bring of the kernel i forget to re-enable)
--Device related--
Add Qcom WFD implementation (due to google in android P has removed it from the source)
Updated CNE, QMI (Qualcomm Framework),IMS, Radio, Motorola Ril from P blobs (tissot tissot_sprout:9/PKQ1.180917.001 and Deen PPK29.68-16-3 ) (Please test VoLTE)
Add QC RIL service support
Hostapd sepolicy
addison: force HAL1 for motorola camera
Add legacy wifi paths for GSI (untested)
Props to enable WFD
Update CarrierConfig overlays for P
addison: add hbtp sys perm
addison: Sepolicy for new RIL
addison:libmmosal_proprietary needed by wfd
Addison: Update CNE
Addison: Use tether automatic upstream selection
10/03/2019
Re-Enabled Burning protection
NetworkTraffic updates
Updated XPERIA Launcher
NightFall Launcher added Icon pack support
NightFall: Added grid size and icon size support
fwb:Implement substratum service
sepolicy: Sepolicy for substratum service
fwb:Fix theming issues in substratum
Removed RetroMusic due to a lot Ads
RainbowUnicorn: Implemented Alessa (WIP)
Updater: Updater: Implement auto update check interval preference
Implemented Our notes app
Implement Busybox
06/03/2019
Hex-Edited camera libs fix camera on GSI (not tested yet)
Re-Implement EAS
Updated SchedAlessa}
-- schedalessa: Use capacity_orig_of instead of capacity_of in overutilized
-- SchedAlessa: Cache tunables on governor exit
Dynamic Sched boost
Update perf profiles for FK manager and add support for EAS
Optimize EAS scripts.
SchedAlessa: Allow thermal throttling to change cpu freqs
addison: add hostapd config files from CAF LA.UM.7.6.2.r1-07100-89xx.0
A lot of sepolicy
Set Sepolicy Enforced
01/03/2019
Recommended GCAM https://f.celsoazevedo.com/file/gcamera/MGC_6.1.021_XCAMBase_F1_v2.apk
or this : https://f.celsoazevedo.com/file/gcamera/MGC_6.1.021_Potter_v7.1_san1ty.apk both works
Added MZPGreenTintFix for GCam Credits to Juniiim for the module and Savitar for the original work (https://forum.xda-developers.com/moto-z-play/themes/magisk-modules-mzpgreentintfix-gcam-t3870280)
HAL 3 enabled by default
Added Sepolicy for offline charger
Merged LA.UM.7.3.r1-06900-sdm845.0 it have Dec 05 security patch
Added Performance profiles (configurables using Franco Kernel Manager)
screenshost:
Hex-edit libmmcamera2_isp_modules for P's mutex restrictions
-- Google has been tightening up mutexes by disallowing calling
pthread_mutex_destroy on an already destroyed mutex in P
-- This normally isn't an issue, but Qualcomm, in their infinite
wisdom, decided to destroy a mutex in a loop in isp_module_stop_session
when they were freeing some related memory allocations
-- This results in a SIGABRT in mm-qcamera-daemon from a
__fortify_fatal call in HandleUsingDestroyedMutex in libc
-- To work around this, phtread_mutex_destroy and phtread_cond_destroy
moved outside of the loop so they only calls 1 time (Credits to @Juniiim for the modified lib )
*Based on kuntao implementation so credits too to Paul Keith "javelinanddart" )
Added extra copy of [email protected] to vendor libs
Added a extra copy of [email protected] to vendor due to aosp hals wont work with CAF rom (in this case our vendor is from caf )<(Test Needed)
Dropped [email protected] (Battery learning kanged from marlin. It needs a better implementation and i dont have the time to deal with it)
Removed tetheroffload from manifest (untested) seems to broke hostopt
Pre-OPtimize SystemUI
Update WCNSS_qcom_cfg.ini from deen's PPK29.68-16-8
Fixed UI issues (Related to theming like black icons in dark themes)
Removed TetherOffload from manifest this breaks Tethering (cause reboot of the device)
wifi: Enable Softap ACS and 11ac (Needed by hostpot. (for softap operations))
Code:
02-28 15:31:32.842 29060 29060 E hostapd : ACS: Unable to collect survey data
02-28 15:31:32.842 29060 29060 E hostapd : ACS: All study options have failed
02-28 15:31:32.842 29060 29060 E hostapd : Interface initialization failed
02-28 15:31:32.842 29060 29060 I hostapd : wlan0: interface state ACS->DISABLED
02-28 15:31:32.842 29060 29060 I hostapd : wlan0: AP-DISABLED
Implemented AITA and Lunar themes (mine themes)
26/02/2019
OnTheSpot support
Moto Mods support (efficiency and battery status still broken)
added sepolicy missing for moto mods
Implement better Screen Zoom levels
Use this for Mod Battery status (https://forum.xda-developers.com/moto-z/themes/app-battery-mod-percentage-t3575753 )
VNDK: Added [email protected] and [email protected] for NFC and camera (in phh's the camera crash due to CANNOT LINK with those files)
VNDK: Add libsensor due to missing symbols in AOSP variant of that lib
Fixed offline charger
05/02/2019
*Rom Things*<
Rebased over SDM845 branch
Merged LA.UM.7.3.r1-06700-sdm845.0
libril: Fix manual network selection with old modem
set flag TARGET_USES_OLD_MNC_FORMAT needed by libril
Drop ipa-cfg-mgr
* Kernel things *
Rebase kernel over alberto's one (Merged all the patches from my kernel)
Dropped EAS support nothing changed anyways
-backport kernel: Add API to mark IRQs and kthreads as performance critical
genirq: Introduce IRQD_AFFINITY_MANAGED flag
genirq: Add IRQ_AFFINITY_MANAGED flag
firmware: qcom: Remove debugfs dependency from tz-log driver
init: Don't force DEBUG_KERNEL in EXPERT mode
Reverted QNovo interface seems to not work properly
Merged LA.UM.7.6.r1-04000-89xx.0 branch in the kernel
Fixed bootloop issues
Seems good now for release please review and send logs and some info about "how to reproduce your bug "
04/01/2019
Merge LA.UM.7.2.r1-05400-sdm660.0 Branch (It will be rebased over sdm845 branch)
Restart motorola camera service too
Custom Qperformance.jar UxPerformance.jar
Fixed VNDK for treble compatibility (now this can work as expected without patches)
Enabled RRO's for GSI's
Do extra copy of NFC to vendor
Moto mods enabled (Battery is working no efficiency mode only normal mode attach the mod and restart the device battery percent of motomod is not working )
Added some VoLTE changes (Untested here cant be used)
pin the Home application in pinner service
Minimal optimizations
Updated a lot of blobs from deen PPK29.68-16-8
--GPS,SMD,Audio,ADSP,SVCE
added [email protected] (Battery mod)
Merge speaker changes from alberto's AOSP 9.0
26/11/2018
Merge LA.UM.7.2.r1-05300-sdm660.0 Branch
Merge sepolicy "LA.UM.7.6.r1-03600-89xx.0"
BT: Fix out-of-bounds reading in btm_ble_vendor_capability_vsc_cmpl_cback
BT: Run the wakelock JNI callbacks on the JNI thread
Fix "Disable Absolute Volume" Bluetooth developer option
Nightfall Launcher (my launcher based in quickstep)
updated gallery
Addison: Use ro.crypto.state to handle non encrypted devices and restart camera and wifi HALS (to fix some issues)
17/11/2018
Merge LA.UM.7.2.r1-05300-sdm660.0 Branch
Added a lot of sepolicy's to fix a bunch of things
Added Smart Pixels (you can disable some pixels to save battery (under settings->XPerience Settings->Misc->SmartPixels)
IOP/UXE: This change is to enable the IOP and UXE
IOP : Adding support for UXPerf Class
BoostFramework: Clean up code
Fling/Pre-fling Boost: Call perf boost from System Server context
Add Game boost & modify launchboostv2 invocation.
Add QPerformance and UXPerformance
Set ro.vendor.extension_library - To communicate between perfd and thermal-engine
BT: Adding aptX-Adaptive codec entry to Framework
Fix Framework Reboot due to invalid display.
Bluetooth: Check for BLE on state after gatt service up
Wallpaper is half black after rotating quickly
BatteryMeterView: Fix glitch with percents
BatteryMeterView: Fix PowerSave mode percents and use same method for charge
Fix a NPE in BatteryStatsImpl
Prevent NFE in SystemUI when parsing invalid int
base: SystemUI: Allow user to add/remove QS with one click
SettingsLib: Allow Skia Vulkan to be used as HW renderer
Wifi: Check for WiFiService's existence before its access
SystemUI: add navbar layout inversion tuning
Reserved
Link off to Dowloads
LINK fixed
Is volte working ???
Only Oreo bootloader will work with this rom?
Wysłane z mojego XT1635-02 przy użyciu Tapatalka
sebx_g1 said:
Only Oreo bootloader will work with this rom?
Wysłane z mojego XT1635-02 przy użyciu Tapatalka
Click to expand...
Click to collapse
you can use N too but I recommend to move around oreo.
milind07 said:
Is volte working ???
Click to expand...
Click to collapse
NO
The auto brightness is working?
Projector work or not yet? Love your roms by the way.
sillycat98 said:
Projector work or not yet? Love your roms by the way.
Click to expand...
Click to collapse
Don´'t expect moto mods for some time.
Great, will try it later, hopefully. How can I restore the google framework ID from the old backup (xpe on 8.1 base)?
Edit: Both download-server are very fast, very great 11MB/s, my Z Play-Wifi at 5GHz at his limits :laugh: There is no more possible. For all with 100MBit/s (12.5MB/s) very sad
hi i use oreo rom but it tell me i don't have the good version of bootloader ?
did you say why ?
Amazing work, I'll try it out later today.
Is this 64 bits?
When I flash the gapps,the phone is in the second startup screen,cannot go on
fooby_sjz said:
When I flash the gapps,the phone is in the second startup screen,cannot go on
Click to expand...
Click to collapse
Not tested yet, but I use stock for normal. What do you use?
TeamMex said:
Don´'t expect moto mods for some time.
Click to expand...
Click to collapse
I figured but wanted to check, I tried the dp and didn't see any must have features, so I guess I'll stick with the 8.1 version for now. Thanks for all the work you do for the play, you're the reason I'm glad I bought this phone.
Forced encryption status? It's not on the list of working or non-working features.
I'm in the same boat as sillycat98, If it weren't for you, I wouldn't have enjoyed this phone as much as I have. You've done some great work making this phone great.
TeamMex said:
Don´'t expect moto mods for some time.
Click to expand...
Click to collapse
Hey just a suggestion, maybe post the mods status really big in the announcement so that people who don't search the whole thread don't ask the question every 5 min. After all, you are the mods master and the reason why I hang on to my Z-play! Thank you!

arter97 Pie Software Collection for the Mi Pad 4

{
"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"
}
arter97 Pie Software Collection for the Mi Pad 4​
/* Summary */
Stock software stack on this Mi Pad 4 is horrendous and full of retarded junks top to bottom.
This is a project to replace most of the software stack on the Mi Pad 4.
This is done by reworking the entire kernel and the vendor image, and providing a custom TWRP recovery with f2fs support.
Please read the entire post to get an idea how to use as this ain’t like other ROMs/kernels on this forum.
(Please don’t quote this entire post and spam the thread.)
/* System */
You may use Android Pie-based GSI images. Oreo is not supported. MIUI is obviously not supported. (Are you f***ing serious?) Compatibilities between other source-built ROMs targeting clover(Mi Pad 4) specifically is not guaranteed and most likely to cause issues.
You can also use Paranoid Android for Mi Pad 4, which is recommended for best performance.
/* Kernel */
The kernel is fully rebased to the latest Pie CAF tag, which is a different base from the stock Oreo CAF tag, not to mention most of Xiaomi’s ultra-poor-quality codes are gone.
- To mitigate the horrendous touch latency, numerous touch panel optimizations were made.
- Mi Pad 4 is using eMMC instead of UFS. Numerous changes were made to improve its performance including the enforcement of f2fs filesystem and optimizations to CFQ I/O scheduler.
- 3/4 GB of RAM is quite insufficient these days. zram is activated with updated LZ4 compression algorithm to provide a better memory management along side revamped lowmemorykiller.
- Touch boost is set aggressively due to the reality of most ROMs lacking QPerformance. This improves responsiveness.
- Kernel module support is disabled to make it a bit lighter.
- WireGuard is supported.
- Automatically sets correct Android version and security level to prevent booting issues caused by keymaster.
- Double-tap-to-wake is enabled by default.
- A whole lot more that I forgot.
/* Vendor */
For the best compatibility with Pie ROMs, Pie vendor must be used. To make this happen, the entire vendor firmware is ported from the Mi A2. This process took me weeks to debug and make it stable to this point.
Since this is the only one of its kind on the Mi Pad 4, the software experience with this vendor image will be quite different from other ROMs.
Also, an overlay is integrated to give the correct corner overlay for rounded corners.
Unfortunately, it’s not bug-free, but way beyond usable. Bugs will be listed below.
/* Recovery */
As I said, f2fs is enforced. Reason for this will be explained below.
You must format your userdata partition(erasing everything on the device) to f2fs before using this project.
You cannot use existing TWRP for 2 reasons:
a) The TWRP kernel won’t support f2fs.
b) TWRP’s mkfs.f2fs tool is outdated.
A custom TWRP is also provided, powered by my kernel and the latest mkfs.f2fs tool. You must use it to format /data to f2fs before using this project.
/* Harmony */
The whole kernel and the vendor image is meant to be used together. If you mix one another(e.g. using my kernel on other vendor image or vice versa), you will definitely encounter issues. Please don’t.
To make the experience consistent and since you’re locked with the kernel/vendor combination anyways, I decided to force f2fs. Please be extremely cautious when you want to test out other kernels that claims to support f2fs. If the f2fs version isn’t inline with my kernel, you may experience random panics, or even worse - data corruption.
It’s extremely recommended for you to wipe the entire /data back to ext4 if you want to switch from using this project.
/* Instructions */
You must be familiar with fastboot.
- Download kernel, vendor and TWRP from the link below.
*.img.xz is for fastboot. Extract the .xz files before feeding it to fastboot. *.zip is for TWRP.
- Download an Android Pie based GSI of your choosing.
- Flash kernel by ‘fastboot flash boot /path/to/kernel/image’.
- Flash TWRP by ‘fastboot flash recovery /path/to/recovery/image’.
- Flash vendor by ‘fastboot flash vendor /path/to/vendor/image’. This process will take about 5 minutes(it took 275 seconds for me).
- Enter TWRP by ‘fastboot boot /path/to/recovery/image’.
- Do ‘Wipe > Format Data’. This will automatically wipe to f2fs.
- Follow the instructions you got from the GSI ROM developer and flash system image.
- Reboot.
- Leave feedback.
Note about Magisk
Due to a (supposed) Magisk bug with f2fs. You must flash Magisk after the first initial setup to avoid memory leaks(which ultimately causes the kernel to shutdown). After Magisk is installed, reboot again after confirming Magisk Manager is installed.
/* Disclaimer */
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this project 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.
/* Warning */
I won’t be granting permissions to redistribute or extract files from this project to serve others, without actually contributing something to this project.
You will be reported to XDA forum moderators.
Making mirrors, re-uploading to another servers are also prohibited with no exceptions.
/* Thanks to */
TheCrazyLex
xboxfanj
joshuous
jjajjaroni - for reporting bugs ahead of public release
nathanchance - for android-linux-stable
/* Downloads and links */
arter97.com
Kernel source
XDA:DevDB Information
arter97 Pie Software Collection for the Mi Pad 4, ROM for the Xiaomi Mi Pad 4
Contributors
arter97
ROM OS Version: 9.x Pie
Version Information
Status: Beta
Created 2019-01-13
Last Updated 2019-03-07
/* Bugs */
- Phone calls won't work
- Fingerprint sensor and GPS on the Mi Pad 4 Plus doesn't work
- For the Wi-Fi variant, the device may get confused and think it’s a phone. Not a big deal.
- Didn’t notice anything else.
/* Changelog */
20190810
This update is made with Paranoid Android in mind.
Go checkout the updated Paranoid Android thread.
Vendor image:
Base firmware updated from V10.0.8.0.PDIMIXM to V10.0.10.0.PDIMIXM
Camera hacks removed and reworked to fix camera on many ROMs
Kernel:
Fixed a commit mismerge that broke deep-sleep
Linux v4.4.188 merged
Wi-Fi drivers updated to 5.1.1.73Q
Bunch of memory allocations from various subsystems were reworked to perform much better (thanks to Sultan)
32-bit vDSO added for improving performance on arm32 programs
Backported speculative page fault to improve system performance
Latest f2fs-stable merged
Switched to zswap/vnswap approach
- Ditched conventional zram swap approach and taken zswap+vnswap for more efficient memory operations
- Backported zsmalloc memory allocator from mainline
- Backported zswap compressed page cache from mainline
- Samsung's Galaxy S9 memory modifications merged for better swapping efficiency tuned for Android
- This new kernel's memory management will be drastically different from existing kernels
20190428
Vendor image:
Base firmware updated from V10.0.1.0.PDIMIFJ to V10.0.8.0.PDIMIXM
Added missing goodix touch firmware
General LTE network stability improvements
Kernel:
Various changes from Proton kernel by kdrag0n
- Use flatmem to save kernel memory usage
- Use optimized memcmp
- Optimize rbtree
- Disable erratum 843419 properly
- Delay vmstat updating interval to avoid jitter
- Disable I/O stat accounting completely for lower overheads
- Reverted a cpuidle change for possible fix for power consumption regression during sleep
- Faster crypto algorithms ported(chacha20, sha2, crc32)
A bit lower power consumption by using WFE for long delays
Add accelerated crc32 routines
Use -O3 for input drivers for avoiding overheads
Various changes made to f2fs rapid GC to make it more efficient
dirty_expire_centisecs set to 30 seconds to reduce flash wearouts and power consumption
Various changes merged from the Razer Phone 2 and Snapdragon 855
Kernel is now built with -O3 optimization flag
Use CONFIG_HZ = 300
- This changes context switching interval from 10ms to 3.33ms
- Pixel used this for years and Google recommends other vendors to do the same for fewer jitters
Removed RTB(interrupt) logging entirely
Wi-Fi drivers updated to 5.1.1.71C
Linux v4.4.179 merged
ExFAT support added(ROM-side support required too)
Idle power consumption improved
Camera drivers stability improved
LA.UM.7.2.r1-06700-sdm660.0 merged
LV.HB.1.1.5-10310-8x96.0 merged
LA.HB.1.1.8-03910-8x96.0 merged
20190223
Fixed an issue causing kernel panics to enter dump mode
Fixed a f2fs merge durp causing issues from the recovery and potentially long-term performance on daily usage
RWSEM priority-aware enhancement merged from CAF
Added CIFS(SMB) support (requested by @currowth)
LA.HB.1.1.5-11310-8x96.0 merged (some minor bug fixes)
20190221
Paranoid Android breakage from 20190128 fixed
A totally new kernel base merged - LV.HB.1.1.5-10010-8x96.0
- Total of 471 commits and about 20,000 lines of code difference
- A lot has changed ranging from scheduler, memory management, GPU and panel handling, MMC device driver, ION, audio subsystem, cpuidle, binder and a whole lot more
Kernel configuration fixed for proper scheduler operation
Background Wi-Fi HAL scanning issue fixed
LA.UM.7.2.r1-05900-sdm660.0 merged
Linux v4.4.175 merged
Mainline f2fs fixes merged
WireGuard updated to 20190123
seccomp disabled in favor of less system-call overheads
Minor issue with f2fs rapid GC fixed
IRQ balancer settings updated to include MMC and USB interrupts for better overall smoothness
20190128
Bunch of stuffs missed from previous port were applied
Fixed video recording
Booting issues fixed for ROMs with 2019 security patch level
MTP fixed
Wi-Fi drivers' inconsistencies fixed
Merged Linux 4.4.172
Enabled ULPS for lower power consumption
Merged several changes from Sultan's kernel
- GPU performance improved with corrected priority
- Faster display wake-up
- Lower power consumption
20190123
Fixed an error causing Wi-Fi to not function for some users
Merged Linux 4.4.171
Disabled MMC SPI CRC for better eMMC performance
Removed brightness remapper to fix adaptive brightness
Compiler updated to GCC 2019.01
20190114
Initial release
/* Fundraiser */
After consulting with 2 forum moderators, I got a clarification that fundraiser is acceptable with some terms like transparency and a rough timeline.
A fundraiser is opened for me to purchase a Mi Pad 4 Plus LTE. This particular variant was chosen since it's extremely likely for me to make Mi Pad 4 non-Plus LTE and Mi Pad 4 Plus Wi-Fi model supported during the process.
Within a month after the goal is met and the device is shipped, I'll work to make the current kernel and vendor image working on the Mi Pad 4 Plus LTE. After this is done, I anticipate other variants to be supported as well. In the unlikely event that it ends up otherwise, I'll work on some members on the community to get logs and test. It'll be way easier then since both LTE and fingerprint sensor will be working on my project.
While I will try my best to keep up with my goal, do note that it is entirely possible that it could not be done(which is extremely unlikely). You're making a donation after all. Just note that donation doesn't give you rights to force me to do anything with the received device.
The price for the lowest end Mi Pad 4 Plus LTE seems to be around $295 with a seller that would actually use DHL for shipment, which is required as the standard Ali-Express shipping usually takes 20~30 days.
There's another 10% importing tax in Korea on top of $295 which would make the total around $330. I've opened a fundraiser for $350 to avoid possible headaches like PayPal and bank's fee for withdrawing the money back to my credit card.
With that said, here's a fundraiser's link.
You can see the progress of the fundraiser as well.
https://fundrazr.com/81RpR8
Reserved
Reserved 4
This device took an enormous amount of my time that it clearly didn't deserve.
Thanks!
To my knowledge Mipad4 will someday get MIUI Pie. Does that effect the vendor then or are you already decided sticking with ported one?
stunned said:
Thanks!
To my knowledge Mipad4 will someday get MIUI Pie. Does that effect the vendor then or are you already decided sticking with ported one?
Click to expand...
Click to collapse
I'm certain that general experience will be still better with mine even after Mi Pad 4 gets official Pie release.
It'll allow me to fix some bugs though.
Thanks arter. That is why I made a small donation to u knowing that u were working on clover.
Hope more people do the same to keep the motivation alive!
P.S. very nice thread title ?
@arter97 few bugs i found
1)wifi seems to be broken, it's turning off by itself and can't find any networks. (broken on both PA & pixelexp GSI)
2)file transfer broken, only charging is permitted, it keeps going back to charging only (able to test only on PA, on Pixel experience GSI, cant get pass the WIFI set up)
arter97 said:
And since the vendor image is rebased, this means anything other than what I’ve used is not supported.
Mi Pad 4 LTE, Mi Pad 4 Plus, Mi Pad 4 Plus LTE model is not supported. Only Mi Pad 4 Wi-Fi model is supported.
Click to expand...
Click to collapse
Hope you will have time and possibility to support mi pad 4 plus version in near future nice done.
Thank you for you work with this (weird) device!
- Performance seems to be so so good, at least for now, the touch latency also seems to be better.
- Wifi is stable for now (It didn't work on the first boot, but I rebooted and it worked).
- File transfer works randomly for me (I'm trying to get logs and dmesg right now).
And just a little of OT: What do you think about zstd? I was using that algorithm with a flash kernel in Taimen and, in my humble opinion, it works very well, maybe it's a placebo, but I think multitasking was a little better.
PS: best post name evear, lol.
onliner said:
Thank you for you work with this (weird) device!
- Performance seems to be so so good, at least for now, the touch latency also seems to be better.
- Wifi is stable for now (It didn't work on the first boot, but I rebooted and it worked).
- File transfer works randomly for me (I'm trying to get logs and dmesg right now).
And just a little of OT: What do you think about zstd? I was using that algorithm with a flash kernel in Taimen and, in my humble opinion, it works very well, maybe it's a placebo, but I think multitasking was a little better.
PS: best post name evear, lol.
Click to expand...
Click to collapse
I am stucked.
onliner said:
Thank you for you work with this (weird) device!
- Performance seems to be so so good, at least for now, the touch latency also seems to be better.
- Wifi is stable for now (It didn't work on the first boot, but I rebooted and it worked).
- File transfer works randomly for me (I'm trying to get logs and dmesg right now).
And just a little of OT: What do you think about zstd? I was using that algorithm with a flash kernel in Taimen and, in my humble opinion, it works very well, maybe it's a placebo, but I think multitasking was a little better.
PS: best post name evear, lol.
Click to expand...
Click to collapse
zstd is ratio oriented algorithm. lz4 is speed and latency oriented algorithm.
Unless you're really starving on memory like Samsung, using zstd for swap is a really bad idea.
For those having Wi-Fi issues, I need an actual logs to debug the issue.
I have 2 devices on my hand and neither of them have an issue with Wi-Fi, alongside 5 other testers.
arter97 said:
For those having Wi-Fi issues, I need an actual logs to debug the issue.
I have 2 devices on my hand and neither of them have an issue with Wi-Fi, alongside 5 other testers.
Click to expand...
Click to collapse
there you go arter, if you need other specific logs let me know
xzr3b0rnzx said:
there you go arter, if you need other specific logs let me know
Click to expand...
Click to collapse
mac adress is read from wrong path and thats why it fails
Thanks very much for this brilliant project
Waiting for mi pad 4 lte
rcstar6696 said:
mac adress is read from wrong path and thats why it fails
Click to expand...
Click to collapse
i didnt alter anything, what should i do to solve this?
@arter97 you're a legend bro, great job. One thing I noticed is that adaptive brightness fails in pitch dark room. The screen stays completely dark. Other than that everything else works great.

[EXYNOS][GalaxyNote4][N910C/U/H/S/L/K][UNOFFICIAL] LineageOS 18.1 12/31/2022

{
"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 18.1 for the Samsung Galaxy Note 4 (N910C/H/U/S/L/K | N915S/L/K | N916S/L/K) ​
--> Personal Notes <--
20221231 Release notes :
Happy to be able to still work on this device whenever the time allows, Lineage 18.1 Android 11 is here, comes with a good number of bug fixes and optimizations. and fixes some old issues we struggled with in past versions, Audio is still sadly a big downside of lineage roms however it is good enough for every day use and media consumption.
I have updated all the wikis on SourceForge, and ROM is mirrored to AFH.
Further more, i will be compiling PixelExperience 11 and releasing it soon, since sadly there is no RR-OS with android 11.
Android 11 itself is moving to EOL, so sooner or later i will have to start working on 12, so that is in the pipeline, other things such as TWRP will also get an update next year.
There isnt much traction to the note 4 anymore, but im happy some people still find it usable to this day
universal543
Happy new year everyone!
SourceForge mirrors, Wiki and TWRP/Bootloader is all found here Head over to WiKi for instructions.
The main device repo contains bug reporting and tracking found here it is the most updated bug list page and you are able to provide your own bug reports there following the steps below.
Submitting new issues/Requests
First read existing issues and the F.A.Q Below to ensure its not a duplicate/workaround
Head over to universal5433 for logging and issue reporting guide
provide as much info as possible and upload your logs on the forum
old release notes
20220430
This is more or less a minor release, You can dirty flash it, Main key points is fixing encryption and few other minor things.
Ive also included VR Support which enables Gyro sensor in VR, however it is VERY funky and you need to force enable the Gyro service in Google VR Services
RR builds are compiled and will be released along side this, with the same changelog as 17.1 however ive also compiled FaceUnlock packages and enabled SystemInfo overlay
20220421:
Hey everyone! Glad to be back again for another release, This one has been in development for couple months now, and comes with massive upgrades and improvements, the most major is a full transition into Exynos7420 Oreo graphics drivers, which modernizes our device graphics stack significantly, and finally allows us to use proper OMX media codecs which solves many issues including the dreaded low quality playback! (You no longer need to flash FakeDeviceInfo)
Further more the new GPU driver significantly boosts performance in games and UI which is always a welcome (including fixing graphical glitches in games)
Other major fixes include full encryption support, Please refer to Updated TWRP to perform first time encryption setup, i must warn however, Encryption might interfere with future rom flashes, so only use it if you can keep your data backed up, as it will fully deny you access to it from TWRP.
This release also includes fixes for the random reboots, and Audio leakage, sadly this does not address the tiny microphone quality, so that remains an issue, Please refer to bugs for an uptodate bug list and instructions on how to easily report new issues
Big thanks to @Fuadmoin , @ISoreo and @TrisTanster for a ton of help with testing
20210630:
Builds for all variants have been updated, this release has been a WIP since April, ive done quite alot of changes for memory management, and added zRAM with LZ4 compression, to significantly improve our RAM situation.
Ive also fixed a broken sdfat driver that caused random reboots, and over all did a clean up of the kernel, removed old commits, updated some drivers, and more importantly, ive removed "ALL" custom GPU modifications, as they cause graphical issues in most games, and overheating, this means there no longer is an option to overclock/undervolt GPU. for now atleast.
finally, ive added a binary to help with N910H devices, which now allows them the option to go to settings > mobile networks > and pick 3G (full guide in F.A.Q) to fix SIM issues
Change-log wise this is a "small" update, but it hopefully addresses various stability problems, i have not done much work in audio tho, nothing ready for release, but i will be looking into that moving further.
03/08/2021
Update : I have released N910U builds with full sim support, they are available in the download section Sim calls / Data and SMS were all tested. it should be at the same level of bugs as other models now
03/05/2021
Alright i finally have time to release the next set of builds, i have done alot of work again on Audio to make it more stable.
and other fixes overall for modem / sim. i have used it for the past 3 days with my sim in it, and its alright.
i have also made a magisk module which you need to flash if you want high quality instagram (and other apps) video playback. all info in F.A.Q
I still have no idea how N910H will perform, so let me know if it works or not. if sim is buggy, try to manually force 3G APNs
N910U Now can show baseband info but still will not load or detect simcards. so no progress there.
We are down to few bugs, i am going to try to tackle some boring tasks in the next releases, like selinux and encryption, i am hoping to get us enforced soon, and maybe encrypted. after that i will probably re-do all our device trees. in case we ever get all the bugs resolved, we might apply to lineage official
2/17/2021
This batch of releases should hopefully address the random reboots and sim issues faced by many, i have also did entire audio from scratch, which would be fun to experiment on, i could not test it fully so i am going to expect that some calling scenarios might not work, would love to know about them.
i would like to also mention that the power management in this build has been re-done and settings > battery > profiles actually do use custom tunable similar to stock ROM, you may override the frequency i set for CPUs via HKTweaks but i personally think its better for over all stability and battery life
i should also mention that performance in general is miles better than both 16 and 17.1 builds of the past, as i found a big flaw in the kernel
over-all these set of builds carry a ton of improvements and fixes, and many missing commits that we should have had ages ago.
Enjoy and do let me know how it goes, to report any issues, follow the guide below on how to capture useful logs
2020 NOV
Alright everyone, so i have taken the stable state of our lineage 16.0 trees and decided to just go for 17.1, i have basically observed the same bugs (wifi thing on idle, no video recording in default cam app and encryption) so figured it was worth it to just spend the extra time to upbring 17.1, i have noticed a ton of improvements myself, i dropped certain hacks, and repaired a bunch of stuff in the tree, and fixed some critical 16.0 bugs related to GPS, Wifi and a ton others. I hope you enjoy this release, and please let me know how it goes, i am basically down to 2 or 3 testers at this point as everyone i knew already left this device, and i personally suck at testing, i loaded my phone with gapps micro, nova prime launcher and my general social apps / debugging tools. and so far its solid, There are some additional notes make sure to read below regarding registering fingerprint, as it gets stuck but actually takes in the FP information.
regarding continuing 16 builds, i dont know honestly, the build server i use is already crowded and building for 5 devices is too much to handle, last 16 build might be the last for a while.
Hope you enjoy this release!
Also BIG WARNING : Dualbootpatcher is no longer a thing with 17.1, it wont work ,dont ask me for support. the tool is deprecated
Lineage 16 release notes :-
Alright, it took a lot of work and effort, but finally our device is running Android Pie in a state that is considered "usable" by myself and the testers. There is still a lot of room for improvement but for now the current C/H build is good enough. S/L/K and U builds will follow later after the C/H one is tested, and while i get myself a server.
This project is only possible due to the awesome people who helped me get my foot into AOSP development, which is very different from what I'm used to. In no particular order, our thanks to @Lunarixus , @ripee , @Stricted (especially for commits that fixed RIL) @tripLr , @bonuzzz and many others from various communities who helped indirectly by sharing their device trees on GitHub.
I will continue to work on Lineage 16.0 and hopefully Lineage 17.0 in the future. I am enjoying AOSP more than TW at the moment.
Expect other flavors of AOSP Pie to come out. I was going to release Havoc but it seems to have a problem with incall UI when you install gapps, so I'm skipping it for now.
If you appreciate the effort behind this, don't hesitate to leave a thanks, provide constructive criticism and maybe consider donating some "totally not illegal stuff" over at my paypal
Documentation
- Our project is also at SourceForge
TWRP
- My builds (3.5.9) WIth encryption support - XDA
ROOT Method
Magisk
- Simple follow Install instructions , Make sure to enable Magisk Hide to restore SafetyNet functionality
- i recommend Magisk V23 + Magisk hide for most usage
Google Apps
Open GApps
- Pick ARM > Android 10. No MicroG support currently
or
BiTGApps
- Pick ARM Package
Odin
- Odin3 v3.13.3
Heimdall
- Glass Echidna
Bootloader/Modem
- Latest Packages here
Hope you enjoy this ROM!
--> Quick Notes about this project <--
ROM is stable for daily-usage.
Only the N910C version is tested by me.
All Exynos models support full functionality (Sim , calls etc)
For Stable Camera (Photo/Video) Use this GoogleCamera or XDA Thanks @Kaper_20 and enable camera2Api
Lineage 17.1/18.1 DOES NOT support dualboot patcher!
The kernel is fully customizable using HKTweaks by corsicanu: Github
--> Known Bugs <--
Footej and This GoogleCamera or Custom Opencamera XDA can record videos only
Kernel is Permissive
Microphone quality outside of calls is weak
Issues Page
--> Credits <--
Special and massive thanks to retiredtab for his contributions to the Exynos5433 project on the Galaxy Tablets!
@bonuzzz for his work in los-15.1 and exynos5433 Tablets and @dl12345 for his los-14.1 contributions
@stricted for help throughout this project, and porting modern BSP for exynos5xxx
@Alastor89 for help with custom powerHAL and contributions from Galaxy S7
@ripee & @tripLr for contributions to maintain the trees and build server
[*][user=8096767]@lukasb06 for contributions in exynos7420
@RaymanFx & @erickwill for their work in maintaining this device on CyanogenMod 13.0, which helped both directly and indirectly with this project.
@lineage project and all team members.
If you helped with this project and I forgot to add you, please PM or mention below.
Thanks for the best testers you could wish for :
@Fuadmoin for extensive N910S/L/K Testing
@ISoreo for extensive N910C Testing
ck on telegram for N910U testing
@Voytec83 @claude96 @Enginyaman @MrNova @podiwadda @muddii_yasser @Mohelsayedplus @SypeR_ @exalented @Seemanthinis @clewisit
Downloads, Change-logs and F.A.Q Below
Source Code: github
ROM OS Version: 11.x
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Latest Bootloader/Modem and TWRP 3.5.9 Encryption
Based On: Lineage OS 17.1
Version Information
Status: stable
Stable Release Date: 2022-12-31
Created 2019-06-09
Downloads and changelogs
Track changes on RefinedChannel : Telegram
Come hang with us on our chat : Telegram
My TWRP (3.5.9) For all Galaxy Note 4 Exynos Variants With Encryption : XDA
This project is also hosted on SourceForge with links to ROM,s Recovery and Bootloader Packages.
--> Downloads <--
Lineage 18.1 (12/31/2022 - STABLE)
N910C/H (treltexx) MD5 : f04e4d721f00944fb69d1e722a596d1b
N910S/L/K (trelteskt) MD5 afd9a56cbbf149b95caafba69565efa4
N915SLK (tbelteskt) MD5 : 8b1313779913f456cb2aaf446d545f6c
N916SLK (tre3calteskt) MD5 : cb852552c3d0295e7afc9251d97d446d
N910U (trhpltexx) MD5 : 636b8a2f0305ef5cbb2c377fdf463ff5
SourceForge : Download
AFH : Download
Note : Build 12/31 Is compiled on 12/29 and 12/30
Old Builds (Only on AFH and SourceForge)
Lineage 17.1 (04/30/2022 - STABLE)
N910C/H (treltexx) MD5 : 510fbbada80fb21eccacb22cdd8b9943
N910S/L/K (trelteskt) MD5 93f6b140d3af105d93718264db5ad9cb
N915SLK (tbelteskt) MD5 : 724e3ad16b217a0ccd53d4ca08a5ea3c
N916SLK (tre3calteskt) MD5 : c21c8c014d1dab3174fe783dd9451094
N910U (trhpltexx) MD5 : 7e5944265b2980d9eb33eff8b2875f95
SourceForge : Download
Lineage 17.1 (04/21/2022 - STABLE)
N910C/H (treltexx) MD5 : 5d3006cec330316f5187aab14c8ec3c7
N910S/L/K (trelteskt) MD5 12fa00de2dfa0affcaab2bd590b72454
N915SLK (tbelteskt) MD5 : 70754e3490c9576899db1e7632e555d8
N916SLK (tre3calteskt) MD5 : cc01e77e0b5e26e122427ddaa41d790f
N910U (trhpltexx) MD5 : 4ee91c68117f2ef77a960dbf1eb771c4
Google Drive : Download
SourceForge : Download
Lineage 17.1 (6/30/2021 - STABLE)
N910C/H (treltexx) : AFH | MD5 : ac96cb3104b2e2b7a85fab8b6ce8ac06
N910S/L/K (trelteskt) : AFH | MD5 : ff84c1b4d4f4fdef8b0382efd1fe8fdc
N915SLK (tbelteskt) : AFH | MD5 : 79e104f0984b0cfa2f9ae88cdf42a42d
N916SLK (tre3calteskt) : AFH | MD5 : 6f1c70a84b40131281d519d659723625
N910U (trhpltexx) : AFH | MD5 : 31e4ef4ec43af360ecaac704f37ff6bb
Google Drive mirror : Download
FakeDeviceInfo v2 : GDrive | AFH (Read more about it in F.A.Q)
Lineage 17.1 N910U Update (3/08/2021 - STABLE)
N910U (trhpltexx) : AFH | MD5 : 331659c66e1dcd82ec0be81de7899bd6
Google Drive : Mirror
Lineage 17.1 (3/05/2021 - STABLE)
N910C/H (treltexx) : AFH | MD5 : a2da420d64b450988f5b23c61120bf07
N910S/L/K (trelteskt) : AFH | MD5 : 762cef4d9353bfc9a0eed7e7b139db9e
N915SLK (tbelteskt) : AFH | MD5 : da3924b4ceff4793bb5a7f9d10e3fca5
N916SLK (tre3calteskt) : AFH | MD5 : ab09e57d034dc3dd5f94dd7b45d96f8d
N910U ALPHA (trhpltexx) : AFH | MD5 : 8d610b1f348990850e527ba544d3d1f6
Google Drive mirror : Download
FakeDeviceInfo : AFH (Read more about it in F.A.Q)
Lineage 17.1 (2/17/2021)
N910C/H (treltexx) : AFH | MD5 : a04e33f9b9143a5e1bddf84b02da2425
N910S/L/K (trelteskt) : AFH | MD5 : ce1a4711a2f9da5801c0a6ef6a2472e8
N915SLK (tbelteskt) : AFH | MD5 : 09826bb4adba8e472f2d77dc337493eb
N916SLK (tre3calteskt) : AFH | MD5 : 8c511737528abf6fdbf6576b77fed985
N910U ALPHA (trhpltexx) : AFH | MD5 : 0694c9a1d3bc9da0c2037ce82b263244
GoogleDrive Mirror : Download
Calls patch : Download
Lineage 17.1 (11/23/2020)
N910C/H (treltexx) : AFH | MD5 : e8de4fa2e53d21ab59c9524c2c09fec9
N910S/L/K (trelteskt) : AFH | MD5 : d2b38f59afc461035f6723551d1716bd
N915SLK (tbelteskt) : AFH | MD5 : b4cbf809ebdd176cb74bdd4294cbc79c
N916SLK (tre3calteskt) : AFH | MD5 : 87da8b64428d52215149efdc0a4c06c9
N910U ALPHA (trhpltexx) : AFH | MD5 : 030c8cfeb8412fb1ed594e3bc946445b
GoogleDrive Mirror : Download
Lineage 16.0 (11/01/2020)
N910C/H (treltexx) : AFH | MD5 : a09788f0384b7d10924acb1467603f48
N910S/L/K (trelteskt) : AFH | MD5 : 48950d5032f0721d1e2bd892a61baf1f
N915SLK (tbelteskt) : AFH | MD5 : 082461f5c5099aac5a200cb2100f48c9
N916SLK (tre3calteskt) : AFH | MD5 : a61060895aae647b42b0107d1e50bc69
N910U ALPHA (trhpltexx) : AFH | MD5 : 6221a2d991083778c502dd5764d6ebe9
GoogleDrive Mirror : Download
->> Lineage 16.0 builds (10/19/2019)
N910C/H (treltexx) : AFH | MD5 : 488840aca19725b0003f5d262da95b2f
N910S/L/K (trelteskt) : AFH | MD5 : 04681665fa88a1c4eacd56e42067bd09
N915SLK (tbelteskt) : AFH | MD5 : c7c975bd401f1e5a5a1ea3c7f8486631
N916SLK (tre3calteskt) : AFH | MD5 : c72ec56a7f67d6d57ab78759f9375718
->> Lineage 16.0 builds (10/10/2019)
N910C/H (treltexx) : AFH | MD5 : c26c8cedf315398c002c4c7629eb2b56
N910S/L/K (trelteskt) : AFH | MD5 : 0b7cf4305d160f7a42c5d5342c1a74cb
N915SLK (tbelteskt) : AFH | MD5 : 0a302764053ce8e1ef666a3f34e97698
N916SLK (tre3calteskt) : AFH | MD5 : a91239b9335bc79231a1ec2bc8e5572c
--> Changelog <--
Lineage 18.1 Update (12/31/2022 - STABLE)
Update and fix trees for Android 11
Update various Packages and drivers/hidls
Cleanup the device trees (leftovers/unused)
Update LPM (offline charging) to Samsung Android 11
Fix Fingerprint first enrollment lag/animation
Place volume on left
ZRAM update (75% Size, Priority, Apply early on init, discard flag)
Update WiFi packages/overlays
Enable WiFi Display (Miracast)
Update NFC Package
Add Custom LiveDisplay (Supports all MDNIE modes)
Switch to 2GB Dalvik VM Config (instead of 4GB)
Enable AAudio MMAP Support (Route through ALSA MMAP/NOIRQ Mode)
Remove broken HEVC Decoder (Causes hangs in streaming)
Fix Notification LED patterns
Enable Haptic on Select text
Cleanup and update overlays
Disable MAC Randomization
Update Memory Pinner list
Adjust default lineage settings (Disable lock/unlock sound, Vibate while ringing)
Other minor/misc optimizations
Fix R22P0 GPU Temp code
Fix Slow Audio in calls
Adjust Power Profiles to have extra performance from big cores
Disable Problematic Hotplug on big and small cores to fix lag / BT playback etc
Sync source to latest lineage Dec patch
Adjust performance overall
Kernel Changes​
Revert higher min clocks
Revert overclocking support
Revert Undervolting
Revert custom HMP Mods
Restore Stock CPUFREQ/HMP For now
Set Audio Sample rate to 48khz by default
Fix R22P0 GPU TMU
Lineage 17.1 Minor Update (04/30/2022 - STABLE)
- Include VR Support Pacakges
- Fix bootloop caused by encryption
- Resync latest LOS Source
Lineage 17.1 Update (04/21/2022 - STABLE)
* This is a cumulative release of the past couple months
- Fix interactive governor performance issues
- build missing OMX hidl
- update media configs to fix some playback issues
- Switch to N935FXXS7CTJ2 OMX to fix video recording (screen record/footej)
- Increase min cpu clock to 700mhz
- restore stock little cpu boosting frequency
- Revert Agressive hotplug power saving mods
- Fix bluetooth audio suttering when screen is off
- Switch to Exynos7420 Oreo R22P0 GPU
- Update Gralloc to oreo buffer
- Patch camera to work with new gralloc
- Fix AdaptivePlayback low quality issues
- add 4K camera recording profile (ofc wont work)
- re-do media configs and bunch of other **** for oreo graphics
- update power_profiles to use proper power values
- Fix Power management in PowerProfile switcher (Balanced / Powersaving and performance now properly apply)
- Add custom audioroute which fixes various Audio issues (leakout in headphone jack, some echo, other audio route issues)
- Enable AOSP dynamic audio processing
- Reserve 128MB of internal storage for critical system operations (to avoid losing data when internal is full)
- Fix parse errors in media configs
- Fix MFC dec/enc permissions
- Improve RIL mobile data stability / latching onto network
- Remove unused things such as DRK, F2FS and deprecated camera configs
- Add Encryption support (Follow F.A.Q For how to get encrypted)
- Add 2017 August Vendor patch level
- Fix USB MIDI mode crash
- Remove unsupported audio sampling rates to avoid extra processing
- Fix WiFI Direct / P2P
- Significantly reduce Drain caused by broken P2P
- Add back GPS NTP server configs
- Fix-up and update XTRA configs for GPS
- Remove unsupported software decoders
- Revert broken audio processing in the lineage audio HAL
- Fix random reboots caused by invalid GNSS/GPS config
- Disable legacy hardware keystore
- Switch from proprietary keystore/tee to OSS for future support
- Various fixes to USB / MTP
- Add a fix for WiFi turning off after doze
- And a bunch of other minor things here and there in the device trees
Kernel :-
- Fully re-do USB upstream to fix weird issues with MTP
- Fix FBE Encryption
- Switch to OSS Mobicore driver
- Remove default Boeffla block list as it broke WiFi and other parts
- Update interactive governor
- Disable broken/unused governors
Lineage 17.1 Update (6/30/2021 - STABLE)
- Sync GPS headers with exynos5420
- add patch for our old gps hal
- remove custom LMK stuff
- add ZRAM configs
- cleanup LMK
- add binary to detect device and set 3g/4g and proper codename/fingerprint
- support devices with engineering bootloader
- Remove problematic old commits from kernel
- re-do memfd and sdcardfs updates for Q
- backport zpool/zbud/zsmalloc and zRAM drivers
- Disable ZSWAP, and samsung swap (vnswap)
- Enable 1.5GB LZ4 ZRAM
- add proper LMK driver
- improve powerHAL frequency changing
- Downgrade sdfat driver to 2.0.6 to fix random reboots
- Add FreeForm multiwindow lineage patches
Lineage 17.1 N910U Update (3/08/2021 - STABLE)
- Fix simcard recognition
- Fix mobile data
- Fix voice call verbs and scenarios
- Now fully functional Sim calls, 3rd party calls, SMS and mobile data
Lineage 17.1 (3/04/2021 - STABLE)
- Fix modem startup on N910C/H/U that caused random reboots and sim issues overtime
- improve modem stability and fix a bug that caused the phone to panic if you unlock it fast after boot
- Enable Full screen gestures (See F.A.Q for how to enable)
- Replace custom fingerprint service with stock AOSP one
- Disable camera debugging and custom params that cause issues
- Rework media profiles to improve camera video quality in gcam
- Fix media performance issues to fix playback issues (Read F.A.Q for quality fix for instagram)
- Remove buggy AptXHD bluetooth codec and keep Aptx only
- Rework DRM service for full L1 support (No secure L1 playback yet)
- Disable absolute volume to fix bluetooth audio issues
- Add Wifi/Gps wakelock group to prevent issues on long uptimes
- More fixes to disable buggy P2P/WiFi Direct spam
- use low-end video profiles for smoother playback in some apps
- Add back and fix missing NFC
- Massive Audio rework to fix issues listed below :-
- Fix calls on earpiece, speaker, bluetooth and headphones for C/H/S/L/K
- Fix microphone issues on speaker calls
- Fix microphone issues on video calls
- Fix bluetooth call issues on all models
- Fix an issue that caused headphone volume to leak from speaker
- Fix an issue that caused earpiece to work when doing bluetooth calls
- Add custom workaround to fix no incall volume and other audio routing when you boot muted
Old releases changelogs
Lineage 17.1 (2/17/2021)
- set default gpu clock to 600mhz to fix instability
- add FB notifier for power hal
- reduce mobicore logging
- fix HMP up/down tune to fix performance issues
- disable P2P Spam
- add support for lineage/twrp recoveries in the device tree
- add odex optimizations
- let aosp only compile the needed resources for our DPI
- add RAM pinner and pin SystemUI, graphics and runtime to RAM
- organize ramdisk into vendor
- add FastCharging hidl to turn on / off fast charging in settings
- add improved SQLITE overlays for app database optimization
- add custom max_volume warning for headphones
- remove guard that made flipflap (sview) not compile on korean variants
- build custom powerHAL
- add stock interactive profiles in powerHAL (balanced, performance and power saving)
- let the powerHAL manage CPU FREQ for all 3 modes and use stock powersaving freqs for max clocks
- overall powerHAL now has real management now and multiple tunable presets
- remove camera param debugging that clutter logs
- rebrand our custom hardware HALs into universal5433
- enable vibration intensity control in settings for some options
- update calling overlays and signal overlays
- organize app overlays in device tree
- add some props for HWC
- add mali gpu props
- fix-up core services startup in ramdisk
- let zram go across all 1.5GB of swap
- add AOSP RCS packages
- disable NFC debugging
- properly override AOSP APNS
- remove outdated configs and features from tree
- add fixes for random reboots
- update and improve audio hal / policy
- add basic support for audio cancelation (not fully working yet)
- re-organize stock aosp audio effect support
- fully reworked audio mixers
- redo mic quality / gains for all mics including headphone mic
- redo verbs and channels for audio recording
- reduce and remove clutter from mixers and update the used paths for speaker/earpiece and heaphones
- let camera use both left and right microphones when recording
- remove useless BT code and try to improve stability in media (untested in calls)
- commonize mixers_path for all variants
NOV 24 limited Test build changelog
- Fix OpenCL and Vulkan devices
- Improve UI performance and scrolling
- Disable loggy script to not fill /cache and cause issues. use adb for debugging
- Add fixes for bluetooth SCO (calls)
- Switch to better dalvik-heap config
- expose our opencl and vulkan devices to apps
- properly set max surface buffers to avoid lag over time
- Fix APN issues that broke LTE , 3G on some phones
- Fix Bluetooth stability issues / stuttering
- Increase proximity detection range to match stock
- overall graphics and UI improvements
Lineage 17.1 (11/23/2020
- Rebased trees and update to lineage 17.1 running android ten
- resolved an issue that broke GPS + RIL Connection and affected GNSS Locking
- Updated widevine and implemented clearkey to match modern devices with netflix playback support (requires magisk hide + reboot and some time to show up on the store)
- Updated kernel net driver significantly to resolve connectivity issues
- Remove broken/unsupported WiFi display that caused severe draining
- Fixed Fingerprint for android Q (read F.A.Q For more details)
- Allow direct booting from offline charging mode
- Added logging service to help with user debugging (When facing issues zip me /cache) read F.A.Q if you want to disable it
- Improve network scanning for RIL
- Improve graphics performance
- Early boot system for faster booting speeds
- Include official lineage power HAL which works better on our phones
- Apply fixes for media playback that required hacks previously
- and everything else Android ten brings!
Lineage 16.0 (11/01/2020).
ROM :-
- Updated to latest lineage sources with October 2020 Patch
- Switched to new BSP to compile most blobs (including video , display etc) big thanks @Stricted
- build and update OMX from BSP to resolve many codec issues
- Fix graphical glitches / issues during games (pink stuff)
- remove unused shims from the trees and do general cleanup
- update GPS shim and and improve its stability
- implement MultiHAL Sensors wrapper to resolve rotation and other sensor issues
- Disable broken CPUSETS
- update WiFi Configs and disable broken wifi features
- update TCP and other throughput configs
- Fix spammy P2P wifi logging
- bring back argosd service to fix slow WiFi / lag when downloading (tested upto 260mbps)
- Fixes to Wifi during Doze
- build open source bluetooth blobs with some call fixes
- update and adjust SWAP rates and switch to ZRAM
- disable nearby service by default which makes wifi unstable when bluetooth is active
- use second mic when using speaker calls to avoid echos
- other misc mixer and audio changes
- Disable GPU errors caused by unsupported screen fade effect
- Fix Front camera in stock/3rd party
- fixed video recording in footej camera and its quality to 1080p
- Fix headphone mic one more time
- Add workaround for muted incall audio
Kernel :-
- Remove broken wakelock controls
- implement devfreq boost driver by @Lunarixus
- update LMK driver to resolve issues with memory leaks
- properly kill GPU DVFS control from the driver
- adjust GPU interactive governor
- Fix an issue that made the GPU stuck at 100% utilization with min frequencies (this also resolved serious lag issues)
- bring back stock input booster settings (to maintain decent performance).
Lineage 16.0 (10/19/2019)
1- Fixed low quality video in instagram/twitter and so on by fixing AVC decoder (And encoder was improved)
2- Fixed offline charging animation
3- inline encryption with stock (untested)
4- Tons of fixes to WiFi, will remain working when screen is off, and more stable in games (and enabled background scan/batched scan)
5- Generally improved the quality of video playback / recording (to inline with stock)
6- LowMemoryKiller tweaks added that should help with the memory leak issue
7- Enabled burn-in protection
8- Added some fixes for mediaserver and made it more stable (It will crash less often now, but it will if you try hard enough)
9- Many changes to ramdisk to fix missing nodes (NFC, DVFS, GPS And sensors)
10- Adjust LowBattery warns (to inline with stock)
11- fix some errors in miracast so it works more often
12- Entire rework to the GPU to fix Graphical glitches, crashes and many more to heavy games (PUBG, CSR, COD etc)
13- Removed 100mhz GPU clock, set default min 266, max 600 as stock, removed 800mhz overclock option (Max is 730)
14- Sync with latest lineageOS source
15- And other misc changes to fix performance and battery in general
Lineage 16.0 (10/10/2019)
Cumulative changes from all the previous test versions
1- Re-work Audio fully with a new mixer_path based on stock tinyucm conf
2- Fix call echo in all scenarios (3rd party calls not tested)
3- restore stock gains (the ones we had were all over the place)
4- fix headphone mic in 3rdpaty apps and in calls
5- add missing wideband/narrowband scenarios
6- update the lineage audio hardware hal
7- restore mic level to stock without hurting voice recorders
8- Fix memory issues (with improved LowMemoryKiller and swap)
9- fix random shutdowns due to low memory after long useage
10- Set the minimum GPU frequency to 160
11- Set the GPU to be always online (due to lack of HWC, this fixes performance issues)
12- reduce the effect of touch booster to save battery
13- Disable swipe-up gestures
14- Massive liveDisplay fixing (ColorProfile , Displaymode (Night/day) , Color temperature , Outdoor mode And color calibration support)
15- Other performance improvments
16- Improvments to calls by reverting some broken changes
17- removed AudioFX (Qcom only)
18- added lineage vibration hal
19- removed custom gnss hal that wasnt needed
20- more fixes to GPS
21- slight changes to sensors
22- built healthd hal (still no offline charging)
23- enabled and fixed HWC
24- added a prop that helps with performance
25- Fixed NFC so it no longer ****s everything up when its turned off (and now can be turned on without also ****ing said things up)
26- other misc changes you can see in git
27- Fixed all HWC leaks (therefore you shouldnt have random reboots anymore)
28- Disabled always_on GPU for better battery saving
29- Animations and layers will have improved performance
30- removed a workaround that delayed boots
31- critical kernel changes to remove many workarounds we had by :
32- updated sdcardfs driver to remove legacy stuff
33- updated sdfat driver and enabling it for exFAT
34- updated EXT4 driver and using it for EXT2/3 instead of dedicated drivers for both
35- updated USB and ADB so we dont need legacy stuff anymore
36- updated and enabled F2FS Driver (support not tested)
37- patch a ion leak
38- updated wireless/wifi driver to remove the need for workarounds
39- Added back AudioFX as it works
40- DRM changes
41- default hotspot name
42- fixes to rotation sensor (it works fine with/without location enabled here, but if it as slow, enable location)
43- remove duplicated tether config
44- fix nfc config
45- Updated powerprofiles
46- slight changes to meda and camera set for the future
47- synced with latest lineage sources
TLDR : tons of fixes, better performance and having an actual usable phone.
Lineage 16.0 (9/21/2019)
1- Full hardware video playback (no lag even on 1080p60 playback)
2- LiveDisplay enabled (color mode changing) with more features to be added later
3- updated and enabled back ambient and aod (not fully tested yet)
4- added and updated APN and SPN configs
5- improvments to camera and include camera2 instead of snap
6- fix a mic bug that introduces artifacts in audio recording
7- OMX and media fully redone based on herolte
8- Rotation sensor should be more robust now
9- few changes to spen
10- Bluetooth range and issues fixed
11- improve RIL for SLK variants
12- Fix NFC issues on N916 variants
13- improvments to NFC on intl variants
14- set default color mode to cinema for vivid colors
15- Removed a binary that caused SLK variants to over-heat
16- latest lineageOS sources
17- compiled stable builds for N910SLK|N915SLK|N916SLK
18- overall the build is more responsive and stable due to MFC/OMX fixes
Lineage 16.0 build (9/16/2019)
1- Fixed Video playback for 3rd party apps
2- Youtube and other social media apps will no longer freeze randomly
3- fixed an issue that took a toll on performance
4- over all the rom will be noticeably smoother
Lineage 16.0 initial build (9/14/2019)
1- Updated and reworked the tree all together
2- A decent powerHAL modded to N4
3- Bluetooth APTX errors resolved
4- Fully fixed RIL (no workarounds needed)
5- Entire Kernel has been built from scratch
6- New binder, sdcardfs, and WiFi drivers
7- all the features of HeliosKernel built it and customizable
8- Updated brightness tables to conform with stock
9- removed ugly workarounds and hacks
10- Audio much more stable
11- stock APN , TCP configs and much more
12- Added more LED modes
13- Added AOD and ambient display support that kinda works
14- updated most libs and shims
15- built lineage trust and touch HALs
16- enabled gesture support
17- enabled smart pixels for ROMs that support it
18- And tons of other changes covered in the github source
F.A.Q And Notes
Q : How to use Encryption ?
A : First, head over to TWRP Thread And follow the notes for First time encryption setup (this involves formatting internal storage while using that twrp, This is mandatory as previous twrps did not create proper partition state for encryption), Then head over to settings > security > encryption > Encrypt Phone, the phone will reboot once or twice
Warning : Encryption will prevent TWRP from reading your internal storage at all, And encryption is very sensitive, any untested customization or mods might brick the ROM, and putting your data at risk, only use if required
UPDATE : You will bootloop if you did not set PIN/lockscreen in setup wizard before encrypting
Q : WiFi Wont Turn on
A : This is a bug in lineage-18.1 when you leave NearbyShare enabled and reboot, Turn it off or follow workaround in github
Q : How to Tune for Performance or battery life ?
A : Latest release offers proper Power profiles which can be adjusted in Settings > Battery > EnergySaver and Performance. The slider will adjust MAX CPU frequency as follows,
Power saving Big: 1.4GHz Little: 1.0GHz
Balanced: Big: 1.7GHz Little: 1.3GHz
Performance: Big: 1.9GHz Little: 1.4GHz
Q: N910H wont detect SIM / network
A: This is due to it trying to force LTE, Go to settings > network > mobile networks And change preferred network type to 3G, then enable and disable Airplane Mode. Here is a Video by @mvrul2k20 to explain the procedure
Q : Korean variants (S/L/K) have tube / robotic audio in calls
A : this bug is unfixable for now as those models rely on stock audio hardware effects to fix this issue, but we cant use that and open source H/W does not support them
Q : How to enable android 11 gestures
A : First you need to enable navigation bar (this will disable touchkeys) then go to gesture settings and enable full screen gestures
Q : Recommended camera app to use ?
A : This Google Camera : Download or Footej2 from the play store
Q: Whenever I try flashing any lineage- build, I get the following error in TWRP: Updater process ended with ERROR: 7
A: Update your TWRP to 3.2.3 or higher available Here or newer
Q : Device is too warm
A : After first boot that is common, let the phone finish setting up and cool down
Q : How to get google apps ?
A : Go to Opengapps.org . Select ARM > 11 > [your choice] and flash opengapps*.zip after the ROM.zip
Q : How to get Root ?
A : Flash Magisk Root From Here (Recommended version 23.0 for better MagiskHide)
Q : How to tune the kernel ?
A : use HKTweaks app from @corsicanu : Github
Additional
Reserved
Reserved
Congrulations mate, keep it up. :good: After the Refined Nougat, you will be became an AOSP dev
Thank you very much for this build.
Thank you very much for this build.
I have flashed initial builds whenever they become available. Flashed build 9 2 hours ago on top of build 8, and I am testing it without a simcard at the moment.
Really appreciate your efforts in getting Android 8.1 to work on N910CQ.
Congrats!
Greatt
thank you very much brother, your the best and proud to be in your testing Team ♥
Cant thank you enough for your immense work on this abandoned but powerful device.. to others, it was totally unexpected that we would get this rom working in this condition for note 4. The development has been really positive and the rom is in a very usable daily state.
Glad to be part of the family and seeing this rom from its inception to its release is heart warming.
Cheers to all..
Finally...
Thanks boss, been waiting for this release since developing stage.
Im on 7th built, flashing 9th soon.
Anyone have a voice in WhatsApp very low??
I have this in my phone n910h
Zeus of Android has arrived...AGAIN!??
Thanks for Your amazing work for old-s(coolest) device Samsung ever made.
Exy5433 is like a phoenix - resurrects from ashes every year?
You again achieved an awesome work ! Keep it up
Well, true passionate work has paid off once more. Words are useless, but satisfaction is immense. In your face samsung, there is someone who deserves much more love and respect. Thank you again Anan
Only i can say is "THANK YOU VERY MUCH" GOD bless mate..
910cq , twrp 3.2.3
thanks you
Deleted
We'll lose the s-pen function with this rom tho, correct?

[Kernel][03.07.2022][Android 12] Kirisakura 2.0.0_S for Asus Rog Phone 3 aka OBIWAN

Kirisakura-Kernel for the Rog Phone 3
Hello everyone,
To keep it short: Here is Kirisakura - Kernel for the Rog Phone 3 aka OBIWAN.
I would appreciate if everybody that flashes the kernel, reads at least once through this opening post and the following ones.
Kirisakura - Kernel is designed to bring a handful of beneficial features to the device, while ensuring excellent performance and smoothness to get you safely through the day!
This project aims to keep most of the subsystems updated, way ahead of the stock kernel, thereby improving security and performance, while keeping stability as the foucs during testing! This includes Linux-Stable, CAF-Upstream and kernel/common.
Kernel Control Flow Integrity (Kernel-CFI), which is achieved by linking the kernel with LLD and Link Time Optimization (LTO), more precisely ThinLTO, are quite unique security features. In fact this, alongside Kirisakura-Kernel for the OnePlus 8 Pro, may be (and probably is) the first 4.19 msm kernel with a fully working Kernel-CFI implementation and CFI-Violations fixed on a smartphone.
The only kernels made by OEMs offering this security feature are the ones for the Pixel 3 and Pixel 4 devices.
The recently released Kirisakura-Kernel for the OnePlus 8 Pro was featured on the XDA-Portal due to the inclusion of CFI. The featured article explains CFI in great details, is easy to understand and definitely worth to read.
Another security feature is Shadow Call Stack (SCS). Similar to CFI, only the Pixle 3 and 4 Kernel use this security feature.
SCS is another security patchset that is aimed at preventing attacks via return oriented programming (ROP).
ROP is a technique where the attacker gains control of the kernel stack to overwrite function return addresses and redirect execution to carefully selected parts of existing kernel code.
If you´re interested here are a few good links:
Google Security Blog explaining SCS.
LLVM doc about SCS
Android DOCs documenting SCS
If reading about upstream in the paragraph above got you curious,have a read about Linux-Stable and why it is important here. The stable-process is not the same for every subsystem, but the general idea, rule of thumb and benefits are applicable for other subsystems as well.
Quick explanation of CAF-Upstream. CAF is short for Codeaurora-Forums. This is the place where development from Qualcomm for their SoCs happens. This includes the Snapdragon 865/+ that´s built into the different SKUs of the Rog Phone 3.
The kernel-bases available on the Codeaurora-Forums, are basically the foundations OEMs use, to build their own kernel additions on top for devices featuring Qualcomm SoCs.
The Qualcomm developers push regular updates to the bases of the different SoCs, a bit similar to how Linux-Upstream works. OEMs usually stop updating the initial base after the phone is released.
This kernel focuses amongst the other features to provide the latest CAF-Updates merged in a regular manner, to provide updates, improvements and enhancements for SoC specific drivers and subsystems! This might take a while, because a lot of device specific testing is done on my end to ensure stability.
The kernel includes a lot of improvements and contributions from other developers as well. Without this kernel would not exist.
I´d like to mention @tbalden ´s excellent CleanSlate features at this place. They improve usability by a big margin for me personally. The highly customizable sweep to sleep implementation (adjustable to different navigation settings), long tap to bring down status bar (very useful on a big device), backlight dimmer and notification reminder are very useful features that I use personally every day.
Another big part of improvements originate from @arter97´s, @kdrag0n´s and @Sultanxda´s work. Many others contributed in some way or another to this kernel.
A big thanks to all of them at this place!
Now lets continue with a list of features in the next paragraph!
Main Features:
- Based on latest kernel sources from Asus for Android 12 and intended for use on the latest Asus Stock-Firmware
- compiled with Clang 13.0.1 and built with -O3 speed optimizations
- Linux-Stable-Upstream included to 4.19.240
- CAF base for the Snapdragon 865/+ (SD865/+) updated to upstream CAF
- Kernel Control-Flow-Integration (CFI) andLink-Time-Optimization (LTO) ported from 4.19 kernel/common and Pixel 4/XL Kernel
- Shadow Call Stack (SCS) Security-Feature
- Use ThinLTO which was first used in the Pixel 4 XL Android R-Preview Kernel instead of full LTO for full program visibility (needed by CFI)
- fix CFI-Violations found in various subsystems like Asus/device specific drivers and qualcomm drivers
- Link the kernel with LLD and use RELR-Relocation
- include important fixes/improvements from kernel/common
- Flashing the kernel will keep root!
- Cleanslate Features included! See @tbaldens´s CleanSlate Thread for more information
- Flashable via EXKM, FKM or TWRP on a rooted system!
- Anykernel zip is based on the Anykernel3 release from @osm0sis
- disable various debugging configs, that are not needed in a perf build kernel according to google.
- disable selinux auditing (we don´t have to adress selinux denials running a stock rom)
- display tweaks to reduce power consumption on statically rendered images
- tweak display to allow better visibility of black levels/colours on low brightness ( example pictures )
- allow experimental 165hz refresh rate for the panel. (use with caution)
EAS related features:
- EAS implementation patched up to latest CAF state
- disable autogroups and use cgroups for more efficient task placement!
- updates from kernel/common
- scheduler updates from Googles Pixel kernel
CPU related features:
- Change various drivers (WLAN, MM, audio, charger, power, thermal, glink etc) to user power efficient workingqueues. This compliments EAS
- include cpuidle patches from CAF
- improvements to cpufreq/times/stats
- improve memory allocations in binder driver
- use s2idle for deepsleep, as pixel 4/5
- vdso32 patches as found on Google Pixel devices (brief documentation here)
- enable lse atomics
- arm64: lse: Prefetch operands to speed up atomic operations, thanks @kdrag0n
- implement fast refcount checking
GPU related features:
- GPU driver updated to latest CAF-State
- remove POPP functionality from GPU driver to avoid constant fight about downscaling with msm-adreno-tz
- don´t wake the gpu on touch input, instead wake when receiving an ioctl
- don´t copy fence names by default to save a bit of cpu-time (explanation)
- msm: kgsl: Stop slab shrinker when no more pages can be reclaimed
- gpu/kgsl improvements from pixel 4/pixel 5 kernel
File System related features:
- improve memory allocations in sdcardfs
- improve eventpoll logging to stop indicting timerfd (improves kernel wakelock readability)
- improve memory allocations in kernfs
- writeback: hardcode dirty_expire_centisecs=3000 based on this commit
- f2fs-stable upstream, that includes ATGC
- ufs improvements from pixel 4/ pixel 5 kernel
UI/UX/Usability related features from CleanSlate:
- CleanSlate features made by @tbalden
- Disclaimer: All CleanSlate features can be controlled via the free companion and config app found on CleanSlate thread here on the ROG 3 Forums on XDA. Please consider buying the premium versions if you enjoy using the CleanSlate features, to give a little something back to @tbalden.
- Flashlight Notification/Call blinking
- Vibrating Notification Reminder
- Sweep to Sleep touchscreen gesture - highly customizable
- DoubleTap on Sweep2Sleep's area gestures - new way to pull down android Notification Area
- Face down screen off - new gesture
- Backlight Dimmer - possibility to use lower panel brightness
- Force FPS Level on Low Brightness
- Squeeze Control
- advanced notification LED control, chromatic charge LED, pulsating LED, LED dimming
Network related features:
- Wireguard Support (Details)
- advanced TCP algorithms enabled
- includes new bbr and bbr2
- fix CVE-2020-14386
Memory related features:
- Speculative Page Faults left enabled (1. 2) (CAF default)
- various fixes for PSI-Monitor, which is used by the userspace lowmemorykiller-daemon
- Fix various memory leaks in different subsystems
- improved mm with patches from mainline
- various other changes from mainline
- included zstd as an option for ZRAM-algorithm (lz4 is probably the best all around, so only change it if you know why and what you are doing)
- improve memory allocations in various subsystems
- ported per process reclaim from Pixel 5 kernel, instead of using outdated CAF implemenation
Security related features:
- Control-Flow-Integration (CFI) and Link-Time-Optimization (LTO) ported from 4.19 kernel/common and Pixel 4/XL Kernel
- Use ThinLTO which was first used in the Pixel 4 XL Android R-Kernel instead of full LTO
- Shadow Call Stack (SCS) Security-Feature
- fix various CFI-Violations found in various subsystems like Asus/device specific drivers and qualcomm drivers
- enable init_on_alloc for even more security, more information can be found in the commit message
- Backport mainline Selinux commits, thanks @arter97 (you must be on magisk 21.0, otherwise the kernel won´t boot)
Misc Features:
TCP Congestion Algorithms:
- advanced algorithms enabled, enable them with your favorite kernel manager
- includes new bbr2
Wakelock Blocker:
- advanced wakelock blocker with the ability to block any wakelocks (dangerous, use with caution)
- please read [URL="https://arstechnica.com/gadgets/2018/08/p-is-for-power-how-google-tests-tracks-and-improves-android-battery-life/"]this for further info
- blocking a kernel wakelock should only be done in case of firmware incompatabilities (WiFi network at work (can´t be changed) causes deep sleep to not work on the phone.) That´s the only use case I see for this feature. The kernel does not features this to improve battery life!
Other features:
- disable logging and debugging to make the kernel more lightweight in various places (includes binder, mm, vma, gpu, ipa etc)
- fix several coding issues detected by newer Clang-Toolchains
- add support for steam controller
- add support for nintendo switch controller
- ufs improvements from pixel 4/ pixel 5 kernel
- gpu/kgsl improvements from pixel 4/pixel 5 kernel
- display tweaks to reduce power consumption on statically rendered images
Feature section for the "non visible" but perceptible improvements:
- updated binder section (responsible for interprocess communication)
- updated sdcardfs ; have a read about it here:
Flashing Guide, Download and Changelog
A description how to flash the kernel, links for download and a changelog can be found in the second post!
Contributors
Freak07
Source Code: https://github.com/freak07/Kirisakura_OBIWAN
Version Information
Status: Stable
Requirements
- unlocked Bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment
- latest magisk stable root environment
- a backup of boot.img and dtbo.img to be able to restore to stock.
How to flash the Kernel:
1. Download the latest kernel.zip and make sure you have properly updated to the latest matching Asus Stock-Firmware. When the Rog 3 receives an update it takes Asus a while to release the source code for the new OS and me a while to build a new kernel. If you don´t want to face any issues, wait until I either release an updated kernel or give green light because there were no kernel changes.
Always make sure to run the firmware the kernel is built for!
1a. Optional: While it may not be necessary all times, you may want to restore stock boot.img as well as dtbo.img, re-root with magisk and optionally install twrp.zip if coming from another kernel. Before reporting issues make sure you do that! Thank you!
2. Make sure to meet all the requirements listed above.
3. Flash the kernel.zip via latest EXKM or FKM app, or TWRP and do a full reboot.
4. Reboot and profit. Set CleanSlate features as you desire by installing both apps and choose according to your liking.
DOWNLOAD:
Download is located always in this folder:
https://www.androidfilehost.com/?w=files&flid=316676
Important: Read after Download
Please take a look at the second post after flashing the kernel!
Changelog:
Android 10
1.0.0 Initial Release
1.0.1 https://forum.xda-developers.com/showpost.php?p=83393257&postcount=12
1.0.2 https://forum.xda-developers.com/showpost.php?p=83409591&postcount=28
1.1.7 https://forum.xda-developers.com/showpost.php?p=83518681&postcount=32
1.2.2 https://forum.xda-developers.com/showpost.php?p=83539471&postcount=33
1.2.3 https://forum.xda-developers.com/showpost.php?p=83552967&postcount=38
1.5.0 https://forum.xda-developers.com/showpost.php?p=83815367&postcount=74
1.8.2 https://forum.xda-developers.com/t/...-rog-phone-3-aka-obiwan.4155505/post-84199477
1.9.4 https://forum.xda-developers.com/t/...-rog-phone-3-aka-obiwan.4155505/post-84404331
2.1.0 https://forum.xda-developers.com/t/...-rog-phone-3-aka-obiwan.4155505/post-84693785
2.1.1 https://forum.xda-developers.com/t/...-rog-phone-3-aka-obiwan.4155505/post-84717725
2.2.0 https://forum.xda-developers.com/t/...-rog-phone-3-aka-obiwan.4155505/post-84752157
2.2.2 https://forum.xda-developers.com/t/...-rog-phone-3-aka-obiwan.4155505/post-84762283
2.2.4 https://forum.xda-developers.com/t/...-rog-phone-3-aka-obiwan.4155505/post-85029489
2.2.5 https://forum.xda-developers.com/t/...-rog-phone-3-aka-obiwan.4155505/post-85119205
Android 11
1.0.0_R https://forum.xda-developers.com/t/...-rog-phone-3-aka-obiwan.4155505/post-85434269
1.0.1_R https://forum.xda-developers.com/t/...-rog-phone-3-aka-obiwan.4155505/post-85437987
1.0.5_R https://forum.xda-developers.com/t/...-rog-phone-3-aka-obiwan.4155505/post-85540573
1.0.7_R https://forum.xda-developers.com/t/...-rog-phone-3-aka-obiwan.4155505/post-85797081
1.0.9_R https://forum.xda-developers.com/t/...-rog-phone-3-aka-obiwan.4155505/post-86238185
1.1.0_R https://forum.xda-developers.com/t/...-rog-phone-3-aka-obiwan.4155505/post-86428163
1.1.1_R https://forum.xda-developers.com/t/...-rog-phone-3-aka-obiwan.4155505/post-86444523
Android 12
2.0.0_S https://forum.xda-developers.com/t/...-rog-phone-3-aka-obiwan.4155505/post-87102871
Donations:
Donations are not mandatory but very welcome if you want to support development or just buy me a coffee/tea
If you like my work: http://paypal.me/freak07
Credits:
Asus for the development device, giving me the opportunity to create this project!
@osm0sis for all his work, including the ak3 installer!
@tbalden for being the best HTC, Pixel, OnePlus and now Asus wingman!
@LeeDroid and @mwilky for their awesome roms and work I used on multiple devices!
@Captain_Throwback for all the mentoring and guidance!
@Eliminater74 for bringing me into the game and the Inspiration
@nathanchance for his upstream guidance and assistance
@RenderBroken for helping me out
@flar2 for all his work
@joshuous for all the help he provided to me in the past!
@arter97 for giving me advice
@kdrag0n for his help and advices!
@topjohnwu for magisk!
FAQ
F.A.Q:
Question: Why does the kernel version show as "unavailable" in settings after flashing it.
Answer: Asus does not allow for custom kernel names in their settings. If the kernel string doesn´t fit their regex, it will display as unavailable there. Nothing can be done about it. Use a kernel manager to check the kernel version.
Question: Is root preserved when flashing this kernel?
Answer: Yes, the AnyKernel.zip will detect root and keep it.
Question: How do I return back to stock or another kernel.
Answer: Extract boot.img as well as dtbo.img from matching firmware you are on and flash the extracted boot.img and dtbo.img via fastboot. If you want to keep root flash back the magisk_patched_boot.img. Or dirty flash your rom.
Question: Why is having Magisk installed mandatory for this kernel?
Answer: Android 10s changes to partitions, doesn´t allow files in system/ and vendor/ to be replaced. This kernel is very far from the stock kernel. To account for this I can´t force load the stock kernel-modules for certain drivers as it happens on kernels that are closer to stock.
Instead we use Magisks function to overlay certain files during boot. Without a working Magisk environment the kernel cannot function.
Question: I have a phone that is converted from CN to WW and now there´s a warning from hardwarestub. Can I hide it?
Answer: Yes, I created a Magisk Module for those that want to hide the notification, so nobody needs to rely on paid apps.
The Magisk module can be found attached to this post.
Please note that refresh rate can´t be changed when the module is flashed. To able to change refresh rate or to remove the module, simple remove it in Magisk Manager and do a full reboot. I´ll attach it to the third post on this thread. There will be no support for this module from my side and no other support for converted devices.
Question: How to report bugs properly?
Answer: Have a look at post #3 in the linked thread. The linked guide is a pretty good starting point.
Before reporting any bug make sure you´re running on a stock configuration. That´s means you´re not using any mods, tweaks in kernel managers or other root tweaks , magisk modules, scripts or other modifications that alter various functions like sound mods, data traffic, sleeping behaviour, scheduler, magical battery tweaks etc.
Try to describe the issue as detailed as possible! Give your exact setup, like rom, magisk version, kernel version.
Is the issue reproducible? Does it happen frequently?
Provide logs, otherwise debugging is a lot harder. If you can already reproduce the issue and provide logs it greatly limits the amount of time I have to spent until I figure out how to reproduce it.
If the device force reboots/randomly reboots (that means you see the bootloader unlocked screen!) provide a .zip with the contents of sys/fs/pstore.
If the issue happens while the device is running provide a dmesg plus a logcat that you take while/shortly after the issue happens. This will log what´s running in the current session. Try to be as detailed as possible what´s happening when the issue appears. It will also help me in reading the log!
CleanSlate Features and how to use them
CleanSlate Features and how to use them
This kernels offers its users the possibility to use CleanSlate features. CleanSlate-Kernel is developed by @tbalden.
CleanSlate kernel follows a different approach than Kirisakura-Kernel.
We know each other well over the years now and often have worked together.
For more information about CleanSlate visit @tbaldens CleanSlate thread on the Rog 3 Forums linked here.
The CleanSlate features add a lot of flexibility to a device. That´s why I like to include the features in my kernel.
Notifications Reminder, Flashlight Notifications, Turn Phone to sleep and a very advanced sweep to sleep interface that works well with Android 10 Gestures.
We decided to transform Brightness Dimmer and FPS-Override into CleanSlate accessible features as well.
That allows users to easily control these features with the CleanSlate apps.
CleanSlate features are easily accessible via the CleanSlate Configuration app. The Cleanslate Companion app provides a userspace backend for the kernel and is required for some features.
Make sure to install both of these apps, when flashing my kernel and you want to utilize these features.
The apps ask for some permissions. Enable them and do a full reboot to make sure everything is playing nicely
that´s how the companion app will look after enabling it.
https://photos.app.goo.gl/x6sFJc5cUFT9Q7U47
It´s needed for userspace related features, like double tap swipe area for notification pull down.
Every section of the Configuration App has different settings. Basic, Advanced and Preset. You can click on these buttons to change between them.
Advanced will offer you more customization if available.
See the screenshots here:
https://photos.app.goo.gl/avPsiHHrzPwpMqMC8
To change settings, change them according to your liking and hit the "Save" Button. It is the second from the bottom right and will be greyed out if your settings are currently applied.
As you can see in the following screenshot:
https://photos.app.goo.gl/qaFKfLbfwUuyHW717
Brightness Dimmer is enabled, FPS override is set to 144FPS on low brightness. Power button is blocked in pocket and screen gets disabled when putting the phone face down on a desk.
You should be able to find both apps for free on the CleanSlate thread. However if you benefit from the features, think about getting the premium apps on the playstore to give a little bit back to @tbalden.
I hope this post might help some
Excellent! Keep it up
tbalden said:
Excellent! Keep it up
Click to expand...
Click to collapse
U aswell... Both of you keep up the great job
This is amazing, can't wait for the others to try and read their reviews..
just a small heads up before anybody complains.
We, @tbalden and me, just noticed a bug went unnoticed during our previous testing.
If you flashed this kernel or CleanSlate-Kernel, have the CleanSlate config app installed and Backlight dimmer enabled in the CleanSlate Config app. Make sure to keep the screen on for 3-4 minutes after rebooting your phone and the boot process finished.
Otherwise your screen will stay black. Display-Panel driver doesn´t seem to like our mod at the moment.
After keeping the screen on for 3-4 minutes the bug will not be triggered and you can use the phone as you wish.
Sorry for the inconvenience
The issue will soon be resolved in a new update
Freak07 said:
just a small heads up before anybody complains.
We, @tbalden and me, just noticed a bug went unnoticed during our previous testing.
If you flashed this kernel or CleanSlate-Kernel, have the CleanSlate config app installed and Backlight dimmer enabled in the CleanSlate Config app. Make sure to keep the screen on for 3-4 minutes after rebooting your phone and the boot process finished.
Otherwise your screen will stay black. Display-Panel driver doesn´t seem to like our mod at the moment.
After keeping the screen on for 3-4 minutes the bug will not be triggered and you can use the phone as you wish.
Sorry for the inconvenience
The issue will soon be resolved in a new update
Click to expand...
Click to collapse
Also just start the app manually on reboot, as a workaround.
Coming here from your OG Pixel kernel. Is this kernel for 2007.47 or 2007.32?
MrxSiN said:
Coming here from your OG Pixel kernel. Is this kernel for 2007.47 or 2007.32?
Click to expand...
Click to collapse
Nice to see you made the jump! Must be a hell of an upgrade on your side!
the .47 sources are merged. I´m using it on .47 at the moment.
I guess you can just give it a try and check if it boots/works on .32. If you decide to do so, it would be nice if you could report back here. It might help others
Make sure to have a PC with working fastboot environment nearby and a boot.img handy.
In case it doesn´t work, just force the phone to power down by holding power button plus volume down, once it powers off, keep holding power and volume up to boot to bootloader.
Connect to side port and flash your backup boot.img via fastboot. Always make sure to flash the matching boot.img for your firmware.
Hey guys and girls,
Here´s the fix that solves the black screen issue, that occurred when the screen was off while Brightness Dimmer got activated via CleanSlate Config App on boot.
It wasn´t detected immediately, because usually the screen of my device is on when I boot the phone as to check the logs and ensure everything is working
Now everything is working, so just flash the kernel and enjoy I´ll do a post soon, explaining the features a bit more for people unfamiliar with how the CleanSlate features work.
I´d advise everybody to read the instructions in the OP and follow them. They are written for a reason, because they ensure everything will be working as expected.
Kernel is made for the latest stock rom from Asus, you must update your phone to the most recent Asus update, before flashing the kernel.
Enjoy!
Changelog:
- Fix Screen not being able to wake up on a certain condition.
I wish you all a nice day/evening!
Download is below
Download:
Disclaimer/Important:
Kernel: https://www.androidfilehost.com/?fid=8889791610682925903
Instructions how to flash the kernel can be found in the OP!
But look at this post too
To make use of the CleanSlate features, like force FPS on Low Brightness or Brightness Dimmer you need to download both CleanSlate Apps:
Please take a look at the CleanSlate thread for CleanSlate features. I will provide the link to the free to download apps here.
If you use the CleanSlate features and benefit over time, maybe think about giving something back to @tbalden and purchase them from PlayStore.
CleanSlate Configuration App (to control the features):
https://www.androidfilehost.com/?fid=8889791610682925529
CleanSlate Companion App (provides additional information from userspace for CleanSlate Kernel features to work correctly)
https://www.androidfilehost.com/?fid=8889791610682925528
Have fun, enjoy the kernel and your phone.
If you like my work please consider a donation.
Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea: http://paypal.me/freak07
I'm using Tencent Version, but already fully converted to Global ROM. Updated from 32 to 47. Already flash your kernel. It's works.
MrxSiN said:
I'm using Tencent Version, but already fully converted to Global ROM. Updated from 32 to 47. Already flash your kernel. It's works.
Click to expand...
Click to collapse
So what's the difference after?
AldRezaine said:
So what's the difference after?
Click to expand...
Click to collapse
If you mean CN to Global ROM, Global has no China bloatware. If you mean 32 to 47, here the changelog from Asus website.
1.Added “Quick launch camera” option in System Settings->Advanced
2.Added “Navigation blocking” feature for Game Genie which disables system gesture operations to avoid accidental touches in games.
3.Improved multi-touch when three or more fingers simultaneously touch the screen in games.
4.Fixed a problem with insensitive multi-finger touch response when playing PUBG
AldRezaine said:
This is amazing, can't wait for the others to try and read their reviews..
Click to expand...
Click to collapse
AldRezaine said:
So what's the difference after?
Click to expand...
Click to collapse
Just to steer this a bit in the right direction. This isn´t directed towards anybody in particular it´s just a general reminder what this thread is about.
There is no need to review the kernel. The kernel offers exactly what is described in the first post of this thread.
My advice is to read the description in the OP. All changes are explained in great detail there. Look around XDA, most OPs are kept way shorter with less explanations.
If you´re not into technical details, use google when descriptions or terms are unclear to you.
This is primarily a development focused thread. That´s why it is in the development section.
If there are issues when using the kernel or its features, provide logs and I will be glad to help you. If there are questions or things unclear, ask and I will try to answer. But I expect people to put in a bit of effort.
If you expect a review like, flashing this kernel causes my phone to use more or less battery as the stock kernel, you may want to re-read the OP on what to expect. I generally don´t like to see this in my threads.
Just to give an example that a "review" will never be applicable to each user:
Everybody uses their phone different. So certain changes to the scheduler may benefit user A, while they don´t benefit user B.
There is no need for a review. Just flash the kernel and try for yourself.
It´s very easy and straightforward to flash the kernel. And it´s also easy to return back to the stock kernel. If you don´t like it describe your problem as detailed as possible, as pictured in the FAQ and I will take a look at it or consider it.
Usually post like: "this kernel reduces my battery life by xyz" will just be ignored
It´s covered in the FAQ how to do all of this.
This is also a general reminder to everyone Let´s keep this thread development related and I hope this will turn out to be a good project!
I´m really looking forward to it. This phone is an absolute beast and so far I really enjoy using it.
For people a bit unfamiliar how everything works I plan to soon post a little guide on how to use the CleanSlate features.
Have a nice day everybody.
Here´s a small tutorial for CleanSlate features:
https://forum.xda-developers.com/showpost.php?p=83387681&postcount=3
Hopefully it will help some, that are not yet familiar with these.
I wish everybody a nice weekend.
Amazing work. Low battery temp while fast charging. Now I can just leave my phone with 30w charger without worry.
Do you have Telegram Channel?
I thought its not working after i flash but suddenly all the features is needed an app CleanState Config/Companion i downloaded it and it works the 144hz in 0 brightness nice2. i will use this kernel as my daily bases.
I turn on the facedown to table to turnoff the screen or vibrate but its not working for me.
Edit: Its working btw there is a 1 sec delay after facedown so far so good.

Categories

Resources