So FIXED on CM based Nougat roms: only change the media.msm8956hw=1 to 0 in the build prop.
Tested with Lineage, Xenon, NitrogenOS. I think when it's enabled the VR playing quality wrong.
This method wont working on MIUI, because 0 is the default value.
How to fix on MIUI 9.5: post
Hi members! Redmi Note 3 Pro QA
So a simple question and remark. I'm using Var's VR Video Player. This is one of the best optimized player at the moment for all VR formats. Tested a lot of players, the quality as the same with others, so the next problem is not an app problem.
VR video quality is very good in the older MIUI v7.1.x.x and 7.2.x.x roms (not tested all MIUI roms) and Krexus (build 3) rom.
Tried on other roms (I think in all roms), and the quality is not as good, not as sharp the picture. Blurred the edges and the lines not as sharp. All other roms, new MIUI's, all CM base and AOSP roms this happening. Tried to change some encoding options in the build.prop, like in Krexus rom, but not helped.
In Krexus the quality looks like when we disabling hardware encoding in the player app in the newest CM roms. Very good picture, looks like in PC. (but on this rom the hw encoding working).
Yesterday tried the lastest MIUI 8 MM rom, the quality as in other CM-s, but the seeking (stepping?) is very fast, at the moment playing. Not buffering 3-4 sec and not stopped the playing like in other CM and AOSP based roms.
I contact with the Var's player devs and finally we came to the conclusion, it's a rom bug.
Anyone experienced this? Or if playing VR anyone could to check Krexus rom? I don't think it's a simple value problem in some files in the rom, maybe a codecs problem?
So the 2 problem what need to eliminating:
- Hardware decoding quality improve, like in the Krexus rom
- Seeking improvement, like in the lastest MIUI 8 MM dev rom.
If I don't know about this quality problem I would not even notice, but always when trying in new roms I'm goes back to Krexus.
I'm not a dev, so only the testing, and this is in above, what I could to do. If you have an idea and it's not comlicated I'm trying, testing the metode in newer CM rom if this will help a bit.
UPDATE:
Made a screenshot on the systems (check the hills and the licence plate on the car):
Left: CM13 / Right: Krexus old
[url=https://postimg.org/image/o0byvant9/]
[/URL]
Logcat
Yesterday I checked 9+ roms.
Working this Krexus (the oldest build 3, in the new similar the problem). TheStrix CM14 build and a really old MIUI rom.
Not working: All CM13 and AOSP builds and similar modded roms, like Resurrection, Slim, Nexus Exp, Qualcomm AOSP, Exodus, Santhosh CM, Orion, DU, Temasek, iZi etc. On iZi the gyro not working in the app.
Any solution devs? Thanks.
Rom's which working good for VR, sharp image etc.
[ROM][CAF][23/10] halogenOS 7 for Redmi Note 3 [0.5-beta] - used the 0.5 beta release
[30/10/2016]CyanogenMod 14.0/14.1 for Xiaomi Redmi Note 3 - used the 30/10/2016 release
[ROM][LAYERS][KENZO] Krexus-CAF 6.0.1 (MMB29M) used the build3 (20160626) release
[CAF][1/16] [UNOFFICIAL] [halogenOS 7.0] [Kenzo] [VOLTE] by @rocknegi (first release - 2017/01/15)
On Androiddevs @Santhosh M ALL RR Nougat release (latest: 2017/01/17) !!
I didn't notice any difference from MIUI 7.x.x.x to 8.x.x.x to CM13 to CM14.
I think it's your brain making you to think that it's blurred, I had this exact problem with my brain when I first tried VR on my Redmi Note 3. I currently have ANT VR (which comes bundled with Lenovo K4 Note but I bought it seperately) and have no problems with it.
superboy123 said:
I didn't notice any difference from MIUI 7.x.x.x to 8.x.x.x to CM13 to CM14.
I think it's your brain making you to think that it's blurred, I had this exact problem with my brain when I first tried VR on my Redmi Note 3. I currently have ANT VR (which comes bundled with Lenovo K4 Note but I bought it seperately) and have no problems with it.
Click to expand...
Click to collapse
Only some older MIUI builds working good with this higher quality. That's why I tested the roms. On the picture is visible the difference (two system, cropped and merged the two screenshot) and from now it's not a brain trick. I'm using VR more than one year, making and editing videos, so have a difference with that.
If check the original channel VR official videos, on SBS 180 and SOS 180 videos have this issue with HEVC, but also see the differences on H264 . If only check youtube and simple 360 video the quality is very similar. So it's a codec problem I think. Btw thanks if you could help with the logs, which cause this affects thanks again
I will compare old MIUI and latest CM13 by flashing them and will tell you the results as soon as possible!
Looking more into this, keep this update cause i just bough xiami VR, and i'm interested to know wich rom is better etc, Using umang unofficial cm13
superboy123 said:
I will compare old MIUI and latest CM13 by flashing them and will tell you the results as soon as possible!
Click to expand...
Click to collapse
I suggest compare with Krexus build 3, as the same, older base.
Yes, I feel huge difference between krexus build 3 and CM13. looks like gpu does not render vr graphic well.
Hey @Steve1207, this is some great debugging, and much more that I'd be able to do to help you, kudos. I have no idea, right now, what could be the culprit. I noticed though that you found the some problem in a newer Krexus-CAF build VS an older one? If this is the case, we could go through the changes in my repos and find out what broke it.
So, the logcats of the working vs the non-working krexus-caf might be helpful, and the changelogs (/system/etc/changelog.txt) of the two ROMs.
KreAch3R said:
Hey @Steve1207, this is some great debugging, and much more that I'd be able to do to help you, kudos. I have no idea, right now, what could be the culprit. I noticed though that you found the some problem in a newer Krexus-CAF build VS an older one? If this is the case, we could go through the changes in my repos and find out what broke it.
So, the logcats of the working vs the non-working krexus-caf might be helpful, and the changelogs (/system/etc/changelog.txt) of the two ROMs.
Click to expand...
Click to collapse
Hello @KreAch3R, I upload the changelogs and the logcat about the last builded krexus (renamed the files for the easier recognition). Hope you found what couse this problem. Thank your help!
Steve1207 said:
Hello @KreAch3R, I upload the changelogs and the logcat about the last builded krexus (renamed the files for the easier recognition). Hope you found what couse this problem. Thank your help!
Click to expand...
Click to collapse
I took a look at the logcats. What I found was, that both cm13 and krexus-wrong build (the ones that don't work) use this driver:
10-09 15:57:32.843 I/Adreno (1223): QUALCOMM build : 2d489f5, I74772a33ad
10-09 15:57:32.843 I/Adreno (1223): Build Date : 08/04/16
10-09 15:57:32.843 I/Adreno (1223): OpenGL ES Shader Compiler Version: XE031.07.00.00
10-09 15:57:32.843 I/Adreno (1223): Local Branch : mybranch21158950
10-09 15:57:32.843 I/Adreno (1223): Remote Branch : quic/LA.BR.1.3.4_rb1.17
10-09 15:57:32.843 I/Adreno (1223): Remote Branch : NONE
10-09 15:57:32.843 I/Adreno (1223): Reconstruct Branch : NOTHING
Click to expand...
Click to collapse
While the only working krexus build uses this driver:
10-09 15:48:34.033 I/Adreno (9424): QUALCOMM build : 4ad80b1, Ibc10b8cc61
10-09 15:48:34.033 I/Adreno (9424): Build Date : 04/14/16
10-09 15:48:34.033 I/Adreno (9424): OpenGL ES Shader Compiler Version: XE031.06.00.02
10-09 15:48:34.033 I/Adreno (9424): Local Branch : mybranch19231206
10-09 15:48:34.033 I/Adreno (9424): Remote Branch : quic/LA.BR.1.3.3_rb2.15
10-09 15:48:34.033 I/Adreno (9424): Remote Branch : NONE
10-09 15:48:34.033 I/Adreno (9424): Reconstruct Branch : NOTHING
Click to expand...
Click to collapse
The changelog seems to agree with me, as you the dates make me assume that this commit is included in the broken build.
So maybe, what you can do is, try to grab all adreno libs from the working krexus, put them into another ROM and see if they work
I gave up for today. Made a flashable pack with the old libs, but dosn't work or when booting with other rom don't change the quality. But I'm trying again tomorrow, now search and read about this libs. Thanks your help @KreAch3R, I think helped a lot for the Kenzo developers with this, maybe someone fix this!
I just stopped using VR!
After trying MIUI and Krexus, CM's VR quality is so bad that I refuse to use VR glass.
UP
Hey all! Any news on this? I'm on miui 8 and was thinking about moving to cm based but now you guys are changing my mind.. I dont wanna lose vr for this, even though I dislike miui. Well, lets hope someone fix it. What about asking in their specific rom thread?
What about that krexus version that has good quality? Does it has any bug? Its safe for daily use?
Vr is not that popular so almost no one cares about development. Lets hope draydream changes that!
Steve1207 said:
UP
Click to expand...
Click to collapse
Hey bro does it fixed by that old adreno blobs? im in Miui 8 MM global beta does Miui 8 MM have also quality issues???
Not any news guys. I'll test the CM14 builds today, now looks like it's pretty stable as I read the threads.
Nice! Please report back to us any news. I moved to RR cm13 rom yesterday and did a little testing with my vr box 2, I actualy saw some improvement, in Miui 8 there was a lot of distortion, it's gone now, the quality still not good, haven't tested with old miui to tell the difference. What I noted is that performance is not that good in games anymore, there was some problems with fps, do you guys know what caused that ? I'm on raidon 3.9 kernel, default settings.
In case the problem for you guys is related to what looks like the two screens being misaligned, I might have a fix. I had the same, and read somewhere to try setting up the phone using qr codes for different viewers through the google cardboard app. It worked for me with a setup by someone called José Francisco. I will try to find the same page again, but for now, just try different setups.
EDIT: It seems that youtube and browser do not work for me. The google web asks me to fill in PPI because it can't detect it. could it be some apps are not able to detect the PPI?
V-incent said:
In case the problem for you guys is related to what looks like the two screens being misaligned, I might have a fix. I had the same, and read somewhere to try setting up the phone using qr codes for different viewers through the google cardboard app. It worked for me with a setup by someone called José Francisco. I will try to find the same page again, but for now, just try different setups.
EDIT: It seems that youtube and browser do not work for me. The google web asks me to fill in PPI because it can't detect it. could it be some apps are not able to detect the PPI?
Click to expand...
Click to collapse
Yep, I was having a bad experience in miui and a terrible one in cm, but I just figured some way to improve, those chinese vrs are a pain, there is no documentation, the solution is to create your own QR Code. It's actualy pretty simple, here is the link https://vr.google.com/cardboard/viewerprofilegenerator/
Send the link through a qr viewer or copy the address into the phone, now your pc and phone are connected, put ur phone in vr and test those configurations. That fixed most problems for me today.
PS: google web ou mention is the qr generator ? It always ask for ppi. There was one qr that I tried one time that bugged my youtube too in VR. Best option isto create your own.
Related
Optimized CyanogenMod 12 Android 5.0.2 Lollipop for the Redmi Note 4G(QCOM) brought to you by haoyangw
NOTE: This is for the QCOM variant of the Redmi Note, otherwise known as Redmi Note 4G, and NOT the MTK variant of the Redmi Note. In short, this ROM will NOT work on the MTK variant of Redmi Note 4G
NOTE: GApps is NOT provided, use any GApps package you can find. I would recommend Open GApps for Lollipop(link below).
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We're 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 us for messing up your device, we will laugh at you.
*
*/
Version Number explanation is in the #2 post, changelog and device tree branches for my github repositories explanation is listed in the #3 post
Comment your reviews below or even better, PM me as I won't be regularly monitoring this thread. Thanks again! You will be listed in the credits too
Downloads
ROMs
All ScarletRice builds and addons(AndroidFileHost)
All ScarletRice builds and addons(BasketBuild)
ScarletRice selected builds and addons(XDA)
I don't have the time to link specific builds everytime there is a new one anymore, so unfortunately you all have to go into XDA downloads or AndroidFileHost folder and download the latest one. So sorry!
Recoveries(compiled by me )
CWM, Philz touch and twrp recoveries(AndroidFIleHost)
Addons(includes my custom kernels So keep an eye on it)
Addons(AndroidFileHost)
Addons(BasketBuild)
XDA Downloads(Addons and ROMs)
Older downloads:
ScarletRice Beta 0.1
ScarletRice Alpha 0.02: https://mega.co.nz/#!40cXxKQL!Dd-pk41oJOPJbhLILLGnS9yAE09ly6nKIIfgRzLCpak
ScarletRice Beta 0.1 AndroidFileHost mirror
ScarletRice Alpha 0.01: https://mega.co.nz/#!EgN1lIxY!n7f-o9bujoh6eAu0H8iuaiiGrQ1fG3OCxYoodAyuLSA
The battery life so far on this ROM is amazing! It doesn't face any kind of drain issues so far, except maybe for the infamous Google Play Services wakelocks. To quote:
Swordsman0815 said:
Battery life seems to be amazing... I am off the charger for over 12hrs and still have around 46% of charge left
Click to expand...
Click to collapse
Well good/bad battery life is actually really subjective, some people might have higher standards due to their past experience etc so it all depends! Try it out yourself and see
Not working:
Cast screen/Screen mirroring
FM Radio
Compass
Back Camera and front camera video Fixed now
Buggy power detection Fixed
Flashing red borders(chrome only) Fixed
Working:
Back and Front camera(video + photo)(wipe dalvik if doesn't work)
Wifi
Headphones
Touch
Auto brightness
Gyroscope
Alarms
Location
Double tap 2 wake(built into ROM zip's kernel and my custom kernels) Removed due to bugs
Anything else
Installation
Download the ROM from the link above
Download GApps package for Lollipop(Recommended: OpenGapps, for 4.4+ and all architectures)
Download any addons/custom kernels from links above or anywhere else
Put the zip files on your SDCard
Reboot in Recovery(choose one of the 3 above if you wish )
Wipe Data / Factory Reset(ONLY IF you are coming from another ROM/upgrading to beta 0.2.x to get working camera)
Recommended: Wipe dalvik-cache
Select "Install zip from SDCard"
Choose CM12 zip file
Select "Install zip from SDCard"
Choose GApps zip file
Optional: Select "Install zip from SDCard"
Optional: Choose addon/kernel zip
Reboot system
Reporting bugs
If you have found a bug, make sure you fill up a form here: Google Form: Bug reporting This allows me to easily track all bugs reported without scanning the whole thread. Do make SURE that you fill in a VERY detailed description! And don't forget logs! For a tutorial on how to get logs, here you go! Log tutorial Of course, feel free to still report bugs here as I will be monitoring this thread But you MUST fill up a form, reporting on XDA is optional
Sources
Manifest
For those who would like a shortcut to sync all the neccessary repos to build stable cm12, just download/copy the contents of this file into .repo/local_manifest: Local manifest xml and the next time you repo sync everything will be there Then just 'lunch cm_dior-userdebug' and 'make -j4 otapackage'
Manually
I've finally given up making my own trees and fixing the annoying bugs in Xiaomi's kernel sources, so here are all the working tree/sources brought to you by our awesome devs! I take no credit for this! GO AND THANK THEM!
Edit: I've made some minor updates and fixes to the trees, but still credit goes to them!
Updated trees(updated by me but originally created by the following devs)
Device tree
Kernel source
Vendor tree(a.k.a. prebuilt/proprietary blobs tree)
Original trees:
@Silesh.Nair's device tree
@Silesh.Nair's vendor tree
@audahadi's kernel source
@stane1983's kernel source
I've uploaded the device tree I used to compile twrp to my device tree above, the branch name is 'twrp'. It's based on syhost's outdated twrp device tree, with problematic flags removed to fix bugs and also translated back into english, so there you go!
NOTE: Currently this device tree is ONLY for compiling CM12, you can face all kinds of build errors if you compile CM11 with it. For example, you will not be able to compile sepolicy in the device tree. You have been warned. Have fun building
Credits
CyanogenMod
XDA
syhost(for his twrp device tree)
Stane1983(for his first working trees)
Silesh.Nair(for his updated trees)
sm_94(for his suggestions on fixes)
And everyone else who contributed logcats and findings and worked hard for the better of all Note 4G users. Thanks!
XDA:DevDB Information
ScarletRice, ROM for the Xiaomi Redmi Note
Contributors
haoyangw
Silesh.Nair
sm_94
stane1983
sadlmadl(Contributed best and most logs and reports)
Swordsman0815(Contribute working/not working reports and logs )
@suhasgta(contributed logs, suggestions and reports )
And all others who contributed logs and reports! Thanks A LOT!
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Stable
Created 2015-03-17
Last Updated 2015-11-29
Version numbers
Version Number explanation
There will be 4 naming conventions for builds, namely Alpha, Beta, Release Candidate and Stable.
Alpha - Build is NOT tested and may not boot
Beta - Build has been tested and boots up, but there are many device-related issues and bugs
Release Candidate, or RC - Build has been tested and device-related issues and most bugs are fixed
Stable - No more than 3 minor bugs and no performance or battery drain issues(caused by ROM on my side)
Changelog + Github Repos' Branches
Changelog:
1.0
Device:
Fixed front and back camera(photo+video) as well as video playback
ROM:
Optimized with O3 and graphite
Enabled optimizing compiler for ART
Kernel:
Added more cpu governors(total 23)
Added gamma control
Added faux sound control
Added alucard and intelli hotplug
Compiled with O2
Maybe more(can't remember)
0.2.4
Device:
Merged changes from sileshn
Fixed some more webview problems(that were not caused by the previous absence of webview completely)
Added FM blobs, FM radio should work properly now (also means you'll need my new local manifest to sync qcom's fm stuff)
Tweaked media configs, hopefully improves some stuff(but playing youtube videos and the like still not working )
0.2.3.1
ROM:
Fixed superuser
Device:
Fixed google play store crashes
Tweaked button brightness, hopefully it isn't too bright nor dim
Old builds' changelogs:
0.2.3
ROM:
Compiled with user instead of eng, should result in increased performance!
Fixed performance issues! Now it's faster than syhost's cm12.1! You know what that means? if we build for cm12.1, then bam, performance will be faster than a rocket! And did I mention Justarchi optimizations and graphite flags?
Many vulnerability fixes like the new Serialization vulnerability
Device:
Bright button lights should now be fixed No light at all Sorry!
Location should be working properly now, without relying on Xiaomi's partners like Qualcomm
Fixed annoying flashing red borders ONCE AND FOR ALL!
0.2.2
Clean install(i.e. with factory reset required for working front camera)
ROM:
Fix Gapps problems(e.g. Play store and google keyboard crashes) by removing system jar compression tweak
Improved performance a little
0.2.1
ROM:
Fix prebuilt WebView that caused browser crashes
Add some missing blobs to increase performance
0.2.0
ROM:
Integrate home button fix
Upstream fixes(most notably stagefright vulnerability fix)
Use prebuilt WebView
System jars 0 compression(store only), but causes problems
Add Open Camera as system app
0.1
ROM:
Finally boots
Fix front camera
Device:
Use Silesh.Nair's device tree to fix problems and make ROM boot
Custom kernel:
V1.2.4:
Updated intelliactive and intellidemand to faux's latest sources, no longer using some outdated files that I got because of laziness So intelliactive is finally working properly(no reboot), and also better performance/battery etc
Added intelli hotplug driver, do check it out!
Updated simple and simpleondemand gpu governors, but they still don't work So do AVOID them!
V1:
Add intelliactive and smartmax governors
Add SIO and ZEN I/O schedulers
Experimental fix for back camera
Github Repository Branch Explanations:
Kernel source repo
cm-12.0: stock cm12 kernel without extra governors and I/O schedulers
cm-12.0-custom: CM12 custom kernel with extra governors and I/O schedulers
stock: Original kernel source from Xiaomi with only fixes for compilation errors
cm-12.0-wip: latest fixes/additions for cm12 that may not work/compile successfully
Upcoming(when it appears on the kernel source repo, cm12.1 is coming ):
cm-12.1: CM12.1 custom kernel with extra governors and I/O schedulers
cm-12.1-custom: stock cm12.1 kernel without extra governors and I/O schedulers
wip-cm12.1: latest fixes/additions for cm12.1 that may not work/compile successfully
Hi, I tried your rom just now on my Redmi Note 4G but it doesn't boot at all.
I wouldn't mind being a tester! I'm installing now and I'll see how it works.
fix
what about camera. fixed or not yet
It's stuck on the MI boot screen.
Finaly
thanks haoyangw for this thread. I would to participate but I just a noob and don't have skill about devs . I just follow and subscribe this thread, hope you can fix any problem about this devices. :good:
i can also help testing,i have min knowledge about what a rom is and logcat.
robreyes07 said:
Hi, I tried your rom just now on my Redmi Note 4G but it doesn't boot at all.
Click to expand...
Click to collapse
Hi, can you send me a logcat please? Or install LiveBoot by ChainFire through recovery and post all the errors you see printed. Thanks a lot! Sorry if the ROM doesn't boot
Good to see someone is working on CM12 for our phone. I tried CM12 syhost version and it's awesome but camera doesn't work and I need it. If you manage to get camera to work that would be awesome.
Thanks for your work. You may want to check the source code for the official cm12 version of the htc desire 816. It has the same gpu/cpu combination so there must be some similarities.
What is the point of this thread when the rom doesn't even boot
i think,
shyampareek said:
What is the point of this thread when the rom doesn't even boot
Click to expand...
Click to collapse
I didn't know but i hv subscribe
shyampareek said:
What is the point of this thread when the rom doesn't even boot
Click to expand...
Click to collapse
The point is to encourage someone to work on device. Right now it gathers little to no interest at all.
shyampareek said:
What is the point of this thread when the ROM doesn't even boot
Click to expand...
Click to collapse
Point is to give support to developer, or this thread will die. I think u shouldn't be on this forum, so ungrateful
haoyangw said:
Hi, can you send me a logcat please? Or install LiveBoot by ChainFire through recovery and post all the errors you see printed. Thanks a lot! Sorry if the ROM doesn't boot
Click to expand...
Click to collapse
Sure, maybe this weekend kind of busy this workdays.
robreyes07 said:
Hi, I tried your rom just now on my Redmi Note 4G but it doesn't boot at all.
Click to expand...
Click to collapse
Nemado said:
Thanks for your work. You may want to check the source code for the official cm12 version of the htc desire 816. It has the same gpu/cpu combination so there must be some similarities.
Click to expand...
Click to collapse
Yeah I thought of that, I copied some bits from the desire 816 device tree for Redmi Note 4G. I've tried building recovery with my sources and device tree and the recovery works perfectly, so I think it must be something in the ROM that is the problem. I'll need a logcat for tracking the malfunctioning part.
robreyes07 said:
Sure, maybe this weekend kind of busy this workdays.
Click to expand...
Click to collapse
Thanks a lot! Hope I can get this ROM working soon, then our beloved device will get Lollipop sweetness.
Have you tried to compile kernel that xiaomi relased for our device?
Lineage/CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
Lineage/CyanogenMod 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. You will need to provide your own Google Applications package (gapps). Lineage/CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Important information:
This thread is for Unofficial Lineage/CyanogenMod 13.0 builds for picassowifi/n2awifi (SM-T520). The following will not be supported here:
Custom kernels
Mods
Xposed
I don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Installation
First time flashing Lineage/CyanogenMod 13.0 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash Lineage/CyanogenMod
Install the Google Apps addon package (Optional)
Reboot
Other issues?
Before posting in this thread, make sure of a few things:
You used the search function of the forums.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread.
Logs! You can use this: https://play.google.com/store/apps/d....tortel.syslog
Downloads
Lineage:
2017/01/14 build
CyanogenMod:
2016/12/30 build
2016/11/5 build
2016/10/9 build
2016/9/22 build
Changelog:
2017/01/14
migrate from CM to Lineage (better chance to upgrade to CM14.1 soon)
Info: OK-Google/MIC should work. (please feedback!)
2016/12/30
Change to exynos common tree sources (chance to upgrade to CM14.1)
Support of "Deathly Adiutor"
Info: OK-Google/MIC broken!
2016/11/05
Nightly without specific changelog. Just latest sources used.
2016/10/09
IR Blaster fixed
Mic fixed
2016/9/22
Initial Release
Google Apps:
http://opengapps.org/- thanks to the OpenGapps team!
The Lineage/CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Source:
Kernel: https://github.com/exynos5420/android_kernel_samsung_exynos5420
Device Tree: https://github.com/exynos5420/android_device_samsung_n2awifi
Credits:
@UpInTheAir for his kernel magic and misc fixes
@crpalmer (for picassowifi device and kernel gits)
@eousphoros (for his work on klimtwifi)
@nvertigo67 (for his work on chagallwifi)
@Nexorrr (for his work on chagalllte)
@LaCruz (For testing my builds on device)
Exynos5420 Dev Team (@deadman96385 @thompatry @ZakooZ @Orion116 @mosimchah @joshndroid @Andmoreagain @thermskin, @javelinanddart )
@awidawad for his first picassowifi builds
XDA:DevDB Information
[6.0.x|SM-T520| Unofficial Lineage/CyanogenMod 13.0 (n2awifi), ROM for the Samsung Galaxy Tab Pro 12.2, 10.1, 8.4
Contributors
deadman96385, LaCruz
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Created 2016-09-22
Last Updated 2017-01-14
Bugs:
None at this time
Hybrid Build:
I have completely replaced all of the proprietary blobs that were from n2awifi (SM-T520) and replaced them with those from n1awifi (SM-P600). It is pretty much your sister tablet the only differences is it has a different screen that supports the s-pen. Internally they are exactly the same. Crucially it also got official Lollipop which your tablet did not. This build is also now using the M kernel base designed for the Galaxy Tab S this allows it to get the latest kernel updates and drivers.
Kernel Info:
M Kernel base from the Galaxy Tab S
M GPU driver from Galaxy Tab S
CPU Voltage Control
CPU OverClock/UnderClock (Up to 2.1GHZ)
MIF/INT Voltage Control
Wolfson Sound Control (No Yamaha support)
UKSM instead of KSM
Added the following IO Schedulers: fifo, fiops, sioplus, tripndroid, vr, zen, bfq (Default)
Full f2fs support updated off the mainline (Stock cm kernel has limited support)
Modified Thermal Throttling temperatures for all devices so hopefully they won't get as hot
Exynos thermal exposed to sysfs
Android Logger disabled by default can be enabled over sysfs
WQ power efficient workqueues (Still need to apply in more places)
Frandom Support
Readahead bumped to 256 from 128
Currently Disabled:
GPU Voltage Control/GPU OverClock/UnderClock (Needs to be rewriten for the M driver)
Mine just in case
Thanks! Will try soon!
Working really great thanks! A good surprise as it seems everything is working. Even the glitches in recent menu are fixed. Kernel is doing good job.
You've done a huge step for this tablet development ...totally unexpected
I Will use it as daily driver and will signal any issue if encountered
Sent from my SM-T520 using XDA-Developers mobile app
Working great.
Camera and gps active!
Thanks a lot for this rom.
OMG thank you! will try it later
sys log - playstore
working in this case or needed Logcat from adb & fastboot ? (ty & sorry for english)
works great, thanks
daitalos said:
working in this case or needed Logcat from adb & fastboot ? (ty & sorry for english)
Click to expand...
Click to collapse
It doesn't need anything! Flash ROM and gapps in twrp nothing else
Sent from my SM-T520 using XDA-Developers mobile app
man for Logcat I asked
Cosmox_ said:
It doesn't need anything! Flash ROM and gapps in twrp nothing else
Sent from my SM-T520 using XDA-Developers mobile app
Click to expand...
Click to collapse
No for how flashed this ROM...
Very nice work!
daitalos said:
working in this case or needed Logcat from adb & fastboot ? (ty & sorry for english)
Click to expand...
Click to collapse
Camera, gps ,wifi ,sd,bluetooth,adb,all working correct,only sometimes some app closed.... ( I have big problem to upload files,maybe my router, I hope be arrived correctly the Logcat) Ty & sorry for english :good:
Great ROM - camera GPS all working.
Had problem with MIC - not sure if working. OK Google does not response (worked on other version of CM13). Tried voice recorder and file was blank
same problem here
DAVECGC said:
Great ROM - camera GPS all working.
Had problem with MIC - not sure if working. OK Google does not response (worked on other version of CM13). Tried voice recorder and file was blank
Click to expand...
Click to collapse
with Ok google...opens,but is not responding...
A thing of beauty - everything I've tested working, no more random brightness fluctuations.
So, how soon do we get CM14?
(I kid, I kid!! No ETAs, I know)
Sent from my SM-T520 using XDA Premium HD app
I jumped ships from CM 12.1. First experiences are very positive, everything works as expected or better. I will report any stray bugs if found.
Thank you very much!
Will this work on picassowifi (SM-T520) or only n2awifi (SM-T520)? I never heard of n2awifi and the link I got to this page was from picassowifi cm13. Thanks!
WVUTampaAlum said:
Will this work on picassowifi (SM-T520) or only n2awifi (SM-T520)? I never heard of n2awifi and the link I got to this page was from picassowifi cm13. Thanks!
Click to expand...
Click to collapse
n2awifi is the proper name for picassowifi, picasso is from the qcom lte device.
Genesius01 said:
A thing of beauty - everything I've tested working, no more random brightness fluctuations.
So, how soon do we get CM14?
(I kid, I kid!! No ETAs, I know)
Sent from my SM-T520 using XDA Premium HD app
Click to expand...
Click to collapse
Well cm-14.0 is mostly working on n1awifi, once its most things are working i will release a build of it
daitalos said:
with Ok google...opens,but is not responding...
Click to expand...
Click to collapse
DAVECGC said:
Great ROM - camera GPS all working.
Had problem with MIC - not sure if working. OK Google does not response (worked on other version of CM13). Tried voice recorder and file was blank
Click to expand...
Click to collapse
Can you post a log of when you are trying to use ok google?
daitalos said:
Camera, gps ,wifi ,all working correct,only sometimes some app closed.... ( I have big problem to upload files,maybe my router, I hope be arrived correctly the Logcat) Ty & sorry for english :good:
Click to expand...
Click to collapse
What apps are forcing closing also are they force closing while you are doing certain things?
some times ..
I am on playstore and i want to Install a app...Touch screen does not respond & says "app does not respond" & closing...After reboot working correct again...This happens only in playstore ( i hope understand me my english is not good) I sent you before Logcat, i think has records this ( if you want I can sent you & another Logcat if it happens again) Ty ( I use nano gapps perhaps i will try & with mini) and google now from any screen display options but not working (see screenshot) [ I got another dmseg & Logcat from fastboot perhaps to help you ] :good:
This. rom. is. awesome!
Thank you! Everything is working so smoothly and without problems so far. best rom ever!
Hello guys,
i am looking for some custom rom for my x910 leeco.
Could i use maybe lineage os, z2 for that?
Heyyo, unfortunately there is no LineageOS build for x910 that I know of.
I am attempting to bring custom ROM support to the x910 but I haven't had any success yet... There's a chance that the kernel source code of the Le Max 2 and Le Pro3 is incomplete for the x910 so it might not be possible but I'm still trying a few things... I'll let you know if I somehow have a breakthrough.
ThE_MarD said:
Heyyo, unfortunately there is no LineageOS build for x910 that I know of.
I am attempting to bring custom ROM support to the x910 but I haven't had any success yet... There's a chance that the kernel source code of the Le Max 2 and Le Pro3 is incomplete for the x910 so it might not be possible but I'm still trying a few things... I'll let you know if I somehow have a breakthrough.
Click to expand...
Click to collapse
any update ?
Cateye said:
any update ?
Click to expand...
Click to collapse
Heyyo, sorry bud after lots of tweaking it seems that the kernel source code for x910 within the Le Max 2 and Le Pro3 is incomplete and I was unable to boot with a source built kernel... Says missing dts
ThE_MarD said:
Heyyo, sorry bud after lots of tweaking it seems that the kernel source code for x910 within the Le Max 2 and Le Pro3 is incomplete and I was unable to boot with a source built kernel... Says missing dts
Click to expand...
Click to collapse
Keep working please. We count on you.
ThE_MarD said:
Heyyo, sorry bud after lots of tweaking it seems that the kernel source code for x910 within the Le Max 2 and Le Pro3 is incomplete and I was unable to boot with a source built kernel... Says missing dts
Click to expand...
Click to collapse
Hello @ThE_MarD. The source built kernel has 23 dtb files appended and all those are specific to Max2. There are about 10 dtb files for max_plus. Please append these back to source kernel and give a try, it should work. I traced my phone dtb from 130 dtbs of mm kernel, added fstabs, appended to the kernel, packed the image and it successfully downloaded to phone in fastboot. The phone display light glows bright once and stops there. Also same status when tried with latest twrp. This gives hope that the kernel will boot by using properly compiled image for 8.1 upgrade. Just give another try adding back max_plus specific dtb files.
xaakx said:
Hello @ThE_MarD. The source built kernel has 23 dtb files appended and all those are specific to Max2. There are about 10 dtb files for max_plus. Please append these back to source kernel and give a try, it should work. I traced my phone dtb from 130 dtbs of mm kernel, added fstabs, appended to the kernel, packed the image and it successfully downloaded to phone in fastboot. The phone display light glows bright once and stops there. Also same status when tried with latest twrp. This gives hope that the kernel will boot by using properly compiled image for 8.1 upgrade. Just give another try adding back max_plus specific dtb files.
Click to expand...
Click to collapse
Heyyo, can you please get me logcat from the start of the device booting? I've tried importing all 18 max_plus dts/dtsi files I saw in the kernel but that still didn't get it to boot.
https://github.com/LineageOsMaxPlus...mmit/7eb4dbf827bba4e05de2a802b6fc2b05741b04b9
Here's so far everything I've tried to do
https://github.com/LineageOsMaxPlus
I've been thinking of upgrading my nearly 2 year old x910 since I've been stuck on this hacked chinese rom version of android 6.0.1 (Kernel version 3.18.20 from April 29, 2016). Apps are starting to crash or drain battery, etc
Is there anything I can do? I know X910 was some sort of engineering sample run and never mass sold. I was lucky enough to find one on aliexpress for about $280 2 years ago. Been a great phone but Android 6 is killin me now.
Heyyo @gozef14 @Cateye @sean_han @xaakx and @LxMxFxD
Please try this! I think I got the kernel dts files solved and properly appending!
https://forum.xda-developers.com/le-max-2/development/twrp-leeco-le-max-pro-t3901466
---------- Post added at 06:30 PM ---------- Previous post was at 06:30 PM ----------
Heyyo @gozef14 @Cateye @sean_han @xaakx and @LxMxFxD
Please try this! I think I got the kernel dts files solved and properly appending!
https://forum.xda-developers.com/le-max-2/development/twrp-leeco-le-max-pro-t3901466
ThE_MarD said:
Heyyo @[email protected]@[email protected] and @LxMxFxD
Please try this! I think I got the kernel dts files solved and properly appending!
https://forum.xda-developers.com/le-max-2/development/twrp-leeco-le-max-pro-t3901466
---------- Post added at 06:30 PM ---------- Previous post was at 06:30 PM ----------
Heyyo @[email protected]@[email protected] and @LxMxFxD
Please try this! I think I got the kernel dts files solved and properly appending!
https://forum.xda-developers.com/le-max-2/development/twrp-leeco-le-max-pro-t3901466
Click to expand...
Click to collapse
Thanks @ThE_MarD. It's successfully booted. All working fine except little lag.
xaakx said:
Thanks @ThE_MarD. It's successfully booted. All working fine except little lag.
Click to expand...
Click to collapse
Sweet! :good:
I do have LineageOS 16.0 booting on max_plus, but it also is laggy. I need to figure out how to fix the dsi panel files for...
dsi-panel-sharp-dualmipi-cmd.dtsi
As they keep spitting out logcat errors for "wait for pingpong failed" in logcat...
https://youtu.be/TYfFmDjOQnk
Hello sir
A noob here with x910
Please tell us that should we hope for a stable custom rom on this device like we have on le max 2?
Heyyo @King Ibsd , I am still trying to work on it! :good:
I do have unified builds with X2 working, so that part is good to go! Just need to resolve this panel issue hmm...
I forgot to mention this earlier... But if you're really interested in trying experimental max_plus unified with X2 builds? The last few builds I've posted in the X2 thread are unified with max_plus... But be warned, it has serious video lag as noted in that YouTube link up above.
There is a chance your max_plus has a blank devinfo block which isn't good as we check that for many things on custom ROMs.
If yours is blank? Please flash this via TWRP to correct it to max_plus.
https://drive.google.com/file/d/0B7RnSWm3LBorZ1NzNmtrcmNlV1ZzZ3U0WFdWQnF4bXB0Sm80/view?usp=drivesdk
Hmm, I think the signed graphics firmware I was given for max_plus is REALLY out of date and could be the reason for the video lag...
Can someone here please link me the latest version of EUI ROM that works for max_plus?
ThE_MarD said:
Can someone here please link me the latest version of EUI ROM that works for max_plus?
Click to expand...
Click to collapse
Do you still need it? Since you wrote "For max_plus users? I have noticed that compared to the dsi-dualmipi-sharp-cmd of the x2? It lacks the pingpong-split config and the timings are off a bit... So hopefully adjusting both of those for max_plus helps with the video lag". If yes, I might be able to find it.
Palm Trees said:
Do you still need it? Since you wrote "For max_plus users? I have noticed that compared to the dsi-dualmipi-sharp-cmd of the x2? It lacks the pingpong-split config and the timings are off a bit... So hopefully adjusting both of those for max_plus helps with the video lag". If yes, I might be able to find it.
Click to expand...
Click to collapse
Heyyo Palm Trees, yes I would like to have it please. Preferably an Official build for max_plus, as I want to compare the kernel dtb to the dts files I have. Same for the vendor blobs and device firmware. I've seen a 26s build but it seems to be hacked together from some of the 13s firmware but not all of it is max_plus and some of it is x2...
ThE_MarD said:
Heyyo Palm Trees, yes I would like to have it please. Preferably an Official build for max_plus, as I want to compare the kernel dtb to the dts files I have. Same for the vendor blobs and device firmware. I've seen a 26s build but it seems to be hacked together from some of the 13s firmware but not all of it is max_plus and some of it is x2...
Click to expand...
Click to collapse
Found the original Max Plus fastboot images. LeEco's naming convention has always been a bit special and it does seem like only 2 firmware versions were released with 5.6.013S (ro.letv.release.branch=MAX_PLUS_FINAL_SHIPPING_20160422_20160516_144606_MAX_PLUS.xml) being the latest and 5.5.169D being the build before that.
(5.6.013S) 乐视_letv-X910_EEXCNFN5601305161S-release-keys_6.0.1
Source: http://url88.cn/fXFA0O
Direct DL-link: http://rom.url88.cn/{3706186}_乐视_letv-X910_EEXCNFN5601305161S-release-keys_6.0.1.zip
ro.build.date=Mon May 16 16:39:58 CST 2016
ro.build.display.id=EEXCNFN5601305161S release-keys
ro.build.description=max_plus-user 6.0.1 EEXCNFN5601305161S eng.letv.20160516.163643 release-keys
ro.build.fingerprint=Letv/LeMaxPro_CN/max_plus:6.0.1/EEXCNFN5601305161S/letv05161638:user/release-keys
# BOOTIMAGE_BUILD_PROPERTIES
ro.bootimage.build.fingerprint=Letv/LeMaxPro_CN/max_plus:6.0.1/EEXCNFN5601305161S/letv05161638:user/release-keys
(5.5.169D) 乐视_X910_5.5.169D_6.0.1
Source: http://url88.cn/19aI6WA
Direct DL-link: http://rom.url88.cn/{3707560}_乐视_X910_5.5.169D_6.0.1.zip
ro.build.date=Thu Feb 25 02:32:50 CST 2016
ro.build.display.id=EEXCNFN5516902251D release-keys
ro.build.description=max_plus-user 6.0.1 EEXCNFN5516902251D eng.letv.20160225.022823 release-keys
ro.build.fingerprint=LeEco/LeMaxPro_CN/max_plus:6.0.1/EEXCNFN5516902251D/letv02250231:user/release-keys
# BOOTIMAGE_BUILD_PROPERTIES
ro.bootimage.build.fingerprint=LeEco/LeMaxPro_CN/max_plus:6.0.1/EEXCNFN5516902251D/letv02250231:user/release-keys
Palm Trees said:
Found the original Max Plus fastboot images. LeEco's naming convention has always been a bit special and it does seem like only 2 firmware versions were released with 5.6.013S (ro.letv.release.branch=MAX_PLUS_FINAL_SHIPPING_20160422_20160516_144606_MAX_PLUS.xml) being the latest and 5.5.169D being the build before that.
(5.6.013S) 乐视_letv-X910_EEXCNFN5601305161S-release-keys_6.0.1
Source: http://url88.cn/fXFA0O
Direct DL-link: http://rom.url88.cn/{3706186}_乐视_letv-X910_EEXCNFN5601305161S-release-keys_6.0.1.zip
ro.build.date=Mon May 16 16:39:58 CST 2016
ro.build.display.id=EEXCNFN5601305161S release-keys
ro.build.description=max_plus-user 6.0.1 EEXCNFN5601305161S eng.letv.20160516.163643 release-keys
ro.build.fingerprint=Letv/LeMaxPro_CN/max_plus:6.0.1/EEXCNFN5601305161S/letv05161638:user/release-keys
# BOOTIMAGE_BUILD_PROPERTIES
ro.bootimage.build.fingerprint=Letv/LeMaxPro_CN/max_plus:6.0.1/EEXCNFN5601305161S/letv05161638:user/release-keys
(5.5.169D) 乐视_X910_5.5.169D_6.0.1
Source: http://url88.cn/19aI6WA
Direct DL-link: http://rom.url88.cn/{3707560}_乐视_X910_5.5.169D_6.0.1.zip
ro.build.date=Thu Feb 25 02:32:50 CST 2016
ro.build.display.id=EEXCNFN5516902251D release-keys
ro.build.description=max_plus-user 6.0.1 EEXCNFN5516902251D eng.letv.20160225.022823 release-keys
ro.build.fingerprint=LeEco/LeMaxPro_CN/max_plus:6.0.1/EEXCNFN5516902251D/letv02250231:user/release-keys
# BOOTIMAGE_BUILD_PROPERTIES
ro.bootimage.build.fingerprint=LeEco/LeMaxPro_CN/max_plus:6.0.1/EEXCNFN5516902251D/letv02250231:user/release-keys
Click to expand...
Click to collapse
WOW DUDE! Thanks for this! It seems to be mostly correct from what I see too, albeit the NON-HLOS.bin shows the model as LeTv X900+ which I believe is the LeEco Le Max (1) but I guess if it works fine for X910 then good enough hehe.
I'll also be trying to compare the extracted dtb files from that 13S fastboot ROM to the reference CAF tag dtb of LA.HB.1.3.2-03800-8x96.0 which seems to be the base of all LeEco msm8996 kernel source code to see if I can figure out exactly what changes I need to port to the current kernel source code I have in order to fix this darn wait for pingpong error... :good:
ThE_MarD said:
WOW DUDE! Thanks for this! It seems to be mostly correct from what I see too, albeit the NON-HLOS.bin shows the model as LeTv X900+ which I believe is the LeEco Le Max (1) but I guess if it works fine for X910 then good enough hehe.
I'll also be trying to compare the extracted dtb files from that 13S fastboot ROM to the reference CAF tag dtb of LA.HB.1.3.2-03800-8x96.0 which seems to be the base of all LeEco msm8996 kernel source code to see if I can figure out exactly what changes I need to port to the current kernel source code I have in order to fix this darn wait for pingpong error... :good:
Click to expand...
Click to collapse
I collected the x900(乐视_X900)/x900+ (乐视_X900加)/Le Max fastboot images (all models are msm8994 "Snapdragon 810"). So I do believe LeEco was lazy when they created the msm8996 phones. As far as I can tell, LeEco was the first company (or one of the first) to use msm8996. So they might have said "Yeah well, let's move from msm8994 to msm8996 without changing stuff" in the NON-HLOS.bin.
If you want to compare the NON-HLOS.bin from the msm8994 phones with the other NON-HLOS.bin files from the msm8996 phones here are the links and descriptions:
1523500103_MAX1_X900 CN FN CEXCNFN5902803208S 5.9.028S //latest fw release (not fastboot images)
Source: http://bug.letv.com/cn/download/phone/32
Direct DL-link: http://ota.scloud.lfengmobile.com/ota/1523500103_MAX1_X900-CN-FN-CEXCNFN5902803208S-5.9.028S.zip
ro.letv.release.version=5.9.028S
ro.product.letv_model=Letv X900+
ro.build.version.release=6.0.1
ro.build.version.security_patch=2017-01-01
ro.build.date=Tue Mar 20 20:00:44 CST 2018
ro.product.model=X900
ro.product.brand=Letv
ro.product.name=max1
ro.product.device=max1
ro.product.board=msm8994
ro.build.fingerprint=Letv/max1/max1:6.0.1/CEXCNFN5902803208S/8:user/release-keys
# BOOTIMAGE_BUILD_PROPERTIES
ro.bootimage.build.date=Tue Mar 20 20:31:41 CST 2018
ro.bootimage.build.fingerprint=Letv/max1/max1:6.0.1/CEXCNFN5902803208S/8:user/test-keys
Geekbuying posted the Indian firmware. The .zip file and general description are incorrectly tagged. Nevertheless, it is in fact the Indian Le Max firmware for msm8994 based on Android L 5.0.2.
LETV X900 LE MAX PRO Snapdragon 820 Quad Core Android 5.1 Smartphone Firmware
Should be tagged something like this LeTV X900 5.5.014S 5.0.2
Source: http://blog.geekbuying.com/2017/08/...ore-android-5-1-smartphone-firmware-20170818/
DL-link:http://www.mediafire.com/file/h8276...oid+5.1+Smartphone+Firmware+-5.5.014S-5.0.zip (Password: geekbuying.com)
# begin build properties
ro.letv.product.info=Max1_r1148.5-5.0.2-userdebug_CHN-OPEN-Dev
ro.letv.release.branch=x1_stable_011_20160125
ro.letv.release.version=5.5.014S
ro.build.date=Sun May 22 03:29:13 CST 2016
ro.product.model=Le Max
ro.product.name=LeMax_WW
ro.product.device=max1_in
ro.product.board=msm8994
ro.build.fingerprint=Letv/LeMax_WW/max1_in:5.0.2/CHXOSOP5501405221S/154:user/release-keys
The Chinese firmware below is pretty much comparable except for a few differences in system.img (some apps are included/excluded). Unpacking the boot.img did show comparable ramdisks.
乐视_X900加-(64G)_5.5.009S（64G版本）_5.0.2.zip
Source:http://url88.cn/Jk9eBy
Direct DL-link:http://rom.url88.cn/{3705256}_乐视_X900加-(64G)_5.5.009S（64G版本）_5.0.2.zip
ro.letv.release.version=5.5.009S
ro.product.model=X900+
ro.build.date=Fri Dec 25 05:59:01 CST 2015
ro.product.brand=Letv
ro.product.name=LeMax_CN
ro.product.device=max1
ro.product.board=msm8994
ro.build.fingerprint=Letv/LeMax_CN/max1:5.0.2/CBXCNOP5500912251S/112:user/release-keys
乐视_X900（64G）_CBXCNOP5500912251S-release-keys_5.0.2.zip
Source:http://url88.cn/1a9Cpmr
Direct DL-link:http://rom.url88.cn/{3704883}_乐视_X900（64G）_CBXCNOP5500912251S-release-keys_5.0.2.zip
Letv/LeMax_CN/max1:5.0.2/CBXCNOP5500912251S/112:user/release-keys
ro.letv.release.version=5.5.009S
ro.product.model=X900
ro.build.date=Fri Dec 25 05:59:01 CST 2015
ro.product.brand=Letv
ro.product.name=LeMax_CN
ro.product.device=max1
ro.product.board=msm8994
ro.build.fingerprint=Letv/LeMax_CN/max1:5.0.2/CBXCNOP5500912251S/112:user/release-keys
ThE_MarD said:
Sweet! :good:
I do have LineageOS 16.0 booting on max_plus, but it also is laggy. I need to figure out how to fix the dsi panel files for...
dsi-panel-sharp-dualmipi-cmd.dtsi
As they keep spitting out logcat errors for "wait for pingpong failed" in logcat...
Video lag for the twrp is completely gone after adding few additional lines that were missing from maxplus device trees as compared to similar dsi panels of Max 2 in your test rom. Following are the additional lines for my device panel mdss_dsi_sharp_qhd_dualdsi_cmd from MSM 8996 v3 + PMI8994 LE_X2_NA-DVT1.1 which looks similar to my device tree dvt3.
qcom,mdss-mdp-transfer-time-us = <0x2710>;
qcom,ulps-enabled;
qcom,config-select = <0x2c>;
config0 {
qcom,split-mode = "pingpong-split";
linux,phandle = <0x2c>;
phandle = <0x2c>;
I couldnt add last two lines for phandle nodes as they are found else where as well. The most important line that fixed the lag of twrp is qcom,config-select = <0x2c> which looks specific to my device. I tried to boot the rom after flashing modified boot without those last two lines for phandle nodes, but the phone screen goes blank while booting. Interestingly, config select and phandle node values are same for pingpong split modes and they are in the range of 0x2a to 0x2f . Once you incorporate these lines with the appropriate pingpong split mode, hopefully the rom should work without any lag as well. Looking forward to next build soon....
Click to expand...
Click to collapse
{
"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
https://wiki.lineageos.org/devices/x2/install
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.5.0-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: Do a factory reset (clean wipe)! No support if you didn't! (Wipe Dalvik, system, cache and data)
- Flash firmware and LineageOS zips.
- Optional: Install the Google Apps addon package. (see Downloads)
- Reboot to system.
HOW TO UPGRADE LINEAGEOS FROM 16.0
Please follow the official LineageOS Wiki instructions for our device. You can use either TWRP or Lineage Recovery.
https://wiki.lineageos.org/devices/x2/upgrade
HOW TO UPDATE LINEAGEOS WITH LINEAGE RECOVERY
Please follow the official LineageOS Wiki instructions for our device
https://wiki.lineageos.org/devices/x2/upgrade
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/p16588
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 17.1: https://osdn.net/projects/lineageos-for-x2/releases/p16562
- Unofficial 17.0: https://osdn.net/projects/lineageos-for-x2/releases/p16488
GOOGLE APPS (GAPPS) DOWNLOADS
- Open GApps:
Please note! Open GApps ARM64 Pico and Nano are the only recommended ones.
Official: https://opengapps.org/
GOOGLE CAMERA (GCAM) DOWNLOADS
Google Camera:
https://www.celsoazevedo.com/files/android/google-camera/f/changelog1075/
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
https://github.com/lineage-x2-devs
https://github.com/LineageOsMaxPlus/
https://github.com/lineageos/android_device_leeco_msm8996-common
https://github.com/lineageos/android_device_leeco_x2
https://github.com/lineageos/android_kernel_leeco_msm8996
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 17.1 (Android 10) for LeEco Le Max 2, ROM for the LeEco Le Max 2
Contributors
ThE_MarD, mosimchah, Lucchetto00, codeworkx,moto999999,1nfrag,shivatejapeddi,KuranKaname,GalaticStryder,andr68rus,Tortel1210,visionary,zhaoguomanong
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: X820, X821, X822 and x829 466d. x910 13s.
Based On: AOSP
Version Information
Status: Nightly
Created 2019-11-16
Last Updated 2020-09-15
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.)
There is random performance hangs where apps may not be responsive for a few seconds (Android 10 issue???)
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
Latest update: 2020-05-04 (May 4, 2020)
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
@codeworkx for his major contributions to the LeEco msm8996-common code and kernel and the awesome open-source camera HAL
@mosimchah for his contributions to the LeEco msm8996-common code and kernel
@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.
@Tortel1210 for his contributions to x2 and helping out with gerrit.
@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!
@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!
@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
Thanks @ThE_MarD
You work hard for Lineage. :iyi:
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
@rberg (Robin Vd Berg since I'm unsure on username) for also also also also helping cover my replacement motherboard costs
@CrisBalGreece for his donation
@erwan574 for his donation
@txekalzen for his donation
I did receive some donations from individuals that wish to remain anonymous, so you know who you are and thank you fine LeEco community members too
(If I got your XDA forum usernames wrong please let me know)
Heyyo @Neutralite, thanks for the kind words. I do what I can, but for Android 10 special thanks definitely goes to @Lucchetto00 and @moshimchah for doing the initial bring up for x2 and zl1/0. I merely added onto the work they have already done and other msm8996 devs such as dd3boh on Zuk Z2 Plus and dianlujitao for the OnePlus 3 and Bruno Martins and LuK1337 on Xiaomi. :good:
Also, I fixed vulkan with our Q graphics stack. Luckily kanging from msm8953 CAF Q blobs and renaming and sed to msm8996 works perfectly fine for us. Slight improvement to vulkan, nothing major, maybe 1-2 frames per second or something as it is only minor upgrades for us.
http://vulkan.gpuinfo.org/compare.php?compare=compare&id%5B7313%5D=on&id%5B5019%5D=on
and again, this exciting los 17 journey has started for our lemax2....
Thanks man it means a lot for us.
I was using lineage os 16 and was eagerly waiting for 17 and you and other developers hard work made it possible for us.
I am grateful to you guys.
( PS - Now i use my x2 as a secondary device ie that i can do some beta testing for ROMs if needed. I will be so happy to get any opportunity to help for further development of our x2 and for our community. )
Thanks And Regards
Reetesh54
ThE_MarD said:
[X82X][9.x][TREBLE] LineageOS 17.0 (Android 10) for LeEco Le Max 2, ROM for the LeEco Le Max 2
Click to expand...
Click to collapse
Fantastic. I was looking for this yesterday evening having an inkling but did not find. Now I saw....
Thanks @ThE_MarD. BT in-call audio resolved?
Edit: Is it possible to "enable" disable option in cam app until crash issue is resolved?
the rom is perfect, vulkan makes the rom look great with the incredible fluidity in pub games, feet 2020, nba and others and runs the ppsspp gold emulator games very well with the gpu vulkan, really amazing, i used the black rom nougat 7.1.2 exactly because of vulkan, now I can use it on android 10, thanks. To say that I did not find any bugs, I found 1, which percentage of the battery that does not appear, the rest is perfect.
Heyyo @monleylord @Reetesh54 @fer198309 ! Thanks guys, yeah super stoked at how good LineageOS 17.0 is meow. :good:
@kayyappan , yes bluetooth audio HAL is fixed and that's why I made the thread.
I think you'd need a root app that scrubs system apps to disable it... that or a launcher that lets you hide the app.
New build is going up! lineage-17.0-20191117-UNOFFICIAL-x2 is only a minor update as the only fix is offline charging animation.
ThE_MarD said:
Heyyo
@kayyappan , yes bluetooth audio HAL is fixed and that's why I made the thread.
I think you'd need a root app that scrubs system apps to disable it... that or a launcher that lets you hide the app.
New build is going up! lineage-17.0-20191117-UNOFFICIAL-x2 is only a minor update as the only fix is offline charging animation.
Click to expand...
Click to collapse
You forgot your training for 17.0!?. Update next day? Thank you. No, I'll wait for you to resolve the cam issue. Glad BT fixed. QS battery settings doesn't change but that can wait. No emergency per se.
@ThE_MarD - landed in trouble with 11/17 update. Dirty install over 11/16 resulted in a different kind of boot loop. The device will boot up to unlock screen, swipe up and it will start all over with boot animation. Never comes out of that. Moving back 11/16 build now.
Edit: TWRP restore of 11/16 resulted in same status. No idea if 11/17 downloaded file is corrupt. I had to do a clean install including format data.
Nice and smooth upgrade with clean wipe and latest official TWRP / latest 30S firmware on a X820.
I confirm bluetooth audio is ok. I did not find the "SBC high bitrate" setting that was in LOS 16.
I installed latest Magisk with no pb after setup and google account restore.
I used latest "PMGC" camera and it seems a nice improvement too in performance.
GPS is ok for me.
Now I will wait for the battery usage graph, but everything seems ok for my usage.
I expect this LOS version to be used a few more years on my phone if nobody breaks it before.
Thanks !
kayyappan said:
@ThE_MarD - landed in trouble with 11/17 update. Dirty install over 11/16 resulted in a different kind of boot loop. The device will boot up to unlock screen, swipe up and it will start all over with boot animation. Never comes out of that. Moving back 11/16 build now.
Edit: TWRP restore of 11/16 resulted in same status. No idea if 11/17 downloaded file is corrupt. I had to do a clean install including format data.
Click to expand...
Click to collapse
This is an old problem of leeco max 2, you always have to remove the password before any update or restart, in which case you can delete the password by twrp no files, data, system and delete the lock, ready restarts without password there only register again.
fer198309 said:
This is an old problem of leeco max 2, you always have to remove the password before any update or restart, in which case you can delete the password by twrp no files, data, system and delete the lock, ready restarts without password there only register again.
Click to expand...
Click to collapse
That was one of the first things I did after installing 11/16. I had a pin, no fp. Removed soon. It was only swipe up. Anyway back on 11/16. Will try later 11/17. Now too on just swipe up. Thank you.
@kayyappan , hmm to be safe I did take that build down. Sorry if it didn't boot for you for some odd reason I guess as I was working for me. I haven't tested Quick Charge toggle yet and I don't have a QC 3.0 block with me as I'm out of town training still oops, so I guess I will try to look at that again later on I guess.
Heyyo @erwan574 , glad to hear you like it! Yeah SBC high bitrate isn't ready yet on LineageOS 17.0 so it is missing. GPS seems to be just as good as Pie which is nice since Pie was pretty snappy most of the time and a lot more accurate than it was on LineageOS 15.1.
Anywho, a new build is going up in 30 minutes from this post! lineage-17.0-20191118-UNOFFICIAL-x2 is with a fresh repo sync and some repopicks of LineageOS 17.0 with a bunch more changes merged (I'm not sure if they'll all be noticeable to us right away or not). Some stuff I was waiting on for libinit was merged on system/core so meow I've also started to merge more stuff on our LeEco msm8996 trees yay. I'm still waiting just a little bit longer on the CAF Q blobs we have right meow just in case there's still something that needs to be fixed there...
This build still has snap camera app crashes and doesn't work and selinux permissive. I might try to next work on some of our selinux denials to see what comes up and what I can fix to start working towards selinux enforcing again. Moshe said he will start working on a kernel rebase for Q CAF tag so that will be nice for us too. :good:
*edit* wow XDA keeps double-posting on me...
@ThE_MarD i think by mistake you named the thread [X82X][9.x] instead of [X82X][10.X] .
Just updated to lineage-17.0-20191118-UNOFFICIAL-x2 using TWRP, with magisk 20.1 installed.
no issue so far. The zip image is 66mb larger but for now I see no visible changes.
Battery usage of previous version seemed very good for me (deep sleep ok).
/*
* 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.
*
Click to expand...
Click to collapse
LineageOS is a free, community built, aftermarket firmware distribution of Android 12 (S), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Based on the Exynos7420 source code.
What's working:
Audio
Bluetooth
Telephony (Calls, SMS, Mobile Data)
WiFi/Hotspot
NFC
Camera
Fingerprint
HWC
GPS
What's not working:
VoLTE and other proprietary Samsung stuff
SELinux Permissive
You tell me
Download Link:
LineageOS Releases on my GitHub
Source Code:
https://github.com/samsungexynos7420/local_manifests/tree/lineage-19.1https://github.com/samsungexynos7420/android_kernel_samsung_universal7420/tree/lineage-19.1
ROM OS Version: 12.x S
ROM Kernel: Linux 3.10.108
Based On: LineageOS
Version Information:
Beta/Testing
ROM creation date: 23/08/2022
Last release: 07/05/2023
If you would like to support me, visit my donation page.
Thanks to:
TALU - various kernel patches used
html6405 and rinando - various lineageos patches used
enesuzun2002 - original exynos7420 source code, without him and his work, none of this would really be possible
Exynos7420/universal7420 contributors
Armash - help with fingerprint issues
Supported Devices:
G920F
G925F
FAQ:
I have echo in phone calls!
Echoing in calls has been a problem for Samsung devices for a long time. Not aware of a fix, but using some old mixer_paths tweaks, the problem can be mitigated somewhat
My banking/other apps arent working!
You need Magisk modules to pass safetynet. Some apps dont like to work if safetynet fails.
My camera wont flash properly when taking a picture
The native AOSP camera app does not properly sync the flash on a lot of Samsung devices. However, you can use third party camera applications, which do not exhibit this behaviour. GCam Go has been reported to work fine.
I have a problem not on this list!
Describe your problem in detail and steps to reproduce it. Take a logcat, kmesg, dmsg using syslog or other method and post here, or preferably an issue on GitHub. If you were able to fix the problem, please post how you were able to resolve it.
Changelog
Spoiler: Click for Changelog
07.05.2023
Synced with LineageOS sources (May '23 security patch)
Swapped to linaro BSP for some HWC components
Provides updated code for our device (better UI/performance)
Update precompiled OMX blobs (linaro ones dont work currently), modified to work in vendor/
Move most stuff to /vendor (finally)
Set minimum clock speed in non-power saver mode to 400MHz for A53 cores
GPU now looks for hi-speed load
Other misc kernel improvements
Update seccomp policies
Memfd legacy patches added (as we arent on kernel 3.18 or newer)
LPM kanged from 8890q
Misc changes to props
12.04.2023
You must perform a clean flash. Backup your data using your preferred method, or else you wont be able to unlock your device.Synced with LineageOS source (April 2023 security)
Reworked the HWC implementation - noticeable improvement to smoothness
All 7 layers are now working
More HWC components built from BSP source + extra flags
Using A810F Gatekeeper blobs - MDFPP implementation from software
Less random errors in logcat
Build fingerprints overridden to latest stock nougat ones
L3 widevine DRM support, some DRM content should work now
Zswap no longer built in the kernel. We don't need it.
In kernel low memory killer is no longer built
Fixed FIPS compilation
Default voltage offset of -37.5mV on the CPU
Upped sustained clock speeds hint in powerhints.json
22.02.2023
Synced with LineageOS sources (March 2023 security updates)
Fixed regression where bluetooth audio crackles when screen is off (core hotplugging is disabled for now)
Fixed VP9 video decoding in apps. We now have more quality options on YouTube. Our hardware can't do 4K60, so only 4K30
ZRAM settings kanged from exynos 7580 (75% of RAM is ZRAM now). This should be better for general usability
Thanks to enesuzun2002 releasing the BSP, we can now build HWC components from source. Shouldn't change too much for now, but its nice
25.02.2023
GPS works now
Fixed regression where mobile data wouldn't work (need different patches for netd/bpf for some reason)
HRM/SPO2 works semi-properly now due to a missing SPO2 permission (taken from universal5433).
ZRAM reduced to 800mb for now
15.02.2023
Synced with LineageOS sources (Feb 2023 security update)
Back on Nougat kernel for now
So edge models should be able to disable hw buttons without issue
Added FB notifier for touchscreen and touchkey - touchkeys no longer vibrate when screen is off
Added CPU/GPU voltage control. Use hkTweaks to undervolt. (at your own risk)
Added BFQ i/o scheduler
Added Dynamic F-Sync (from anans cronos kernel)
Wireguard VPN support
Battery store_mode support
Hwbinder for sensors, memtrack, renderscript, GNSS
uprev BT audio hal to 2.1
Fixed headphone jack being too loud
AdvancedDisplay added
Logs no longer spammed with errors about CPUs being online. Moved to a less jank way of disabling cores on power saver. You can control amount of cores online by editing the value in /sys/power/cpucore_max_num_limit (8 = all cores online, 4 = all big cores disabled etc)
Misc changes:
Source code moved to samsungexynos7420. Please build from there.
7420_patches cleaned up, a lot werent needed.
Using protobuf 2.6 now instead of 2.4 - precompiled and included in vendor
Newer aptX from crosshatch
secril blobs from latest official nougat
ZRAM settings changed a bit, nothing big
12.12.2022
Synced with lineage sources - android december security update
Removed AudioFX as a test
22.11.2022
Synced with LineageOS sources, we have novemeber security updates
UI performance dramatically improved due to prebuilt HWC components
Bluetooth audio fixed, we were building 64bit HAL for some reason
ZRAM values tweaked
Added experimental aptX
Added experimental freeform windows
Core hotplugging disabled, causes issue with BT audio when screen is off
Swapped to LE video codecs for now
New power saver mode - 4 small cores, 2 big cores, tweaked frequencies (jank implementation lol)
OpenCL fixed
Fixed GPS rollover bug
08.10.2022
Fixed S6 Edge not booting (weird kernel glitch)
Modified powerhints.json
07.10.2022
Synced with LineageOS sources
Swapped to EQ1 kernel based on S6 Nougat firmware. However due to last minute issues, only necessary features were added.
Added and enabled ZRAM with lz4, improves general usability
Graphics should be slightly smoother
AOD now has acceptable brightness, better implementation later
Added Heart Rate Monitor permission
Switched to new Pixel Power HAL from hw/samsung
Fingerprint reader fixed (ty @ArmashOnXDA for the help)
Added basic vibration intensity control
Overall system responsiveness improved
G925F touch key disabler should work properly now
USB tethering fixed
28.08.2022
Initial G925F release
AOD enabled
Keydisabler is working, meaning on-screen buttons and gestural navigation can be selected
Reduced default display density to compensate for A12's new UI
23.08.2022
Initial Release for flat models
wow great work!!! Will try it soon, my S6 is not with me yet. Wish I can try it now :cheers:. Also thanks for bringing this old phone up to-date.
WOAHHHHHHHH :OOOOOOOOOOOOOOOO
Will it be available for the S6 Edge soon? zeroltexx/SM-G925
ArmashWasTaken said:
:OOOOOOOOOOOOOOOO
Will it be available for the S6 Edge soon? (G925F/I)
Click to expand...
Click to collapse
yes. but for now while its a bit buggy, focusing on 1 device
Good news, I just have a bootloop on my S6 so I did a factory reset so there's nothing on my phone right now (Nothing to worry because I backed up all my data into laptop already). Might try it in tommorow. This phone is my main phone currently so I'll test on it
mine is G920F so hoping that everything is fine
fakemanoan said:
LineageOS is a free, community built, aftermarket firmware distribution of Android 12 (S), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
After a long wait, here is Android 12L for the Samsung Galaxy S6! Though it is a beta with some issues, I figure I release it.
Based on the Exynos7420 source code.
What's working:
Bluetooth
Telephony (Calls, SMS, Mobile Data)
WiFi/Hotspot
NFC
GPS
Camera
HWC
What's not working:
VoLTE and other proprietary Samsung stuff
Fingerprint
You tell me
Download Link:
LineageOS Releases on my GitHub
Source Code:
GitHub - fakemanoan/local_manifests
Contribute to fakemanoan/local_manifests development by creating an account on GitHub.
github.com
GitHub - fakemanoan/android_kernel_samsung_universal7420
Contribute to fakemanoan/android_kernel_samsung_universal7420 development by creating an account on GitHub.
github.com
ROM OS Version: 12.x S
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information:
Beta/Testing
ROM creation date: 23/08/2022
Last release: 23/08/2022
Thanks to:
Talu(atgithub) - various patches used
html6405 and rinando - various lineageos patches used
enezusun2002 - original exynos7420 source code, without him and his work, none of this would really be possible
All Exynos7420/universal7420 contributors
Click to expand...
Click to collapse
Congratulations !1 You are the man !
fakemanoan said:
Will the Edge models be supported? (G925)
Yes, but for the moment just flat models whilst everything gets sorted.
I have echo in phone calls!
Echoing in calls has been a problem for Samsung devices for a long time. Not aware of a fix as of yet.
I have a problem!
Post relevant problem and debugging information (ie logcat, last_kmesg etc) here or on github
If you want to see the project improve , help by contributing code!
Changelog:
23.08.2022
Initial Release for flat models
Click to expand...
Click to collapse
Paypal link?
Concept48 said:
Congratulations !1 You are the man !
Click to expand...
Click to collapse
I,m installing now /sucess/ Reboot /after 18 cycles booted up / setting up /and I,m inn . waw I waited sooo long for this to happen .
You don't wanna know how happy we are ,,The S6 is making it's comeback - THANK YOU !!
Concept48 said:
I,m installing now /sucess/ Reboot /after 18 cycles booted up / setting up /and I,m inn . waw I waited sooo long for this to happen .
You don't wanna know how happy we are ,,The S6 is making it's comeback - THANK YOU !!
Click to expand...
Click to collapse
Glad to hear it works for you. I'll be working on some other releases soon (tm), probably crdroid, pixel experience and others (any suggestions?).
Concept48 said:
Paypal link?
Click to expand...
Click to collapse
Check the OP
fakemanoan said:
Glad to hear it works for you. I'll be working on some other releases soon (tm), probably crdroid, pixel experience and others (any suggestions?).
One suggestion , don't leave us and stay !
Click to expand...
Click to collapse
thanks lot for your time and work man ♥
please will you update this room later ?
Just installed it 20 mins ago, everything until now is smooth and no over heat. Good work!!
adelbouzi said:
thanks lot for your time and work man ♥
please will you update this room later ?
Click to expand...
Click to collapse
He just started and said in chat he will do allot more
Concept48 said:
He just started and said in chat he will do allot more
Click to expand...
Click to collapse
When are you making the review of the ROM?
ArmashWasTaken said:
When are you making the review of the ROM?
Click to expand...
Click to collapse
I was so tired when I came home so I Shot the video , fell a sleep while making it , but just posted it , it's up my friend I must just finish some text and links !! So Right Now !
ROM works like a charm for now uptime 12 hrs Plus no RR (random Reboots) etc here a promotional video
Damnnnnnnnnn that's so coolllll!!!! I can't wait for S6 edge (zeroltexx) to get the update. Any estimate as to when will G925 get the update?
Concept48 said:
ROM works like a charm for now uptime 12 hrs Plus no RR (random Reboots) etc here a promotional video
Click to expand...
Click to collapse
appreciate the support!
ArmashWasTaken said:
Damnnnnnnnnn that's so coolllll!!!! I can't wait for S6 edge (zeroltexx) to get the update. Any estimate as to when will G925 get the update?
Click to expand...
Click to collapse
dont hold me to this, but (hopefully) i plan to have all s6 variants with an A12L release by the end of the week, including W8 variants.
I still can't get the fingerprint sensor working properly. I don't want to keep the releases back if that doesn't work though, as everything else appears to work fine.
After I release the new builds, i'll try get SELinux to enforcing, DT2W and the new pixel power HAL working. We'll see how that goes lol