HUGE thanks to @giri45 for actually providing the fix!
What's this?
A Unity installer ensures that you can use this module with any kind of root solution (as long as it supports init.d)! If you have Magisk, flash the module through the Magisk Manager, but if you don't have Magisk, just flash the module through TWRP. When you want to uninstall the module, flash it again in Magisk Manager or TWRP.
As for the module itself, it provides a fix for LiveDisplay/Night Light on the Moto G5/G5S for anyone running an AOSP-based ROM running Android 9 or higher, and enables Camera2 API + EIS if you wish so.
Do NOT attempt to install this on other devices, or ROMs based on Android <9! Device and Android version checks have been applied to make sure this module will not install on incompatible devices. This module assumes that you are using the latest stock Oreo firmware (including bootloader, GPT and etc.)! Do not report issues if you are not on the latest firmware.
Tested ROMs:
Havoc OS 2.2
Pixel Experience 9.0
AOSPExtended 6.3
crDroid 5.0
Known issues:
Fix doesn't work on Nougat firmware. You must have fully flashed the stock ROM/flashed it via OTA, for this fix to work.
Downloads:
Download from Magisk Repo.
Flash via Magisk Manager or TWRP. Make sure you have a root solution which supports init.d!
Thanx for trying to fix this. Unfortunately it's not working on my xt1794 running AospExtented. First try flashing through twrp failed, the updaterscript didn't recognize my phone (correctly), then installing as magisk module, but no night light..
Ænimal said:
Thanx for trying to fix this. Unfortunately it's not working on my xt1794 running AospExtented. First try flashing through twrp failed, the updaterscript didn't recognize my phone (correctly), then installing as magisk module, but no night light..
Click to expand...
Click to collapse
That's really weird. Installs fine and works on PE, installs fine but doesn't work on ViperOS, and now doesn't work on AOSPExtended.
Could you try providing installation logs located in the Internal storage?
Have you also tried manually replacing the files? If that works, then it's not a problem with the ROM...
JarlPenguin said:
That's really weird. Installs fine and works on PE, installs fine but doesn't work on ViperOS, and now doesn't work on AOSPExtended.
Could you try providing installation logs located in the Internal storage?
Have you also tried manually replacing the files? If that works, then it's not a problem with the ROM...
Click to expand...
Click to collapse
Deleted
PE 9.0LOG is attached
@JarlPenguin You mentioned fix is working on AOSPExtended 6.3, is that for the g5, or is there a montana build? If so, please provide a link if possible, thanx
Ænimal said:
@JarlPenguin You mentioned fix is working on AOSPExtended 6.3, is that for the g5, or is there a montana build? If so, please provide a link if possible, thanx
Click to expand...
Click to collapse
It's an internal build. You can test it out here: https://t.me/montanadevelopment
JarlPenguin said:
It's an internal build. You can test it out here: https://t.me/montanadevelopment
Click to expand...
Click to collapse
I'm running this build now and tried the fix but to no avail, still (xt1794)
Ænimal said:
I'm running this build now and tried the fix but to no avail, still (xt1794)
Click to expand...
Click to collapse
Are you on the Oreo firmware? GPT and bootloader included. Did you do a screen repair before?
JarlPenguin said:
Are you on the Oreo firmware? GPT and bootloader included. Did you do a screen repair before?
Click to expand...
Click to collapse
Nougat firmware and Oreo baseband, screen is original. Do you think that partition table is the problem?
Ænimal said:
Nougat firmware and Oreo baseband. Do you think that partition table is the problem?
Click to expand...
Click to collapse
Okay, I think I have found the problem now. What have you not upgraded?
JarlPenguin said:
Okay, I think I have found the problem now. What have you not upgraded?
Click to expand...
Click to collapse
As I said, I upgraded the baseband, the rest is firmware from nougat. On another device I'm running lollipop firmware and no problems regarding night light on pie ROMs..
Edit: I see you updated op, will report back once I fully upgraded firmware (for now I want to be able to revert back to nougat). Thanx for your efforts
Ænimal said:
As I said, I upgraded the baseband, the rest is firmware from nougat. On another device I'm running lollipop firmware and no problems regarding night light on pie ROMs..
Edit: I see you updated op, will report back once I fully upgraded firmware (for now I want to be able to revert back to nougat). Thanx for your efforts
Click to expand...
Click to collapse
Thanks. I updated the OP a while ago, but I do want to figure out the root cause of the problem, whether it is the vendor image, bootloader, GPT, or something else.
JarlPenguin said:
Thanks. I updated the OP a while ago, but I do want to figure out the root cause of the problem, whether it is the vendor image, bootloader, GPT, or something else.
Click to expand...
Click to collapse
I'm planning on upgrading everything except bootloader and gpt.bin, then I'll try your fix again and report back:good:
Edit: OK, done. I did flash bootloader, did not erase userdata and did not flash stock recovery. Good news is: system feels alot snappier - not so good news is that fix is still not working for me..
For anyone with similar issue: use cf.lumen instead and don't forget to thank the dev
Ænimal said:
I'm planning on upgrading everything except bootloader and gpt.bin, then I'll try your fix again and report back:good:
Edit: OK, done. I did flash bootloader, did not erase userdata and did not flash stock recovery. Good news is: system feels alot snappier - not so good news is that fix is still not working for me..
For anyone with similar issue: use cf.lumen instead and don't forget to thank the dev
Click to expand...
Click to collapse
That's weird... One thing I know that is that this fix doesn't work on Nougat firmware.
Working flawlessly on crDroid 9.
Thank you devs!
I have installed the mod with magisk and not working on my device with Pixel Experience 9.0
Arn'oh said:
I have installed the mod with magisk and not working on my device with Pixel Experience 9.0
Click to expand...
Click to collapse
Hehe, same like me , if you didn't updated officially than this fix won't work on any PIE ROM
zahidm said:
Hehe, same like me , if you didn't updated officially than this fix won't work on any PIE ROM
Click to expand...
Click to collapse
I had updated to Oreo official beta test with fastboot commands
Arn'oh said:
I had updated to Oreo official beta test with fastboot commands
Click to expand...
Click to collapse
Did you flash everything? Try fully flashing Stock Oreo via Fastboot and then install TWRP, custom ROM and this fix.
Related
Newbie here.
How can I enable f2fs in arter's kernel? What would be the procedure? and how can I have both f2fs+supersu?
Is there any downside of it?
Thanks in advance.
ShiShTuBaBu said:
Newbie here.
How can I enable f2fs in arter's kernel? What would be the procedure? and how can I have both f2fs+supersu?
Is there any downside of it?
Thanks in advance.
Click to expand...
Click to collapse
I used f2fs on RR ROM a while back. It doesn't have any noticeable performance improvement over ext4. Plus you will have to incompatibilities with custom ROMs and kernels.
I used official RR Rom With blue spark kernel.
Kernel Link: http://forum.xda-developers.com/oneplus-3/development/kernel-t3404970
As I said before you won't notice any improvements but if you want to give it a try :good:
Prince Chandela said:
I used f2fs on RR ROM a while back. It doesn't have any noticeable performance improvement over ext4. Plus you will have to incompatibilities with custom ROMs and kernels.
I used official RR Rom With blue spark kernel.
Kernel Link: http://forum.xda-developers.com/oneplus-3/development/kernel-t3404970
As I said before you won't notice any improvements but if you want to give it a try :good:
Click to expand...
Click to collapse
True. I didn't notice any improvements in arter97's kernel too. tried to revert back to my OOS backup and now my home button isn't working. any solution?
ShiShTuBaBu said:
True. I didn't notice any improvements in arter97's kernel too. tried to revert back to my OOS backup and now my home button isn't working. any solution?
Click to expand...
Click to collapse
Flash the correct firmware version from http://forum.xda-developers.com/oneplus-3/development/firmware-updates-oos-3-1-2-3-5-2-t3465312
Check your OxygenOS version in Settings > About Phone
kgs1992 said:
Flash the correct firmware version from http://forum.xda-developers.com/oneplus-3/development/firmware-updates-oos-3-1-2-3-5-2-t3465312
Check your OxygenOS version in Settings > About Phone
Click to expand...
Click to collapse
I have flashed OOS op3lite rom and everything working good. But recently I'm seeing my phone is encrypted. I have to give my pattern everytime while accessing twrp and system.
any solution for this? Thanks.
fastboot erase userdata
You will lose data
kgs1992 said:
Flash the correct firmware version from http://forum.xda-developers.com/oneplus-3/development/firmware-updates-oos-3-1-2-3-5-2-t3465312
Check your OxygenOS version in Settings > About Phone
Click to expand...
Click to collapse
if I restore my oos 3.2.7 backup and then flash 3.2.6 firmware over it will my home button work? and will this firmware change anything of my backup rom?
Thanks again.
ShiShTuBaBu said:
if I restore my oos 3.2.7 backup and then flash 3.2.6 firmware over it will my home button work? and will this firmware change anything of my backup rom?
Thanks again.
Click to expand...
Click to collapse
Flash 3.2.7 firmware if you restore a 3.2.7 backup.
Stock firmware is compatible only with it's corresponding stock ROM.
Custom ROMs are compatible mostly with firmware <=3.2.6 & 3.5.0 (varies with ROM).
Also, take a look at this if you have problems with unlocking your phone after restore.
This thread has gone way off-topic. Please post your questions here.
So, I'm very eager to upgrade to a 7.1.1 custom ROM from 6.0.1 (currently using Dirty Unicorns 6.0.1), but I seem to have an issue with any android 7.1.1 version of a custom ROM I install where the sensors for auto rotate and auto brightness stop working. I've tried complete wipes and resets and installed crDroid, resurrection remix dirty unicorns and lineage OS. All of them have the same result. When downloading any apps that can be used to test and calibrate sensors, they all will read for that the sensor is unavailable for all hardware in the phone except for Wifi and GPS. Is this a general issue with android 7.0.1 on nexus 5x or is this just me? I've yet to find any other forums or pages with anyone experiencing this.
Any suggestions at all on this? I don't want to be stuck using Android 6 forever.
Any advice that can be offered would be greatly appreciated!
Ryan
kvothe26 said:
So, I'm very eager to upgrade to a 7.1.1 custom ROM from 6.0.1 (currently using Dirty Unicorns 6.0.1), but I seem to have an issue with any android 7.1.1 version of a custom ROM I install where the sensors for auto rotate and auto brightness stop working. I've tried complete wipes and resets and installed crDroid, resurrection remix dirty unicorns and lineage OS. All of them have the same result. When downloading any apps that can be used to test and calibrate sensors, they all will read for that the sensor is unavailable for all hardware in the phone except for Wifi and GPS. Is this a general issue with android 7.0.1 on nexus 5x or is this just me? I've yet to find any other forums or pages with anyone experiencing this.
Any suggestions at all on this? I don't want to be stuck using Android 6 forever.
Any advice that can be offered would be greatly appreciated!
Ryan
Click to expand...
Click to collapse
Make sure you read the OP of the ROM you are installing.
Clean flash everything with correct vendor image.
kvothe26 said:
So, I'm very eager to upgrade to a 7.1.1 custom ROM from 6.0.1 (currently using Dirty Unicorns 6.0.1), but I seem to have an issue with any android 7.1.1 version of a custom ROM I install where the sensors for auto rotate and auto brightness stop working. I've tried complete wipes and resets and installed crDroid, resurrection remix dirty unicorns and lineage OS. All of them have the same result. When downloading any apps that can be used to test and calibrate sensors, they all will read for that the sensor is unavailable for all hardware in the phone except for Wifi and GPS. Is this a general issue with android 7.0.1 on nexus 5x or is this just me? I've yet to find any other forums or pages with anyone experiencing this.
Any suggestions at all on this? I don't want to be stuck using Android 6 forever.
Any advice that can be offered would be greatly appreciated!
Ryan
Click to expand...
Click to collapse
I have a similar problem with every 7.1.1 custom ROM. Lift to check phone is not working (and yes, ambient display is enabled, vendor is correct). Every stock-based 7.1.2 ROM does work. Try flashing Stock+ 7.1.2 and see if your sensors work.
indian84 said:
Make sure you read the OP of the ROM you are installing.
Clean flash everything with correct vendor image.
Click to expand...
Click to collapse
I am always clean flashing. What do you mean by correct vendor image? It's always a bullhead version of the ROM. Maybe I misunderstand what you mean.
kvothe26 said:
I am always clean flashing. What do you mean by correct vendor image? It's always a bullhead version of the ROM. Maybe I misunderstand what you mean.
Click to expand...
Click to collapse
There is something called vendor image that you have to flash along with the ROM. It's generally linked to the build number.
Read the OP of the ROM you are using, it should have the correct vendor image you should use. If THE OP does not mention anything about the Vendor image, just search the thread or politely ask what vendor image to use.
Hopefully someone should link the download link for you. If not, you can easily Google it.
indian84 said:
There is something called vendor image that you have to flash along with the ROM. It's generally linked to the build number.
Read the OP of the ROM you are using, it should have the correct vendor image you should use. If THE OP does not mention anything about the Vendor image, just search the thread or politely ask what vendor image to use.
Hopefully someone should link the download link for you. If not, you can easily Google it.
Click to expand...
Click to collapse
Ohh. I was never aware of having to do something like this. I've always just downloaded the ROM and flashed it. Really appreciate this! Thanks! I'll have to give this a try.
kvothe26 said:
Ohh. I was never aware of having to do something like this. I've always just downloaded the ROM and flashed it. Really appreciate this! Thanks! I'll have to give this a try.
Click to expand...
Click to collapse
I have a strong feeling flashing correct vendor image will solve your problems.
indian84 said:
I have a strong feeling flashing correct vendor image will solve your problems.
Click to expand...
Click to collapse
You were right!
I downloaded the latest image from google and used the flash-all.bat script through fastboot, reflashed twrp, flashed crDroid 7.1.1, got a vendor image mismatch error on boot, then flashed the recommended vendor image version and now I'm booting without error and all sensors are working! I noticed Wifi detection and connection were working a but slow before, now everything is working perfectly. I was completely unaware that this needed to be done. It never came up as an issue for me when I was on Nexus 5.
I love the XDA community! Thanks a million for your help!
kvothe26 said:
You were right!
I downloaded the latest image from google and used the flash-all.bat script through fastboot, reflashed twrp, flashed crDroid 7.1.1, got a vendor image mismatch error on boot, then flashed the recommended vendor image version and now I'm booting without error and all sensors are working! I noticed Wifi detection and connection were working a but slow before, now everything is working perfectly. I was completely unaware that this needed to be done. It never came up as an issue for me when I was on Nexus 5.
I love the XDA community! Thanks a million for your help!
Click to expand...
Click to collapse
Separate Vendor partition was introduced with 5X and 6P. It was not needed on earlier devices.
Android 8.x
https://sourceforge.net/projects/cheeseburgerdumplings/files/15.1/cheeseburger/recovery/
Changes:
- TWRP 3.2.3 from android-8.1
- added vendor partition
Sources
https://github.com/TeamWin/android_device_oneplus_cheeseburger/tree/android-8.1
https://github.com/lineageos/android_kernel_oneplus_msm8998/tree/lineage-15.1
################################################################################################
Android 9.x (requires Pie firmware)
https://sourceforge.net/projects/cheeseburgerdumplings/files/16.0/cheeseburger/recovery/
Changes:
twrp-3.3.1-0-20190713-codeworkx-cheeseburger.img
- fix bug in default device properties
twrp-3.3.1-1-20190623-codeworkx-cheeseburger.img
- add support for synthetic password version 3 (may update)
twrp-3.3.1-0-20190427-codeworkx-cheeseburger.img
- updated twrp to 3.3.1
- removed compatibility check
- removed twrp app check
- modified version string
Sources
https://github.com/TeamWin/android_device_oneplus_cheeseburger/tree/android-9.0
https://github.com/lineageos/android_kernel_oneplus_msm8998/tree/lineage-16.0
Tested/ working fine Running Oero Public Beta 2 with encrytion enabled,
thanks
Data decryption seems to be working fine on oos5 with encryption enabled
Not working with omnirom encrypted........will try with others when got time...
canteo said:
Not working with omnirom encrypted........will try with others when got time...
Click to expand...
Click to collapse
Which version of omni?
File based or full disk encryption?
Ext4 or F2FS?
Which oneplus firmware version 4.5.15?
codeworkx said:
Which version of omni?
File based or full disk encryption?
Ext4 or F2FS?
Which oneplus firmware version 4.5.15?
Click to expand...
Click to collapse
Upps... it is true, i am sorry, last omnirom it's 8.1 and all of us know that none twrp is working decrypting data
omni 8.1, ext4, flashed over second last oreo oss test rom( second open beta) before 5.0 oss with full disk encryption( i think..)
canteo said:
Upps... it is true, i am sorry, last omnirom it's 8.1 and all of us know that none twrp is working decrypting data
omni 8.1, ext4, flashed over second last oreo oss test rom( second open beta) before 5.0 oss with full disk encryption( i think..)
Click to expand...
Click to collapse
We'll get that fixed during next few days.
So this TWRP is to decrypt a encrypted rom?
obol2 said:
So this TWRP is to decrypt a encrypted rom?
Click to expand...
Click to collapse
Decrypt and access userdata when running OxygenOS 5.0 (Oreo). Probably mainly for doing backups and restores.
Amazing! It's working for both FBE and FDE?
codeworkx said:
Please test data decryption.
Click to expand...
Click to collapse
Working perfectly on my OP5 with Oreo (non-beta) encrypted.
Can confirm that it can see encrypted data, backup and restore perfectly!
Great job!!
Sent from my OnePlus5, OOS Oreo, Flash Kernel
Big Thanks, @codeworkx Testing features now and usb-otg is not working. I see the commit but I dont know if it's a oreo thing but you could add this line in init.recovery.qcom.rc
write /sys/class/power_supply/usb/otg_switch 1
Testing on official oreo release on Christmas release, on FBE encryption- only made a backup so far, will report more later.
Thanks also for posting additional commits also.
Works perfectly. Encrypted OP5 (Oreo FBE);and tested with several Rom upgrades with no issues.
morgoth6 said:
Works perfectly. Encrypted OP5 (Oreo FBE);and tested with several Rom upgrades with no issues.
Click to expand...
Click to collapse
Did you try xxx 9.2 on your encrypted device?
mcduffie2010 said:
Did you try xxx 9.2 on your encrypted device?
Click to expand...
Click to collapse
Yes. I installed 9.2 over 9.1a +Flash kernel and it works just fine. To be honest I read all the comments about xxx upgrade on encrypted OP5 after that ... Sic. Glad it worked for me.
morgoth6 said:
Yes. I installed 9.2 over 9.1a +Flash kernel and it works just fine. To be honest I read all the comments about xxx upgrade on encrypted OP5 after that ... Sic. Glad it worked for me.
Click to expand...
Click to collapse
I posted your findings on the xxx thread. Hope it helps people.
mcduffie2010 said:
I posted your findings on the xxx thread. Hope it helps people.
Click to expand...
Click to collapse
I wonder what can produce this problems. I personally like to have encrypted device, but makes me think twice before update to new ROM now.
Is there a way to check what kind of encryption is used ? I mean FDE or FBE (or both) ? Maybe the problem is there. I buy this phone quite recently and started with clean Oreo (with format data) so I probably ended with ext4/FBE. Maybe problematic cases used FDE+FBE ?
I would like to see someone find what can be the cause for this problems as clean install or reinstalling Rom ten times is not a solution :/
morgoth6 said:
I wonder what can produce this problems. I personally like to have encrypted device, but makes me think twice before update to new ROM now.
Is there a way to check what kind of encryption is used ? I mean FDE or FBE (or both) ? Maybe the problem is there. I buy this phone quite recently and started with clean Oreo (with format data) so I probably ended with ext4/FBE. Maybe problematic cases used FDE+FBE ?
I would like to see someone find what can be the cause for this problems as clean install or reinstalling Rom ten times is not a solution :/
Click to expand...
Click to collapse
I agree but like I said in xxx thread I can't test because I'm decrypted and planning to stay that way. Hopefully people are gonna test it and than we know or get feedback.
morgoth6 said:
I wonder what can produce this problems. I personally like to have encrypted device, but makes me think twice before update to new ROM now.
Is there a way to check what kind of encryption is used ? I mean FDE or FBE (or both) ? Maybe the problem is there. I buy this phone quite recently and started with clean Oreo (with format data) so I probably ended with ext4/FBE. Maybe problematic cases used FDE+FBE ?
I would like to see someone find what can be the cause for this problems as clean install or reinstalling Rom ten times is not a solution :/
Click to expand...
Click to collapse
Afaik oxygen is using keymaster1 and lineage/omni/aosp are using keymaster3. That seems to be a problem.
The upgraded firmware is also a problem for old twrp builds using N libs.
Sent from my OnePlus5T using XDA Labs
mcduffie2010 said:
I posted your findings on the xxx thread. Hope it helps people.
Click to expand...
Click to collapse
Thanks for your help, I tried to flash this TWRP via fastboot but same issue as before, can't seem to ask for a password in order to decrypt storage. I'm trying to sideload 9.2 to see if it can work by flashing on it again, we never know... In either case I'm screwed lol.
Any way to decrypt storage using a flashable zip in TWRP? Like no_verity, etc ? I feel like the answer is no since it will say that it is decrypted, but it won't decrypt the data that is already encrypted (would be too easy right?).
flsah nx563j_firmware_515
MK81.0-nx563j-201805210138-EXPERIMENTAL
Magisk-v16.4
https://download.mokeedev.com/?device=nx563j
https://drive.google.com/drive/folders/1T4onVKVtUa8kmeMGrMoHuVu8hKzD7z5G?usp=sharing
kenzo_cz said:
flsah nx563j_firmware_515
MK81.0-nx563j-201805210138-EXPERIMENTAL
Magisk-v16.4
https://download.mokeedev.com/?device=nx563j
https://drive.google.com/drive/folders/1T4onVKVtUa8kmeMGrMoHuVu8hKzD7z5G?usp=sharing
Click to expand...
Click to collapse
Great news!
Any informations about steps of installation?
And now we wait for first impressions.
camera launching very slow
kolibre said:
camera launching very slow
Click to expand...
Click to collapse
How did you install this rom? And what rom had you before?
surfer30 said:
How did you install this rom? And what rom had you before?
Click to expand...
Click to collapse
you have to unlock bootloader and install twrp recovery before install 3rd party rom, go Google for tutorial. btw, this rom is not suitable for new flasher.
kolibre said:
you have to unlock bootloader and install twrp recovery before install 3rd party rom, go Google for tutorial. btw, this rom is not suitable for new flasher.
Click to expand...
Click to collapse
You flashed rom directly from trwp on existing rom?
I have unlocked phone and trwp recovery before I used different roms so far. Now I'm on RR, latest build by arceoxis
surfer30 said:
You flashed rom directly from trwp on existing rom?
I have unlocked phone and trwp recovery before I used different roms so far. Now I'm on RR, latest build by arceoxis
Click to expand...
Click to collapse
cool, then you can format data, clear system/data/cache/internal storage, after that install base band (the one with 5.15) then install rom, then install open gapps if you want, reboot, enjoy
Returns on this Rom? Bluetooth? GPS? Android Oreo? NFC?
Any widevine support? I can't go through the pain of installing yet another ROM unless it's perfect
Deeoon said:
Returns on this Rom? Bluetooth? GPS? Android Oreo? NFC?
Click to expand...
Click to collapse
ishurmer said:
Any widevine support? I can't go through the pain of installing yet another ROM unless it's perfect
Click to expand...
Click to collapse
same requirements here ^_^
MrBlubke said:
same requirements here ^_^
Click to expand...
Click to collapse
Anyone can try the ROM ?
I haven't tested IR blaster so far, but the only big that I found so far is the camera launching, it's so slow, the strange thing is that in the previous UNOFFICIAL build it was launching well, I hope he will fix it in the next build.
arceoxis said:
I haven't tested IR blaster so far, but the only big that I found so far is the camera launching, it's so slow, the strange thing is that in the previous UNOFFICIAL build it was launching well, I hope he will fix it in the next build.
Click to expand...
Click to collapse
from what I remember from another ROM is that this slow camera launch seems to fix itself after a few reboots (Lineageos 15.1 seemed to suffer from this too)
so, is bluetooth audio working? and what about widevine drm? haven't found any z17 oreo rom that has widevine support yet...
MrBlubke said:
from what I remember from another ROM is that this slow camera launch seems to fix itself after a few reboots (Lineageos 15.1 seemed to suffer from this too)
so, is bluetooth audio working? and what about widevine drm? haven't found any z17 oreo rom that has widevine support yet...
Click to expand...
Click to collapse
not this one, I have rebooted for so many times but lagging still remain, did not act like 15.1.
Bluetooth is searchable and should be pairabled. never tried yet since I don't have a good headset.
MrBlubke said:
from what I remember from another ROM is that this slow camera launch seems to fix itself after a few reboots (Lineageos 15.1 seemed to suffer from this too)
so, is bluetooth audio working? and what about widevine drm? haven't found any z17 oreo rom that has widevine support yet...
Click to expand...
Click to collapse
BT working flawlessly, I passed DRM info app and this were the results:
arceoxis said:
BT working flawlessly, I passed DRM info app and this were the results:
Click to expand...
Click to collapse
Ok, so they're definitely improving, but just not there yet...
Wonder what needs to be done for widevine support like this... (Screenshot from lineageos 14.1)
MrBlubke said:
Ok, so they're definitely improving, but just not there yet...
Wonder what needs to be done for widevine support like this... (Screenshot from lineageos 14.1)
Click to expand...
Click to collapse
It seems that I solved it, I've just copied vendor/lib/mediadrm/libwvdrmengine.so from other Oreo ROM and now it looks like this. I've attached a little flashable .zip with the patch, I hope it could help.
kenzo_cz said:
flsah nx563j_firmware_515
MK81.0-nx563j-201805210138-EXPERIMENTAL
Magisk-v16.4
Click to expand...
Click to collapse
Ok, I tried installing everything in one go adding each zip after the other in twrp... apparently, this doesn't work... Device just turns off again after Nubia logo (yes I did the normal wipe)
I did select to prevent to overwrite TWRP
update: apparently you need to boot the device between installing Rom (and open Gapps) and installing Magisk... installing magisk 16.4 apparently needs to be done later... I'll report back when I'm done
arceoxis said:
It seems that I solved it, I've just copied vendor/lib/mediadrm/libwvdrmengine.so from other Oreo ROM and now it looks like this. I've attached a little flashable .zip with the patch, I hope it could help.
Click to expand...
Click to collapse
Thanks for that arceoxis. The patch looks really promising; I'm going to try this later.
Since we don't really have a developer for our device, my thought was we can open a thread and share our experiences with treble Rom's.
Anyone got an Android P Treble Rom running?
For example:
-------------------------------------------
Havoc 2.0 :
- https://forum.xda-developers.com/pr...-device-development/rom-havoc-os-8-1-t3819050
- Don't boot (Stuck at "You're Device is unlocked")
-------------------------------------------
Havoc 1.0
- https://sourceforge.net/projects/ha...oc-arm64_aonly_vanilla_nosu-0819.zip/download
- For me the best UI ever (a lot like Android P)
-> Not Working:
- Fingerprint Scanner, automatic brightness adjustment (fix: https://forum.xda-developers.com/pr.../overlay-enable-night-light-adaptive-t3741965 )
-> Working:
- everything else
(if you want me to check some specific just ask )
-------------------------------------------
Schubi97 said:
Since we don't really have a developer for our device, my thought was we can open a thread and share our experiences with treble Rom's.
Anyone got an Android P Treble Rom running?
For example:
-------------------------------------------
Havoc 2.0 :
- https://forum.xda-developers.com/pr...-device-development/rom-havoc-os-8-1-t3819050
- Don't boot (Stuck at "You're Device is unlocked")
-------------------------------------------
Click to expand...
Click to collapse
Good Idea. Keep it alive. I just have my bootloader unlocked, no root, no custom recovery, so no experience from my side ?
Phh Treble
https://forum.xda-developers.com/pr...opment/experimental-phh-treble-t3709659/page1
-Not working: NFC, Volte, Hotspot
burgess_boy said:
Phh Treble
https://forum.xda-developers.com/pr...opment/experimental-phh-treble-t3709659/page1
-Not working: NFC, Volte, Hotspot
Click to expand...
Click to collapse
I thought hotspot was fixed a while ago, I tried Phh but went to back to EMUI but I don't recall having hotspot broken
You all have fingerprints working on these roms?
Fingerprints were not getting stored....
deepsrd said:
You all have fingerprints working on these roms?
Fingerprints were not getting stored....
Click to expand...
Click to collapse
No I do not think that works for any Treble Rome yet
Not treble rom per se.. ..
But grab Luk's P20 Pro rom, and extract the system.img from it and flash on the P20.
Works great.. (including fingerprints)
NFC does not work..
Cheers!
To install treble rom i need unlocked bootloader?
g_oral said:
To install treble rom i need unlocked bootloader?
Click to expand...
Click to collapse
Yes, unfortunately you do
Schubi97 said:
Havoc 1.0
- https://sourceforge.net/projects/ha...oc-arm64_aonly_vanilla_nosu-0819.zip/download
- For me the best UI ever (a lot like Android P)
-> Not Working:
- Fingerprint Scanner, automatic brightness adjustment (fix: https://forum.xda-developers.com/pr.../overlay-enable-night-light-adaptive-t3741965 )
-> Working:
- everything else
(if you want me to check some specific just ask )
-------------------------------------------
Click to expand...
Click to collapse
How are you installing Havoc 1.0, the link you have added is for Kirin 960 devices. Did you extract the firmware file?
burgess_boy said:
How are you installing Havoc 1.0, the link you have added is for Kirin 960 devices. Did you extract the firmware file?
Click to expand...
Click to collapse
Just download the file Havoc-arm64_aonly_vanilla_nosu-0819.zip on https://sourceforge.net/projects/havoc-os/files/arm64aonly/
- Extract it
- and flash the .img file
Schubi97 said:
Just download the file Havoc-arm64_aonly_vanilla_nosu-0819.zip on https://sourceforge.net/projects/havoc-os/files/arm64aonly/
- Extract it
- and flash the .img file
Click to expand...
Click to collapse
I've tried flashing with fastboot commands and can't boot. I'll try with TWRP.
UPDATE: Flashed successfully, however I get a vendor img mismatch error. Is this normal?
burgess_boy said:
I've tried flashing with fastboot commands and can't boot. I'll try with TWRP.
Click to expand...
Click to collapse
Are you sure you've downloaded the correct version not the PIE one?
Stuck it on Bootscreen?
If yes did you erased Data in TWRP?
Schubi97 said:
Are you sure you've downloaded the correct version not the PIE one?
Stuck it on Bootscreen?
If yes did you erased Data in TWRP?
Click to expand...
Click to collapse
Yeh I was flashing the Android Pie system file. Did you get a vendor img mismatch message on boot. Also which package of gapps did you install with this rom.
burgess_boy said:
Yeh I was flashing the Android Pie system file. Did you get a vendor img mismatch message on boot. Also which package of gapps did you install with this rom.
Click to expand...
Click to collapse
Yeah i do so but that isn't a problem for me.
For Gapps: "Mind the Gapps" https://androidfilehost.com/?fid=3700668719832236382
Schubi97 said:
Yeah i do so but that isn't a problem for me.
For Gapps: "Mind the Gapps" https://androidfilehost.com/?fid=3700668719832236382
Click to expand...
Click to collapse
Havoc OS 1.0 works extremely well and I am very impressed with it. It also has a vast amount of Android P UI features already built in which is impressive for an 8.1 rom.
The only issue I have had, which I am monitoring, is that some apps randomly crash. A reboot appears to fix this issue.
burgess_boy said:
Havoc OS 1.0 works extremely well and I am very impressed with it. It also has a vast amount of Android P UI features already built in which is impressive for an 8.1 rom.
The only issue I have had, which I am monitoring, is that some apps randomly crash. A reboot appears to fix this issue.
Click to expand...
Click to collapse
I do not have that problem..
Did you make a clean flash ("erase data" and "factory reset" after flashing)
Schubi97 said:
I do not have that problem..
Did you make a clean flash ("erase data" and "factory reset" after flashing)
Click to expand...
Click to collapse
Seems to have worked itself out l, I did erase data and factory reset. How did you find battery life? Seems to be discharging a lot quicker than stock. I've got better battery stats set up to investigate.
burgess_boy said:
Seems to have worked itself out l, I did erase data and factory reset. How did you find battery life? Seems to be discharging a lot quicker than stock. I've got better battery stats set up to investigate.
Click to expand...
Click to collapse
Did you install the overlay mentioned in my first post?
This fixed my problems with the battery
Schubi97 said:
Did you install the overlay mentioned in my first post?
This fixed my problems with the battery
Click to expand...
Click to collapse
Thanks, I had installed it but found out it was working correctly. Changed file permissions and everything is working.