Database Info

[ROM][9][Pie][Flo][UNOFFICIAL] Pixel Experience Plus (2/13/2020)

{
"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"
}
PixelExperience Plus for ASUS Nexus 7 2013 [Flo/Deb]
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential features for the proper functioning of the device
Based on Android 9.0 PIE
DON'T FLASH GAPPS, ALREADY INCLUDED IN ROM!​
Installation:
1. Download the ROM and Magisk from the links below.
2. Wipe everything except internal storage.
3. Reboot recovery you will have no OS installed but that's ok i promise your device will boot back into recovery.
4. Flash the ROM and DO NOT flash GApps as it is already included!
5. Flash Latest Magisk to get root access.
6. Reboot and Enjoy!
Known issues:
- You will be required to repartition your device to at least 1.3gb. If you have anything higher or exact than 1.3gb than your fine.
- Navigation bar glitches sometimes.
- Deep Sleep does not work when NFC is enabled so i recommend you disable it when your not using it to get your tablet to go in deep sleep.
- When you boot up the ROM for the first time you may notice that the boot animation will freeze and then your device reboots back to the google logo. This is not a device side issue but a ROM side issue but let the tablet reboot a couple times if necessary & your tablet will eventually boot to the setup wizard and into the ROM. This is normal.
- Use Latest Official TWRP recovery below for Flo which is version 3.3.1.0 and you won't have the install supersu thing when you reboot recovery.
- You tell us!
Downloads:
Latest 2/13 build for Flo is here: https://www.androidfilehost.com/?fid=4349826312261722127
Download folder for Flo is here: https://www.androidfilehost.com/?w=files&flid=293644
Magisk: https://github.com/topjohnwu/Magisk/releases
TWRP: https://dl.twrp.me/flo/twrp-3.3.1-0-flo.img.html
Sources:
Flo Device Tree: https://github.com/followmsi/android_device_asus_flo/tree/pixel-pie
Deb Device Tree: https://github.com/followmsi/android_device_asus_deb/tree/pixel-pie
Kernel: https://github.com/followmsi/android_kernel_google_msm/tree/followmsi-pie
Vendor: https://github.com/followmsi/android_vendor/tree/flo-deb-lineage-16.0

Thanks dude, I have a LTE version, will you help to release Q for DEB as well? Thanks.

Reserved for future use

one more just in case

Thanks very much for making time to maintain this.
May I ask which blobs are used for this build? If Im reading it correctly, it's the same ones that @followmsi has switched to rather than the previous QC ones?
I'll definitely install this and give feedback but am of the current belief that the previous blobs provided much better performance,(on deb at least), than the ones used in the other most recent build.
Hadn't mentioned it yet as was still trying to pinpoint why it feels less responsive. Not sure if it's GPU or disk IO or even CPU because the numbers all look fine but the device feels noticeably less responsive when playing something taxing like PoGo.
Edit: just saw the blobs link.

sir_bazz said:
Thanks very much for making time to maintain this.
May I ask which blobs are used for this build? If Im reading it correctly, it's the same ones that @followmsi has switched to rather than the previous QC ones?
I'll definitely install this and give feedback but am of the current belief that the previous blobs provided much better performance,(on deb at least), than the ones used in the other most recent build.
Hadn't mentioned it yet as was still trying to pinpoint why it feels less responsive. Not sure if it's GPU or disk IO or even CPU because the numbers all look fine but the device feels noticeably less responsive when playing something taxing like PoGo.
Edit: just saw the blobs link.
Click to expand...
Click to collapse
I am using followmsi's latest pixel and pie aosp sources which includes fixes for hardware decoding and compass. I don't have any slow downs when i tested the build however i wouldn't know how to even fix it if there were slow downs because i am just building using his sources. There is nothing changed or added besides those sources. You can expect a new build from me every month with new security patches because i am currently the one mantaining pixel experience
Cheers and have a good day

Is Netflix working on this rom?

guillaumeserton said:
Is Netflix working on this rom?
Click to expand...
Click to collapse
yes but you have to install the older version of netflix look at other peoples posts on different rom threads because i don't care about netflix and you will find the fix there in those threads and posts

Issues
Latest build (05/02) borked all the sensors (gyroscope, compass, accelerometer). After dirty flashing it over an earlier build they all stopped working.
Had to go back to stock 6.0.1 and it's all ok now. 6.0.1 feels like a rocket by the way. I don't know about your experience with these pie roms, but for me it's been high battery drain (especially when watching youtube) and overall intermittent choppiness.

prodOne said:
Latest build (05/02) borked all the sensors (gyroscope, compass, accelerometer). After dirty flashing it over an earlier build they all stopped working.
Had to go back to stock 6.0.1 and it's all ok now. 6.0.1 feels like a rocket by the way. I don't know about your experience with these pie roms, but for me it's been high battery drain (especially when watching youtube) and overall intermittent choppiness.
Click to expand...
Click to collapse
The only thing that shouldn't be working is compass and I will hopefully fix it in the next build but gyroscope and accelerometer is working for me on my flo with no problems however I can't say this for deb as I don't have that device to test. But I would do a clean flash wipe everything except internal storage and try flashing the ROM again. Also remember to not flash gapps as its already included

prodOne said:
Latest build (05/02) borked all the sensors (gyroscope, compass, accelerometer). After dirty flashing it over an earlier build they all stopped working.
Had to go back to stock 6.0.1 and it's all ok now. 6.0.1 feels like a rocket by the way. I don't know about your experience with these pie roms, but for me it's been high battery drain (especially when watching youtube) and overall intermittent choppiness.
Click to expand...
Click to collapse
Actually I saw the same thing when dirty flashing to the changed blobs build from the other thread.
An additional restart was required to get them working.
Haven't had a chance to try this build, (deb), yet but it's likely the same.

sir_bazz said:
Actually I saw the same thing when dirty flashing to the changed blobs build from the other thread.
An additional restart was required to get them working.
Haven't had a chance to try this build, (deb), yet but it's likely the same.
Click to expand...
Click to collapse
You can fix deep sleep by flashing this zip I provided and I tested it and now my tablet goes into deep sleep. This zip add-on works for all pie ROMs except unlegacy because its already included. Huge thanks to @followmsi for providing the fix
Download here and flash in recovery:
https://www.androidfilehost.com/?fid=1395089523397959956

