Develop Bugs

[ROM][5.1.1] CM12.1 Official Nightlies for Find 7A/S

Hello all
Official CM 12.1 nightlies based on Android Lollipop 5.1.1 for Find 7A/S have been officially released effective 22nd April 2015. Its time to thank the entire CyanogenMod Team and @[U]jajb[/U] for their efforts in the development and encourage them to keep supporting us the same way in the future.
Let the flashing go on!!!!:highfive:
Nightly Downloads
CM12.1 Find 7A
http://download.cyanogenmod.org/?device=find7
CM12.1 Find 7S (QHD)
http://download.cyanogenmod.org/?device=find7s
5.1 Minimal Gapps (for a light and blazzing fast experience):highfive:
https://www.androidfilehost.com/?fid=95916177934550851
Installation Instructions
Coming from 5.0 or less ROMS
Download cm-12.1-xxxxxxxx-NIGHTLY-find7x.zip to your sdcard
Boot into Recovery
Wipe data, cache & dalvik cache
Flash cm-12.1-xxxxxxxx-NIGHTLY-find7x.zip from sdcard
Flash 5.1 Minimal GApps.zip from sdcard
Reboot:highfive:
Coming from previous CM 12.1 build
Wipe cache & dalvik cache
Flash cm-12.1-xxxxxxxx-NIGHTLY-find7x.zip from sdcard
Reboot:highfive:

Somebody successfully flashed it ? It works ?

raber111 said:
Somebody successfully flashed it ? It works ?
Click to expand...
Click to collapse
It doesn't work. http://forum.xda-developers.com/showpost.php?p=58255547&postcount=397
I tried to flash the last CM11 build and I'm still stucked there.

Anyone tried 20150119 build yet? is it working??

CyanPile said:
Anyone tried 20150119 build yet? is it working??
Click to expand...
Click to collapse
It seems so, but wifi is terribly slow.

It's going to be announced soon in CM's blog, but find7a and find7s are split now and get separate builds. You need to flash "find7" on find7a devices and "find7s" on find7s qhd devices. You should update the recovery too, but I think there are no recovery images available yet. I might provide some if nobody else does it.

I successfully flashed cm 12 1901 build . WiFi works normally. Fonts and icons too small

on 2.0.4
Can we flash this on color os 2.0.4 version without any issues or have to downgrade to 1.2.7

sheraz1015 said:
Can we flash this on color os 2.0.4 version without any issues or have to downgrade to 1.2.7
Click to expand...
Click to collapse
You will have to flash it over 1.2.x Color OS. I flashed 19 build over 1.2.7.
Installed without an issue.
For QHD use Find 7s version.

mikeioannina said:
It's going to be announced soon in CM's blog, but find7a and find7s are split now and get separate builds. You need to flash "find7" on find7a devices and "find7s" on find7s qhd devices. You should update the recovery too, but I think there are no recovery images available yet. I might provide some if nobody else does it.
Click to expand...
Click to collapse
Thank for your
help and shall flash it.
Its there any way to backup imei of oppo find 7
ganeshbiyer said:
You will have to flash it over 1.2.x Color OS. I flashed 19 build over 1.2.7.
Installed without an issue.
For QHD use Find 7s version.
Click to expand...
Click to collapse
Sent from my LG-D802 using XDA Premium 4 mobile app

You can always use tantrums recovery flasher...they recently updated to v10.....has all the latest recoveries

Anyone having problems when using unified partition layout? After I flashed the ROM the phone just tells me that there's an encryption error and I have to wipe data. I wiped data and still the same error. When I went back to previous ROM I'm using everything else is fine, except with the proximity sensor bug. Cheers

darthbadar said:
Anyone having problems when using unified partition layout? After I flashed the ROM the phone just tells me that there's an encryption error and I have to wipe data. I wiped data and still the same error. When I went back to previous ROM I'm using everything else is fine, except with the proximity sensor bug. Cheers
Click to expand...
Click to collapse
De-unify first, then flash. You need to have to revert back to 1.2.x.
Flash Open TWRP and then flash CM12 Nightlies. COs 1.2.x and CM12 do not support Unification.

