[ROM][OFFICIAL][fajita][13] LineageOS 20 - OnePlus 6T ROMs, Kernels, Recoveries, & Other Dev

[ROM][OFFICIAL][fajita][13] LineageOS 20 - OnePlus 6T ROMs, Kernels, Recoveries, & Other Dev

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Related

[ROM][6.0.1][T810][UNOFFICIAL] CyanogenMod 13.0 for Tab S2 9.7 [BETA]

{
"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"
}
The first nightly is build and on-line. :victory:
I've created new thread for the OFFICIAL build.
Switching to that thread.
This ROM is BETA and not ready for daily use at the moment
Marked as Beta from the start, as almost everything works.
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community
First I would like to thank the following developers :
@CTXz
@RaymanFX
@BigBot96
@moonbutt74
@sub77
@hennymcc
I used @RaymanFX's T815 image to base my cm 13.0 build on.
Biggest difference was the build environment, somehow the gts2-common blobs weren't included.
Before you start
THIS ROM IS ONLY FOR THE SM-T810
Code:
*
* Your warranty will be voided !
*
* 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.
*
About the ROM
Current state of ROM : BETA
Everything except what's reported below is working. Nothing 'fixed' yet, first build.
What is Fixed
Device crashes when playing some video content. (not known which, at least youtube causes the crash)
External SD only available via /mnt/media_rw for user root.
On screen lock screen rotates back to 0 position
Chromecast rotates screen 90 degrees.
After selinux enforcing, mDNIe is not working.
What is not working
Important
Fingerprint scanner not working
Minor
mic not working?
Instructions
How to install CM13.0
If you haven't run stock Android 6.x, flash that first with odin. (image won't boot without this step)
If you don't have TWRP yet, get it from here : TWRP by ashyx
Download the ROM and the Gapps that are located below to your device
Reboot into TWRP by holding VOL UP + POWER + HOME on boot
In case things go wrong make a backup
After the backup has completed return to home and select Wipe and then Advanced Wipe
Now ONLY tick Dalvik Cache, System, Data and Cache
After ticking those, Swipe below to wipe
Once the wipe has completed return to home and select the ROM
After you selected the ROM swipe below to install it
After the ROM has installed flash the Gapps
When all of this is done, reboot into system, wait, and enjoy CM12.1
How to recover from issues
Looks like the reset to recovery (<HOME><VOL-UP><POWER>) is still broken on some or all T810 devices with this build.
Press and hold <HOME><VOL-DOWN><POWER> to enter 'download' screen.
Select cancel <VOL-DOWN>
Immediately press and hold <HOME><VOL-UP><POWER> to enter TWRP
Restore back-up made during installation phase
How to ROOT
In CM 13.0 Enable the developer options
Select Root access
Select Apps Only
Done
Questions and bug reporting
The following questions will be ignored
Inappropriate questions
Forced orders, EX. : "PLS FIX!!!!!!"
ETA's
Often repeated questions usually by the same user
Requests that are out of CM's framework (Ex. Adding Samsung Apps)
How to report a bug/issue
Explain exactly what happens
Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)
If you can't mention a log, explain as precise as possible when, why and where it occurs!
Changelog
Code:
**********
28/06/2016 - Reverted wifi settings, as it breaks EU wifi (at least mine, channel 13 on 2.4 GHz)
- Some gralloc patches to improve 2D performance.
**********
27/06/2016 - Awaiting nightlies, wifi setting changed so it should work on all channels in the world.
**********
25/06/2016 - Last build to check if all is in place for nightlies. (I hope)
**********
22/06/2016 - First build from CyanogenMod source location.
- Working on sorting out system blobs (common vs device)
**********
21/06/2016 - Selinux back to enforcing, mDNIe fixed.
- Screen rotate fixed in virtual display (rotation on lock and cast was caused by this)
**********
20/06/2016 - Selinux back to permissive, enforcing breaks mDNIe.
**********
19/06/2016 - Broken camera fixed.
**********
18/06/2016 - Switched to gts2-common device from CyanogenMod after patches were accepted.
- Selinux defaults to enforcing. (userdebug image, so still configurable)
- External sdcard available under /storage.
**********
17/06/2016 - Switched to gts2 kernel from cyanogenmod after kernel config was accepted.
- Video works.
- McDaemon quiet now.
**********
15/06/2016 - Minor tweaks in cpu usage and opengl settings copied from T815 sources.
**********
14/06/2016 - Rebuild without Telephony support. (Clean flash could be required, testing)
- Switched back to original modem.
**********
13/06/2016 - Configured correct modem, disabled lte.
**********
12/06/2016 - First build based on T815 code from [user=3463426]@RaymanFX[/user]
- Init permissive (hard coded)
**********
Downloads
Latest CM 13.0 build : https://www.androidfilehost.com/?fid=24591020540823040
All CM 13.0 releases can be found here : https://www.androidfilehost.com/?w=files&flid=45563
All CM 13.0 beta releases can be found here : https://www.androidfilehost.com/?w=files&flid=68015
Recommended GAPPS by opengapps.org : http://opengapps.org/ (I use pico)
Source
Special Thanks to @RaymanFX for releasing his Exynos 5433 source, without him this ROM would most likely not be possible!
All my sources can be found here : https://github.com/CyanogenMod/android_device_samsung_gts210wifi
Screenshots
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
XDA:DevDB Information
CyanogenMod 13.0 for Samsung Galaxy Tab S2 9.7 T810, ROM for the Samsung Galaxy Tab S2
Contributors
T_I,CTXz, Sub77, Moonbutt74, RaymanFX, Hennymcc
Source Code: https://github.com/Galaxy-Tab-S2
ROM OS Version: 6.0.x Lollipop
Based On: CyanogenMod
Version Information
Status: Beta
Created 2016-06-13
Last Updated 2016-06-27
XDA:DevDB Information
CyanogenMod 13.0 for Tab S2 9.7, ROM for the Samsung Galaxy Tab S2
Contributors
T_I, CTXz, RaymanFX
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock Android 6.x flashed at least once before install
Based On: Cyanogenmod
Version Information
Status: Nightly
Beta Release Date: 2016-06-12
Created 2016-06-13
Last Updated 2016-06-29

Reserved

Reserved 2

For people who use Titanium Backup with a license file, place it in /storage/emulated/0/ to get it active again. You'll need to copy the backup location to internal storage as well, to be able to access it again, while we're hunting for the reason why the external_sd isn't mounted correctly.