Tested deb for a few days, ( with the patch linked above), and it's pretty good.
Dirty flashed, wiped cache and dalvik, installed ElementalX kernel and then the deep sleep patch.
My early concerns regarding the changed blobs and performance were unfounded. Everything appears to work and the rom runs smoothly.
Did experience an issue with sensors no longer responding after a couple of days and although easily resolved with a reboot, I rolled back to an earlier PE build to avoid a repeat.
Looking forward to trying any further builds though. Hopefully will have time to troubleshoot, or at least a grab a useful log next time.

JT1510365 said:
You can fix deep sleep by flashing this zip I provided and I tested it and now my tablet goes into deep sleep. This zip add-on works for all pie ROMs except unlegacy because its already included. Huge thanks to @followmsi for providing the fix
Download here and flash in recovery:
https://www.androidfilehost.com/?fid=1395089523397959956
Click to expand...
Click to collapse
Hi mate I cant seem to install this I keep getting error code 7 I have updated the twrp in recovery any ideas

pcmender2005 said:
Hi mate I cant seem to install this I keep getting error code 7 I have updated the twrp in recovery any ideas
Click to expand...
Click to collapse
i have no idea it flashes and works fine for me

JT1510365 said:
i have no idea it flashes and works fine for me
Click to expand...
Click to collapse
Ok no probs will have a look at the update script.

I've given this rom a try, and I am also receiving an error 7 from twrp-3.3.0-0-flo
Code:
BLKDISCARD ioctl failed: Invalid argument
failed to execute command [erase 4,756,4689,298235,326400]
new data receiver is still available after executing all commands.
script aborted: E1001: Failed to update system image.
E1001: Failed to update system image.error: 1001
Updater process ended with ERROR: 7
This device must be re-partitioned before installing this rom
Otherwise works just like it was stated on the original post.

sir_bazz said:
Tested deb for a few days, ( with the patch linked above), and it's pretty good.
installed ElementalX kernel and then the deep sleep patch.
e.
Click to expand...
Click to collapse
which Kernel did you use ? tried both 6 and 7 EX - soft brick

Custom setting
@JT Your Havoc ROM has custom status bar settings, etc., but it seems that this ROM doesn't. Why?

jhford said:
@JT Your Havoc ROM has custom status bar settings, etc., but it seems that this ROM doesn't. Why?
Click to expand...
Click to collapse
Because havoc is more customizable and feature filled compared to pixel experience. Pixel experience is meant to give you the same experience as if you were to use and buy the google pixel phones its the same ROM basically as what the pixel has. There's nothing I can do about this pixel experience is meant to be more of a stock bare minimal experience rom compared to havoc which is more feature filled and customizable.
Cheers

karmacoma7 said:
which Kernel did you use ? tried both 6 and 7 EX - soft brick
Click to expand...
Click to collapse
Apologies man.
Sometimes I completely forget that not everyone here is up to date with development for our devices.
I should've made clear that kernel build is by @followmsi and found in his online file repository.
https://drive.google.com/drive/mobi...k92ZUdnTTg?usp=drive_open&sort=13&direction=a

[ROM][discovery][Pie][9.0] AOSP [Sony Open Devices Project]

{
"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"
}
To God be the glory, a working AOSP ROM for those on both the 50.1 and the 50.2 firmware, Pie flavored! There may still be a few bugs here and there, please read this entire post before using!
**** This is an UNOFFICIAL ROM. Install at your own risk! ****
WARNING: This build SHOULD work on both the H3213 and H3223, but I could only test on a H3223.
Disclaimer: I am not responsible for any damages to your device.
A huge thanks to the Android Open Source Project and Sony Open Devices Project!​
The Sony Open Devices Project (SODP) is an initiative to build Android for phones while being as vendor binary large object (blob) free as possible. There are still a few vendor blobs used in this project, but the goal is to one day be vendor blob free. I don't know if that will ever fully happen, but it is nice to move in that direction. That said, all of my work is completely available for any who wish to use or modify it. I didn't make AOSP, the device trees, or vendor blobs. I simply used and edited existing material. A huge thanks should go to those who actually created this stuff.
This Unofficial AOSP ROM was built for the H3223 (discovery), but may work on some of the other variants, please try at your own risk. However, if you do try it on another variant, please be sure to let me know in the comments how well it worked.
Downloads:
Rom Download link:
Note: This is designed to work with any firmware version of the XA2 Ultra, because you flash a custom OEM partition. I've tested this on 50.1 and 50.2 firmware phones.
http://www.mediafire.com/folder/dl8dcra6ojog5/Sony Open Device Project
IF there is an ENG build, it is marked "ENG" for testing purposes only. It's your phone, you can install anything you want, but I do not recommend installing the ENG build. Use the "USER" or "USERDEBUG" builds.
There are two versions of the project, a vanilla AOSP without Google Apps, and a vanilla AOSP with Google Apps. I have tested both on my phone. If you want Google Apps, you cannot use the gappless version and then flash gapps, it doesn't work, you must use the gapps version if you want Google's apps.
Installation instructions: (DIFFERENT THAN NORMAL! DONE THROUGH FASTBOOT!)
- Download the zip file for AOSP 9.
- Unzip the zip file, and you will find 5 images.
- If using Windows, put these in your folder you use for fastboot, if using Linux, you can do this from any folder.
- Reboot the phone into bootloader/fastboot mode.
- Flash them to your phone, like so (example for Linux)
Code:
$ fastboot flash boot ./boot.img
$ fastboot flash oem ./oem.img
$ fastboot flash system ./system.img
$ fastboot flash userdata ./userdata.img
$ fastboot flash vendor ./vendor.img
$ fastboot reboot
Your phone will now boot into AOSP Pie!
If you plan to install magisk, then let the rom boot once, then go back to TWRP and flash magisk. I recommend making a backup of at least the boot partition first. Magisk is optional, of course. And you do so at your own risk!
What works:
Code:
So far these things that I have tried work, such as
- Display/touch
- Camera (front and back) for pictures and video!
- Phone calls
- Data 3g/LTE
- Bluetooth
- WiFi
- Sound in system, in calls, over bluetooth devices
- MicroSD card (external SD card).
- GPS
- Fingerprint sensor
- Camera Button launches camera and takes photos
- MTP file transfer
etc....
What doesn't:
Code:
Gappless version:
- FM Radio does not work
- The built in Gallery app cannot play back recorded videos from camera. VLC or other apps work fine though.
- Nothing else that I know of, but let me know if you find something!
Gapps version:
- FM Radio does not work
- The built in Gallery cannot play back recorded videos from camera. VLC or other apps work fine though.
--But the Google Photos app can.
-The built in Google Camera app does not work, however, Open Camera, or other camera apps do.
- Nothing else that I know of, but let me know if you find something!
Source Code: https://source.android.com/
Device, kernel, and vendor trees: https://github.com/sonyxperiadev
My GitLab: https://gitlab.com/alaskalinuxuser/
ROM OS Version: 9.0 Pie
ROM Kernel: Linux 4.9.194
Based On: Android Open Source Project
Created 2019-10-03
Last Updated 2019-10-24

