Hello!
This is a development thread for the project of upgrading of the Linux kernel for the U8500 platform.
Builds provided here (at the moment of writing this message) are not considered to be used as a daily driver, by any means, - these are rather a dev preview versions.
For now, there are a several LK builds (the highest currently supported kernel version is 3.10).
Because builds here are really not stable, I'll just leave a disclaimer here.
Code:
#include <std/disclaimer.h>
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modificiations, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
Working features
RIL
Camera (front & rear) - only works in <3.8
Video (playback & recording)
Audio (playback & recording)
Wifi
Bluetooth (broken in >=3.8, needs a workaround to manually startup)
USB, ADB
Tethering (not tested)
GPS (not tested)
Sensors
Known bugs
IRQs are mishandled by some device drivers (abb_btemp, abb_fg)
proximity sensor might not work (not tested, cause it's broken on my device)
deep sleep might not work at a times
MMC driver works unreliably in >=3.8 (contiguous usage might lead in a data corruption)
networking is not fully-functional (no mobile data)*
camera is broken in 3.8
*some other features of the android kernel might not present - it's because these kernels lacks android-specific patches.
Sources
LK 3.5
LK 3.6
LK 3.7
LK 3.8
LK 3.9
LK 3.10
Downloads
http://xda.mister-freeze.eu/XDA-files/ChronoMonochrome/misc/upgrading
Installation
install chrono kernel r5.2 or higher (this is needed to pick up the necessary scripts, incl. bootscripts, etc)
reboot to recovery
install build linked in "Downloads" section
Credits
Linux kernel development community
Google
ST-Ericcson
Samsung
Team Canjica
XDA:DevDB Information
U8500 Linux kernel upgrading project, Kernel for the Samsung Galaxy Ace II
Contributors
ChronoMonochrome
Kernel Special Features:
Version Information
Status: Alpha
Created 2017-05-09
Last Updated 2017-05-10
Reserved
Porting
The porting a higher kernel version tehnique I'll describe here is not intended to be a guide for dummies. I'll assume you've already built a kernel for your device, familiar with git versioning control usage and with some porting / coding tehniques.
Firstly, you need a cleaned source for your device. By "cleaned" I mean, there are no Linux incremental patches, android changes applied, manufacture-specific patches are avoided when possible and so on - you need sources as closest to a "pure" Linux kernel as possible. Otherwise you'll have later need to deal with conflicts resolution, you'll most likely be unable to resolve and the kernel won't boot.
So, without a further forewords, the tehnique is below:
1) As was previously mentioned, a clean kernel source is required, I'll assume we are starting from LK-3.4 ( https://github.com/ChronoMonochrome/Chrono_Kernel-1/commits/ea228ee0f5e9935841aff25c62fa163cd78dc01d ) and porting a higher kernel versions. A kernel base needs to be tested for any bugs just to distinguish, which bugs were intruduced during porting from those ones that already present in a kernel base.
2) The following steps will mostly use git bisect and git merge commands in order to merge all the changes from a higher kernel versions and help to find / resolve the bugs that were introduced. I suggest copying a git kernel repo that you use for building to a somewhere else, so you can use it , e.g. for grepping a different versions source, bisecting the revisions and so on, so don't need to bother messing up in your main repo that you use for build.
3) Firstly, lets just try to merge a higher kernel version, e.g. LK 3.5 by issuing a command git merge lk-3.5. You'll likely have a lot of merge conflicts, most of which you can resolve with resetting the paths to a some revision (either a kernel base - lk 3.4, or the version you do port, or just another suitable conflict resolution). So I suggest to write those paths to a text file, like so:
Code:
arch/arm/boot
arch/arm/mach-ux500
arch/arm/plat-nomadik
drivers/mmc
include/linux/mmc
drivers/usb
include/linux/usb
drivers/mfd
include/linux/mfd
...
Write all the paths you intend to reset to the kernel base, you most likely need to re-use them later. To actually perform a resetting source, you can issue
Code:
for path in $(cat file_with_a_paths.txt | xargs)
do
git checkout COMMIT $path
done
Be sure not to put to this file anything not the device-specific! Resetting to the kernel base should be avoided when possible (never ever try resetting archictecture-specific paths, e.g. arch/arm/kernel, arch/arm/mm and so on - unless you really know that kernel will boot thereafter, instead, you have to manually resolve such conflicts). Resolve any other conflicts by resetting paths to the porting source (e.g. LK 3.5).
Note. While resetting with a paths is probably not the most accurate tehnique, but people don't live that long to use more accurate approach, e.g. performing git cherry-pick for every upstream commit and then manually resolving all the conflicts, you'll just sooner or later get bothered and will abandon it.
4) When you're done with the previous steps you can try building kernel. You'll likely have a build errors - because some part of a source got not updated (e.g. the device-specific drivers), you need manually implement the necessary by a higher kernel version changes. Firstly check if an upstream kernel contains the necessary fixes (example: https://github.com/ChronoMonochrome/Chrono_Kernel-1/commit/9fae8c449b710f502662da1cbcf26ece5a098af9 , https://github.com/ChronoMonochrome/Chrono_Kernel-1/commit/fe027c25d6db0d100937deb5248e249ec5b24ee7 ). If the driver you are porting doesn't exist in the upstream, you can also try to find a similar change and mimic it: https://github.com/ChronoMonochrome/Chrono_Kernel-1/commit/5f2e7afbf2ac3284dc62b3d96a0627c7f99ed4e9 ( ported similarly to https://github.com/ChronoMonochrome/Chrono_Kernel-1/commit/526c597 ). In the worst case scenario you will need to examine the upstream changes and apply the changes so that the drivers complies to the upstream changes: https://github.com/ChronoMonochrome/Chrono_Kernel-1/commit/ea6432d167 .
5) If everything is done properly and you're lucky enough, the compiled kernel might already bootup. If not, you'll need to find a culprint that doesn't let the device to boot up. Switch to a copy of your kernel sources, reset the source to the base kernel version (e.g. LK 3.4), issue git bisect good, then issue git bisect bad lk-3.5, git will reset to a somewhere in a middle between of LK 3.4 and LK 3.5.
6) Save your changes in the kernel repo, by assigning a some branch to it, switch to the source base, merge all the fixes you've already introduced, then merge the revision you have got in the previous step by bisecting the tree. Repeat these steps until you'll find a first bad commit.
7) If you are already on this step, the most trickiest part starts here - testing (hopefully) working kernel for bugs (if any). While logs can be useful sometimes (so you can google the failing messages and find something useful), there are also many bugs you can find only performing git bisect tehnique decribed above.
The decribed algorithm only possible thanks to having a clean kernel source. The usage of this guide is not limited only to the kernel porting, it can be used on other projects as well, this is just what I've come across to, when I've ever started porting Linux kernel versions higher than LK3.4.
Reserved
I wonder if any of this expertise couldn't look pretty cool here too.
Wooooowwwewe
Oooh
Look whose good boys have been trying to win the STE mastermind prize as of lately
https://github.com/novathor-mainline/linux
https://git.kernel.org/pub/scm/linu...inux-nomadik.git/log/?h=ux500-skomer-v5.5-rc1
mirhl said:
Oooh
Look whose good boys have been trying to win the STE mastermind prize as of lately
https://github.com/novathor-mainline/linux
https://git.kernel.org/pub/scm/linu...inux-nomadik.git/log/?h=ux500-skomer-v5.5-rc1
Click to expand...
Click to collapse
Seriously!
mirhl said:
Oooh
Look whose good boys have been trying to win the STE mastermind prize as of lately
https://github.com/novathor-mainline/linux
https://git.kernel.org/pub/scm/linu...inux-nomadik.git/log/?h=ux500-skomer-v5.5-rc1
Click to expand...
Click to collapse
Wow, that's incredible
Exynos4412 already got some mainline support, it would be very nice to have this one supported too.
Aaaaand it's done, kinda.
ST-Ericsson NovaThor U8500 - postmarketOS
wiki.postmarketos.org
device/testing/linux-postmarketos-stericsson · master · postmarketOS / pmaports · GitLab
postmarketOS package build recipes
gitlab.com
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is 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 restores 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 our Gerrit Code Review.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
SUPPORTED DEVICES
- LEX820 (X2_CN)
- LEX821 (X2_WW)
- LEX822 (X2_CN)
- LEX829 (X2_NA)
- LEX910 (MAX_PLUS. Currently only supported on unofficial test builds)
HOW TO INSTALL LINEAGEOS WITH LINEAGE RECOVERY
- Make sure your phone is running firmware from at least 466d for x2 and pseudo 466d for max_plus. If not? Please either the minimum recommended version below (or optional updated versions) and install it via Lineage Recovery. It can be flashed before or after the ROM
Please follow the official LineageOS Wiki instructions for our device
Install LineageOS on x2 | LineageOS Wiki
wiki.lineageos.org
HOW TO INSTALL LINEAGEOS WITH TWRP
- Make sure your phone is running firmware from at least 466d for x2 and pseudo 466d for max_plus. If not? Please either the minimum recommended version below (or optional updated versions) and install it via TWRP. It can be flashed before or after the ROM
- Unlock bootloader and install TWRP 3.7.0_9-0 (designed for Pie and above and for treble) or higher. TWRP instructions are here.
- Download the LineageOS and firmware zips. (see Downloads)
- Boot into TWRP.
- Copy the downloaded zip files to internal sdcard.
- Perform a backup of your current ROM. (Optional)
- RECOMMENDED: If this is a fresh install? Do a format data (wipe > "format data" button > type "yes"). If this is an upgrade from the previous version then you can skip this step
- Flash firmware and LineageOS zips.
- Optional: Install the Google Apps addon package. (see Downloads)
- Reboot to system.
HOW TO UPGRADE LINEAGEOS FROM 17.1
Please follow the official LineageOS Wiki instructions for our device. You can use either TWRP or Lineage Recovery.
Upgrade LineageOS on x2 | LineageOS Wiki
wiki.lineageos.org
HOW TO UPDATE LINEAGEOS WITH LINEAGE RECOVERY
Please follow the official LineageOS Wiki instructions for our device
Upgrade LineageOS on x2 | LineageOS Wiki
wiki.lineageos.org
HOW TO UPDATE LINEAGEOS WITH TWRP
- Download the LineageOS zip(s). (see Downloads)
- Copy the LineageOS zip to internal sdcard.
- Reboot to TWRP.
- Flash LineageOS. (Wiping Dalvik and Cache is optional, but recommended)
- Reboot to system.
MAIN DOWNLOADS
Lineage Recovery for x2:
- Official:
https://download.lineageos.org/x2
- Unofficial:
https://osdn.net/projects/lineageos-for-x2/releases/p17327
TWRP for x2: Official https://twrp.me/leeco/leecolemax2.html
TWRP for max_plus: Official https://twrp.me/leeco/leecolemaxpro.html
Lineage:
- Official:
https://download.lineageos.org/x2
- Unofficial 18.1:
https://osdn.net/projects/lineageos-for-x2/releases/p17328
GOOGLE APPS (GAPPS) DOWNLOADS
- MindTheGapps
Codefire - Listing of gapps
GOOGLE CAMERA (GCAM) DOWNLOADS
Google Camera:
Parrot043: MGC_7.3.020_Parrot043-v2.apk
Download MGC_7.3.020_Parrot043-v2.apk by Parrot043.
www.celsoazevedo.com
Enable "Fix tint on front camera" and set it to "Fix green tint." Found inside Settings > Advanced > Experimental settings.
MISC DOWNLOADS
ThE_MarD's LineageOS for x2 Sourceforge, directory: (also contains some mods and tweaks)
https://sourceforge.net/projects/lineageos-for-x2/
FIRMWARE DOWNLOADS
Minimum required versions:
- LEX820 (X2_CN) 466D
- LEX821 (X2_WW) 466D
- LEX829 (X2_NA) 466D
- LEX910 (MAX_PLUS) 13s
Link for x2 firmware:
https://sourceforge.net/projects/lineageos-for-x2/files/Firmware Updates/
Link for max_plus firmware:
https://sourceforge.net/projects/lineageos-for-max-plus/files/firmware/
DEVELOPER RESOURCES
lineage-x2-devs
lineage-x2-devs has 7 repositories available. Follow their code on GitHub.
github.com
LineageOsMaxPlus
LineageOsMaxPlus has 7 repositories available. Follow their code on GitHub.
github.com
GitHub - LineageOS/android_device_leeco_msm8996-common
Contribute to LineageOS/android_device_leeco_msm8996-common development by creating an account on GitHub.
github.com
GitHub - LineageOS/android_device_leeco_x2
Contribute to LineageOS/android_device_leeco_x2 development by creating an account on GitHub.
github.com
GitHub - LineageOS/android_kernel_leeco_msm8996
Contribute to LineageOS/android_kernel_leeco_msm8996 development by creating an account on GitHub.
github.com
HOW TO CONTRIBUTE?
Send your patches up for review: https://review.lineageos.org/
Read the guides on the LineageOS Wiki: https://wiki.lineageos.org/
XDA:DevDB Information
[OFFICIAL][X82X][10.x][TREBLE] LineageOS 18.1 (Android 11) for LeEco Le Max 2, ROM for the LeEco Le Max 2
Contributors
ThE_MarD, mosimchah, Lucchetto00, CrisBalGreece,Tortel1210,codeworkx,moto999999,1nfrag,shivatejapeddi,KuranKaname,GalaticStryder,andr68rus,visionary,zhaoguomanong
Source Code: https://github.com/LineageOS
ROM OS Version: Android 11
ROM Kernel: Linux 3.x
ROM Firmware Required: X820, X821, X822 and x829 466d. x910 13s.
Based On: AOSP
DONATIONS
Pay Marc Bourgoin using PayPal.Me
Go to paypal.me/ThEMarD85 and type in the amount. Since it’s PayPal, it's easy and secure. Don’t have a PayPal account? No worries.
www.paypal.com
Reserved
Frequently Asked Questions
I've been asked to provide logcat, how do I do that?
You can either root and use an app like MatLog, or if boot logcat is required? You will need adb logcat from a PC. Here's a simple guide from the LineageOS Wiki https://wiki.lineageos.org/logcat.html
My lock screen crashes after reboot, what should I do to fix it?
https://forum.xda-developers.com/le-max-2/how-to/guide-to-fixing-x2-lockscreen-crash-t3918911
I don't see an option for call recording, what's going on?
Only the stock dialer app supports it. If you install a Gapps package that overwrites the stock dialer app? It won't have call recording as well. Only the included dialer app of LineageOS is compatible to call recording since it needs to be a ROM implementation and I haven't seen a Play store app that adds support for custom ROM call recording. Please also note that call recording is blocked for countries and carriers that have laws against any form of call recording.
What is Power-off Alarm?
This feature allows you to set an alarm clock with the stock clock app included with LineageOS and then turn off the phone, and it will boot up a minute before the designated alarm time and then properly alarm. It works with the device either powered off and also offline charging.
Using a clock app from OpenGapps Stock or from the Play store is not compatible with custom ROM implementations of power-off alarm... So consider this your heads up if you didn't know that already... As I am not responsible for anyone being late for their wedding/work/school/vacation if you tried a non-stock clock app with your LeEco msm8996 device powered off. :silly:
What apps are recommended with the Open Source ConsumerIR?
Zaza Remote (only with selinux enforcing) and Mi Remote work great. Smart Remote for Sharp TV also works. I'd recommend avoiding Peel Universal Smart Remote as it hijacks the lock screen with ads...
Pls sir, I can't connect to my network or IMS/VoLTE doesn't work! What can I try?
Please look below at the "APNS Update from Google" section and try that. I can't offer much else for help sorry as I have zero experience with IMS/VoLTE as Canada blacklists BYOD from that feature... Otherwise, if you need extra help? Hopefully, someone else in the x2 community can give you advice.
What is the difference between the official LineageOS builds and unofficial?
Unofficial test builds are builds I put out to test changes before I push them to the Official builds... So please stick with Official builds if you want to play it safe... But if you wish to help test and provide feedback on changes before they go official? Unofficial test builds are the best way to do so.
Where is the QuickCharge toggle?
Settings > System > Advanced > LeEco Settings
The rear-facing camera won't focus, what should I try?
Please go into Settings > System > Advanced > LeEco Settings, and then enable the focus fix. You may need to restart any open camera app or potentially reboot the system in order for the focus fix values to work... If that doesn't resolve it? Please try EUI ROM... If it still won't focus? I'm sorry, but your hardware camera actuator is defective and you either need to try the Le Max 2 rear camera magnet trick (please Google it) or replace the rear camera hardware.
Why is our Widevine level only L3?
Unfortunately, Widevine L1 failed to work correctly on X2 and zl1/0... It would report we have L1 hardware support but vp9.secure and avc.secure codecs were failing to render, thus apps that used L1 like Amazon Prime would error out and revert to L3 and worst-case scenario apps like Vudu would crash.
I haven't seen any fixes for those codec issues, so I gave up on it as L3 works fine.
Also, Netflix HD will never work on LeEco devices as they never got them "Netflix certified" which sounds like a money-grab move since L1 is all they should need. For example, Asus Zenfone 5z is L1 certified but not "Netflix certified" just like we are and they don't get the option to stream in HD.
This explains it a lot better
https://androidpcreview.com/netflix-hd-android-tv-box/
My device doesn't show any apps in the Play Store what should I do?
https://lineageos.org/Google-Play-Certification/
exfat does not work on LineageOS, what is up with that?
LeEco Le Max 2 does not ship with exFAT licensing so we are not allowed to incorporate it in LineageOS Le Max 2 builds. This was tested by both CrisBalGreece and I. If by chance there is an OFFICIAL EUI ROM build that includes exfat? Please let me know so I can test it as well... Here are the LineageOS device charter requirements on exfat
https://github.com/LineageOS/charter/blob/master/device-support-requirements.md#exfat-support
KNOWN BUGS for x2 and max_plus
WiFi randomly disconnects when the device is asleep
Lockscreen may sometimes fail to unlock after a reboot (seems to mainly happen when the battery is low and power-saving mode is on. The workaround is to reboot again and it will unlock. Please note, this is NOT related to the lock screen crash bug where it always fails to unlock due to the encryption footer getting corrupted by an old beta build of TWRP. The fix for that is still in the lock screen crash fix thread I have linked up in the FAQ.)
Updating using the built-in LineageOS updater with TWRP as your recovery when encrypted causes Google Play Services to crash repeatedly (Lineage Recovery works without issue or updating manually via TWRP is fine though)
Microphone and button on 3.5mm headsets using the 3.5mm to Type-C adaptor only works with reversed orientation (IE, official LeEco adaptor with the logo facing downwards)
Dual-role USB does not work (our Type-C port can't detect if it should offer the option to host data transfer, charge the other device, or charge while using Aux out).
Taking a photo during 4K UHD video recording produces a photo with green static instead of a photo. This bug only happens in Snap camera... Google Camera Mod and Open Camera (with Camera API v2 enabled) produces pictures without issue.
Infinity focus not working (for panoramas, AR and some QR code scanners. Infinity focus also doesn't work in EUI ROM hmm... oddly enough some imx230_lg modules infinity focus can work if you don't need focus fix... so I blame LeEco for the messed up camera haxxs they did since s2 and zl1 have the same issues.)
KNOWN BUGS for max_plus
ES9018 Hi-Fi Audio DAC for 3.5mm headsets to Type-C adaptors does not work (this is the bug that is preventing official unified builds of LineageOS of x2 and max_plus...)
Fingerprint does not work when the device is asleep (this is due to the ancient device firmware on max_plus being officially stuck on 13s... there is a pseudo 466d modem firmware fix attempt I made but have not received feedback on yet)
Boot animation does not work unless you tap the power button twice to turn the display off and on again (this is due to a fix for screen tearing... maybe one day I'll figure out a fix for boot animation to work with the screen tearing fix)
When launching a camera app, viewfinder goes green for a second and then works normally
After using the USB port with Type-C headset or OTG with a flash drive, the device cannot charge until a reboot is performed (known bug even on EUI ROM)
APNs Update from Google
This is an optional update if the current APN settings from LineageOS might not be up to date for your carrier and you need newer ones. This is the official APNs list from Google.
After flashing it? Please reboot to system and then go into Settings > Network & Internet > Mobile Internet > Advanced > Access Point Names > "..." menu button > reset to default.
https://sourceforge.net/projects/lineageos-for-x2/files/Mods and Tweaks/APNs Update from Google/
The official Google source git for this file can be found here:
https://android.googlesource.com/device/sample/+/refs/heads/master/etc/apns-full-conf.xml
Please note! This APNs list WILL get overwritten by the ROM on any ROM update and will need to be reinstalled.
Reserved
Special Thanks
@mosimchah for his contributions to the LeEco msm8996-common code and kernel. Especially on Android 11 for his clang kernel rebase and getting our trees started
@Tortel1210 for his contributions to x2 and helping out with gerrit. He did a lot of help during Android 11
@Lucchetto00 for converting Tortel's devicesettings into LeEco settings and adding QC toggle, plus his method of detecting if a setting exists and whether to display it or not. He also did the initial bring up for x2 on Q so super special thanks on that too! He also helped out a bunch with Android 11 trees
@codeworkx for his major contributions to the LeEco msm8996-common code and kernel and the awesome open-source camera HAL
@moto999999 for helping the x2 get LAOS 15.1 working. When others left LAOS he helped get the momentum started again.
@infrag for his contributions to x2 such as the multiple audio fixes, LEDs and sorting out the open-source camera HAL blobs and assisting with QS Torch
@shivatejapeddi for his contributions to x2 such as finding the fix for QS Torch and the regularly requested VoLTE support XD
@KuranKaname for his contributions to x2 such as helping get Dalvik VM and HWUI sorted out when 14.1 settings didn't work on 15.1, plus his never-ending mission to finding the most optimized code.
@andr68rus for everything he has contributed to x2. He may have moved to the Xiaomi Mi Mix 2 (sexy device!) but will be fondly remembered for everything he did for the x2 to make Nougat great. We will finish what you started.
@GalaticStryder for his fix for truly display panel that is better than my fix and his other awesome kernel improvements.
ViSi0Naryy for his contributions to LeEco msm9996-common with testing and contributions with Gerrit
@jabashque for helping fine-tune the performance for LeEco msm8996-common devices! LeEco has never been so smooth!
@DD3Boh for helping with msm8996 in general and also for helping out us LeEco devs
cristiansilaghi (no idea if he has XDA as he communicates with me on Telegram) for helping diagnose the battery percentage issues and finding some extra commits to help make it as accurate as possible and a selinux fix for offline charging animation.
...and finally the community. This is for the community, by the community. Give yourselves a pat on the back.
If I missed anyone? Please let me know and I can add them.
Donations
DonMomente (not sure if he's on XDA forums or not) for his very generous donation. Thank you and your family too!
@popeye13 for helping cover my replacement motherboard costs
@Bollex for also helping cover my replacement motherboard costs
@kurtn for also also helping cover my replacement motherboard costs
@xlcashlx for also also also helping cover my replacement motherboard costs
Robin Vd Berg since I'm unsure on username for also also also also helping cover my replacement motherboard costs
Heyyo, a new test build is going up! The upload will be done in about 30 minutes of this post. lineage-18.1-20201223-UNOFFICIAL-x2 contains a fix for Consumer IR so it works with MiRemote and Zaza Remote again, yay hehe. So meow it's just WiFi Hotspot with password and WiFi Display that are known bugs left
https://osdn.net/projects/lineageos-for-x2/releases/74121
where is download link
Heyyo @innocent80 , please check the first post under "main downloads" as I always have the unofficial build links in there. One day we shall have Official LineageOS 18.1 builds, but not yet...
ThE_MarD said:
Heyyo @innocent80 , please check the first post under "main downloads" as I always have the unofficial build links in there. One day we shall have Official LineageOS 18.1 builds, but not yet...
Click to expand...
Click to collapse
your roms are awesome its like a a user need u will oneday make offcial roms i am sure about that
ThE_MarD said:
- Unofficial 18.1:
https://osdn.net/projects/lineageos-for-x2/releases/p17328
Contributors
ThE_MarD, mosimchah, Lucchetto00, CrisBalGreece,Tortel1210,codeworkx,moto999999,1nfrag,shivatejapeddi,KuranKaname,GalaticStryder,andr68rus,visionary,zhaoguomanong
Click to expand...
Click to collapse
Thank you. Did not expect 18.1 soon.... . Boots without GApps too. Navigation buttons seem to stop working after sometime. Logcat attached. But keep in mind my X2 screen is broken but nav buttons continue to work on other ROMs. It could very well be sort of touch and go on my device.
Edit: forgot to add that I was referring to hw nav buttons. No probs with onscreen ones.
Heyyo @kayyappan , thanks man! Yeah it was pretty fast to bring up since we are a legacy device meow, so unfortunately we can't upgrade blobs and conform to Android 11... The only real negative to that with LineageOS is Wifi Display might have to be dropped for us if we can't find new blobs that aren't from CAF leaked bsp (since we don't have a public release license for Board Support Package like a stock ROM does) so hopefully a compatible device comes along that we can Kang blobs from for WFD on their stock ROM....
Also bro, unfortunately I can't see your attached logcat. Can you please PM it to me?
Hi @ThE_MarD,
I tried to flash Lineageos 18.1 in my Le Max Pro X910 but I think I screwed it in a big way because by mistake I flashed the firmware of Le Max 2 instead of the proper one for X910 model. As a result, I bricked it and now it doesn't turn on, it doesn't charge, no fastboot , no recovery just a beautiful brick. Do you think it could be possible to unbrick it? Is there any guide step by step of how to do it ?
Regards!
Heyyo @txekalzen , yikes! Afaik the only QFIL available for x910 is here. Tbh I tried to buy it myself but the guy didn't reply to me... Hopefully you will have better luck than I did.
https://www.needrom.com/download/le...ultilanguage-rom-unbrick-phone-qfil-fastboot/
Which recovery version were you using btw? The official TWRP for max_plus or something else?
Hi , it works fine, but the only problem is the battery that's empty quickly
ThE_MarD said:
Heyyo @txekalzen , yikes! Afaik the only QFIL available for x910 is here. Tbh I tried to buy it myself but the guy didn't reply to me... Hopefully you will have better luck than I did.
https://www.needrom.com/download/le...ultilanguage-rom-unbrick-phone-qfil-fastboot/
Which recovery version were you using btw? The official TWRP for max_plus or something else?
Click to expand...
Click to collapse
Hi,
Thank you very much for the link. I will have a look at it.
I was using the last official TWRP for max_plus.
twrp-3.4.0-0-max_plus.img39.3M2020-06-22 15:56:11 EDT
txekalzen said:
Hi,
Thank you very much for the link. I will have a look at it.
I was using the last official TWRP for max_plus.
twrp-3.4.0-0-max_plus.img39.3M2020-06-22 15:56:11 EDT
Click to expand...
Click to collapse
Hi @ThE_MarD,
I found the following link that allows to download a ROM for Le Max Pro X910. What do you think? Does it look legit and could it be a valid ROM to flash?
LeEco Letv Max Pro X910 Firmware Flash File (WiFi fix) — Leakite
@txekalzen , if you can get to fastboot? Then yes give it a try... If not? You will still need QFIL so it can get out of EDL mode
ThE_MarD said:
@txekalzen , if you can get to fastboot? Then yes give it a try... If not? You will still need QFIL so it can get out of EDL mode
Click to expand...
Click to collapse
Hi,
Thanks for your comments.
Hi, WiFi tethering is not working, it always says password incorrect
ffigos said:
Hi, WiFi tethering is not working, it always says password incorrect
Click to expand...
Click to collapse
it is a known bug
Heyyo, a new test build is going up! It will be done uploading within 30 minutes of this post, and as always the link will be in the first post. lineage-18.1-20210108-UNOFFICIAL-x2 has a bunch of small fixes and also fixes WiFi Hostspot with WPA2 on both 2.4GHz and 5GHz, which means the only remaining bug is WiFi Display which hopefully a good solution shows up that we can use.
Great job , I'm waiting . thanks for your work , my phone is continues"alive" thanks to that
riceDroid for OnePlus 8T|9R [kebab][lemonades]
View attachment 5815623
What is riceDroid?
* Ricedroid is a FREE OPENSOURCE Android Operating System based on LineageOS and crDroid, that aims to provide necessary "ricing" aka customizations for ANDROID while being fast and stable. This operating system is highly inspired by Oxygen OS (10-11) and nothingOS, we strive to make things different but not too far from AOSP.
What is RiseUI?
* RiseUI is the name for our firmware skin/user interface.
Terminology
* The term \'rice\' is used to describe a person's unix desktop where \'ricing\' is an act where someone customizes their desktop such as the changing icons, panels or system interface.
source: https://jie-fang.github.io/blog/basics-of-ricing
Based on Android 13 | Tiramisu QPR1
What's working?
Most basic stuffs
Bugs and Issues
Please tell me with a logcat attached
Variants available
CORE build only - comes with basic gapps, no setupwizard
Device specific changes
Based on OOS 12 Firmware, Flashing OOS 12 firmware is a must before installing, boots on OOS13 firmware but touchscreen doesn't work
Shipped with OOS Camera - most features exposed working.
Shipped with Chaeyo.0 kernel - based from OOS 12 kernel source - CFS scheduler focused kernel.
Credits
LineageOS kebab team - for most of device/kernel tree changes
chandu078 - base device/vendor tree
cjh1249131356 - oneplus camera source
Notes
I will only maintain Official GMS core variant based on OOS 12 due to limited free time. Other variants will be officially maintained by sir manidreddy a.k.a Lord Itachi
If you have any type of concerns, please address it here, I'll try to accommodate as soon as I see the message.
Changelog
Source Changelog
Download link
riceDroid-13.0-202301210506-kebab-v10.1-CORE-OFFICIAL.zip
Installation Guide
Fastboot - recommended method
Download SDK platform tools here and follow this tutorial
Reboot to fastboot
Enter fastboot mode
Perform flashing commands listed on attached file: fastboot-commands
Enter recovery mode
Wipe data/cache/dalvik-cache
Sideload preferred zip files (magisk, gapps etc.)
Reboot to system
Sideload - recommended for those who were able to flash oos 12 on A/B slots
Fastboot flash recovery.img from firmware payload.bin
Reboot device into recovery mode
Enter ADB sideload mode
adb sideload ROM.zip
Wipe data/cache/dalvik-cache
Sideload preferred zip files (magisk, gapps etc.)
6. Reboot to system
Android OS version: 13.0.0_r24
Security patch level: January 2023
Build author/Device Maintainer: dlwlrma123
Device tree source code: https://github.com/ricedroidOSS-devices/device_oneplus_kebab
Device vendor source code: https://github.com/ricedroidOSS-devices/vendor_oneplus_kebab
Kernel source code: https://github.com/ricedroidOSS-devices/android_kernel_oneplus_sm8250
Firmware source code: https://github.com/ricedroidOSS
Firmware created by: The ricedroidOSS Team
Reserved for changelog purposes.
Bro! I love this rom. Working amazing without any problem. But remember, IU a.k.a Lee Ji-eun is mine (my). Rest is everything fine.
Currently I am on Elixir OS android 13 based so can I directly flash ricedroid over it ? Or do I have to roll back to oxygen os 12?
Can anyone help please ?
therajatshahare said:
Bro! I love this rom. Working amazing without any problem. But remember, IU a.k.a Lee Ji-eun is mine (my). Rest is everything fine.
Click to expand...
Click to collapse
Can you share the download link please?