ganeshbiyer said:
De-unify first, then flash. You need to have to revert back to 1.2.x.
Flash Open TWRP and then flash CM12 Nightlies. COs 1.2.x and CM12 do not support Unification.
Click to expand...
Click to collapse
Soo, there's no way I'm using CM12 Nightlies with unified storage? Thanks for answering man. :highfive:

Changelog ?
changelog here http://www.cmxlog.com/12/find7/
and here http://www.cmxlog.com/12/find7s/

Chrome
Is the only way to switch between tabs the recent apps thingy? I mean I don't habe a problem but still kinda awkward not knowing where the tab went. BTW I got twrp 2.8.4 and there's always this horizontal line where the display shifts. It's like these lines on old videos that walk through the picture. Trying my best on English (I'm German )

alex1.salge said:
Is the only way to switch between tabs the recent apps thingy? I mean I don't habe a problem but still kinda awkward not knowing where the tab went. BTW I got twrp 2.8.4 and there's always this horizontal line where the display shifts. It's like these lines on old videos that walk through the picture. Trying my best on English (I'm German )
Click to expand...
Click to collapse
Regarding the line in recovery, use Nameless TWRP recovery from HERE.
I have not tried the latest TWRP Open Recovery 2.8.4 for Find7, but with Nameless TWRP Recovery, I am able to use OTG in recovery. This allows me to take backups into 32gb usb drive and restore from there.

Custom Ringtones
Hello Just flashed to build 2015/01/21 and I noticed that I was unable to change my ringtone. This may seem like a trivial thing but I would just like to know if it's my device specific. Find 7a running CM12 stock kernels and all.
Edit: Turned off NuPlayer in developers options and set SELinux Kernel to Permissive.

Enyioha said:
Hello Just flashed to build 2015/01/21 and I noticed that I was unable to change my ringtone. This may seem like a trivial thing but I would just like to know if it's my device specific. Find 7a running CM12 stock kernels and all.
Edit: Turned off NuPlayer in developers options and set SELinux Kernel to Permissive.
Click to expand...
Click to collapse
sorry for noob question
how can I change SELinux Kernel to Permissive ?

Missing languages
In the 21/01 build, some languages are missing - texts simply do not appear and the language list is empty near the end.
EDIT:
23/01 build solves it.
EDIT2:
Gyro doesn't work, screen doesn't rotate.

Has anyone tried DirtyUnicorns?

Seems that there are DU builds for the HTC 10 (pme). Here: https://download.dirtyunicorns.com/pme/
Has anyone tried them? If yes, what are your impressions? :laugh:

errikosd said:
Seems that there are DU builds for the HTC 10 (pme). Here: https://download.dirtyunicorns.com/pme/
Has anyone tried them? If yes, what are your impressions? :laugh:
Click to expand...
Click to collapse
It is AOSP based compared to LOS (CM) which the majority of the ROMs posted are.
DU is a great ROM. I found that it lacked some important features that I like, but a very solid ROM.

Yes i tried on Sprint but there was no data...even after entering the apn in

errikosd said:
Seems that there are DU builds for the HTC 10 (pme). Here: https://download.dirtyunicorns.com/pme/
Has anyone tried them? If yes, what are your impressions? :laugh:
Click to expand...
Click to collapse
Encryption was not working, even with a full data format prior to flashing.
Any other opinions?

I have been running the weekly and official builds with nebula eas kernel for about 5 weeks or so. I personally feel its the best non-sense based ROM for my usage. It does lack some customisations most others have but makes up for it by being super stable, fast, battery friendly and just works as its supposed to with bull. I use superSU, substratum and A.R.I.S.E audio mod with selinux permissive without dramas.

mrrflagg said:
I have been running the weekly and official builds with nebula eas kernel for about 5 weeks or so. I personally feel its the best non-sense based ROM for my usage. It does lack some customisations most others have but makes up for it by being super stable, fast, battery friendly and just works as its supposed to with bull. I use superSU, substratum and A.R.I.S.E audio mod with selinux permissive without dramas.
Click to expand...
Click to collapse
Does it come with root or Magisk out of the box?
To reverse the question, can I use it as clean Android without root, passing SafetyNet? Thanks!