Changelog:
20191024
- Fixed MTP crash issue.
20191023
- Sync'd source and fresh rebuild
- Now have a "Gapps included" variant and a "Gappless" variant.
20191004
- Rebuilt kernel
- Fixed camera turning green or crashing
- Fixed general stability.
20191003
- First build, a bit unstable.
- Camera turns green.
- PTP, MTP cause crashes.
- FM Radio does not work.
Notes:
This ROM is very, very, vanilla. It is straight up AOSP. No frills, no mods, no extras. Just pure source.
I personally don't use Gapps anymore, but I did test that the gapps version boots up and connects. That's about all I test with Gapps, though.
I also don't use social media except XDA, so I don't know how well every app works. But if you have issues and have logs, perhaps I can look at them and see what is wrong.
Can I flash back to firmware 50.x.xxxx after flashing this?
Yes, you can. I flashed this and then flashed back to the 50.2 firmware several times while testing. As always, you assume full responsibility for your device, but it worked for me.
Issues/workarounds:
- Video playback from camera. Any camera videos you record work fine, but the built in player can't play them. I downloaded and used VLC app to play them and they work just fine. You can get VLC or other apps from the play store, or here: https://www.f-droid.org/en/packages/org.videolan.vlc/, or if you are using the Gapps included version, you can use Google Photo.
- If you are using the Gapps included variant, the built in Google Camera app does not work. However, using the playstore, I downloaded a number of camera apps, such as Open Camera, and they all worked. I'll try to look into it if I get time.

The only thing i didnt like about aosp is that you cant add features like gravitybox does. And Unfortunatly I need snapchat cause my woman uses it. lol Breaks the safety Net

Couldn't flash gapps? I'll boot into twrp and flash gapps after booting into aosp and nothing? What am I doing wrong... The is will boot and no gapps appear?

Yodasgodfather said:
Couldn't flash gapps? I'll boot into twrp and flash gapps after booting into aosp and nothing? What am I doing wrong... The is will boot and no gapps appear?
Click to expand...
Click to collapse
Good question, I'm not sure, I don't use gapps, but I could try flashing it to see tomorrow. Which gapps did you flash? Opengapps, 64 bit arm, for pie?

alaskalinuxuser said:
good question, i'm not sure, i don't use gapps, but i could try flashing it to see tomorrow. Which gapps did you flash? Opengapps, 64 bit arm, for pie?
Click to expand...
Click to collapse
64 bit nano for pie

Yodasgodfather said:
64 bit nano for pie
Click to expand...
Click to collapse
I installed AOSP, let it boot, downloaded 64 bit nano opengapps, fastbooted into TWRP, flashed the gapps via adb sideload, and rebooted. It didn't crash or hang up on me. However, I've noticed that it doesn't install the playstore app. I'm very confused. I tried this several times with pico, nano, micro, and mindthegapps.

AlaskaLinuxUser said:
I installed AOSP, let it boot, downloaded 64 bit nano opengapps, fastbooted into TWRP, flashed the gapps via adb sideload, and rebooted. It didn't crash or hang up on me. However, I've noticed that it doesn't install the playstore app. I'm very confused. I tried this several times with pico, nano, micro, and mindthegapps.
Click to expand...
Click to collapse
Thank you for looking into it? but yeah same I'm very confused as well but I believe I have found something that I'm not at all familiar with. I found this link that has someone that has a similar issue with the responder saying they can use "adb pull" command to flash Google factory images so it might be worth looking into?
https://stackoverflow.com/questions/41695566/install-google-apps-on-aosp-build

Whoo-hoo! Praise God! Good traction on Android 10! After some tinkering with XOSD source, I've got a booting version of Android 10 with the new 4.14 kernel! Certainly not a daily driver by any means yet, but I'll keep tinkering. I'll add a few teaser shots as well. :victory:

AlaskaLinuxUser said:
Whoo-hoo! Praise God! Good traction on Android 10! After some tinkering with XOSD source, I've got a booting version of Android 10 with the new 4.14 kernel! Certainly not a daily driver by any means yet, but I'll keep tinkering. I'll add a few teaser shots as well. :victory:
Click to expand...
Click to collapse
Awesome look at you go! ?

AlaskaLinuxUser said:
Whoo-hoo! Praise God! Good traction on Android 10! After some tinkering with XOSD source, I've got a booting version of Android 10 with the new 4.14 kernel! Certainly not a daily driver by any means yet, but I'll keep tinkering. I'll add a few teaser shots as well. :victory:
Click to expand...
Click to collapse
Hell yeah man. Thank God we still got one developer on the xa2 ultra threads.

So I've messed with aosp a bit and have found a way to help make things easier. I've installed nanodroid which will give you micro g and it's service and more!
https://nanolx.org/nanolx/nanodroid
I haven't been able to figure it out but it has a setup wizard as well which does give you the option to install the official play store. If any one else can't get that to work then perhaps install osm(gapps) with fdroid and install the "fakegapps" xposed module to get signiture spoofing. Hope this helps?

Yodasgodfather said:
So I've messed with aosp a bit and have found a way to help make things easier. I've installed nanodroid which will give you micro g and it's service and more!
https://nanolx.org/nanolx/nanodroid
I haven't been able to figure it out but it has a setup wizard as well which does give you the option to install the official play store. If any one else can't get that to work then perhaps install osm(gapps) with fdroid and install the "fakegapps" xposed module to get signiture spoofing. Hope this helps?
Click to expand...
Click to collapse
Great work, and good find!
I am currently building this ROM again with built in gapps ... Hopefully, I can have that and an updated version of aosp that is gappless available tomorrow or the next day (so I can test it a bit). I spoke with a few guys on the SODP telegram channel, and they make aosp with gapps built in, so I thought I'd try that to see if that helps you guys who want to use this ROM with gapps.

