Related
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.
Hello,
I've started to bring the ROM forward to LineageOS X.x for the G850F. If anybody knows how to port a ROM or knows C/C++ and want to work together, feel free to contact me! Reading and understanding strace output is essential.
SOURCES
I will post my progress in this thread.
I already booted it but it has many bugs : Ril, Camera, Etc...
나의 IM-100S 의 Tapatalk에서 보냄
good job bros keep going
SerenityS said:
I already booted it but it has many bugs : Ril, Camera, Etc...
나의 IM-100S 의 Tapatalk에서 보냄
Click to expand...
Click to collapse
So you already fixed ril.h, kernel build issues, SlteRIL.h, gralloc.h ... ???
modpunk said:
So you already fixed ril.h, kernel build issues, SlteRIL.h, gralloc.h ... ???
Click to expand...
Click to collapse
Check this - https://github.com/SerenityS/android_device_samsung_slte
Im using CM13 kernel source with SELinux permissive , CM13 vendors.
It has little bit dirty commit status & sources because i try many things to fix errors.
SerenityS said:
Check this - https://github.com/SerenityS/android_device_samsung_slte
Im using CM13 kernel source with SELinux permissive , CM13 vendors.
It has little bit dirty commit status & sources because i try many things to fix errors.
Click to expand...
Click to collapse
I've started too, the main repo is now here:
https://git.cryptomilk.org/projects/android/android_device_samsung_sltexx.git/
The kernel already has all the fixes and compiles.
I would be great if you could start again based on my android_device_samsung_sltexx.git branch and we work together to get things done. There is #cyanogenmod-exynos5 on irc.freenode.net for developers.
A lot of stuff will not work, because the features have not been ported to cm-14.1 yet. For example the Samsung camera code is not in framworks_av, color support is missing etc.
So the first steps are just to get it compiling.
Next:
Update ril.h (this is a manual task which needs to be done carefully)
Update sepolicy
modpunk said:
A lot of stuff will not work, because the features have not been ported to cm-14.1 yet. For example the Samsung camera code is not in framworks_av, color support is missing etc.
So the first steps are just to get it compiling.
Next:
Update ril.h (this is a manual task which needs to be done carefully)
Update sepolicy
Click to expand...
Click to collapse
https://github.com/SerenityS/android_device_samsung_slte
In branch cm-14.1, I updated ril.h & some other fixs, so we need to verify it.
+ source are based on your cm-14.1
SerenityS said:
https://github.com/SerenityS/android_device_samsung_slte
In branch cm-14.1, I updated ril.h & some other fixs, so we need to verify it.
+ source are based on your cm-14.1
Click to expand...
Click to collapse
Yes, I've looked into your changes already but a lot of some are not really correct.
SLTE doesn't need a modemloader, this is only required for treltexx and gts2 devices. We also do not have to set the hwrevison for cbd.
I like your ril.h changes, they are small and easy to review! Great work!
I review and cherry-pick them tomorrow. I don't have time today.
Thanks for your help!
That will be great!
modpunk said:
Yes, I've looked into your changes already but a lot of some are not really correct.
SLTE doesn't need a modemloader, this is only required for treltexx and gts2 devices. We also do not have to set the hwrevison for cbd.
I like your ril.h changes, they are small and easy to review! Great work!
I review and cherry-pick them tomorrow. I don't have time today.
Thanks for your help!
Click to expand...
Click to collapse
Okay I revert commits what we doesnt need.
I've just tried to test about seclabels and domain_deprecated just now, but I think it doesn't need now.
I don't know why it work soon without that patches, maybe there is something about the work at Cyanogen Team.
Now I'm in clean build, I'll let you know that we need patches surely when the build is done.
+ Please check my hardware_5430 repo and vendor repo.
Mobicore works without any error (according to logs).
@SerenityS can you tell me what works and what doesn't so far:
RIL (radio)
phone calls
Wifi
Camera
Audio
...
modpunk said:
@SerenityS can you tell me what works and what doesn't so far:
RIL (radio)
phone calls
Wifi
Camera
Audio
...
Click to expand...
Click to collapse
No problem.
I will rebuild with your source and notice which function working or not working.
modpunk said:
@SerenityS can you tell me what works and what doesn't so far:
RIL (radio)
phone calls
Wifi
Camera
Audio
...
Click to expand...
Click to collapse
Work
WIFI
Bluetooth
Audio
NFC
etc,,
Not work
RIL (slte.java?)
Camera (SHIM not working properly now + maybe more framework's problem)
GPS (Need hexedit : https://github.com/TheMuppets/propr...mmit/976064c4c69acbb91c8355b09c0c7645ba6cd76d)
In cm-14.1_dev branch
Fix more sepolicy denied (Fix for CBD - now can working cpboot service normally)
Fix settings FC
Update README
Fix module name for stlport (I don't know why you using stlport instead of libstlport)
logcat : https://gist.github.com/SerenityS/d437342e6516461b402cde28aead6b1f
SerenityS said:
Work
WIFI
Bluetooth
Audio
NFC
etc,,
Not work
RIL (slte.java?)
Camera (SHIM not working properly now + maybe more framework's problem)
GPS (Need hexedit : https://github.com/TheMuppets/propr...mmit/976064c4c69acbb91c8355b09c0c7645ba6cd76d)
In cm-14.1_dev branch
Fix more sepolicy denied (Fix for CBD - now can working cpboot service normally)
Fix settings FC
Update README
Fix module name for stlport (I don't know why you using stlport instead of libstlport)
logcat : https://gist.github.com/SerenityS/d437342e6516461b402cde28aead6b1f
Click to expand...
Click to collapse
I will try to look into RIL tonight.
The Samsung Camera support in frameworks/av is missing.
Can you give more details on the GPS hexedit ...
modpunk said:
I will try to look into RIL tonight.
The Samsung Camera support in frameworks/av is missing.
Can you give more details on the GPS hexedit ...
Click to expand...
Click to collapse
Check commit message in themuppets'.
Now camera is working
+ If sepolicy permissive, video recording and shim working too.
So we need to fix sepolicy..
나의 IM-100S 의 Tapatalk에서 보냄
Is it usable now ? And where can i download the file if yes ?
What works:
RADIO
Camera taking normal picture
Audio
Wifi
What doesn't work:
GPS
Video decoding
Haven't tested more yet ... time to go to bed ...
@SerenityS Do you have gpsd working. Did you use a newer gpsd binary?
UPDATE: As of today this fixes already went into LineageOS official, but keeping the thread for future reference and extra info...
PROBLEM
Some users report that their US996 and LS997 variants are only able to utilize 2 cameras in LineageOS or AOSP based ROMs.
The problem happens regardless of camera being used.
This is not the 'dark screen' capture on the Snap Camera happening on LineageOS, the problem is the 3rd camera not being active at all.
On further investigation this phones use a similar (spec wise) but different camera sensor and actuators for the 3rd camera.
DESCRIPTION
As of today (Sep-12-2017) The current LineageOS and AOSP builds that use LGE 8996 common repository are still missing some information for some variants of our beloved US996 and LS997 phones. Seems like these variants use a different camera sensor on some called the s5k2p7.
So I have decided to share my personal patches for users who might have problems with only being able to utilize 2 cameras (users whose only cameras that work are wide angle and selfie, and not the normal rear camera). I hope this is temporary and that we can get the fixes upsteam sometime soon but I am sure I can make some V20 users happy with this.
The other added benefit of using this is that this Kernel is based on CM's August version and will not have the touch-screen bug that has been recently seen and experienced on LineageOS recent automated builds.
The way it works is that in order for LineageOS or any AOSP ROM to see and activate this camera it needs a proper library and binary blobs for qcamera server. I have extracted these new'ish updated binary blobs from the US996 firmware and after doing so and flashing them on top of your ROM you should now be able to see the 3rd camera on these phones. However after patching the above it is still lacking proper Kernel support so that focusing works and hence will need to flash a re-compiled Kernel on top of your ROM to make it work.
INSTRUCTIONS
Be in recovery, if you are looking for this post you most likely already have AOSP and are facing these issues
Please just try the builds from this post #20 and flash it as @x86cpu has incorporated those fixes in this UNOFFICIAL builds
Flash the optional "flashable-snap.zip" if your Snap camera starts up black by default. This will make some users happy, this is not related to the sensor fix but it is just using an older Snap version that does proper auto shutter speed.
Reboot
KERNEL CHANGES
The changes lie in the following files that can be obtained and extracted from LG's LS997 Kernel sources:
Code:
drivers/media/platform/msm/camera_v2/sensor/actuator/msm_actuator.c
drivers/media/platform/msm/camera_v2/sensor/ois/msm_ois.c
drivers/media/platform/msm/camera_v2/sensor/ois/Makefile
drivers/media/platform/msm/camera_v2/sensor/ois/lgit_s5k2p7_rohm_ois.h
drivers/media/platform/msm/camera_v2/sensor/ois/lgit_s5k2p7_rohm_ois.c
DOWNLOADS
flashable-lge-v20-s5k2p7-eeprom-camera-libs.zip [NOT NEEDED ANYMORE, THIS IS JUST A PLACEHOLDER, READ THE INSTRUCTIONS]
flashable-snap.zip
Please just try the builds from this post #20
<< If you like my work here is my hat, please donate! >>
CHANGELOG
v1.0
Added support for US996 (Tested Kernel and libraries on two phones, all working well).
Added support for LS997 (Kernel Untested, I hope to get feedback soon).
Binary blobs based on US996 latest version of 10h.
I'll be testing it out soon as I get home. I love aosp and if all 3 cameras work it will be awesome.
Sent from my LG-LS997 using XDA-Developers Legacy app
---------- Post added at 04:48 PM ---------- Previous post was at 04:07 PM ----------
I keep getting error 1 when installing the kernel.
Sent from my LG-LS997 using XDA-Developers Legacy app
philiptibbs said:
I'll be testing it out soon as I get home. I love aosp and if all 3 cameras work it will be awesome.
Sent from my LG-LS997 using XDA-Developers Legacy app
---------- Post added at 04:48 PM ---------- Previous post was at 04:07 PM ----------
I keep getting error 1 when installing the kernel.
Sent from my LG-LS997 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thanks for testing for the LS997, I was explicitly waiting this to happen ... since I hadn't tested this myself on LS997. Can you check the zip and open anykernel.sh:
Change
Code:
do.devicecheck=1
to
Code:
do.devicecheck=0
Save the *.zip and reflash?
Since I used an equivalent zip I created for US996, I had used the following:
Code:
device.name1=omni_us997
device.name2=ls997
device.name3=LG-LS997
But seems like none of those names match the LS997 device, do you know what name it uses so that I can fix it properly?
Elsa is what TWRP has it for and ls997 .
Sent from my LG-LS997 using XDA-Developers Legacy app
---------- Post added at 05:44 PM ---------- Previous post was at 05:43 PM ----------
I will try in a little bit going to dinner.
Sent from my LG-LS997 using XDA-Developers Legacy app
I still get error 1 after changing the do.devicecheck=0 file ? I tried it on TWRP 3.0.2.1 and 3.1.1.0
Omar-Avelar said:
PROBLEM
Some users report that their US996 and LS997 variants are only able to utilize 2 cameras in LineageOS or AOSP based ROMs.
The problem happens regardless of camera being used.
This is not the 'dark screen' capture on the Snap Camera happening on LineageOS, the problem is the 3rd camera not being active at all.
On further investigation this phones use a similar (spec wise) but different camera sensor and actuators for the 3rd camera.
DESCRIPTION
As of today (Sep-12-2017) The current LineageOS and AOSP builds that use LGE 8996 common repository are still missing some information for some variants of our beloved US996 and LS997 phones. Seems like these variants use a different camera sensor on some called the s5k2p7.
So I have decided to share my personal patches for users who might have problems with only being able to utilize 2 cameras (users whose only cameras that work are wide angle and selfie, and not the normal rear camera). I hope this is temporary and that we can get the fixes upsteam sometime soon but I am sure I can make some V20 users happy with this.
The other added benefit of using this is that this Kernel is based on CM's August version and will not have the touch-screen bug that has been recently seen and experienced on LineageOS recent automated builds.
The way it works is that in order for LineageOS or any AOSP ROM to see and activate this camera it needs a proper library and binary blobs for qcamera server. I have extracted these new'ish updated binary blobs from the US996 firmware and after doing so and flashing them on top of your ROM you should now be able to see the 3rd camera on these phones. However after patching the above it is still lacking proper Kernel support so that focusing works and hence will need to flash a re-compiled Kernel on top of your ROM to make it work.
INSTRUCTIONS
Be in recovery, if you are looking for this post you most likely already have AOSP and are facing these issues
Flash your favorite AOSP based ROM (I recommend lineage-14.1-20170728-nightly-us996-signed.zip for US996 if you want Bluetooth working).
Flash "flashable-lge-v20-s5k2p7-eeprom-camera-libs.zip".
Flash "flashable-*-gamma-kernel-1.0.zip".
Flash the optional "flashable-snap.zip" if your Snap camera starts up black by default. This will make some users happy, this is not related to the sensor fix but it is just using an older Snap version that does proper auto shutter speed.
Reboot
KERNEL CHANGES
The changes lie in the following files that can be obtained and extracted from LG's LS997 Kernel sources:
Code:
drivers/media/platform/msm/camera_v2/sensor/actuator/msm_actuator.c
drivers/media/platform/msm/camera_v2/sensor/ois/msm_ois.c
drivers/media/platform/msm/camera_v2/sensor/ois/Makefile
drivers/media/platform/msm/camera_v2/sensor/ois/lgit_s5k2p7_rohm_ois.h
drivers/media/platform/msm/camera_v2/sensor/ois/lgit_s5k2p7_rohm_ois.c
DOWNLOADS
flashable-lge-v20-s5k2p7-eeprom-camera-libs.zip
flashable-ls997-gamma-kernel-1.0.zip
flashable-us996-gamma-kernel-1.0.zip
flashable-snap.zip
<< If you like my work here is my hat, please donate! >>
Click to expand...
Click to collapse
Do you have the exact source (against the LOS kernel) you changed? And what blobs had to be updated. I did try this adding into the LOS kernel on my us996 and blobs. Except it didn't work, nothing could open the camera any more. Kernel compiles, but not sure if I got an mis-config there or missing some blobs. https://review.lineageos.org/189552
Hey @x86cpu, thanks... So I had to do it con branch cm-14.1_20170811.
I didnt get to try it with the latest upstream, and for the blobs it is all contained un that zip (libs, and *.xml). Sorry that I cannot be more verbose as I am away from my computer.
Btw, updating the prebuilts on an already flashed system requires you to update the SELinux policies to match again:
Code:
chown root:shell /system/bin/mm-qcamera-*;
chmod 0755 /system/bin/mm-qcamera-*;
chcon -t system_file /system/bin/mm-qcamera-app;
chcon -t mm-qcamerad_exec /system/bin/mm-qcamera-daemon;
set_perm_recursive 0 0 0755 0644 /system/vendor/lib;
set_perm_recursive 0 0 0755 0644 /system/vendor/lib64;
set_perm_recursive 0 0 0755 0644 /system/etc/camera;
chmod 0644 /system/media/*.bin;
restorecon -r /system/vendor/lib;
restorecon -r /system/vendor/lib64;
restorecon -r /system/etc/camera;
restorecon -r /system/media;
Omar-Avelar said:
Hey @x86cpu, thanks... So I had to do it con branch cm-14.1_20170811.
I didnt get to try it with the latest upstream, and for the blobs it is all contained un that zip (libs, and *.xml). Sorry that I cannot be more verbose as I am away from my computer.
Btw, updating the prebuilts on an already flashed system requires you to update the SELinux policies to match again:
Code:
chown root:shell /system/bin/mm-qcamera-*;
chmod 0755 /system/bin/mm-qcamera-*;
chcon -t system_file /system/bin/mm-qcamera-app;
chcon -t mm-qcamerad_exec /system/bin/mm-qcamera-daemon;
set_perm_recursive 0 0 0755 0644 /system/vendor/lib;
set_perm_recursive 0 0 0755 0644 /system/vendor/lib64;
set_perm_recursive 0 0 0755 0644 /system/etc/camera;
chmod 0644 /system/media/*.bin;
restorecon -r /system/vendor/lib;
restorecon -r /system/vendor/lib64;
restorecon -r /system/etc/camera;
restorecon -r /system/media;
Click to expand...
Click to collapse
Yeah, I built the entire ROM. Kernel changes went it, but for LOS to use it it'll need to have the other g5 (lucye) changes in there too. kernel is the same source for both sets. The touchscreen kernel bug should be fixed shortly. Trying to get this into LOS might be next. My us996 though doesn't have that sensor, so I can only test that my builds do not break my camera (which they do currently).
What would happen if i would flash the camera libs on a h990ds which has the same s5k2p7 sensor?
jody2k said:
What would happen if i would flash the camera libs on a h990ds which has the same s5k2p7 sensor?
Click to expand...
Click to collapse
You would get the 3rd camera 'working' and showing in the apps. But without focus (OIS). Once @x86cpu gets the Kernel changes upstream then we could get the DS Kernel built and hopefully get this working soon for your device.
x86cpu said:
Yeah, I built the entire ROM. Kernel changes went it, but for LOS to use it it'll need to have the other g5 (lucye) changes in there too. kernel is the same source for both sets. The touchscreen kernel bug should be fixed shortly. Trying to get this into LOS might be next. My us996 though doesn't have that sensor, so I can only test that my builds do not break my camera (which they do currently).
Click to expand...
Click to collapse
I see, yeah... seems like it still needs more dissecting to cherry-pick and keep the support for the G5/G6's intact... :highfive: thanks for being proactive on getting these upstream as I haven't had much extra time
Omar-Avelar said:
I see, yeah... seems like it still needs more dissecting to cherry-pick and keep the support for the G5/G6's intact... :highfive: thanks for being proactive on getting these upstream as I haven't had much extra time
Click to expand...
Click to collapse
I think I got it. Those kernel changes are correct. The blobs I had were messed up. I'm hoping to have a build (UNOFFICAL) shortly that will have the latest LOS, kernel no touchscreen fixed, blueborne patches in too. Only for us996, but it is a start. I'll validate it works for me and does not break my camera at least. I won't be able to tell if it works for the s5k2p7 sensor as mine does not appear to have it.
Omar-Avelar said:
You would get the 3rd camera 'working' and showing in the apps. But without focus (OIS). Once @x86cpu gets the Kernel changes upstream then we could get the DS Kernel built and hopefully get this working soon for your device.
Click to expand...
Click to collapse
My friend we have working focus already thx to jahlex
https://forum.xda-developers.com/v20/development/dirtysanta-h990-t3624296/page71
But the kernel is bit basic for moment, no kcal colors tweaking and no gouvernors or schedulers etc but we cant complain
I'm currently using kernel with lot of features (from leicxan) but focus is not working thats why i asked about the libs maybe i could get focus to work on that kernel with flashing libs
x86cpu said:
I think I got it. Those kernel changes are correct. The blobs I had were messed up. I'm hoping to have a build (UNOFFICAL) shortly that will have the latest LOS, kernel no touchscreen fixed, blueborne patches in too. Only for us996, but it is a start. I'll validate it works for me and does not break my camera at least. I won't be able to tell if it works for the s5k2p7 sensor as mine does not appear to have it.
Click to expand...
Click to collapse
https://drive.google.com/open?id=0B51rjK5Hd_P5NmpwY1o4VmlyaUk
us996 test one to ensure what I did is sane. My us996 works still. In the s5k2p7_sensor_test folder.
jody2k said:
My friend we have working focus already thx to jahlex
https://forum.xda-developers.com/v20/development/dirtysanta-h990-t3624296/page71
But the kernel is bit basic for moment, no kcal colors tweaking and no gouvernors or schedulers etc but we cant complain
I'm currently using kernel with lot of features (from leicxan) but focus is not working thats why i asked about the libs maybe i could get focus to work on that kernel with flashing libs
Click to expand...
Click to collapse
Seems like you only need to flash the libs and propeitary files (flashable-lge-v20-s5k2p7-eeprom-camera-libs.zip) without my Kernel then and it should work. I wasn't aware of that Kernel
x86cpu said:
https://drive.google.com/open?id=0B51rjK5Hd_P5NmpwY1o4VmlyaUk
us996 test one to ensure what I did is sane. My us996 works still. In the s5k2p7_sensor_test folder.
Click to expand...
Click to collapse
Awesome! Can anyone with the US996 with the s5k2p7 sensor try this build? I gave that phone to my sister and cannot test it myself either... this would bring confidence on the fixes all together and getting this upstream in a not too distant future
Omar-Avelar said:
Seems like you only need to flash the libs and propeitary files (flashable-lge-v20-s5k2p7-eeprom-camera-libs.zip) without my Kernel then and it should work. I wasn't aware of that Kernel
Awesome! Can anyone with the US996 with the s5k2p7 sensor try this build? I gave that phone to my sister and cannot test it myself either... this would bring confidence on the fixes all together and getting this upstream in a not too distant future
Click to expand...
Click to collapse
Not sure what you mean with properitary files ? My knowledge is pretty low of tweaking files
Oh oxejar whats gama kernel
---------- Post added at 09:58 PM ---------- Previous post was at 09:51 PM ----------
Omar whats gama kernel
Omar-Avelar said:
Seems like you only need to flash the libs and propeitary files (flashable-lge-v20-s5k2p7-eeprom-camera-libs.zip) without my Kernel then and it should work. I wasn't aware of that Kernel
Awesome! Can anyone with the US996 with the s5k2p7 sensor try this build? I gave that phone to my sister and cannot test it myself either... this would bring confidence on the fixes all together and getting this upstream in a not too distant future
Click to expand...
Click to collapse
I'm hoping to have an UNOFFICIAL build for this today (us996/ls997/h918/vs985). This would have the necessary blobs/configs that you had in your .zip file as well as the update into the kernel at the latest LOS release. I want to test first with my us996 just to ensure that I do not break my own camera. I do not have the s5k2p7 sensor, so I cannot test if that part works, but it should not prevent my camera from working either.
Omar-Avelar said:
Seems like you only need to flash the libs and propeitary files (flashable-lge-v20-s5k2p7-eeprom-camera-libs.zip) without my Kernel then and it should work. I wasn't aware of that Kernel
Awesome! Can anyone with the US996 with the s5k2p7 sensor try this build? I gave that phone to my sister and cannot test it myself either... this would bring confidence on the fixes all together and getting this upstream in a not too distant future
Click to expand...
Click to collapse
Are you able to test: https://drive.google.com/drive/folders/0B51rjK5Hd_P5NmpwY1o4VmlyaUk The ls997 for 09202017 has the necessary files/kernel fixes to make this sensor work....or at least I think it does. Just need confirmation things might work.
Ported Rom
resurection Remix 5.8.5 android 7.1.2
W.I.P.
Issues:
1. camera not working.
2. Phone "thinks" it has fingerprint hardware --will be removed next port --related to --#3--
3. Battery is not lasting more than 20hr stand-by---removed fingerprint drivers and other changees --V7 now shows 13 days YMMV , test has not been for that long yet just the battery monitor screen shows that long
4. Not connecting to google servers. --fixed in V5
5. Screen dies durring call and cannot get speakerphone button or any screen till after phone hangs up.----Fixed in V7
Rom was taken from here Full listing of features and settings can be read on blog post. Or from the menus inside ==>settings, ==>about phone, ==>about
Source:
Stock kernel
XDA:DevDB Information
Resurection Remix (port) , ROM for the BLU R1 HD
Contributors
mrmazak
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
Based On: lineageOS
Version Information
Status: Testing
Created 2017-11-05
Last Updated 2017-11-08
camera log
Since making changes to camer driver and references to them in the boot.img I have been getting different errors in the logcat.
mrmazak said:
Since making changes to camer driver and references to them in the boot.img I have been getting different errors in the logcat.
Click to expand...
Click to collapse
Thanks for the development friend, hopefully you can resolve what the camera, greetings from Venezuela!
I am having issue with this causing phone screen to lock up when makeng a call, not allowing call to be ended without rebooting phone.
Gapps not installed.
Anybody else see this problem?
UPDATE:
updated the sensor.so file and fixed screen (proximity sensor problem) V7 has this fix and also improvement to battery life. __removed fingerprint drivers / libs
Hey, does the camera still not work in v7?
What about renaming camera.mt6735.so to camera.mt6737m.so like you did for Slim6 port?
Also https://forum.xda-developers.com/android/software-hacking/guide-port-64-mtk-roms-t3555933
Under "to fix camera", did we try that yet?
Any idea why it's returning -22 ?
if (hw_get_module(CAMERA_HARDWARE_MODULE_ID,
(const hw_module_t **)&mModule) < 0) {
ALOGE("Could not load camera HAL module");
mNumberOfCameras = 0;
}
Click to expand...
Click to collapse
Means it has to return a value greater than 0 right?
I'm not that advanced as you but I'm just trying to help.
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