errikosd said:
Does it come with root or Magisk out of the box?
To reverse the question, can I use it as clean Android without root, passing SafetyNet? Thanks!
Click to expand...
Click to collapse
It comes WITHOUT root. So you can choose your preffered method or no root at all.
I don't know about safetynet as I am not using android pay or anything that relies on it to pass.
Also I have not had any encryption issues as someone earlier replied

mrrflagg said:
I have been running the weekly and official builds with nebula eas kernel for about 5 weeks or so. I personally feel its the best non-sense based ROM for my usage. It does lack some customisations most others have but makes up for it by being super stable, fast, battery friendly and just works as its supposed to with bull. I use superSU, substratum and A.R.I.S.E audio mod with selinux permissive without dramas.
Click to expand...
Click to collapse
What firmware and TWRP Version are you using with it ? With the Nougat firmware and latest TWRP, I get the encryption issue..

Scutariu said:
What firmware and TWRP Version are you using with it ? With the Nougat firmware and latest TWRP, I get the encryption issue..
Click to expand...
Click to collapse
401.4 FW and 3.1.0 TWRP. What kind of encryption issue? I did have once only rebooted into recovery and it asked for the password but I just rebooted in recovery from TWRP and it never happened again.

mrrflagg said:
401.4 FW and 3.1.0 TWRP. What kind of encryption issue? I did have once only rebooted into recovery and it asked for the password but I just rebooted in recovery from TWRP and it never happened again.
Click to expand...
Click to collapse
I've tried several combinations, with older/latest firmware.
Every time, It would ask for the encryption password on bootup.
Even if I haven't set one up.. With data format prior to installing
Anyway, got sick of re-setting apps on my phone, just installed Maximus HD ROM, and that's that ?

Dirty Unicorns
errikosd said:
Seems that there are DU builds for the HTC 10 (pme). Here: https://download.dirtyunicorns.com/pme/
Has anyone tried them? If yes, what are your impressions? :laugh:
Click to expand...
Click to collapse
The 4-8-17 build is Android 7.1.2 and so far it is running really well. I am surprised that there​ is not a thread in the ROM section for DU.

morr22066 said:
The 4-8-17 build is Android 7.1.2 and so far it is running really well. I am surprised that there​ is not a thread in the ROM section for DU.
Click to expand...
Click to collapse
I think it was the DU team's decision to close all and not allow any XDA threads. Someone correct me if I am wrong.
No idea why though.

morr22066 said:
The 4-8-17 build is Android 7.1.2 and so far it is running really well. I am surprised that there​ is not a thread in the ROM section for DU.
Click to expand...
Click to collapse
A quick question.
What variant , firmware and TWRP are you using?
Everytime I try that rom..it encrypts itself with an unknown password, and upon restart I'm unable to access my phone

Encryption
Scutariu said:
A quick question.
What variant , firmware and TWRP are you using?
Everytime I try that rom..it encrypts itself with an unknown password, and upon restart I'm unable to access my phone
Click to expand...
Click to collapse
I have had that happen when switching from a sense based ROM to LOS or AOSP and it's a "pita"... Anything that I want to keep gets moved to my SD card before I reboot to recovery.
I read through several threads and tried several possible solutions so I can't remember exactly which one worked.
I am currently on Verizon, official Nougat with the flashed us unlocked "patch", TWRP 3.1.0-1. If you are on Verizon or Sprint you need to patch the image with a missing image that is found in the us unlocked model (there are threads discussing it where you can find the file).

LOS
Scutariu said:
A quick question.
What variant , firmware and TWRP are you using?
Everytime I try that rom..it encrypts itself with an unknown password, and upon restart I'm unable to access my phone
Click to expand...
Click to collapse
The Lineage is wiki spells things out pretty well.
https://wiki.lineageos.org/devices/pme/install
Here is another thread on twrp issues
https://forum.xda-developers.com/htc-10/how-to/guide-fix-pin-pattern-password-t3538438

morr22066 said:
The Lineage is wiki spells things out pretty well.
https://wiki.lineageos.org/devices/pme/install
Click to expand...
Click to collapse
It was not related to the data partition.
The format user data was done prior and after flashing it.