Good news!
I was able to build AOSP 9 with Gapps built in, and will be posing that once I get it uploaded. (It will take a long time, because I have slow internet.) I'm testing it out on my phone now, everything seems to work here. I will also be posting an update of the gappless version as well.

Thank you so much! I have been waiting for this but when do you think it will be available?

Yodasgodfather said:
Thank you so much! I have been waiting for this but when do you think it will be available?
Click to expand...
Click to collapse
Good news! It is up and posted. Be sure to fully read Post #1, and Post #2 before proceeding.
I tested both the gapps included, and the non-gapps versions on my phone, both worked. With the Gapps version I was able to connect and download several apps, my emails synced, as did photos, etc....
For this rom, the things that I am actively working on are MTP/PTP computer connections.
Also, Android 10 is still in the works, it's just giving me a few fits at the moment, but I will keep working on it. I don't want to release a "half baked" rom, I would like it to be 95%+ functional before putting it up for you to use. Hopefully, that will not take forever. :fingers-crossed:

Love it I did notice the ctsintegrity was false but I fixed it with a magisk module other than that it's great!? I understand from your last post you are working on Android 10 but any idea on when your roms will be updated to 5.0.2 version?

Great news! Praise God! With some great guidance from @MartinX3, and a post by @oshmoun, I was able to apply a patch to the kernel that fixed MTP communications for transferring files to your PC! I have the builds now, and will upload them. My internet is really slow, so it will take a while....

Great news! Praise God! With some great guidance from @MartinX3, and a post by @oshmoun, I was able to apply a patch to the kernel that fixed MTP communications for transferring files to your PC! I have the builds now, and will upload them. My internet is really slow, so it will take a while....

AlaskaLinuxUser said:
Great news! Praise God! With some great guidance from @MartinX3, and a post by @oshmoun, I was able to apply a patch to the kernel that fixed MTP communications for transferring files to your PC! I have the builds now, and will upload them. My internet is really slow, so it will take a while....
Click to expand...
Click to collapse
The new builds have been uploaded, the 20191024 builds have working MTP for file transfers, and the OP has been updated! Enjoy!

[ROM][H830|H850|RS988] UNOFFICIAL LineageOS 18.1 for LG G5

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer
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.
Introduction
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. More info.
Install
Update recovery to the latest TWRP or Lineage Recovery build
Format data if coming from an UNOFFICIAL or non-Lineage build.
Flash the ROM
Flash any addons
Reboot
Bugs
If you encounter issues/bugs that are not known, please report. If I can replicate your issue then I can track it down.
If I cannot, please provide as much detail as possible. Logcats are a must.
Please indicate what g5 variant you have (h830, h850, rs988), the dated version, and any third party mods.
I am aware people run mods or change things. If needed I may ask you to data wipe or remove a mod that might be interfering.
Please avoid bringing up issues with your favourite gapps package. If a bug only exists with gapps, it's not my problem.
Changelog
Code:
[03/03/2021]
March security patch (android-11.0.0_r32)
[20/12/2021]
January security patch (android-11.0.0_r27)
Fixed camera crashes
[04/12/2021]
Updated LineageOS apps and frameworks
[13/12/2020]
LineageOS 18.1 - Android 11 QPR1
[30/11/2020]
Fixed boot after encrypting with a lockscreen set
Updated LineageOS apps and frameworks
[B]16/11/2020[/B]
First release
Downloads
Official builds
Archived unofficial builds: sourceforge
Sources
Gerrit
https://github.com/LineageOS
https://github.com/LineageOS/android_kernel_lge_msm8996
https://github.com/LineageOS/android_device_lge_msm8996-common
https://github.com/LineageOS/android_device_lge_g5-common
h830
h850
rs988

Will los 18.0 be coming to g6

hi will this work on h845 as well? if not, is it okay to flash h850 or h830 on my h845?

lgg5.845lol said:
hi will this work on h845 as well? if not, is it okay to flash h850 or h830 on my h845?
Click to expand...
Click to collapse
No, it won't work, don't try flashing an h830/h850 ROM as flashing a ROM not meant for the variant of your device will most likely land you in an unfixable hard brick. Ask me how I know.

Great to see you with new topics! I will try soon as possible :good:

ROMSG said:
No, it won't work, don't try flashing an h830/h850 ROM as flashing a ROM not meant for the variant of your device will most likely land you in an unfixable hard brick. Ask me how I know.
Click to expand...
Click to collapse
damn...sorry for that... its weird there's no new custom rom for h845, at least. on android 8 or 9 :laugh:

lgg5.845lol said:
damn...sorry for that... its weird there's no new custom rom for h845, at least. on android 8 or 9 :laugh:
Click to expand...
Click to collapse
The h845 is very different from the G5 h850/h830/rs988 instead of the sdm 820 it uses the sdm 652. A much cheaper and slower soc. So you see the sources listed in the op.
Sources
Gerrit
https://github.com/LineageOS
https://github.com/LineageOS/android_kernel_lge_msm8996
https://github.com/LineageOS/android...msm8996-common
https://github.com/LineageOS/android..._lge_g5-common
h830
h850
rs988
Even though @synescu has made a twrp pot almost all of these would have to be heavily modified to work with the g5 se. I tried to build android 7 for the se but the only device tree available is horribly out of date and even android 7 wouldn't build successfully ( @synescu who wrote this tree and made twrp for the g5 se has been inactive for a year). It also doesn't help that the g5 SE is very rare in the united states as it was a Europe exclusive and even using sites that will import from Europe the g5 se is super overpriced (sometimes even more than $300!) on the used market. So unless someone can find a g5 se for cheap a rom for the se won't be happening anytime soon, unfortunately.

