3.18 kernel development
Source: link
What works / not work:
K05TS - 1st version P8000: fingerprint and mainspeaker not working (sound is working with headphone or during a call)
K05TE - 2nd version P8000: maybe mainspeaker problems
K06TE - 3rd version P8000: everything work well
Some technical background:
K05TS - 1st version P8000: Lollipop bootloader
K05TE - 2nd version P8000: Marshmallow bootloader version 1
K06TE - 3rd version P8000: Marshmallow bootloader version 2
You can flash all stock rom to all devices.
If you flash a custom recovery or a custom kernel you have to use matching bootloader.
3.10 custom kernel = Lollipop bootloader
3.18 custom kernel = Marshmallow bootloader version 2
there are no custom kernel for bootloader marshmallow version 1 (k05te) - no kernel source
!!!!! Backup IMEI first !!!
Kernel will work only with Roms that based on K06TE.
You have to flash the stock Android 6 from K06TE first.
After this bootloader is matching to k06te based kernel.
Download: Stock K06TE Android 6.0 rom
Unlock bootloader and flash recovery.
I need some help to fix the audio routing.
Sound works well on K05TS with Stock Android 6.0 from K05TE Android 6.0 but there is no kernel source
!! boot.img-kernel.img = zimage = kernel only !!
@walter79
K05TE - 2nd version P8000: maybe mainspeaker problems ---> FingerPrint Sensor is working for this version?
boka18 said:
@walter79
K05TE - 2nd version P8000: maybe mainspeaker problems ---> FingerPrint Sensor is working for this version?
Click to expand...
Click to collapse
Dont know. Some should test it.
walter79 said:
Dont know. Some should test it.
Click to expand...
Click to collapse
Neither the recovery nor the boot img (kernel) works for K05TE - 2nd version P8000.
When I flash the recovery nothing changes (looks like the stock recovery), when i flash boot.img (through other recovery) I get bootloop.
Flashed this on my K06TE with the stock 6.0 rom - everything works (including fingerprint), but there is a wake up bug where most of the time instead of showing the lock screen the phone just lights up black, then goes back to sleep. Takes about 2-4 tries for the actual lock screen to show up.
lostmysaves said:
Flashed this on my K06TE with the stock 6.0 rom - everything works (including fingerprint), but there is a wake up bug where most of the time instead of showing the lock screen the phone just lights up black, then goes back to sleep. Takes about 2-4 tries for the actual lock screen to show up.
Click to expand...
Click to collapse
Maybe display wakeup delay is to short.
https://github.com/walter79/android...mmit/7e2a8d33a3b7c0ccc416efdf456a79e94b231239
We should test 200 ms.
Edit:
New kernel with 200 ms uploaded. Only for k06te.
boka18 said:
Neither the recovery nor the boot img (kernel) works for K05TE - 2nd version P8000.
When I flash the recovery nothing changes (looks like the stock recovery), when i flash boot.img (through other recovery) I get bootloop.
Click to expand...
Click to collapse
You have to flash stock Android 6 from K06TE first !!
walter79 said:
Maybe display wakeup delay is to short.
https://github.com/walter79/android...mmit/7e2a8d33a3b7c0ccc416efdf456a79e94b231239
We should test 200 ms.
Edit:
New kernel with 200 ms uploaded. Only for k06te.
Click to expand...
Click to collapse
Still the same problem, though now it seems to work every other time (like blackscreen-lockscreen-blackscreen-lockscreen and so on).
lostmysaves said:
Still the same problem, though now it seems to work every other time (like blackscreen-lockscreen-blackscreen-lockscreen and so on).
Click to expand...
Click to collapse
Can you test 400ms ?
walter79 said:
Can you test 400ms ?
Click to expand...
Click to collapse
It seemed ok at first but after like 20 button presses the black screen happened again
After that i decided to spam the button faster (in the name of science) and got a weird graphical glitch that looked like some liquid being poured inside the screen lol. Might be a different problem, i dunno.
I cant replicate any of these problems on stock boot and i just noticed that the wakeup delay is noticeably longer on it. Maybe try 800ms?
lostmysaves said:
It seemed ok at first but after like 20 button presses the black screen happened again
After that i decided to spam the button faster (in the name of science) and got a weird graphical glitch that looked like some liquid being poured inside the screen lol. Might be a different problem, i dunno.
I cant replicate any of these problems on stock boot and i just noticed that the wakeup delay is noticeably longer on it. Maybe try 800ms?
Click to expand...
Click to collapse
600ms
walter79 said:
You have to flash stock Android 6 from K06TE first !!
Click to expand...
Click to collapse
r u surw? wont i brick it?
The kernel installed through TWRP?
boka18 said:
r u surw? wont i brick it?
Click to expand...
Click to collapse
I flashed all Stock roms on my K05TS and i have no problems to go back to a working rom.
You have to know how to restore your EMEI. It is possible that you can maybe lost it during flashing different stock roms.
Supervaiser said:
The kernel installed through TWRP?
Click to expand...
Click to collapse
Yes. or via fastboot if you bootloader is unlock.
walter79 said:
I flashed all Stock roms on my K05TS and i have no problems to go back to a working rom.
You have to know how to restore your EMEI. It is possible that you can maybe lost it during flashing different stock roms.
Yes. or via fastboot if you bootloader is unlock.
Click to expand...
Click to collapse
I did everything as u said and it works. The wake-up bug is gone! Wow Good job!
Bug - Fingerprint sensor not found (as default).
One question: Will the battery bug with the 15% problem drop remain?
boka18 said:
I did everything as u said and it works. The wake-up bug is gone! Wow Good job!
Bug - Fingerprint sensor not found (as default).
One question: Will the battery bug with the 15% problem drop remain?
Click to expand...
Click to collapse
k05te ? or k05ts ? or k05ts updated to k06te or k05ts updated to k06te ?
15% bug not testet
walter79 said:
k05te ? or k05ts ? or k05ts updated to k06te or k05ts updated to k06te ?
15% bug not testet
Click to expand...
Click to collapse
5te updated to 6te
But i did not managed to install recovery. something went wrong so i reflashed 5te android 6, put recovery and restore los13.
Can you provide recovery that works with 6te?
boka18 said:
5te updated to 6te
But i did not managed to install recovery. something went wrong so i reflashed 5te android 6, put recovery and restore los13.
Can you provide recovery that works with 6te?
Click to expand...
Click to collapse
Did you flash k06te MM Rom. ? Recovery is attached in first post. Did you Fingerprint ever worked with a stock rom?
walter79 said:
Did you flash k06te MM Rom. ? Recovery is attached in first post. Did you Fingerprint ever worked with a stock rom?
Click to expand...
Click to collapse
nope. never worked the fs.
walter79 said:
600ms
Click to expand...
Click to collapse
I put on the core K06TE stock Android 6.0. No error awakening. fingerprint scanner works. Sound works. WiFi and BT work. Others no errors. I will be tested for battery failure after 15%
Related
REMOVED PROJECT
XDA:DevDB Information
AOSP For The Huawei P10 Lite, ROM for the Huawei P10 Lite
Contributors
Meticulus
Source Code: http://github.com/Meticulus/android_kernel_huawei_hi6250_4.1
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked Bootloader/ My TWRP / Knowlege of dload method.
Based On: AOSP
Version Information
Status: Testing
Created 2017-12-10
Last Updated 2018-01-18
My device is WAS-LX1A , 4 GB , Dual sim.
My experience till now :
After full wipe and format /data in TWRP, ROM booted normally. (surprisingly fast, took only few minutes)
Flashed the latest supersu from chainfire, root is working.
As suggested by dev, rear video camera recording with Open camera works. With fps set at 25.
Finger print is working, GPS too.
Didn't encounter problems with "Tap and pay" NFC payments.
Titanium backup restored my apps+data backups from MIUI 5.1 without any issues.
Flashed xposed and installed gravitybox and APM+.
Using this ROM for 2 days now. Can't say much yet about battery usage.
I have some issues with delayed whatsapp messages. But had this with other phones and rom's too.
Untill now had only 1 random reboot.
In TWRP made backup. Selected everything except /cache.
With 3 button dload method i was able to go back to stock rom :
https://forum.xda-developers.com/p10-lite/help/original-service-rom-huawei-p10-lite-t3688097 - WAS-LX1C432B182
After booting stock rom, unlocked bootloader again, flashed TWRP and then tried to restore the backup.
Got a 255 error. So i did a full wipe and formatted /data.
After this succesfully restored the backup and phone booted normally with everything intact.
So, internal storage is not encrypted in TWRP.
Rom is pretty smooth. Didn't encouter any issues. Except the known bugs.
Looks like someone is doing some kernel work: https://github.com/RRM5/P10Lite
Meticulus said:
Looks like someone is doing some kernel work: https://github.com/RRM5/P10Lite
Click to expand...
Click to collapse
hehehe, I'm still experimenting, I come from SD and with kirin I'm still trying things hehehe, @Meticulusculus.:good:
dieg00 said:
hehehe, I'm still experimenting, I come from SD and with kirin I'm still trying things hehehe, now I'm trying to compile RR with your sources @miciculus.:good:
Click to expand...
Click to collapse
Sorry bud, already uploading RR...
Meticulus said:
Sorry bud, already uploading RR...
Click to expand...
Click to collapse
ok no problem, I get the kernel hehehe:good: , good jobs!.
RR UP : https://forum.xda-developers.com/p10-lite/development/rom-resurrection-remix-hi6250-devices-t3717360
On RR the Sim Card is not working and on AOSP the Sound is not working :/
Any ideas how to fix this?
I'm using a WAS-LX1
And on AOSP for me, sound works though Using WAS-LX1A
EDIT: Got SIM working by disabling dual sim under "Extra"
Zillinda said:
On RR the Sim Card is not working and on AOSP the Sound is not working :/
Any ideas how to fix this?
I'm using a WAS-LX1
Click to expand...
Click to collapse
I noticed that when you scan a QR code in landscape mode, the screen stays in landscape. Untill you close the new window.
Thanks for your work! I just buy my phone about 2 weeks ago, just waiting a while to be sure everithing is ok before void warranty and start trying your rom.
jekblub said:
And on AOSP for me, sound works though Using WAS-LX1A
EDIT: Got SIM working by disabling dual sim under "Extra"
Click to expand...
Click to collapse
But i think there are no hardware differences between WAS-LX1 and WAS-LX1A except the RAM, so it should work for me too :/
Does it work on WAS-TL10?
Installed on my LX1C, every function seems to work just fine, only thing is the framerates for the animations are ussualy really low (in the 20-ish)
Otherwise quite a good ROM.
This is great, I just traded my Xiaomi redmi pro for p10 lite and although is has a slower CPU and GPU, its way better optimized. Can't wait for stable aosp. Great job
If P10 Lite gets treble with Android O (The mate 9 does have it) we will have a much stable ROM
I've got a problem. Touchscreen is unresponsive with developer's twrp (was-lx1). I've tried to reboot recovery and reflash but no success
working great for me on WAS-LX3 with exception for connecting to bluetooth took forever the first time and I thought the phone was locked up, it eventually loaded and works fine.
Steps to restore to your STOCK ROM
Guys in case If you annoyed with the bugs in the Custom ROM which is uder development Stage and if you can't wait still the stable version, then cool you can always restore your sock ROM at any stage and try the Custom ROM after a stable release .
Watch this video to restore your stock ROM with simple steps .
[ If you can understand the video below than you can try any ROM without any hesiation , as you can return to your STOCK anytime , but if you can't understand the video Below ,then you may be at risk , Proceed with caution ! ]
https://youtu.be/0vDgDXePAR4
Don't forget to upvote if you find this useful
Please do this for the normal P10 please, can't i flash this on the P10?
Hi,
I have search around but do not find what should be done with twrp in order to keep miui for ota with normal install.
I want to flash a kernel on miui.
Shall i keep read only ?
Shall i disable dm-verity ?
I already went once after flashing magisk to screen please enter Android password. Reboot solve the issue by the way.
Thanks
there is a kernel for miui roms? the only one I saw were for aosp / lineage
gohan456 said:
there is a kernel for miui roms? the only one I saw were for aosp / lineage
Click to expand...
Click to collapse
Blackbox kernel - currently brightness issue
rodolphe06 said:
Blackbox kernel - currently brightness issue
Click to expand...
Click to collapse
Blackbox is for AOSP, not MIUI...
Ok so i finally just flashed no name kernel without anything else and all ok.
Gonna try also bb
AnTuTu 95k...
On internet they spotted 112k
Edit:
It seems it broke something as i Can not anymore call.
I tried to restore boot but i Can only Receive call now.
Error sim is displayed.
What Can i do ?
Factory reset ?
rodolphe06 said:
AnTuTu 95k...
On internet they spotted 112k
Edit:
It seems it broke something as i Can not anymore call.
I tried to restore boot but i Can only Receive call now.
Error sim is displayed.
What Can i do ?
Factory reset ?
Click to expand...
Click to collapse
Dude, we are telling you 3rd time, its for AOSP roms. Of course it broke something, its for AOSP, not for MIUI.
rodolphe06 said:
AnTuTu 95k...
On internet they spotted 112k
Edit:
It seems it broke something as i Can not anymore call.
I tried to restore boot but i Can only Receive call now.
Error sim is displayed.
What Can i do ?
Factory reset ?
Click to expand...
Click to collapse
Reflash the stock rom.After that if you want to flash any custom kernels then try blackbox kernel(latest one).It supports MiUi roms
Incogn said:
Dude, we are telling you 3rd time, its for AOSP roms. Of course it broke something, its for AOSP, not for MIUI.
Click to expand...
Click to collapse
No offence but You are telling wrong:
Blackbox 1.3 support miui (see OP)
Noname has a miui version shared in telegram owner group
(Sorry for my bad english)
This Rom is the OFFICIAL 8.1 STOCK rom, heavly debloated and flasheable via TWRP. Based on J730FM but functional on any J730XX
Instructions (twrp)
1-download zip
2-wipe cache, system and data
3-flash the rom
Kernel: STOCK
BUGS WITH STOCK Kernel J730G: Fingerprint and bluethoot.
If anyone can help fixing those bugs we would all appreciate it.
TIP: The rom work perfectly with Helios Kernel by Ananjaser
DOWNLOAD: https://drive.google.com/file/d/1dK3r720bEENQKYgnZB6hsDTwVfKxJI-F/view
Credits: Miguel Escalante
This link is for STOCK 8.1 ROM WITH ALL BLOATWARE. But works perfectly
Link: https://mega.nz/#!z0MSwQIZ!Kp1nVdfo8YxXuuFu45sMlKsBt3QaSjZJBxIOwlnJGME
Man, I'm on stock kernel, but no problems with fingerprint and bluetooth, no problems with usb or anything. What's wrong with custom rom?
ion1s said:
Man, I'm on stock kernel, but no problems with fingerprint and bluetooth, no problems with usb or anything. What's wrong with custom rom?
Click to expand...
Click to collapse
You are on This Rom? And you no have bugs?
I'm on stock 8.1.0 from J730FM and I have J730F, but everything works fine with stock kernel.
ion1s said:
I'm on stock 8.1.0 from J730FM and I have J730F, but everything works fine with stock kernel.
Click to expand...
Click to collapse
The bugs is in J730G
Where did you get the official 8.1 rom from?
quanghuy226 said:
Where did you get the official 8.1 rom from?
Click to expand...
Click to collapse
From J730FM
lite rom with (1,3GB)
xloolx said:
lite rom with (1,3GB)
Click to expand...
Click to collapse
Hi, I'm Miguel Escalante.
A super lite version (1.1Gb) you can find in EDOS V2.
In this rom there are many features (themes without limit time, goodloock, call records, etc), you can see in this post
https://forum.xda-developers.com/ga...m-oreo-8-1-j7-pro-exynos-7870-f-fm-g-t3842058
will it work on j730gm???
sgrkoirala said:
will it work on j730gm???
Click to expand...
Click to collapse
My girlfriend have this model and dont have problems
sgrkoirala said:
will it work on j730gm???
Click to expand...
Click to collapse
yes, its working and i am using J730gm only
So if i used helios kernel, bluetooth and fingerprint will work in my j730g? Is that what you mean?
eugene15 said:
So if i used helios kernel, bluetooth and fingerprint will work in my j730g? Is that what you mean?
Click to expand...
Click to collapse
Everything is working fine when you install Helio kernel along with the rom
can fix it the touchscreen issue?
Princepaul12 said:
can fix it the touchscreen issue?
Click to expand...
Click to collapse
I am using this rom for a week and i dont encounter any problems bro. Volte(Jio) is working very good and there is no touch screen issues still
From time to time loudsreaker is silent! Helps only to tern off and then tern on/
works excellent Thanks !
I have a J7 2017 (J730F) and it does not let me flinch by Odin but I do through TWRP and I would like to know if I can somehow convert the 4 files of the original stock ROM into a single file flashed by TWRP.
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.
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.