Woohooo CM13
Awesome T_I ..
started testing this morning (as much as the jobs allows
Flashing worked like a charm, booting etc nice ..
Currently trying to restore apps via Titanium.
Only thing i noticed is the autorotation only works 270 degrees,
turning upside down.
Rest i can tell if i have my vital apps working
Thanks already. :good:

CuckooPenguin said:
Only thing i noticed is the autorotation only works 270 degrees,
turning upside down.
Click to expand...
Click to collapse
Default is to rotate 0, 90 and 270 degrees (should work, does here) and lock-screen rotation disabled. I've enavled the 180 degrees rotate and lock-screen rotate after boot.

So no camera? Or is it just my tab again????

suzook said:
So no camera? Or is it just my tab again????
Click to expand...
Click to collapse
Looks like it's your tab again. Do you really have a T810? Can you do an adb logcat while you open the camera app, so we can check what's going wrong? I did advanced wipe this morning (Dalvik Cache, System, Data and Cache) and installed. I can use both camera's and the apps are switching nicely between them.
I even managed to kill off the lte part in the latest build. (OP updated) The only issue I now have it the fact the device refuses to mount the microsd under /storage/<UUID> . It creates the directory, just no mount, only under /mnt/media_rw/<UUID>, which is only accessible by root.

Guys, how is it with updates? Have I to do fresh install after each update released or there is internal updater?
Thank you

Vardenf said:
Guys, how is it with updates? Have I to do fresh install after each update released or there is internal updater?
Thank you
Click to expand...
Click to collapse
This is an UNOFFICIAL build, so yeah, all updates are manual.
Flashes can be done dirty, even from cm 12.1 to 13.0, as long as you've had stock Android 6 on the device at least once. But remember, no guarantees whatsoever, other then "you're lucky when you don't brick the device".

T_I said:
Looks like it's your tab again. Do you really have a T810? Can you do an adb logcat while you open the camera app, so we can check what's going wrong? I did advanced wipe this morning (Dalvik Cache, System, Data and Cache) and installed. I can use both camera's and the apps are switching nicely between them.
I even managed to kill off the lte part in the latest build. (OP updated) The only issue I now have it the fact the device refuses to mount the microsd under /storage/<UUID> . It creates the directory, just no mount, only under /mnt/media_rw/<UUID>, which is only accessible by root.
Click to expand...
Click to collapse
Yup, I really have a t810. Idk what's going on. I will check again tonite. Thanks again...this build is awesom.

Where can i download the stock Android 6.x rom to flash with odin?
I only found for T710, T815..
edit:
ok, i found it here

suzook said:
Yup, I really have a t810. Idk what's going on. I will check again tonite. Thanks again...this build is awesom.
Click to expand...
Click to collapse
Had some issues myself, the external sdcard just won't mount, log complains about finding 2 root filesystems...
BTW for the people that had the lte image or my 12-6 image, before flashing the 13-6 image, do a complete wipe. Logcat, while hunting for my ext_sd issues, showed loads of crashing processes on mobile data bits that are now missing, eating loads of cpu time, from time to time crashing the tablet.
Sent from my T810 running cm-13.0

Arm or arm 64 for the gapps?
Sent from my SM-T810 using Tapatalk

Do you guys have a issue with Netflix? I have a T815, I'm running RaymanFX build and I can't have it workingworking!

TheMorpheus said:
Do you guys have a issue with Netflix? I have a T815, I'm running RaymanFX build and I can't have it workingworking!
Click to expand...
Click to collapse
Just set it up. When I start a video in netflix my tab reboots. ?
Sent from my SM-T810 using XDA-Developers mobile app

Yes!!!!! I got camera!!!! Woohoo!!! Thanks op.....cm13 is awesome!

stoehner said:
Arm or arm 64 for the gapps?
Click to expand...
Click to collapse
arm. (just using the dtb from samsung, which is arm, haven't looked into building one myself, which I guess is needed by arm64)
DAE1964 said:
Just set it up. When I start a video in netflix my tab reboots.
Click to expand...
Click to collapse
Have same stability issues, solved them by clean installing the 13-6 version. Now it's not crashing, just slow.
I'm suspecting that the modem I used is giving some issues. (or other stuf that are still expecting an lte modem)
I'd advice a clean install of the 12-6 build and test if that is unstable as well.
suzook said:
Yes!!!!! I got camera!!!! Woohoo!!! Thanks op.....cm13 is awesome!
Click to expand...
Click to collapse
Nice, congratulations, but now the real question, do you have both?

DAE1964 said:
Just set it up. When I start a video in netflix my tab reboots. ?
Sent from my SM-T810 using XDA-Developers mobile app
Click to expand...
Click to collapse
My YouTube reboots my tab as well.
Sent from my SM-T810 using Tapatalk

Just checked with with the 12 and the 13 build and in both I get loads of these errors:
Code:
06-14 06:18:34.927 5820 5820 I McDaemon: Daemon starting up...
06-14 06:18:34.927 5820 5820 I McDaemon: Socket interface version is 0.2
06-14 06:18:34.927 5820 5820 I McDaemon: *** t-base-300-Ares-2-Android-V001 ###
06-14 06:18:34.927 5820 5820 I McDaemon: Build timestamp is Jun 13 2016 08:20:31
06-14 06:18:34.927 5820 5820 E McDaemon: ERROR - checkMciVersion():
06-14 06:18:34.927 5820 5820 E McDaemon: ***** (null)
06-14 06:18:34.927 5820 5820 E McDaemon: ERROR - initDevice():
06-14 06:18:34.927 5820 5820 E McDaemon: ***** checkMciVersion failed
06-14 06:18:34.927 5820 5820 E McDaemon: ERROR - run():
06-14 06:18:34.927 5820 5820 E McDaemon: ***** Could not initialize <t-base (because /dev/mobicore could not be openend)!
06-14 06:18:34.927 5820 5820 E McDaemon: ERROR - main():
06-14 06:18:34.927 5820 5820 E McDaemon: ***** Exiting <t-base Daemon
There is no difference when the image nags about not having network and when it doesn't. I noticed that the device started to lag a lot after a while. (Could be due to the junk I have on there, it's pretty packed with apps )
Doing a new build without Telephony stack from cm amd with the regular base stack from aosp instead of the telephony stack. I'm also forcibly using the T810 blobs. (de-commonized the blobs) Doesn't look to bad during the build.

[CLOSED] [Treble][ARM64][AOSP][J530X]Project_Spaget X

{
"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"
}
Welcome to Project Spaget X ARM64 Treble For Galaxy J530X/J730X/G610X/J701X/J710X
Some information you should know..
This is a full Treble ARM64 Vendor/Kernel implementation for the Exynos7870 Supported devices
If you want to report a Bug, read the F.A.Q First Then provide a logCat OR LoggingKit.zip with detailed explanation
Read the instructions and the F.A.Q Before installing the rom or posting a reply.
[FOR DEVS] You are allowed to customize this vendor if you want to use it in ROMs with proper credits. but not to distribute 1:1 copies
- Personal Notes
And here we are, few leaks and reworks later. X is here. i went with a letter this time just because it looks cool. This is officially going to be EOL for ARM64 AONLY vendors that i make (unless a critical bug was here that needed attention) . i dont have alot of time to work on 7870 And when i do i prefer it to be on something more productive than Treble
Anywya, TLDR : alot changed, alot was fixed. its a new vendor, flash and enjoy
Old releases
Alright, The "second" Treble update is here, this time it is FULLY ARM64 compatible. Thanks to the hard-work of @Astrako who managed to boot ARM64 Exynos 7885 bases on our device. This project is HEAVILY based on his work. and i would like to make that very clear. This is not a OneMan job. this took alot of hardwork by many people to make it reach the stage it is at. basically we are official minus the tag. This project is also possible thanks to my dear friends @Kique119 @me2 @SPARTANICUS and my other testers who spent day and night testing this with me.
At this stage, everything is mostly GSI related.
And finally, the cherry on top, is support for 3 more devices. Thanks to the devs who assisted me on adding support for their own devices. mentioned below.
If you appreciate this ambitious project, consider hitting thanks, supporting the thread, and donating (Paypal) to support my development (using cocaine of-course)
- Initial Notes:
Supports ONLY the mentioned devices Above
1. Don't forget to check bugs before asking questions
2. Since most of the GSIs are AOSP, forget about VoLTE, Knox features, Samsung apps, Camera mods or features, or other Samsung related features.
3. You can use any non-treble rom even if you have treble vendor installed, as long as you flash a non-treble kernel. The rom will ignore your vendor and everything will be as non treble.
- General Features :
- based on G965F Vendor with VNDK-28
- Adapted to J730/J530/G610/J710/J701 devices
- latest CronosKernelV5 included with most of the features of OneUI kernel + many more
- misc things enabled in framework overlay for better experience
- Seamless GSI patching, without user intervention
- Seamless setup process, with dynamic Scripts
- And Spaget
- How to Install Project Spaget:
- Flash `Exynos7870_CreateVendor` and reboot recovery
- Flash `Exynos7870_Spaget_X`
- Flash your desired ARM64_AONLY GSI
- Read OPTIONAL below
- What GSIs are support/recommended ?:
- Avoid sGSIs and flash source built GSIs (Such as PHH,PE)
- ARM64_AONLY GSIs only
- I recommend Pixel-experience or evo x and luke GSIs
- if you want a daily rom. avoid sGSIs
- More can be found here : Treble
- I dont have googleapps. what do i do ?:
ONLY for gsis that does not come with google apps
- Download Gapps pacakge from Here (ARM64 > VER > Micro or lower
- Go to TWRP > Wipe > Advanced Wipe > Tick System > Repair > Resize
- Flash opengapps_xxxx
- I need more info. where do i get it ?
Ask in this thread. if you need more , head to
Spaget Notes and support : Telegram Group
General bugs (GSI):
- offline charging is broken in Android 10 roms
- Bluetooth Calls
- Some GSIs might not include a camera, use Footej
- Some camera apps will have stretch
- I dont like it, how do i revert ?:
- Reboot to recovery
- Flash `Exynos7870_RevertVendor`
- Reboot recovery
- Flash any non treble rom or restore your previous twrp backup
Is that all ? I have treble now ? what about all the complicate process before ?
Yes, you now have a project treble device, ready to flash any GSI/sGSI of your choice aslong as it fits in your SYSTEM partition.
The entire process changed and now is much more seamless and noob-friendly. yet take caution as always
What if i didn't boot ?
In some cases, you might be stuck at a bootanimation loop or a splash loop, in this case follow the troubleshooting steps in the F.A.Q post
Credits
@corsicanu For great help with the repartition scripts, GSI patching and tons other throughout the years.
@Astrako for making booting ARM64 a possibility. and allowing this project to exists. kudos
@Kique119 For his awesome testing and documenting this project, without him there would be no spaget
@KassemSYR, for G610F Support and testing.
@Zero_Cool7870 , @DAvinash97 , @mohitsama and ORIGINALNAME123 for J710/J701 support
@SPARTANICUS For his great work maintaining KRAKEN kernel, which supports this project fully
Testers :
@Kique119 @LuanTeles @ion1s @djedjy @vsmhell @fetaiharbin @Mizo2019 @Me2 @LelMwhLwl @@rlukas210
@PedroDomeneghi @DaffyMirror4318 @bien2004official @AleeX157 @Alijouhara
And many more i cant remember the usernames of. please mention
Downloads. Changelogs , F.A.Qs below
OldPost (a64)---
So, i have been hesitated to release this project since last year. GSIs are not the most stable and many J users prove they are unable to read. they just want ready stuff. with this project that is not the case. if you skip the instructions/F.A.Qs and notes, dont bother installing this project as you probably wont be able to get it running.
This is a fully featured VENDOR and KERNEL designed for this device to support project treble, it is based on other Exynos 7870 Vendors and modified to support our devices, i have also added few patches and updates that even official 7870 vendors do not have. to get the best possible experience
I have also added a GSI_PATCH zip that should be used if you want to have the least amount of bugs.
The vendor is pretty much bugles, therefore any bugs you face, Report them to the appropriate Threads of the GSI you installed. or github issues section. as those are not mine to fix. i only provide the vendor and kernel that allows GSIs to run on.
- STEPS FOR INSTALLING TREBLE VENDOR:
Flash “Treble_Jx30F.img” in TWRP as Image (Selecting RECOVERY)
Reboot recovery.
Wipe System, Data, Dalvik and Vendor.
Flash "jxy17lte_Vendor_9.0_v1.0.zip".
- STEPS FOR INSTALLING GSIs:
Download the desired GSI (it MUST be arm_binder64/A64 Variant)
unpack it if it wasn't in .IMG format
Go to TWRP , Install , Install IMAGE
Pick your GSI and select SYSTEM IMAGE
Flash "GSI_Patch.zip".
[OPTIONAL] Flash the “Gapps_patched.zip”
- STEPS FOR INSTALLING GAPPS:
If you flash Gapps, Google will spam you with fullscreen warnings and notifications about your device not being certified. But don't worry, you can certify it.
Just reach the homescreen, then proceed to install the "Device ID.apk". Use it to grab the Google Services Framework ID and paste it here: https://www.google.com/android/uncertified/
And paste the ID there. Then wait a few minutes and reboot. Few seconds after rebooting, you'll be done and you'll be able to normally log in as always.
- [OPTIONAL]STEPS FOR INSTALLING Magisk_GAPPS:
** Note : This gapps is recommended for all **
Download latest gapps from http://opengapps.org
place in /sdcard or /external_sd
flash magisk.zip
flash magiskgapps.zip
- Confirmed working GSIs :
** You can only use ARM_BINDER64 / A64 GSIs **
PHH AOSP V113 : Github
OmniROM GSI : XDA
Liquid Remix : GoogleDrive
Pixel Experience With Gapps : GitHub
Resurrection Remix : RR
XenonHD : TeamHorizon
P.S : only Omni and PHH Do not require the GSI_PATCH_FP The rest do in order to get Fingerprint working
- Known GSI Bugs:
Bluetooth calls are broken
Some 3rd party cameras have stretched pictures
And more here at Github Issue
Credits
@corsicanu For general help through out the years
@prashantp01 For overlay fixes and native camera fix. and other contributions
@Kique119 For his awesome testing and documenting this project
Testers :
@Kique119 @LuanTeles @ion1s @djedjy @vsmhell @fetaiharbin @Mizo2019 @Me2 @LelMwhLwl
And few more that didn't give me their usernames
Downloads. Changelogs , F.A.Qs below
XDA:DevDB Information
Treble, ROM for the Samsung Galaxy J5
Contributors
ananjaser1211
Source Code: https://github.com/ananjaser1211/Helios_7870
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Latest bootloader and modem
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: X
Stable Release Date: 2020-01-13
Created 2019-05-11
Last Updated 2020-01-13

Downloads and changelogs
NewsChannel : Telegram
Come hang with us on our chat : Telegram
Official Treble support Group : Telegram
----------------------------------------------------------------
SpagetX Treble ARM64 Vendor Based on G965F VNDK-28
GoogleDrive : Download
P.S : If you failed to download please login and save the folder
P.S 2 : This requires Pie bootloader and modem on devices that supports them (I.E not j710 or g610)
----------------------------------------------------------------
Spaget Treble ARM64 Vendor V3.0 Based on A750FN Vendor
MegaDrive Download : MEGA
GoogleDrive Mirror : GDrive
Documentation : Here
Spaget X
- ReMade fully based on VNDK-28 S9 Vendor
- Based on Project Pizza Treble (8890)
- included most fixes for audio, webview and others
- added fixes for camera
- removed alot of obsolete hacks
- samsung offline charging added
- Re-did props and features and overlays
- Added patches for Android 10 Roms
- Fixed nuke.sh script on 10 roms
- fixed performance in some GSIs
- Fixed thermal , power , memtrack and other HALs
- Improved OMX fixes
- Removed alot of samsung security services
- Improved Wifi, NFC, graphics , camera and other fixes
- Fixed some reboots on G610
- Fixed Youtube Crashes and OMX issues on most devices
- Addressed alot of random reboots
- Fixed GNSS/GPS on some variants
- Removed HKTweaks due to reboots
- Fixes for J710 Wifi and bluetooth
- Tons of other changes and improvments
[COLOR=""]Spaget V3.0[/COLOR]
- Fully based on A750FN 64Bit Vendor
- Seamlessly integrated ALL patches into the vendor
- No longer do you need customized TWRPs, patches, zips whatever. just the vendor and GSI
- Fixed all the VENDOR related issues we had
- Audio, camera, NFC, everything is redone from scratch and improved
- Supports Android Q booting
- Updated overlays and configs
- Added support for J710/J701/G610
- Updated to Helios V4.0 Kernel with tons of changes and goodies
- Automatic GSI patching at first boot
- New repartition script with extended support. fail safes, backup features and tons more
- Live TWRP patching, so it will patch whatever twrp you have instead of using my own
- And tons more through out the months of testing, using and developing
- Please read the thread agian to understand how to use it
OLD(a64)
----------------------------------------------------------------
Treble Vendor V1.5 Based on Stable A600FN Pie Vendor
Full TREBLE Documentation and guides here : GoogleDocs
Treble folder mirror : MEGA
Treble Vendor V1.0 Based on Stable A600FN Pie Vendor
GoogleDrive Project : Download
Full TREBLE Documentation and guides here : GoogleDocs
Treble folder mirror : MEGA
---------------------------------------------------------------
V1.5
1- HeliosPro 3.1 Kernel
2- Added HKTweaks
3- Fingerprint fix for All GSIs
4- Hotspot fix for All GSIs
5- AdaptiveBrightness
6- Updated included overlays with more features and pie base
7- DualbootPatcher J5/J7 Seperation
GSI_PATCH_V2.0
1- Patch fingerprint libs for all GSIs
2- Switch to samsung fingerprint
3- Add device model number detection
4- replace gsi fingerprint with stock one
GSI_PATCH_FP
1- Special patch for PE/RR/LR and other roms that do not have working FP
2- Do not flash on OMNI/PHH
3- Must be flashed AFTER the Vendor/GSI
Kernel updates
- Updated base to latest pie source
- reworked and updated helios ramdisk tweaks
- Reverted old hacks to fix some bugs
- Performance and battery greatly improved
- F2FS enabled
- LZ4 Enabled
- GPU Performance Greatly improved
- Full CPU/GPU/DEVFREQ/MIF/CAMERA Voltage control and more
- Magisk V19.1 included
Bugs :
1- some users might face SDCard issues while using PE
- if you did , back up its data and format it in PE
V1.0
-initial release
- Helios Kernel 2.8

F.A.Q And Notes
Q: Device requirements ?
A : you MUST be on an Pie Bootloader and Modem, otherwise you will have no sim, no lockscreen etc (Devices such as J710 and G610 can use OREO)
Q : Do i need to format internal storage ?
A : No
Q : Can i use the Treble recovery for normal ROMs ?
A : Yes, it is preferred especially when making backups. just be sure to wipe vendor when switching to non treble roms
Q : What Camera is recommended ?
A : Footej and open camera works the best
Q : Can i flash any GSIs ?
A : Any GSI that is ARM64_AONLY is supported [8/9/10]

Additional
Reserved 3

Yo good job! Glad to be a tester ?

Hi, is this stable? And when I tried to install a gsi 2 weeks ago i could only install it as boot or recovery image.

Treble folder mirror : http://bit.ly/2E53Vqb
PHH gsi is uploaded there. Omni and RR will follow

Can I use PixelExperienceP?

Sim is not working and i tried even the command form the issue forum. The modem and the bootloader is at the latest version im on j530F single sim. What can i do to fix it?

Enzio2 said:
Sim is not working and i tried even the command form the issue forum. The modem and the bootloader is at the latest version im on j530F single sim. What can i do to fix it?
Click to expand...
Click to collapse
I also had that problem. And i cant resolve it. I try command line.
I try to change build.prop but bild prop has only few lines.
I back on prometheus 9.0.

Enzio2 said:
Sim is not working and i tried even the command form the issue forum. The modem and the bootloader is at the latest version im on j530F single sim. What can i do to fix it?
Click to expand...
Click to collapse
Go to vendor/etc find a line called ro.multisimcount 2 and change the value 2 to 1 and reboot

LelMwhLwl said:
Go to vendor/etc find a line called ro.multisimcount 2 and change the value 2 to 1 and reboot
Click to expand...
Click to collapse
thank you so much i t worked.

All seems to be working as advertised. I just have one problem with signal strength. I shows that I always have zero bars signal. Calls and internet works fine.

drjacek14 said:
All seems to be working as advertised. I just have one problem with signal strength. I shows that I always have zero bars signal. Calls and internet works fine.
Click to expand...
Click to collapse
If it works I dont think its a big problem.
Anyway I will test this in few hours when I get home.

Does any of you have brightness problem ?

drjacek14 said:
All seems to be working as advertised. I just have one problem with signal strength. I shows that I always have zero bars signal. Calls and internet works fine.
Click to expand...
Click to collapse
And what GSI you use? If its RR I will test it later.
Its the only one im familiar with
---------- Post added at 04:27 PM ---------- Previous post was at 04:26 PM ----------
Enzio2 said:
Does any of you have brightness problem ?
Click to expand...
Click to collapse
Do u mean auto brightness?
It says in the bugs its not working.

I know that i mean the brightness slider when is at 50 % it feels like its 15 or 20%

Enzio2 said:
I know that i mean the brightness slider when is at 50 % it feels like its 15 or 20%
Click to expand...
Click to collapse
You could reinstall the rom with clean flash(wipe system,data,internal storage,vendor and preload.
Then install the rom again with vendor zip.
If that doesnt work send a logcat.

victorAndrie said:
If it works I dont think its a big problem.
Anyway I will test this in few hours when I get home.
Click to expand...
Click to collapse
It workes fine. And I use RR

victorAndrie said:
You could reinstall the rom with clean flash(wipe system,data,internal storage,vendor and preload.
Then install the rom again with vendor zip.
If that doesnt work send a logcat.
Click to expand...
Click to collapse
i did the reinstall and here is the logcat
---- May 12, 2019 3:39:45 PM ----
--------- beginning of main
05-12 15:36:53.000 6180 6180 W scd.lcex: Using default instruction set features for ARM CPU variant (generic) using conservative defaults
05-12 15:36:53.307 6180 6203 I ConfigStore: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasWideColorDisplay retrieved: 0
05-12 15:36:53.307 6180 6203 I ConfigStore: android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasHDRDisplay retrieved: 0
05-12 15:36:53.307 6180 6203 I OpenGLRenderer: Initialized EGL, version 1.4
05-12 15:36:54.575 6180 6203 W libEGL : EGLNativeWindowType 0xde8ed008 disconnect failed
05-12 15:37:11.475 6180 6180 I AppCompatDelegate: The Activity's LayoutInflater already has a Factory installed so we can not install AppCompat's
05-12 15:37:15.274 6180 6203 W libEGL : EGLNativeWindowType 0xde8ed008 disconnect failed
05-12 15:37:22.132 6180 6180 I AppCompatDelegate: The Activity's LayoutInflater already has a Factory installed so we can not install AppCompat's
05-12 15:37:23.763 6180 6203 W libEGL : EGLNativeWindowType 0xde8ed008 disconnect failed
05-12 15:37:36.722 6180 6180 I AppCompatDelegate: The Activity's LayoutInflater already has a Factory installed so we can not install AppCompat's
05-12 15:37:37.781 6180 6203 W libEGL : EGLNativeWindowType 0xde8ed008 disconnect failed
05-12 15:37:38.809 6180 6180 I AppCompatDelegate: The Activity's LayoutInflater already has a Factory installed so we can not install AppCompat's
05-12 15:37:39.539 6180 6203 W libEGL : EGLNativeWindowType 0xde8ed008 disconnect failed
05-12 15:38:29.075 6180 6203 W libEGL : EGLNativeWindowType 0xde8ed808 disconnect failed
05-12 15:39:04.366 6180 6180 I AppCompatDelegate: The Activity's LayoutInflater already has a Factory installed so we can not install AppCompat's
05-12 15:39:05.011 6180 6203 W libEGL : EGLNativeWindowType 0xe4fd4808 disconnect failed
05-12 15:39:42.419 6180 6180 I AppCompatDelegate: The Activity's LayoutInflater already has a Factory installed so we can not install AppCompat's
---- May 12, 2019 3:39:45 PM ----

[ROM][UNOFFICIAL][10.0][tb8703f/x/r/n] LineageOS 17.1 for Lenovo TAB 3 8 plus P8

{
"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"
}
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* 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, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
What works:
Calls/SMS/Mobile data
Wifi
Bluetooth
GPS
Camera
Audio
FM radio
Torchlight
USB and WLAN tethering
Broken
You tell me
Source code:
device : https://github.com/lenovo-devs/android_device_lenovo_TB8703
device tb-comon https://github.com/lenovo-devs/android_device_lenovo_tb-common
kernel: https://github.com/lenovo-devs/android_kernel_lenovo_msm8953
vendor: https://github.com/lenovo-devs/proprietary_vendor_lenovo
2020-09-06
Updated lineage code
Fixed FM radio
dpm daemon disabled for wifi version, hope this will resolve issues with wifi only tablet version (please report, I dont have wifi version to test)
mailru: lineage-17.1-20200906-UNOFFICIAL-TB8703.zip
gdrive: lineage-17.1-20200906-UNOFFICIAL-TB8703.zip
2020-06-01
Fixed boot on 8703f (wifi tablet version)
mailru: lineage-17.1-20200601-UNOFFICIAL-TB8703.zip
gdrive: lineage-17.1-20200601-UNOFFICIAL-TB8703.zip
Previous versions:
2020-05-31
Updated Lineage code
Updated system graphics and media binaries
selinux enforcing
mailru: lineage-17.1-20200531-UNOFFICIAL-TB8703.zip
gdrive: lineage-17.1-20200531-UNOFFICIAL-TB8703.zip
2020-03-31
Fixed boot issue on TB8703F (Wifi only version)
mailru: lineage-17.1-20200331-UNOFFICIAL-TB8703.zip
gdrive: lineage-17.1-20200331-UNOFFICIAL-TB8703.zip
2020-03-29
Fixed error message on boot on WiFi only tablet
Fixed issues with WiFi and Bluetooth MAC addresses
fixed other minor issues
Updated Lineage code
mailru: lineage-17.1-20200329-UNOFFICIAL-TB8703.zip
gdrive: lineage-17.1-20200329-UNOFFICIAL-TB8703.zip
2020-02-22
Initial release
mailru: lineage-17.1-20200222-UNOFFICIAL-TB8703.zip
gdrive: lineage-17.1-20200222-UNOFFICIAL-TB8703.zip
How to install
To install this you have to install TWRP using by QFIL utility, follow this instruction: https://forum.xda-developers.com/general/general/twrp-lenovo-p8-tb-8703f-tb-8703x-t3689442/post76277192
Special TWRP build
To install and boot any custom roms and to boot it after installing mods that change boot partitition like Magisk please use this TWRP:
2018-08-25
Fixed long time to wakeup screen in TWRP
Added NTFS filesystem for sdcards
mailru: twrp-tb8703-3.2.1-20180825-bootsign.img
gdrive: twrp-tb8703-3.2.1-20180825-bootsign.img
Previous version
[*] Первая версия
mailru: twrp-tb8703-3.2.1-bootsign.img
gdrive: twrp-tb8703-3.2.1-bootsign.img
This TWRP build has special function Sign boot which you have to click after install new version of ROM or mod like Magisk. It will append stock boot signature to your boot partition. This allows to boot with locked bootloader.
TWRP with Boot Sign function screenshots:
Fortunately you dont need to unlock bootloader, because not every Lenovo tab can be unlocked. Custom kernel and ROM can be runned by appending boot.sig signature extracted from stock rom to boot.img like
Code:
cat boot.img boot.sig > boot-signed.img
It still cant be loaded by fastboot, but you always can flash it from TWRP. You can get boot.sig in my repo https://github.com/HighwayStar/android_device_lenovo_TB8703/blob/cm-14.1/twrp/recovery/root/boot.sig
XDA:DevDB Information
[ROM][UNOFFICIAL][10.0][tb8703f/x/r/n] LineageOS 17.1 for Lenovo TAB 3 8 plus P8, ROM for the Lenovo Thinkpad Tablet
Contributors
highwaystar_ru
Source Code: https://github.com/lenovo-devs/android_kernel_lenovo_msm8953
ROM OS Version: Android 10
ROM Kernel: Linux 3.10.x
Based On: LineageOs
Version Information
Status: Testing
Created 2020-02-22
Last Updated 2020-03-31

Just installed it. Upon boot, a message poped up saying there's an internal error in the device, and that I should contact the maker (Lenovo). The message appeared once more before setup. Let's see how it goes now. Has someone else experienced this?

Installed over LOS16, I added GApps and Magisk. Everything is working fine, so far.
Inviato dal mio Lenovo TB-8703X utilizzando Tapatalk

Same error message for me. Upgraded from 16.
Installed Rom, gapps, magisk.
But then it's working. But performance seems worse compared to 16. I will give the system a little bit to settle down and check performance again.

Thanks for bringing Android Q to the Tab 3 8 Plus! Going to try it out later today

Catscratch said:
Same error message for me. Upgraded from 16.
Installed Rom, gapps, magisk.
But then it's working. But performance seems worse compared to 16. I will give the system a little bit to settle down and check performance again.
Click to expand...
Click to collapse
I had 15, 16 didn't work for me. But I did a factory reset, and then installed. Everything seems fine now, but performance appears to be worse off.

marcurelio said:
Just installed it. Upon boot, a message poped up saying there's an internal error in the device, and that I should contact the maker (Lenovo). The message appeared once more before setup. Let's see how it goes now. Has someone else experienced this?
Click to expand...
Click to collapse
I had the same, but the tablet seems to work great.

BTW. The error message appears on every boot for me. I also did a clean flash with factory reset.
Otherwise I can tell that a clean flash helped for most of the problems. When I upgraded from 16 I had visual glitches and system ui freezing sometimes. These problems are completely gone after doing the clean flash. Only thing that remains is the error message. But this message does not seem to effect the daily work.

Back to lineage 16
Big drain battery in 17

The system always stuck when using recorder

grivam said:
Back to lineage 16
Big drain battery in 17
Click to expand...
Click to collapse
This is true. Guess I'm going back to 15. I couldn't get 16 to keep wifi on when listening to music.

No deep sleep in lineage 17.....

Can someone make for x70l ?

@highwaystar
I tried to compile your sources but get errors is it possible there is missing something?

@highwaystar_ru
Hi,Can you help me ,i try to build crdroid with your device tree.But it miss dsp label.I try to add this label to file_context,failed with the message
Code:
Abort message: 'Error creating cache dir /data/dalvik-cache/arm64 : No such file or directory'
Thanks

Update here
2020-03-29
Fixed error message on boot on WiFi only tablet
Fixed issues with WiFi and Bluetooth MAC addresses
fixed other minor issues
Updated Lineage code

highwaystar_ru said:
Update here
2020-03-29
Fixed error message on boot on WiFi only tablet
Fixed issues with WiFi and Bluetooth MAC addresses
fixed other minor issues
Updated Lineage code
Click to expand...
Click to collapse
After clean install the rom reboots to recovery after 5 seconds everytime that is power on, sorry for my english, please fix it, thank you

Tablet freezes when using record screen in the chinese interface.

ferchnando said:
After clean install the rom reboots to recovery after 5 seconds everytime that is power on, sorry for my english, please fix it, thank you
Click to expand...
Click to collapse
Please upload files from /sys/fs/pstore from recovery after such reboot. There is seems to be some issue with wifi version, I only have LTE version to test, so any log will be appreceated.

ferchnando said:
After clean install the rom reboots to recovery after 5 seconds everytime that is power on, sorry for my english, please fix it, thank you
Click to expand...
Click to collapse
Uploaded fixed version
2020-03-31

[ROM][STABLE][10] LineageOS 17.1 for Xperia SP

{
"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"
}
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.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android,which is designed to increase performance and reliability over stock Android for your device.All the source code for LineageOS is available in the LineageOS GitHub repo.And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.Official LineageOS website : http://lineageos.org
Downloads Links
LineageOS 17.1 (Unlocked Bootloader) :Xperia SP (Huashan) - Development : https://mega.nz/folder/r11xAbSL#Lwt5FOvHpV1POu_3OHU6UwGoogle Applications (optional) :OpenGApps : https://opengapps.org (Use packages for ARM, Android 10.0, pico)Information : Flash the GApps before the first boot. If not, a clean flash is recommended.Recommended Recovery (optional) :TWRP 3.5.x : http://forum.xda-developers.com/xperia-sp/orig-development/-t3309938Disable the default Low-RAM features (optional) :Low-RAM Property Patcher : http://forum.xda-developers.com/-/-t3737373Tools required for bootimage patches such as root :Boot Bridge for Sony ELF : https://forum.xda-developers.com/-/-/-t3506883Informations and references :About LineageOS updates : ChangeLog available on https://download.lineageos.org/huashan/changes/About LineageOS device side : See my GitHub trees linked below
Flashing and updating
LineageOS clean install :- (Optional) Flash the boot.img kernel from the ROM zip with Fastboot or Flashtool- (Optional) Install TWRP Recovery to the FOTA partition (Read the TWRP thread)- (Optional) Wipe the data & cache (Backup to make sure not to lose data)- Flash the LineageOS ROM zip from recovery- (Optional) Flash a GApps package to have the Google Applications- (Optional) Every additional zip you want to flash- RebootLineageOS update / upgrade :- (Warning) Do not update / upgrade between OFFICIAL and UNOFFICIAL builds- (Information) Do not wipe anything unless you want to- Flash the latest LineageOS ROM zip from recovery- (Optional) Flash a GApps package on first install / upgrade. Not required later, but do update sometimes- (Optional) Every additional zip you want to flash- Reboot
About the builds
Device tree : https://github.com/LineageOS/android_device_sony_huashanKernel sources : https://github.com/LineageOS/android_kernel_sony_msm8960tDevice tree (Development) : https://github.com/AdrianDC/android_device_sony_huashanKernel sources (Development) : https://github.com/AdrianDC/android_kernel_sony_msm8960tVendor blobs : https://github.com/TheMuppets/proprietary_vendor_sony
Issues and reports
- Report issues only if you use the ROM original kernel- If an additional mod is installed, make sure it is unrelated, and mention it- Make sure the issue was not discussed earlier in the thread- Acquire ADB logcat logs to a file : how-to-take-logs-in-android- If the device crashed and rebooted, retrieve this file from the device : /proc/last_kmsg- Use Permissive Kernel Patcher and share logcat logs if it solves issues
Legal
About LineageOS Legal : http://lineageos.org/legal/The LineageOS team would like to thank everyone involvedin helping with testing, coding, debugging & documenting! Enjoy!
LineageOS available for Xperia SP also thanks to :
- Google AOSP- The LineageOS Team- Arne (arco68)- Everyone involved in working and testing
XDA:DevDB Information
LineageOS 17.1, ROM for the Sony Xperia SP
Contributors
AdrianDC
Version Information
ROM OS Version: Android 10
ROM Kernel: Linux 3.4.x
Status: Stable

ALSO WORKING ON SONY HUASHAN
Music Lights Effects implementation fully working
Presentation of the features : https://forum.xda-developers.com/showpost.php?p=73049970&postcount=399
YouTube Presentation :
IMPORTANT FEATURES TO KNOW
Boot sequence : Once the LEDs light up :
- Press Volume - to open LineageOS Recovery,
- Press Volume + to open the FOTA recovery (TWRP usually) if available
Powered-off alarm : When you have set an alarm
- If you power down the device, it will wake automatically 5 minutes before
- If you let the device charge offline, it will automatically reboot 5 minutes before
Gestures : Events like hand-wave and pocket removal can be enabled in the Settings
Force reboot : You can reset the device by holding Power and Volume+ 5 seconds

FEATURES AND ISSUES
Code:
Boot : Ok
GApps : Ok (OpenGApps Pico recommended)
Partitions (Data, Cache) : Ok
Bluetooth : Ok
WiFi : Ok
WiFi Hotspot : Ok
RIL - Phone - Data : Ok
GPS : Ok
Camera : Ok
Camcorder : Ok
Lights : Ok
MicroSD : Ok
Accelerometer : Ok
Compass : Ok
Gyroscope : Ok
AOSP sensors : Ok
Touchscreen : Ok
FM Radio : Ok
Vibrator : Ok
Microphone : Ok
Audio & music : Ok
Bluetooth audio : Ok
Video playback : Ok
NFC : Ok
Kernel : Ok
Graphics : Ok
3D Rendering : Ok
Clock : Ok
DRM : Ok
Offline Charging : Ok
USB : Ok
USB OTG : Ok
Encryption : Ok
SEPolicies : Ok (Enforced)
Kernel CVE : Partially outdated (ToDo)
Root : Ok (with ADB, supported with Magisk + BootBridge)
TWRP : Ok (TWRP 3.5.0 recommended, system restore may need a ROM reflash due to a TWRP internal issue)
CHANGELOG
Code:
Future release:
- Kernel CVEs updates to check
28/12/2020:
- Update release on Security level 2020-12-05
25/10/2020:
- Update release on Security level 2020-10-05
20/09/2020:
- Upgrade release on Security level 2020-09-05 (android-10.0.0_r46 August)
- Back gesture navigation with keyboard swipe conflicts resolved (topic:ten-back-gesture-go)
30/08/2020:
- Multiple kernel optimizations and debugging features cleanups (thanks Tomoms)
- Previously patched SEPolicies included and now considered stable
27/08/2020:
- Patch regarding SEPolicies for FM Radio support (extends the 26/08/2020 patch)
26/08/2020:
- Patch regarding SEPolicies for FM Radio support and sensors detection
23/08/2020:
- Migration to userspace Low Memory Killer daemon (LMKD) instead of the old kernel LMK
- Massive kernel updates against upstream, especially LZ4 and ZRAM (257 commits)
- Additional SEPolicies updates
20/08/2020:
- Updates to enforced SEPolicies
- Actionbar previous button in DeviceSettings fixed
- High Touch Sensitivity (Glove mode) reimplemented in display settings
19/08/2020:
- Enforced SEPolicies security with all rules refactored and cleaned up,
if anything looks "blocked", please report with ADB logs
16/08/2020:
- GPS legacy support fixed
15/08/2020:
- Video playback fixed
- ZRAM 768MB reenabled
- Bootimage support for Magisk
- RIL updates
- Minor lights selection fix
13/08/2020:
- Initial public release on Android 10.0.0_r41 June
11/08/2020:
- Initial beta testers release on Android 10.0.0_r41 June
2019 - 2020:
- Initial AOSP 10 / LineageOS 17.0 / 17.1 ports
- Internal bringup

The next release will resolve these :
Video playback : Due to Android 10 newer codecs, recorded videos now play properly
Boot : The bootimage will support Magisk as the current one does not
Notifications : Minor fix on lights selection (https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/283994)

Great work as usual @AdrianDC . Got featured on XDA portal. Even though I've not had this device for a couple of years now, I'm still subscribed to this device forum just because of the work you put into it when I had it. :good:

Totally wasn't expecting this to happen !
Definitely need to check it out.
I'm still using my XSP as a daily phone

Woow this great!!

OMG ...
Thank you AdrianDC for keeping this device alive in 2020
This phone is still my daily driver

I remember asking you if you'd ever stop, to which you replied "never".
Long live the king.

A new release 19/08/2020 is available :
Enforced SEPolicies security with all rules refactored and cleaned up (if anything looks "blocked", please report with ADB logs)
Huashan should be fine, everything looks to be working fine right now with the enforced security.
Please PM me ADB logs if you see anything not working / behaving as it should and explain what you did.

Hi AdrianDC,
first of all a BIG THANK YOU for putting so much effort in bringing LOS 17.1 to our good old huashan. I'm still running several devices and really appreciate to have LOS 17.1 on them. now..
Overall, it looks / runs really really good - so: :good: THUMBS UP :good:
One little thing I noticed: The upper left "back arrow" of the "Lights effects" settings menu does not work (which did on LOS 16.0) ... only standard android back button functionality does. I'll try to grab some logs, but maybe you can reproduce it yourself..
But again: Thank you for all the work you put into LOS 17.1 for huashan
NyQuilXT

NyQuilXT said:
One little thing I noticed: The upper left "back arrow" of the "Lights effects" settings menu does not work (which did on LOS 16.0) ... only standard android back button functionality does. I'll try to grab some logs, but maybe you can reproduce it yourself..
Click to expand...
Click to collapse
You're correct, it broke due to the refactoring of our DeviceSettings against Android 10 changes.
The back feature was not handled by the new activity.
Please try this patch on top of the latest release and let me know if it's fine for you too.

AdrianDC said:
You're correct, it broke due to the refactoring of our DeviceSettings against Android 10 changes.
The back feature was not handled by the new activity.
Please try this patch on top of the latest release and let me know if it's fine for you too.
Click to expand...
Click to collapse
Yep, it's working now! Thanks a lot!

NyQuilXT said:
Yep, it's working now! Thanks a lot!
Click to expand...
Click to collapse
Good news.
This also made me notice Huashan was missing it's LineageOS High Touch Sensitivity option in displays,
(my DeviceSettings specific Glove setting activity was meant only for AOSP support, the service is common though),
this is now reimplemented for LineageOS and will be there in the next release.

A new release 23/08/2020 is available, on my side, the performance and normal usage have improved a lot :
Migration to userspace Low Memory Killer daemon (LMKD) instead of the old kernel LMK
Massive kernel updates against upstream, especially LZ4 and ZRAM (257 commits)
Additional SEPolicies updates

After some testing, i must say: this release really kicks ass! I'm really amazed, how fast my devices now performs...Even the one, which suffers the "write amplification effect", is running much better now. Adrian, you are sooo awesome! I'm deeply impressed by the effort, you put into the development for this device! I cannot say that often enough!!!

Wow, I did not expect to find a 17.1 build for a device that old.
Good job!
As I'm using my Xperia SP basically 99% just as a backup for my 2FAs and stock-ROM does not support Google Authenticator 5.10 which introduced the "Transfer codes"-function, I'm very much looking forward to update.
But as I run into troubles with the camera-support of 17.1 on my Samsung Galaxy Tab 4 (bad resolution, couldn't read the big QR-Code) I want to shoot up a question before doing so:
Is the camera-support good enough to read complex/big QR-Codes?
Thanks in advance for any report on one's experiences!
Aequita

After running the 20.08 and 23.08 builds for a bit i must say that they feel realy nice in daily usage
I've stumbled on a few minor things comparing to lineageOS 15,1 from which i updated:
- FM radio doesn't work, it displays a toast saying "currently unavailable" (log fragment from pressing play button below)
Code:
08-25 18:25:40.922 4384 4409 I android_hardware_fm: TurnOn, [freq=100]
08-25 18:25:40.922 4384 4409 I android_hardware_fm: Pwr_Up,[freq=100000]
08-25 18:25:40.922 4384 4409 D android_hardware_fm: BT soc is ''
08-25 18:25:40.922 4384 4409 D android_hardware_fm: open_dev, [fd=59]
08-25 18:25:40.922 4384 4409 D android_hardware_fm: Pwr_Up: cur_fm_state = 0
08-25 18:25:40.922 4384 4409 I android_hardware_fm: start_fm_patch_dl: start_fm_patch_dl = 59
08-25 18:25:40.922 4384 4409 D android_hardware_fm: start_fm_patch_dl: executed cmd
08-25 18:25:40.925 4384 4409 D android_hardware_fm: set versionStr done
08-25 18:25:40.927 4384 4409 D android_hardware_fm: set FM_MODE_PROP done
08-25 18:25:40.933 4384 4409 D android_hardware_fm: set FM_INIT_PROP done
08-25 18:25:41.042 4465 4465 I qcom-fm : /system/etc/init.qcom.fm.sh: In FM shell Script
08-25 18:25:41.092 4466 4466 I qcom-fm : /system/etc/init.qcom.fm.sh: mode: normal
08-25 18:25:41.120 4467 4467 I qcom-fm : /system/etc/init.qcom.fm.sh: Version : 199217
08-25 18:25:41.168 4468 4468 I qcom-fm : /system/etc/init.qcom.fm.sh: inserting the radio transport module
08-25 18:25:41.194 4469 4469 E libc : Access denied finding property "ro.qualcomm.bt.hci_transport"
08-25 18:25:41.175 4469 4469 W fm_qsoc_patches: type=1400 audit(0.0:18): avc: denied { read } for name="u:object_r:bluetooth_prop:s0" dev="tmpfs" ino=6774 scontext=u:r:fm_dl:s0 tcontext=u:object_r:bluetooth_prop:s0 tclass=file permissive=0
08-25 18:25:41.223 4470 4470 E qcom-fm : /system/etc/init.qcom.fm.sh: FM QSoC firmware download and/or calibration failed: exit code 255
08-25 18:25:49.071 884 884 D ServiceStateProvider: subId=1
08-25 18:25:49.078 506 791 D AlarmManagerService: Kernel timezone updated to -120 minutes west of GMT
08-25 18:25:49.082 2248 2248 D CellBroadcastReceiver: onReceive Intent { act=android.intent.action.SERVICE_STATE flg=0x1000010 cmp=com.android.cellbroadcastreceiver/.CellBroadcastReceiver (has extras) }
08-25 18:25:49.990 4384 4409 E android_hardware_fm: FM patch downloader failed: -1
08-25 18:25:49.990 4384 4409 D android_hardware_fm: close_dev, [fd=-1] [ret=0]
08-25 18:25:49.990 4384 4409 D android_hardware_fm: TurnOn, [ret=-1]
08-25 18:25:49.993 4384 4384 D FmMainActivity: mHandler.handleMessage, what = 9,hashcode:150427765
08-25 18:25:49.993 4384 4384 D FmMainActivity: refreshStationUI, set station value null when it is first time
08-25 18:25:50.088 4384 4404 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
08-25 18:25:52.032 506 791 W NotificationService: Toast already killed. pkg=com.android.fmradio [email protected]
- it seems that the screen on/off animation is missing. There was a post in earlier lineageOS thread with details how to enable it, but i cant fing it
A major thing may be connected to phone deep sleep - i've had a situation after enabling the alarm, that it would ring only after lighting the screen up with power button. I will investigate this further as it does not happen every time.
Thanks again for the updates !

Aequita said:
Wow, I did not expect to find a 17.1 build for a device that old.
Good job!
As I'm using my Xperia SP basically 99% just as a backup for my 2FAs and stock-ROM does not support Google Authenticator 5.10 which introduced the "Transfer codes"-function, I'm very much looking forward to update.
But as I run into troubles with the camera-support of 17.1 on my Samsung Galaxy Tab 4 (bad resolution, couldn't read the big QR-Code) I want to shoot up a question before doing so:
Is the camera-support good enough to read complex/big QR-Codes?
Thanks in advance for any report on one's experiences!
Aequita
Click to expand...
Click to collapse
I can scan simple or comple QR-Code properly here, can't tell much more though.
Jadimo said:
After running the 20.08 and 23.08 builds for a bit i must say that they feel realy nice in daily usage
I've stumbled on a few minor things comparing to lineageOS 15,1 from which i updated:
- FM radio doesn't work, it displays a toast saying "currently unavailable" (log fragment from pressing play button below)
- it seems that the screen on/off animation is missing. There was a post in earlier lineageOS thread with details how to enable it, but i cant fing it
A major thing may be connected to phone deep sleep - i've had a situation after enabling the alarm, that it would ring only after lighting the screen up with power button. I will investigate this further as it does not happen every time.
Thanks again for the updates !
Click to expand...
Click to collapse
Thanks for the report, FM Radio is now resolved with an incremental patch release for the 23/08/2020 release.
Patch regarding SEPolicies for FM Radio support and sensors detection
Regarding the screen on / off animations, this is due to the Android Go (Low RAM) configurations,
if you want to restore the related features with a bit of performance losses, look at my "Low-RAM Property Patcher" linked in the OP.

AdrianDC said:
I can scan simple or comple QR-Code properly here, can't tell much more though.
Thanks for the report, FM Radio is now resolved with an incremental patch release for the 23/08/2020 release.
Patch regarding SEPolicies for FM Radio support and sensors detection
Regarding the screen on / off animations, this is due to the Android Go (Low RAM) configurations,
if you want to restore the related features with a bit of performance losses, look at my "Low-RAM Property Patcher" linked in the OP.
Click to expand...
Click to collapse
Well, today I am surprised with this version that I never imagined that it would come out, I am using the 16 I will try to see how it goes with this on my old xperia sp

[ROM][OFFICIAL][enchilada][11] LineageOS 18.1

It's cool

wondering anyone tried this?

[email protected] said:
wondering anyone tried this?
Click to expand...
Click to collapse
Just booted with NikGapps and canary Magisk - GPS seems to work neither here nor on POSP, which I migrated from. Otherwise seems okay!
Edit: the fingerprint auth doesn't work too and the camera crashes upon detecting a face - prolly should've done a factory reset when migrating lmao. Will report in a while how that went
Edit 2: after a factory reset I managed to get GPS working, however fingerprint auth and face detection still fail

dikivan2000 said:
Just booted with NikGapps and canary Magisk - GPS seems to work neither here nor on POSP, which I migrated from. Otherwise seems okay!
Edit: the fingerprint auth doesn't work too and the camera crashes upon detecting a face - prolly should've done a factory reset when migrating lmao. Will report in a while how that went
Edit 2: after a factory reset I managed to get GPS working, however fingerprint auth and face detection still fail
Click to expand...
Click to collapse
Just curious, did you flash with TWRP or use the Lineage recovery? If TWRP works it will make installing Magisk much simpler.

dikivan2000 said:
Just booted with NikGapps and canary Magisk - GPS seems to work neither here nor on POSP, which I migrated from. Otherwise seems okay!
Edit: the fingerprint auth doesn't work too and the camera crashes upon detecting a face - prolly should've done a factory reset when migrating lmao. Will report in a while how that went
Edit 2: after a factory reset I managed to get GPS working, however fingerprint auth and face detection still fail
Click to expand...
Click to collapse
Also, How's the experience with POSP. I'm currently on Pixen Android 11 which is good with issues majorly in Camera during Face Detection.. Battery Life ais great and ROM is very snappy. Liking it.

Clean flash, latest OOS, TWRP, LOS 18 in both slots, and Nikgapps and Magisk Modded. It boots, but NFC it´s no working. All the rest in my initial setup works ok. I didn´t try camera at moment.
With Magisk Canary it doesn´t boot, goes to fastboot mode.
At first it doesn´t pass Safetynet test. With Magisk Props module it´s ok. (Correction: Magisk props works with Manager Canary app over Magisk Modded, but root it´s lost)
Thanks dev for your work!

Dirty flashed, latest OOS, current TWRP, flashed Lineage 18 both slots. No magisk or other mods. Mobile data not working and when I try to open the network from settings it crashes back to the home screen. Wiping cache doesn't help.
Oh well, guess it's time to wipe and start with a fresh install I was hoping ...

Nut_House said:
Just curious, did you flash with TWRP or use the Lineage recovery? If TWRP works it will make installing Magisk much simpler.
Click to expand...
Click to collapse
Afaik LOS recovery does not allow flashing; I used TWRP

dikivan2000 said:
Afaik LOS recovery does not allow flashing; I used TWRP
Click to expand...
Click to collapse
Thanks. Makes sense, I never used LOS recovery, always just booted to TWRP when I needed to update or flash something.
Got impatient, went ahead and made the leap earlier and tried a dirty flash. It didn't go well. Just finished doing a wipe and clean install and so far so good. Will start reinstalling apps and see how things play out.

@LuK1337 Thanks for bringing LineageOS 18 for OP6.
I have found a few bugs,please have a look at them
1) Front camera FC when face is brought closer to the camera.
2) unable to make call when Volte is enabled.
3) NFC does not work(quick toggle is greyed out).
Update: 2nd build fixed camera and volte

Hi @LuK1337,
thanks a lot for taking care of our devices,
to install, which base must be on ? Latest OOS, or beta preview for P ?
And about gapps, do we have to use gapps for 11 or can we use opengapps 10 ? (did not see beta 11 for opengapps)

Cygnust said:
Hi @LuK1337,
thanks a lot for taking care of our devices,
to install, which base must be on ? Latest OOS, or beta preview for P ?
And about gapps, do we have to use gapps for 11 or can we use opengapps 10 ? (did not see beta 11 for opengapps)
Click to expand...
Click to collapse
>to install, which base must be on ? Latest OOS, or beta preview for P ?
No idea what firmware I'm even on but i'm definitely not on Android 9 one...
>And about gapps, do we have to use gapps for 11 or can we use opengapps 10 ? (did not see beta 11 for opengapps)
It depends whether you actually want your phone to work or not.

Thanks to Luk for delivering high quality ROMs - the second build indeed fixes the camera. However, does not boot with Magisk (21000) anymore

qualo said:
Clean flash, latest OOS, TWRP, LOS 18 in both slots, and Nikgapps and Magisk Modded. It boots, but NFC it´s no working. All the rest in my initial setup works ok. I didn´t try camera at moment.
With Magisk Canary it doesn´t boot, goes to fastboot mode.
At first it doesn´t pass Safetynet test. With Magisk Props module it´s ok. (Correction: Magisk props works with Manager Canary app over Magisk Modded, but root it´s lost)
Thanks dev for your work!
Click to expand...
Click to collapse
Hi,
which magisk version are you using ? mine goes on fastboot too

Cygnust said:
Hi,
which magisk version are you using ? mine goes on fastboot too
Click to expand...
Click to collapse
The one shared in post #42 in POSP 11 beta ROM.
(Sorry, I didn't find how to share the direct link to post)
With this Magisk_debug2.zip it boots and you can pass safetynet with MagiskProps without updating manager

I'm running the 10/09 build of LOS with magisk v21.0 (21000) and it boots with no issues. In fact, after a few days of usage I'm impressed with just how well everything works for such an early release. Twice it appeared to unlock with my pattern and then dumped me back to the login screen and the connection to my Garmin watch has dropped a couple of times, which never happened with LOS 17.1. Otherwise, it's been smooth sailing.
LuK1337, well done :good:

installed fine with magisk canary and manually patched boot.img from payload to flash in twrp.
just high cpu usage with zygote 64 and system_server other than that nice job LuK1337

Stoowyguy said:
installed fine with magisk canary and manually patched boot.img from payload to flash in twrp.
just high cpu usage with zygote 64 and system_server other than that nice job LuK1337
Click to expand...
Click to collapse
I noticed the CPU usage bug too. Hopefully Luk1337 can sort it out.
Sent from my ONEPLUS A6003 using Tapatalk

Just want to say thank you for LuK1377, the ROM is REALLY GREAT ! The smoothness and new features of Android 11 makes me wanna stick to it, even though it's still in early development.
I'm running the latest build from today and just want to give my feedback about one point: even though the screen is set to time out in 30 seconds (in my case), it turns off and a second later, it turns on again without anyone touching the phone.
If I block my phone using the power button, it works correctly. If I wait the 30 seconds, it stays awake (phone not charging, stay awake option on dev options is off).
The battery life was also not great (when I was using the build from october 11th, still testing this one) but it's expected and I'm not concerned about it.
Thank you again LuK1337!

Database Develop

welcome