When I try to build 18.0, all goes well. Then there is an error when it comes to signing the build. (I'm using the same scripts I use for 17.1, except s/17.1/18.0/g.)
Code:
ERROR: Failed to run signapk.jar: return code 1:
Error: Unable to access jarfile /home/rfrazier/android/lineage/lineage-18.0/build/make/tools/framework/signapk.jar
And here's the command.
Code:
## Signing
echo "Signing the APK."
time ./build/tools/releasetools/sign_target_files_apks -o -d ~/.android-certs \
$OUT/obj/PACKAGING/target_files_intermediates/*-target_files-*.zip \
signed-target_files.zip &>>${LOGFILE}
I suspect that it is operator error, but any suggestions would be welcome.
Best wishes,
Bob
PS signapk.jar exists in the directory in which I think i should be looked for: out/host/linux-x86/framework
So, I suspect that an environmental variable is being incorrectly set. Something to look into when I get some more time.
RLF

Great to see more development for the G5, thanks!
How is the stability of this compared to Lineage 17.1?

H820?
How about H820?

ajasei said:
How about H820?
Click to expand...
Click to collapse
As far as I know the H820 is not bootloader unlockable. There aren't any lineage builds for h820 anyway.

I think that the signing problem is related to a change in /build/tools/releasetools/common.py, and more particularly in changes to the following.
class Options(object):
def __init__(self):
Now if I could only read it (not being a programmer). I guess I'll give it a go later.
Best wishes,
Bob

Yes, something is definitely going on there. I hardwired in the path in /build/tools/releasetools/common.py , and it was built and signed just fine.
Code:
class Options(object):
def __init__(self):
# Set up search path, in order to find framework/ and lib64/. At the time of
# running this function, user-supplied search path (`--path`) hasn't been
# available. So the value set here is the default, which might be overridden
# by commandline flag later.
exec_path = sys.argv[0]
if exec_path.endswith('.py'):
script_name = os.path.basename(exec_path)
# logger hasn't been initialized yet at this point. Use print to output
# warnings.
print(
'Warning: releasetools script should be invoked as hermetic Python '
'executable -- build and run `{}` directly.'.format(script_name[:-3]),
file=sys.stderr)
# self.search_path = os.path.realpath(os.path.join(os.path.dirname(exec_path), '..'))
self.search_path = "out/host/linux-x86"
The last commented out line
self.search_path = os.path.realpath ...."
was replaced with
self.search_path = "out/host/linux-x86"
I haven't figured out the logic of the rest of the stuff, so don't know what's wrong with it.
Best wishes,
Bob
PS I tried a dirty update (on my spare phone), but it didn't work. I had to format data. It might have been because I had Magisk installed and that messed up the recovery partition, but I'm not sure. In any case, after formatting data it came up just fine. I haven't checked much yet, but WIFI works.
RLF
PPS It looks like a mistaken assumption about the location of the .jar file related to the file which calls it, i.e., that the files should be in the same subdirectory as common.py(c), which calls it, i.e., build/make/tools/<framework ...>. While, actually, the files are in out/host/linux-x86*/<framework ...>.
*Or, whatever platform is being used.
Unless, of course, one is supposed to do something to get those files (.jar lib) into the correct directories.
In any case. hardwiring isn't ideal, but at least it works.
RLF

Since it was working okay on my spare phone, I decided to give it a go on the phone I used. It installed okay, I set it up okay, got all the apps installed okay, etc. NFC works (yubico), BT works (keyboard). Unfortunately, I decided to encrypt. Wouldn't work. Said my data may be corrupted, I would have to format data and start again. Bummer.
And, of course, it was harder than ever to back up settings, including app settings, so, mostly, they aren't. There's an area ripe for improvement.
Note to self. Try encryption on the spare phone before even contemplating putting it on the main phone.
Best wishes,
Bob
PS I have /tmp/recovery.log, if anyone wants to see it. Although it may not be as useful as it could have been, as I reinstalled system on a whim before the last time of giving it a shot.
RLF
PPS I reinstalled, and everything seems to be working smoothly. Although I haven't tried much beyond basic call, NFC, BT, wifi, and the like. I'll try encrypting again, on my spare phone, in a couple of weeks, perhaps when the December security update comes out.
RLF

Thank you for the time you spent trying to check what's working and what's not. There was an annoying bug in the previous LineageOS versions: IR blaster doesn't work, or works once and then you need to reboot the phone to use it again. Can you please test if it works in 18.0? It's an underestimated feature that I use on a daily basis. This bug was the main reason, together with the lack of camera apps better than the G5's default (and G7's camera port, also based on LG framework), why I never used Lineage for more than a couple of days before reverting to stock based roms.

I didn't see IR blaster in the pull-down from the status bar, and didn't see it in the connected devices section. Also, I don't think that I have anything amenable to being blased by IR.
Best wishes,
Bob

wifi - works
bluetooth - works, and so does AudioFX, listening to music works great
ir blaster - not working |Confirmed working (with bug, can only blast one command before losing functionality, restarting device restores functionality for one blast) in latest 17.1 build|
encryption - not working, hangs after reboot on animation boot |Confirmed working in latest 17.1 build|
nfc - unknown, couldn't test since my G3's seem to have issues also
auto rotate - works
camera - works, front and back
torch - works
testing done on h830
quite the shame about how bugged the ir blaster is, my G3 running latest lineageos build blasts great.

NFC works - G5 (h850) Yubico Authenticator, with YubiKey 5 NFC.