There is a DU Oreo-based build for the HTC 10: https://download.dirtyunicorns.com/?device=pme
For the time being it is under "RC". Downloading now, will report back!
Edit: ROM is very nice and is flying by. Only downside is that camera app is VERY slow... Also, woofer is not working (as expected).
What I like the most is that it is AOSP, i.e. no LineageOS stuff like AudioFX, etc. Customisation features are nice and the experience is close to Pixel with Stock OpenGapps. If the camera app is fixed, then this would be perfect (I believe it will, since this is the first RC release)!
Further notes: Capacitive buttons backlight is off by default (can't find any standard option to turn on, maybe with a kernel tool?) and notification LED does not work either. Don't mind for the capacitive buttons too much, but the LED is a real problem.

errikosd said:
There is a DU Oreo-based build for the HTC 10: https://download.dirtyunicorns.com/?device=pme
For the time being it is under "RC". Downloading now, will report back!
Edit: ROM is very nice and is flying by. Only downside is that camera app is VERY slow... Also, woofer is not working (as expected).
What I like the most is that it is AOSP, i.e. no LineageOS stuff like AudioFX, etc. Customisation features are nice and the experience is close to Pixel with Stock OpenGapps. If the camera app is fixed, then this would be perfect (I believe it will, since this is the first RC release)!
Further notes: Capacitive buttons backlight is off by default (can't find any standard option to turn on, maybe with a kernel tool?) and notification LED does not work either. Don't mind for the capacitive buttons too much, but the LED is a real problem.
Click to expand...
Click to collapse
Yea I'm having that sane problem with the touch key lights not working n it bothers me a bit. I didn't notice if the led was working or not. Keep me posted if u figure out the the key problem plz.

[ROM][H930(G)/US998][Oreo][8.0.0] Stock debloated Oreo for H930 [v1.01]

Welcome to the first WORKING Oreo based Custom ROM for the H930
THEORY OF EVERYTHING
INTRODUCTION
Welcome to my first FULLY working ROM, this time its a stock based Oreo ROM based off of the V300L21b firmware.
This ROM is a bit debloated, meaning mainly all the korean apps are gone (a full list of debloated apps is in post #2).
The name of the ROM is from @einhuman197 (Tobs) from the V30 Telegram group
I think thats a good name (as I am myself a physics student, and a real admirer of Stephen Hawkins work).
FEATURES
debloated (some google apps like sheets, slides... and korean ones)
removed automatic encryption (even "normal" encryptable forced an encryption for me, so removed that alltogether)
1. March security patch
ThinQ update (AI Camera and all that)
WORKING
everything
NOT WORKING
tell me
FLASH INSTRUCTIONS
Make sure your /data isnt encrypted though. I dont know how it will react if the ROM finds an encrypted /data partition, as I disabled it alltogether (****ed it up for me, even though forcencryption was off)
Download ROM + (potential) hotfix
Copy it on your sdcard/internal memory
Boot into TWRP
Make a Backup of Boot/System/Data/Cache
Wipe /system, /data, /cache, /dalvik/cache in TWRP
Flash .zip file(s)
SCREENSHOTS
see attachment
​
DOWNLOAD
V1: https://www.androidfilehost.com/?fid=746010030569964396
V1.01 Hotfix: https://www.androidfilehost.com/?fid=890129502657593599
XDA:DevDB Information
V300L21b Stock debloated for H930, ROM for the LG V30
Contributors
SGCMarkus
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Kernel Source: https://github.com/SGCMarkus/android_kernel_lge_msm8998/tree/lge-oreo
Based On: V300L21b
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2018-03-24
Created 2018-03-24
Last Updated 2018-03-24

CHANGELOG
V1. Initial Release
Debloated
Custom exfat driver (stock sources dont provide one)
V1.01 Fingerprint Hotfix update
Fixed fingerprint (using fingerprint.msm8998.so from nougat to match firmware version)
FAQ
Does this also work on the US998?
Seems to work fine, but some bands seem to be not working (for Verizon, maybe missing APNs? needs more testing)
Is the ROM already rooted?
No, but Im using Magisk 16.2 myself, so you can flash that afterwards
How do i restore to my previous ROM or go to another ROM?
Reboot into TWRP, wipe system, data, cache (do not format data if you wanna keep your internal memory), and restore your backup, or flash another ROM.
Warning: DO NOT USE LG UP TO RESTORE NOUGAT WITHOUT PERFORMING A FACTORY RESET BEFORE, YOU MIGHT END UP IN A BOOTLOOP

List of debloated Apps
Code:
[LIST]
[*]system/app/Drive*
[*]system/app/Duo*
[*]system/app/EditorsDocs*
[*]system/app/EditorsSheets*
[*]system/app/EditorsSlides*
[*]system/app/Facebook_AppManager*
[*]system/app/FidoASM*
[*]system/app/FidoAuthenticator*
[*]system/app/FidoClient*
[*]system/app/FidoCryptoService*
[*]system/app/FidoService*
[*]system/app/Gmail2*
[*]system/app/LGAccount*
[*]system/app/LGAirDrive*
[*]system/app/LGFOTA*
[*]system/app/lguplus-permission*
[*]system/app/lguplusp_mcc
[*]system/app/Maps*
[*]system/app/UBox*
[*]system/app/UplusTVonPhone*
[*]system/app/USIM_Agent*
[*]system/app/UsimOTAKR*
[*]system/app/UVSService*
[*]system/app/CNasTermsApp*
[*]system/app/CNasManagerService*
[*]system/app/CNasMainApp*
[*]system/priv-app/Facebook_Installer*
[*]system/priv-app/LGAirDriveSetting*
[*]system/priv-app/LGBackup*
[*]system/priv-app/LGBackupLauncher*
[*]system/priv-app/LGPay*
[*]system/priv-app/LGPay_QLauncher*
[*]system/priv-app/LGQHelpService*
[*]system/priv-app/ONEStoreClient*
[*]system/priv-app/ONEStoreService*
[*]system/priv-app/LGTDMB*
[*]system/priv-app/LG_PushAgent*
[*]system/priv-app/LGUDownloader*
[*]system/priv-app/oemsearch*
[/LIST]

Will install as soon as I can download it! Thanks for your work!
I let you know If I encounter any problems.

Thank you for your Work ! So Thema Fingerprint don't Work right?
How about mods Like the Dual speaker one ?
Again, thx you for your Work.

Nice job! If you fix the fingerprint sensor before LG releases Oreo for the US998 I'll give it a shot on mine. Take your time though, I'm sure LG won't release it for another 4-5 weeks ?

Got the system up and running
For now I can life without the fingerprintsensor (but still please fix it fast xD)
Flashed it via TWRP, System runs smooth and I can boot into TWRP without any problems.
The AI camera really improves the quality of the camera!
Small details like the boot splashscreen and name titels are still V300L21b not the V30 H930.
If you need any logs or when you need me to try something let me know :good:

Found the solution (thanks @Rashed97 <3 )
making a hotfix zip now, has to be flashed over v1... dont wanna upload 2.4GB just for 1 file change xD

SGCMarkus said:
Found the solution (thanks @Rashed97 <3 )
making a hotfix zip now, has to be flashed over v1... dont wanna upload 2.4GB just for 1 file change xD
Click to expand...
Click to collapse
Nice! Thank you!

Think you, seems perfect so far!
One thing before flashing, is this rom already rooted? With Magisk or SU?
Think you again?

Nice one. Thanks! Now i have reson to unlock bootloader

Downloading !! and also now is a reason to unlock bootloader ;D
(can one make check/know it's contatins Polish lang. ? (PL)

niko99 said:
Downloading !! and also now is a reason to unlock bootloader ;D
(can one make check/know it's contatins Polish lang. ? (PL)
Click to expand...
Click to collapse
There is PL
---------- Post added at 10:26 AM ---------- Previous post was at 10:16 AM ----------
bvannier said:
Think you, seems perfect so far!
One thing before flashing, is this rom already rooted? With Magisk or SU?
Think you again?
Click to expand...
Click to collapse
No, you have to flash root by yourself

bvannier said:
Think you, seems perfect so far!
One thing before flashing, is this rom already rooted? With Magisk or SU?
Think you again
Click to expand...
Click to collapse
Its just stock, so unrooted, Im using Magisk 16.2 myself and have no problems
Gonna include that in the FAQ

***EDIT****
OK its finally working BUT there is no POLISH / POLAND / PL lag. any idea how to add lang ?

niko99 said:
***EDIT****
OK its finally working BUT there is no POLISH / POLAND / PL lag. any idea how to add lang ?
Click to expand...
Click to collapse
Only way i have found (could be wrong though) how to add a new language to the whole system, is by manually decompiling all apps, and translating every string... and you can imagine, thats a damn lot of work (especially because i have no clue about polish xD).
And then to make it selectable in settings... Thats something i have no idea about, sorry :/

Can this be flashed over stock?
I've got TWRP and magisk already in place but running stock rom.
7.1.2 january scurity patch.
Thanks for the rom!

i think you gonna wipe: cache, dalvik cache, system and data before but I gonna be wrong. Maybe @SGCMarkus add to OP step by step procedure?

swayjd said:
Can this be flashed over stock?
I've got TWRP and magisk already in place but running stock rom.
7.1.2 january scurity patch.
Thanks for the rom!
Click to expand...
Click to collapse
I didnt try that, and i suppose i wouldnt recommend it, as its a system update, and not even to the same model build as you have currently (as this is based off of the korean V300L).
You can try it though, but make sure to make a backup of EVERYTHING you wanna keep, in case something goes wrong.

swayjd said:
Can this be flashed over stock?
I've got TWRP and magisk already in place but running stock rom.
7.1.2 january scurity patch.
Thanks for the rom!
Click to expand...
Click to collapse
Do a Clean flash - it is always good to avoid problems.
Also its grand update, not a little one.

[UNITY] Various Fixes for the Moto G5/G5S [9+]

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.

New front camera (Omnivision OV13B10) doesn't connect with custom Q, on RN8

UPDATE:
temblor55 has made a Magisk patch for this problem, which he posted on 18 september::
https://drive.google.com/file/d/1-3y1CR6nfVhFYf9VpE11FXOmDEQl5VMt/view
Pat57 has confirmed that it works for him.
________________________________________________________________________________________________________
I have a RN8 from 11-2020 board ID 3.29
Instead of the usual Omnivision OV13855 frontcam, there is a new version OV13B10 inside.
This camera sensor is also installed in later Redmi phones
This new version works OK with Miui 11.0.11 -A9, and higher
Custom A11 rom's will problably work also all with this frontcam (I tried CrDroid 7.4 -A11 with succes)
But I can't find a custom A10 rom that can connect to this frontcam.
Always get the message "can not connect to camera"
Because of speed, stability and more development, I prefer a A10 custom rom (Resurrection Remix)
I think it isn't the Xiaomi FW, so maybe it could be the kernel.
I have tried the updated 2021 -A10 roms and A10 kernels without succes.
So problably it is about missing libs inside rom.
Is there a way to find these libs in a A11 custom rom or Miui rom and add them inside A10 rom?
I don't want to deep dig in it, because A11 will be the future solution.
But development on A11 rom's is fast ongoing, so there are bugs which some are irritating.
So if someone could give a direction, I will be thankfull

Elinx said:
I have a RN8 from 11-2020 board ID 3.29
Instead of the usual Omnivision OV13855 frontcam, there is a new version OV13B10 inside.
This camera sensor is also installed in later Redmi phones
This new version works OK with Miui 11.0.11 -A9, and higher
Custom A11 rom's will problably work also all with this frontcam (I tried CrDroid 7.4 -A11 with succes)
But I can't find a custom A10 rom that can connect to this frontcam.
Always get the message "can not connect to camera"
Because of speed, stability and more development, I prefer a A10 custom rom (Resurrection Remix)
I think it isn't the Xiaomi FW, so maybe it could be the kernel.
I have tried the updated 2021 -A10 roms and A10 kernels without succes.
So problably it is about missing libs inside rom.
Is there a way to find these libs in a A11 custom rom or Miui rom and add them inside A10 rom?
I don't want to deep dig in it, because A11 will be the future solution.
But development on A11 rom's is fast ongoing, so there are bugs which some are irritating.
So if someone could give a direction, I will be thankfull
Click to expand...
Click to collapse
I had similar problem, but i don't think it's not from the libs, it's a "persist" thing
restore "persistbak" and flash it (or if you already have a recovery backup of persist just restore it)

loopypalm said:
.... i don't think it's not from the libs, it's a "persist" thing
restore "persistbak" and flash it .....
Click to expand...
Click to collapse
No, I think it has nothing to do with the persist partition.
Because I have flashed several different rom's and kernels and found that only Miui and A11 custom does recognize the selfiecam
If the persist partition was corrupted, this wasn't possible.
Because FW is from Miui, it could be the kernel or rom.
A lot of A10 custom roms are EOL, they are build with the original early hardware drivers/libs
From 11-2020 PCB-ID 3.29 the camsensor is changed and the RN8 was also almost EOL.
In september 2020 the first A11 build came out and at the end of 2020 more and more builds.
So I assume most developers don't even think about updating the kernel or libs on their "old" A10 versions.
Inside the screenshots of the app "Device info HW" you see the 19 supported cams of CrDroid 7.4 and only 17 on RR 8.6.7

Elinx said:
No, I think it has nothing to do with the persist partition.
Because I have flashed several different rom's and kernels and found that only Miui and A11 custom does recognize the selfiecam
If the persist partition was corrupted, this wasn't possible.
Because FW is from Miui, it could be the kernel or rom.
A lot of A10 custom roms are EOL, they are build with the original early hardware drivers/libs
From 11-2020 PCB-ID 3.29 the camsensor is changed and the RN8 was also almost EOL.
In september 2020 the first A11 build came out and at the end of 2020 more and more builds.
So I assume most developers don't even think about updating the kernel or libs on their "old" A10 versions.
Inside the screenshots of the app "Device info HW" you see the 19 supported cams of CrDroid 7.4 and only 17 on RR 8.6.7
Click to expand...
Click to collapse
yes, on paper the problem sounds like it has nothing to do with persist
but as stupid as it sound ,it just worked ! (restoring persist) + latest stable A10 fw
devs didn't update the port because it just worked, and i heard it's a hard thing to mess with ...

loopypalm said:
...... as stupid as it sound ,it just worked ! (restoring persist) + latest stable A10 fw
devs didn't update the port because it just worked, and i heard it's a hard thing to mess with ...
Click to expand...
Click to collapse
For who has worked this? Have you one or more links to it?
I had read already the guides for restoring, but because all sensors does work I'm a bit holding back.
I like to read first some experiences with this, before I touch the persist partition.

Elinx said:
For who has worked this? Have you one or more links to it?
I had read already the guides for restoring, but because all sensors does work I'm a bit holding back.
I like to read first some experiences with this, before I touch the persist partition.
Click to expand...
Click to collapse
link to what ?
i had similar problem on my 128 variant and asked help in RR TG group (group is deleted by rodrigo) rr official dev is always offline, so rr users moved to milestone by zhan (which is miles better)
"all sensor work fine except camera"
nobody have idea and no dev support, so i try lot of things
and flashing latest A10 fw and restore persistbak + clean flash of RRos + 16 kernel are the last things i did and it worked
if you have orangfox do a backup of persist ,so if anything goes wrong you can just restore it

loopypalm said:
link to what ?
i had similar problem on my 128 variant and asked help in RR TG group (group is deleted by rodrigo) rr official dev is always offline, so rr users moved to milestone by zhan (which is miles better)
"all sensor work fine except camera"
nobody have idea and no dev support, so i try lot of things
and flashing latest A10 fw and restore persistbak + clean flash of RRos + 16 kernel are the last things i did and it worked
if you have orangfox do a backup of persist ,so if anything goes wrong you can just restore it
Click to expand...
Click to collapse
Ok I will try after backup
Which RN8 batch have you? Which camera didn't work?

Elinx said:
Which RN8 batch have you? Which camera didn't work?
Click to expand...
Click to collapse
what do you mean by batch ? i have ginkgo 6/128
the error was "can't connect to camera" (i guess,both front and back since i can't do anything while that error is apearing)

loopypalm said:
... batch ? i have ginkgo 6/128
the error was "can't connect to camera" (i guess,both front and back since i can't do anything while that error is apearing)
Click to expand...
Click to collapse
The batch date 11-2020 is the phone with problems.
First the problem with FW 12.01. This is the only phone that can't be flashed with that version. If you did with twrp, you had a brick.
Second the HW change of the selficam. I have seen I'm not the only one with Andoid Q "not connecting" to this specific cam.
On LOS 17 topic a saw there is a formel bug report published about this issue
I can use all other cams without problems. The error is only with selfiecam and A10. Not with Miui and not with A11.
That is why I think of a missing driver.
I read something about adding missing drivers, but think it isn't easy.
Also I understand that the vendor image contains the hardware drivers.
So trying kernels only hasn't influence on HW changes
I can imagine that A11 custom uses also later vendor images, that's why these roms work with selficam.
Next question would be.
Are vendor images for Ginkgo intechangable?

Elinx said:
That is why I think of a missing driver.
Click to expand...
Click to collapse
have you tried A10 latest stable FW ? (it has updated drivers in it)
Elinx said:
Are vendor images for Ginkgo intechangable?
Click to expand...
Click to collapse
as far as i tested(A10), they are all almost the same, except for some roms have some carrier overlays and BT in it and other have them in system
also audio mods and enhancement, some roms have it and other don't

loopypalm said:
have you tried A10 latest stable FW ?....
...
as far as i tested(A10), they are all almost the same, except for some roms ...
Click to expand...
Click to collapse
Yes I have the latest stable FW. First I thought that these contains the HW drivers.
But reading, I learned that with latest Android versions all drivers are inside vendor image.
That is why updating FW and kernel doesn't make any difference for RR.
Because of all brick/EDL troubles I'm being carefull what I flash.
I have made for now a twrp backup of vendor and efs partition.
The persist parttion must be backup with adb or terminal
My phone is still an empty phone so I can format data and so on.
I saw that Miui vendor files are downloadable.
The latest Global is 11.0.11

Elinx said:
The persist parttion must be backup with adb or terminal
Click to expand...
Click to collapse
use also recovery (you never know) ...
Elinx said:
I saw that Miui vendor files are downloadable.
Click to expand...
Click to collapse
before changing system try RR with A11 vendor just to make sure
(i did that between 2 A10 roms and it worked,but A11 = not tested)
you can wipe everything and flash rr since your data is not important

loopypalm said:
.....
before changing system try RR with A11 vendor just to make sure
(i did that between 2 A10 roms and it worked,but A11 = not tested)
...
Click to expand...
Click to collapse
Dit you flash the complete vendor.img from another A10 rom?
or replaced the 3 vendor files inside the rom's?

Elinx said:
Dit you flash the complete vendor.img from another A10 rom?
or replaced the 3 vendor files inside the rom's?
Click to expand...
Click to collapse
i flashed a rom (Don't remember the name) and i did a mess in vendor ,so instead of reflashing, i restored a recovery backup of vendor of an older rom (AEX) that was on my SD
of course error like app x stopped working popped off,so this is not a fix
this is just a crazy suggestion to test the compatibility of the drivers
also test this cam :
ɬɧɛ Ɩųŋąɬıƈ in Dtuxed Roms Public Group
t.me
it has updated libs
maybe it will work

loopypalm said:
...., i restored a recovery backup of vendor of an older rom (AEX) that was on my SD
.....
maybe it will work
Click to expand...
Click to collapse
Ok you flashed vendor.img with twrp
The download link is Miui camera.
There where no HW drivers inside
I already found also such a zip with libs, but without result
It is for improving camera results

Elinx said:
There where no HW drivers inside
Click to expand...
Click to collapse
i made a mistake in the zip
the cam that i wanted to give you is in the same group
i will see if i can find it

Try this bro

Thank you, I surely want to try this Magisk mod file, but the file isn't accessible without requist.
Maybe you have your reasons for that, but in that case it isn't possible to download.
I have tried to comment this with the video too, but you have disabled comments there.

temblor55 said:
Try this bro
Click to expand...
Click to collapse
temblor55 you forgot to make the file public​

Sorry guy's made it public now
https://drive.google.com/file/d/1-3y1CR6nfVhFYf9VpE11FXOmDEQl5VMt/view