whoops, reflashed between 17.1 and 18 a lot, during one of the quick setups of 18 I forgot to uncheck the box for lineageos custom recovery, but went back to uncheck it before finishing the rest.
TWRP still got erased and now with LineageOS recovery, whats the easiest way back to getting TWRP?
(I know I could reflash 20A and dirtycow, but i'm hoping for a cleaner way)

DrowningInFreedom said:
whoops, reflashed between 17.1 and 18 a lot, during one of the quick setups of 18 I forgot to uncheck the box for lineageos custom recovery, but went back to uncheck it before finishing the rest.
TWRP still got erased and now with LineageOS recovery, whats the easiest way back to getting TWRP?
(I know I could reflash 20A and dirtycow, but i'm hoping for a cleaner way)
Click to expand...
Click to collapse
Just flash it using fastboot. Look at the lineage wiki entry for your device.
Best wishes,
Bob

[ROM][11.0][4.9][AOSP][KUGO] Explosive Lobster

[ROM][11.0][4.9][AOSP][KUGO] Explosive Lobster
KUGO F5321
Hi! Just wanna share with you Android 11 ROM builded for Sony Xperia X Compact
Many Thanks for development @Cubbins
I'm not responsible for any damage caused with your device after flashing this ROM. Flash only on your own risk.
This ROM bring us Treble support ( ARM64 A/B ) structure for all GSI images based on 11 Android. Just flash any GSI at System partition after it.
How to Install:
1) Copy ROM to SD card and flash with recovery
2) Download SW_BINARIES_FOR_XPERIA_ANDROID_9.0_2.3.2_V9_LOIRE.ZIP, unzip and copy image to sdcard too
3) Flash Binaries with recovery to OEM/ODM partition
4) reboot
5) After reboot we need to flash/format userdata partition. So, download it and flash with ADB: fastboot flash userdata userdata.img or fastboot erase userdata
6) reboot.
Warning:
We use /cache partition at thid ROM as a /vendor, so if you format /cache partition on recovery - you'll catch a bootloop.
Features:
Working:
- Wi-Fi
- Bluetooth
- Fingerprint
- Sensors
- Camera
- Calling
- Music Playing
- GPS
Not Working:
You tell me
Sources:
build ROM sources:
github.com/ExplosiveLobster
kernel sources:
github.com/ExplosiveLobster/kernel_sony_msm-4.9
bug reports:
github.com/ExplosiveLobster/bug_tracker/issues
Screenshots:
{
"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"
}
Download:
Google Drive
Explosive Lobster - Google Drive
drive.google.com
Mega
3.11 GB folder on MEGA
12 files and 3 subfolders
mega.nz

So good to see some people still working on this device. I'm considering leaving the official rom to this one as soon as GPS is operational. Thank you very much.

mhemart said:
So good to see some people still working on this device. I'm considering leaving the official rom to this one as soon as GPS is operational. Thank you very much.
Click to expand...
Click to collapse
GPS Working fine with latest build, so you can try it right now

lubik1 said:
GPS Working fine with latest build, so you can try it right now
Click to expand...
Click to collapse
Really good, I have to backup my data and I'll give a try tonight. Thanks !

[QUOTE = "lubik1, post: 84244519, member: 5897890"]
Which vendor should I use?

mister-13x said:
Which vendor should I use?
Click to expand...
Click to collapse
F5321 is for X compact.

mister-13x said:
Which vendor should I use?
Click to expand...
Click to collapse
SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_loire.img
The one vendor binaries for both devices - suzu and kugo

Are the Flame Gapps in your Google Drive the Gapps you recommend, or can we just use OpenGapps as usual? This is my first experience with Android 11.
Edit1: Installation worked like a charm with your description. For me, there was no change after flashing userdata.img. The phone behaved the same way, whether I flashed userdata.img or I did not. What did NOT work was just to delete userdata - then my phone would show an error message after boot and just shut down again.
After every boot, I receive the error message “There’s an internal problem with your device Contact your manufacturer for details”. According to Google, this has something to do with Treble. I will install my apps now and get the tests going. Thank you SO much for this. If you leave your PayPal here somewhere, I will send you some small bucks that I can afford for the good development.

Spaceoid said:
Are the Flame Gapps in your Google Drive the Gapps you recommend
Click to expand...
Click to collapse
You can flash any Gapps you want, but this gapps was tested with EL ROM and work fine.
Spaceoid said:
Thank you SO much for this. If you leave your PayPal here somewhere
Click to expand...
Click to collapse
It's allways on my profile, on section "about"

Hello. I had no time to perform an install yet but I have a question (maybe stupid ?). I noticed the binaries were for Android 9 but I saw that there was a newer version called SW_binaries_for_Xperia_Android_10.0.7.1_r1_v7a_loire (no more binaries for android 11). Do you think it could be used with your ROM ? Maybe it would prevent the message that Spaceoid see at every boot ?
Just in case, here is the link to the newest version : https://developer.sony.com/file/download/software-binaries-for-aosp-android-10-0-kernel-4-14-loire/

I just send you two coffees via PayPal for the good work. I know it is not much, sadly I am a student with little income... But I hope it keeps you energized for further improvements to the ROM!
After half a day of testing the pure ROM, without any apps and just Gapps, here is what I found so far:
- Wifi is working, but, at least for me, after like 30 minutes after every boot, it seems to break. After that, I am not able to reconnect to my home wifi network, or to find any Wifi networks in general. Only a reboot fixes this.
- Regarding the error message mentioned in my last post, I found this:
How to Fix Android system There's an internal problem with your device
How to Fix Android system error "There's an internal problem with your device Contact your manufacturer for details" and How to remove NFC Service 'NFC keeps stopping'.
www.recovery-mode.com
I cannot say how reliable/safe this procedure is, though.
- Connected to this, the NFC tile in the pulldown menu (from the status bar) does not work. I can activate NFC via the settings, though; I did not try yet if it really works, but at least it can be activated.
- After every reboot, the phone forgets the time and date until it is connected to cellular network or wifi for the first time.
(- one minor thing - the alarm clock does work well, but it does only sound the alarm and not wake up the screen. So, before disabling the alarm, one has to unlock the screen first.)
Will start installing my apps now and keep on further testing.

mhemart said:
Hello. I had no time to perform an install yet but I have a question (maybe stupid ?). I noticed the binaries were for Android 9 but I saw that there was a newer version called SW_binaries_for_Xperia_Android_10.0.7.1_r1_v7a_loire (no more binaries for android 11). Do you think it could be used with your ROM ? Maybe it would prevent the message that Spaceoid see at every boot ?
Just in case, here is the link to the newest version : https://developer.sony.com/file/download/software-binaries-for-aosp-android-10-0-kernel-4-14-loire/
Click to expand...
Click to collapse
I was about to ask the same. Are the 10 binaries not compatible?

@betacrypt
Binaries for 10 are available however the kernel development was abadoned. Kernel 4.14 did not mature into an operational state. Kernel 4.9 is the current stable version, using the 9 binaries are the most recent option at the moment.

@lubik1
This is being trebled? SELinux is permissive? If that's the case, I imagine the cache.img and boot.img can be used to GSI other OS'.
Warning:
We use /cache partition at thid ROM as a /vendor, so if you format /cache partition on recovery - you'll catch a bootloop. [QUOTE/]
Click to expand...
Click to collapse

&(*) said:
@betacrypt
Binaries for 10 are available however the kernel development was abadoned. Kernel 4.14 did not mature into an operational state. Kernel 4.9 is the current stable version, using the 9 binaries are the most recent option at the moment.
Click to expand...
Click to collapse
Ah that makes sense. Somehow I thought 4.14 was stable.
Also thanks @lubik1 for your efforts to create this! Glad to see continued support for the XC - was worried we'd lost support for it. I own two and had been hoping to see an update.

betacrypt said:
Ah that makes sense. Somehow I thought 4.14 was stable.
Also thanks for your efforts to create this! Glad to see continued support for the XC - was worried we'd lost support for it. I own two and had been hoping to see an update.
Click to expand...
Click to collapse
Don't forget to thank @Cubbins too for the build.

@lubik1 ,
Can you also provide a GSI variant (of boot.img and cache.img) for those of us who like to use other systems?

Anything different to do when rooting with Magisk? I flashed the latest Magisk in TWRP successfully but when I boot into system the Magisk App says no root.

betacrypt said:
Anything different to do when rooting with Magisk? I flashed the latest Magisk in TWRP successfully but when I boot into system the Magisk App says no root.
Click to expand...
Click to collapse
Strange. I did the same this morning, downloaded latest Magisk version from Github, and it worked for me. I already used root for Titanium Backup. I used v21.2.
On another note, after one day of usage, I'd already consider this ROM quite stable. The wifi problem really is the main problem, as I only can connect to my home wifi in 20% of the day. I already lost all my mobile data because of that, now I am surfing in less than 2G speed on my phone xD

Spaceoid said:
- Wifi is working, but, at least for me, after like 30 minutes after every boot, it seems to break. After that, I am not able to reconnect to my home wifi network, or to find any Wifi networks in general.
Click to expand...
Click to collapse
We'll switch to another wi-fi driver on next build.
Spaceoid said:
- Regarding the error message mentioned in my last post, I found this:
Click to expand...
Click to collapse
Will be Fixed on next build
Spaceoid said:
- Connected to this, the NFC tile in the pulldown menu (from the status bar) does not work. I can activate NFC via the settings, though; I did not try yet if it really works, but at least it can be activated.
Click to expand...
Click to collapse
Will be added on next build
Spaceoid said:
- After every reboot, the phone forgets the time and date until it is connected to cellular network or wifi for the first time.
Click to expand...
Click to collapse
Missing rtc-service, will be added on next build

Development [ROM] [UNOFFICIAL] [12.1.0] [TB-J607F] Evolution X Snow

{
"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"
}
Evolution X 6.5 for the Lenovo Xiaoxin Pad Plus (Lenovo P11 5G WiFi) [TB-J607F]​
Code:
/*
* Your warranty is void. Or valId, probably?
*
* I am not responsible for bricked devices, dead SD cards, Ebolation X,
* thermonuclear war, or the current economic crisis caused by you following
* these directions. YOU are choosing to make these modifications, and if
* you point your finger at me for messing up your device, I will LMAO at you.
*/
Keep Evolving
Pixel UI, customization, and more, we are Evolution X!
- Team Evolution X -
@joeyhuab
@RealAkito
@AnierinB
Reach us on Twitter! @EvolutionXROM​
Just flash and check "The Evolver". We have tons of features combined together from different ROMs.
DO NOT FLASH GAPPS, ALREADY INCLUDED​
* Probable lost frames when dragging the apps from app drawer to the home screen.
* If you open the Wallpaper Picker in 2-Pane layout (Like open it via Settings), the Wallpaper will be zoomed incorrectly and look blurry. (Note: if you want to set the wallpaper, open the wallpaper picker from the Launcher).​
First Time Install / Clean Flash
1. Reboot to Recovery
2. Download the zip for your device
3. Flash whichever recovery you desire in both slots
4. Format Data
5. If you are going to flash from stock ROM, switch to the other slot in recovery, then reboot to recovery
6. Enable ADB Sideload feature, then Sideload the package to your tablet
Code:
adb sideload <path to the flashable zip>
7. Reboot to System and #KeepEvolving
Update / Dirty Flash
1. Reboot to Recovery
2. Download the update for your device
3. Flash the ROM via ADB Sideload
4. Reboot to System and #KeepEvolving​
Android OS version: 12.1.0_r11
Security patch level: July 2022
Build author: bigsaltyfishes
Source code: https://github.com/Evolution-X
Kernel Source code: https://github.com/bigsaltyfishes/kernel_lenovo_J607Z
ROM Developer: Joey Huab

Changelog:
2022-07-07:
Notes: Clean Flash Required
Device Changes:
1. Switch to Proton Clang
2. Switch to SkiaGL Threaded Renderer
3. Import Vulkan Overlay from Pixel 5
4. Enable DT2W
5. Import missing governor script from stock rom
6. Import Lenovo side changes to init scripts
Kernel Changes:
1. Upstream kernel to 4.19.250
2. Merge Tag LA.UM.9.12.r1-14300-SMxx50.0

Very good work. Is it possible to get an EvolutionX rom for the tb-j706f ?

Can we get 606f support as well?

I noticed that you recently merged latest caf on your kernel. Did you recover your device?
If you did, could you please tell me how your touch panel is detected as, in your deviceinfohw? (It would be more helpful if you upload your device info onto deviceinfohw, although I understand that it may be hard to in some regions)
I have a similar but different J606F, and the bad manufacturer lenovo didn't include touch panel driver in the kernel, lol.
Thanks

LegendOcta said:
I noticed that you recently merged latest caf on your kernel. Did you recover your device?
If you did, could you please tell me how your touch panel is detected as, in your deviceinfohw? (It would be more helpful if you upload your device info onto deviceinfohw, although I understand that it may be hard to in some regions)
I have a similar but different J606F, and the bad manufacturer lenovo didn't include touch panel driver in the kernel, lol.
Thanks
Click to expand...
Click to collapse
I've already recover my device. Here are the screenshot of Device info Hw, hope it is helpful for you.

LegendOcta said:
I noticed that you recently merged latest caf on your kernel. Did you recover your device?
If you did, could you please tell me how your touch panel is detected as, in your deviceinfohw? (It would be more helpful if you upload your device info onto deviceinfohw, although I understand that it may be hard to in some regions)
I have a similar but different J606F, and the bad manufacturer lenovo didn't include touch panel driver in the kernel, lol.
Thanks
Click to expand...
Click to collapse
Hi!
I've got an J606L, and I'm going crazy because of Lenovo didn't include the touchscreen driver in the opnesource package... I've tried to make TWRP/OrangeFox recovery, but the touchscreen don't work.
Can we somehow use this J607 kernel source in your opinion? In HWinfo almost everything is the same for me. Touchscreen, wifi, als/ps, acc.meter, gyro etc. Thanks for the dev/screenshot OP!

Marci344 said:
Hi!
I've got an J606L, and I'm going crazy because of Lenovo didn't include the touchscreen driver in the opnesource package... I've tried to make TWRP/OrangeFox recovery, but the touchscreen don't work.
Can we somehow use this J607 kernel source in your opinion? In HWinfo almost everything is the same for me. Touchscreen, wifi, als/ps, acc.meter, gyro etc. Thanks for the dev/screenshot OP!
Click to expand...
Click to collapse
I don't think you can't directly use this J607 kernel source as the soc of J606(sm6115) is different from J607(sm7225), but I found that the kernel version of J606 in stock rom is same as J607, maybe the J607 kernel source code can serve as a reference for you to fix the J606 kernel source code. Also, If you want to fix touchscreen in TWRP/OrangeFox, you need to import touchscreen firmware from stock rom.

bigsaltyfishes said:
I don't think you can't directly use this J607 kernel source as the soc of J606(sm6115) is different from J607(sm7225), but I found that the kernel version of J606 in stock rom is same as J607, maybe the J607 kernel source code can serve as a reference for you to fix the J606 kernel source code. Also, If you want to fix touchscreen in TWRP/OrangeFox, you need to import touchscreen firmware from stock rom.
Click to expand...
Click to collapse
Hi!
Yes I've seen your kernel source. I think it will help me for the building, because there is many similarity. Even the filesystem is 1:1 same. I've got final exams in the next few weeks in the Uni too, but after that I will try to make it.
One question tho. How can you export the touchscreen files from the stock rom? I dont know how look your tablet's firmware, but the J606L has a very stupid firmware structure, with superpartitions, and I cannot get any useful stuff out from it, just the vbmeta, boot/recovery images.
Thank you, and sorry for the offtopic.

Marci344 said:
Hi!
Yes I've seen your kernel source. I think it will help me for the building, because there is many similarity. Even the filesystem is 1:1 same. I've got final exams in the next few weeks in the Uni too, but after that I will try to make it.
One question tho. How can you export the touchscreen files from the stock rom? I dont know how look your tablet's firmware, but the J606L has a very stupid firmware structure, with superpartitions, and I cannot get any useful stuff out from it, just the vbmeta, boot/recovery images.
Thank you, and sorry for the offtopic.
Click to expand...
Click to collapse
You can find firmware you need in /vendor/firmware. If it is hard for you to extract them from your tablet, you can simply extract them from 9008 Images. Partitions in super partition are simply named as super_*.img in 9008 package, they are raw images, you can directly mount them with ro option (They have share_blocks feature, you can't mount them in rw mode).

can i flash it on j706f?

Marci344 said:
Hi!
I've got an J606L, and I'm going crazy because of Lenovo didn't include the touchscreen driver in the opnesource package... I've tried to make TWRP/OrangeFox recovery, but the touchscreen don't work.
Can we somehow use this J607 kernel source in your opinion? In HWinfo almost everything is the same for me. Touchscreen, wifi, als/ps, acc.meter, gyro etc. Thanks for the dev/screenshot OP!
Click to expand...
Click to collapse
The thing that's missing is the kernel module for the NT356(something)_HostDL or something in the kernel's {SRCROOT}/drivers/input/touchscreen/NT35something_HostDL.
The driver, IS available in a P11 LTe or something's kernel source available in lenovo downlooad page. (Sorry, my memory is very inaccurate, I was trying bunch of stuffs when I bought my P11 last year, it's a bit hazy now)
I made the driver located there, modded Makefile, got some kernel compile issue, and I somehow solved it, but the spi read only got value 00000000 and it didn't work. (You can get more info from postmarketOS-offtopic Matrix chatroom, chat history is logged in there, I got help from somebody a long time ago and there are conversations about this)
I got touchscreen to work with a prebuilt kernel (Lost the device tree) but that's it..
I hope we make something out of lenovo's junky kernel source codes.. The device has potentials!

bigsaltyfishes said:
I've already recover my device. Here are the screenshot of Device info Hw, hope it is helpful for you.View attachment 5625467
Click to expand...
Click to collapse
Wonderful that you recovered it!
Thanks a lot for the screenshot. It seems like that you have the himax touchscreen variant. (I was trying to ask you to test the driver for nt365blahblah touch screen, if your variant was the one that had it)

hi sir, i flashed crdroid gsi on my j706f, but the settings doesnt look like your rom which show in two pane, can i edit build.prop to get it show as your rom settings? or what should i edit? thank you very much.

sabosanbosocho said:
hi sir, i flashed crdroid gsi on my j706f, but the settings doesnt look like your rom which show in two pane, can i edit build.prop to get it show as your rom settings? or what should i edit? thank you very much.
Click to expand...
Click to collapse
You can't enable it by simply editing build.prop. This feature related to an optional package called androidx.window.extensions. Ask GSI builder add this package or build it yourself.

great work!
overall pretty pleasant experience, and nice feature set. However, two problems
1. as mentioned, adding app icon to the homescreen doesn't work sometimes and it laggs out
2. this is the deal breaker for me, as the volume slider doesn't work. and video play back stuffers probably due to this.
---
update:
the second issue ragarding to the volume slider, it only breaks after playing emby, not sure if other app also break it but that's the only one i found so far. a reboot would fix it

Please make Evolution X happen to TB-J606F also! it's with an older SOC, and we don't get A12 update. A lot of people have it, but not much support

Does widevine security L1?

bigsaltyfishes said:
You can't enable it by simply editing build.prop. This feature related to an optional package called androidx.window.extensions. Ask GSI builder add this package or build it yourself.
Click to expand...
Click to collapse
did you add that by yourself or that was included in evox source code?

mdve123 said:
Please make Evolution X happen to TB-J606F also! it's with an older SOC, and we don't get A12 update. A lot of people have it, but not much support
Click to expand...
Click to collapse
you can flash google gsi (android 12), its works good.
Generic System Image releases | Platform | Android Developers
developer.android.com