yashsingh1/xdaforums huggingface dataset:
[P8 Lite (2017) Development] amonpaike:
Finally I managed to install this rom on my P10 lite, also thanks to the comments of @GizmoTheGreen , which were very useful to me in avoiding bootloops.

@AltairFR This rom is fantastic, congratulations! but I encountered a problem that I actually found even in older custom roms, and it is that the Bluetooth BLE low energy sensors have difficulty pairing and sometimes fail to connect at all, to be honest this rom has improved things slightly, but the fact is that the problem is still present, while in the stock rom with Emui 8.0 these components connect pairing almost immediately.

In particular I often use a speed and cadence sensor on my bicycle, turning my P10 into a bike computer, the problem is that it gets frustrating when they can't connect...

On this rom as in another custom rom, once paired, the bluetooth sensors then work well ...

I wonder, what could be the problem?

Is it possible in your opinion to access the low level Bluetooth BLE settings of emui 8.0 and see what are the differences between these roms, which do not allow an immediate Bluetooh BLE pairing?

If I only knew where the configuration files are I would try to make a comparison myself, but I have not the faintest idea where to put my hand
[P8 Lite (2017) Development] Thtrr:
I also managed to install this for my p10 lite and it is working perfectly. Fortunately even my banking apps work. Could not install Nikgapps but opengapps worked out.
[P8 Lite (2017) Development] amonpaike:
strange that the nikgapp are not installing, everything went smoothly to me, did you resize the system partition?
[P8 Lite (2017) Development] Thtrr:
I followed the instructions but the Installation failed regardless. Yep it was quite a unexpected result. The error message was related to the storage though
[P8 Lite (2017) Development] amonpaike:
ok, i guess i got it, i installed a stock firmware version which has large system partition, specifically i installed this version, which doesn't have wifi bug not connecting if i use siberia kernel

this one:

Huawei P10 Lite WAS-LX1 WAS-L21 Warsaw-L21A 8.0.0.370(C432) Firmware 8.0.0 EMUI8.0 05014JNC
[P8 Lite (2017) Development] AltairFR:
Last version https://androidhost.ru/xX3
[P8 Lite (2017) Development] AltairFR:
8.0.0.394 version
[P8 Lite (2017) Development] amonpaike:
Suggested to me by a sameone in a tread on the xda forum of p10lite, I had already installed this version, and actually it was fine, but I had problems with the siberia kernel, the wifi no longer worked, then I installed that other version that I suggested a little above, 8.0.0.370, but after writing that post, always with the siberia kernel I discovered that I did not receive nor could I make calls, so I tried yet another rom, and finally with the siberia kernel everything works for me. is the rom:

Huawei P10 Lite WAS-LX1 WAS-L21 hw eu Warsaw-L21A 8.0.0.380(C432) Firmware 8.0.0 r1 EMUI8.0 05014JNC

i also managed to install magisk

Magisk-v23-Canary-phh-Aonly-A11.zip

and Magisk-v23.0.apk

patching the siberia kernel, only thing is that you have to format the data partition, otherwise it goes into the boot loop.

... also the problem of pairing bluetooth ble, seems to have improved a lot.

in general now the rom seems to be fine, I just have to be careful not to mess too much with options to enable the display of notifications with the fingerprint (huawei features) and enable the type of gesture menu of the navigation bar the "invisible one" because there must be some small bug-conflict between these two functions and it ruined my interface once by doing a forced restart and making the options menu phh treble setting and many more options disappear
[P8 Lite (2017) Development] AltairFR:
Thank you for the message. I still have a question:

Did you reformat the data partition before installing the Siberia kernel? The wifi configuration is indeed in the directory /data/misc/wifi
[P8 Lite (2017) Development] amonpaike:
No, actually I did not format the "data" partition, I thought that the rom was wrong, and I installed another StockRom ... then yes, having installed the other stock rom I formatted also* data partition having to decrypt and reinstall everything ...

So, with the question you ask me, I don't know, it could be that it works even with the lastest stock rom available ... I can't tell you, I haven't checked, but there could be this possibility that everything works fine simply by formatting "data"

I would like to ask you a question, I have a problem that at this point is quite delicate for me, I tried to make a backup of the partition "data" via TWRP, and it gives me error 255, I did a search and it is because there are some encrypted folders in the partition, how could I get around this problem?

(I have done the huawei decryption correctly, so I already know it's not about this problem)
[P8 Lite (2017) Development] -Alf-:
if you choose "Install" in TWRP, do you have access to the folders in internal memory?

Try TWRP 3.2.1-0 by pretoriano80 , download here

Maybe it will help you...
[P8 Lite (2017) Development] amonpaike:
I used the latest recovery 3.6.09 https://dl.twrp.me/prague/twrp-3.6.0_9-0-prague.img.html which allowed me to install the system through "install image" function which is also contained in the version of pretoriano80,

are you referring to being able to access the internal "data" folder?

however now out of curiosity I'm going to do a test by flashing the version of pretoriano80
[P8 Lite (2017) Development] -Alf-:
encrypted "data" :

Decrypted "data" :
[P8 Lite (2017) Development] amonpaike:
I tried the version of praetoriano80 and I get the exact same result, error 255, however my data partition is not encrypted, I still see all the files, it does a bakup of about 350 mb then the error emerges

this is the log when the error emerge

I:addFile '/data/misc/media' including root: 1
==> set selinux context: u:object_r:media_data_file:s0
I:addFile '/data/misc/audioserver' including root: 1
==> set selinux context: u:object_r:audioserver_data_file:s0
I:addFile '/data/misc/cameraserver' including root: 1
==> set selinux context: u:object_r:system_data_file:s0
I:addFile '/data/misc/vold' including root: 1
==> set selinux context: u:object_r:vold_data_file:s0
found policy '/data/misc/vold' - '1DK' - '5f40f2361c8ebbb4'
I:addFile '/data/misc/vold/KN6PgCqg2McE2ZpBpTMBnD' including root: 1
==> set selinux context: u:object_r:vold_data_file:s0
found policy '/data/misc/vold/KN6PgCqg2McE2ZpBpTMBnD' - '1DK' - '5f40f2361c8ebbb4'
I:addFile '/data/misc/vold/KN6PgCqg2McE2ZpBpTMBnD/874GdaJgP+1wyrQOF0zg,C' including root: 1
==> set selinux context: u:object_r:vold_data_file:s0
found policy '/data/misc/vold/KN6PgCqg2McE2ZpBpTMBnD/874GdaJgP+1wyrQOF0zg,C' - '1DK' - '5f40f2361c8ebbb4'
I:addFile '/data/misc/vold/KN6PgCqg2McE2ZpBpTMBnD/874GdaJgP+1wyrQOF0zg,C/7B49JubmVOJJU17vxN8W3D' including root: 1
==> set selinux context: u:object_r:vold_data_file:s0
found policy '/data/misc/vold/KN6PgCqg2McE2ZpBpTMBnD/874GdaJgP+1wyrQOF0zg,C/7B49JubmVOJJU17vxN8W3D' - '1DK' - '5f40f2361c8ebbb4'
I:addFile '/data/misc/vold/KN6PgCqg2McE2ZpBpTMBnD/874GdaJgP+1wyrQOF0zg,C/7B49JubmVOJJU17vxN8W3D/FO+efaSrB3xAyLrslKbtFC' including root: 1
==> set selinux context: u:object_r:vold_data_file:s0
found policy '/data/misc/vold/KN6PgCqg2McE2ZpBpTMBnD/874GdaJgP+1wyrQOF0zg,C/7B49JubmVOJJU17vxN8W3D/FO+efaSrB3xAyLrslKbtFC' - '1DK' - '5f40f2361c8ebbb4'
I:addFile '/data/misc/vold/KN6PgCqg2McE2ZpBpTMBnD/874GdaJgP+1wyrQOF0zg,C/7B49JubmVOJJU17vxN8W3D/FO+efaSrB3xAyLrslKbtFC/uUDsBtszpDu4HKithlV+SD' including root: 1
==> set selinux context: u:object_r:vold_data_file:s0
I:Error adding file '/data/misc/vold/KN6PgCqg2McE2ZpBpTMBnD/874GdaJgP+1wyrQOF0zg,C/7B49JubmVOJJU17vxN8W3D/FO+efaSrB3xAyLrslKbtFC/uUDsBtszpDu4HKithlV+SD' to '/external_sd/TWRP/BACKUPS/H3XDU17919003343/2022-02-15--11-01-15_RQ3A211001001/data.f2fs.win000'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/external_sd/TWRP/BACKUPS/H3XDU17919003343/2022-02-15--11-01-15_RQ3A211001001/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
I:Copying file /tmp/recovery.log to /external_sd/TWRP/BACKUPS/H3XDU17919003343/2022-02-15--11-01-15_RQ3A211001001/recovery.log

EDIT:

in the end I decided to delete these encrypted files in the vold folder, I don't know what those files are for, I don't know how they got there ... will it be some app that I installed? I don't know, for now I have nothing encrypted wanted by me, for now crdroid seems to work fine, I was able to backup the data partition ..
[P8 Lite (2017) Development] AltairFR:
Before install image crDroid , You must format the data partition because the internal storage wipe does not delete the/data/misc/vold directory
[P8 Lite (2017) Development] AltairFR:
Procedure is

go to TWRP

format data

reboot to TWRP again

do a full wipe (system, data, cache, dalvik/art cache) !

reboot to bootloader
[P8 Lite (2017) Development] AltairFR:
This files contain policy encryption
[P8 Lite (2017) Development] GizmoTheGreen:
this rom is great on my p10 lite (warsaw)

I can't get Magisk to work it either bootloops (tried stock and siberia)

after I restore kernel it boots again.

tried patching siberia kernel in Magisk app, then flash it.

it boots but magisk still isn't seen by the app. but if I try to install magisk directly from the app (with universal root from rom) it now says magisk patched image detected... so...

I am confuse xD
[P8 Lite (2017) Development] amonpaike:
starting from the stock rom, I installed the latest available twrp-3.6.0_9-0-prague.img, from there I decrypted and formatted the partitions, I installed the crdroid image, i installed the siberia kernel, I installed the nik google apps, I patched the kernel with Magisk-v23-Canary-phh-Aonly-A11_1.zip and I rebooted, then I installed the Magisk app. Beware that if you boot the system before patching the kernel and do this after, you get a bootloop in that case you are forced to format the "data" partition again to eliminate the bootloop
[P8 Lite (2017) Development] GizmoTheGreen:
Have you managed to get v24 going?

Why would magisk patch ruin encryption? This confused me, no other device i have does this
[P8 Lite (2017) Development] amonpaike:
no I only put magisik 23, and I can't tell you why it goes into bootloop.

however this rom unfortunately has a problem, it is the second time that this happens to me, I have already mentioned it a few posts ago, from time to time it happens that it gets damaged, notifications no longer work, in the settings the phhtreble settings menu disappears, it is as if you reset to vanilla android settings, even some settings that I customized are reset, such as the dark theme, the top panel that of all the quick settings those contains only the first row, the others are gone, not c 'is not even the icon for access to settings .. if I restart android it stays like this ..

I turned off the phone tonight, turned it back on this morning, the first time it took a long time trying to restart, it didn't boot, it turned on again, and then the system was messed up as I described, it seems like something is wrong, not manages to read some settings and restarts without accessing certain settings

if someone can tell me in which folder the settings are located I see what happened, maybe I delete it and try to restart to see if it fixes, or if I try to consult the logcat, but someone has to help to understand where I have to go to watch
[P8 Lite (2017) Development] GizmoTheGreen:
I am running 7.14 with siberia kernel (without magisk) on my warzaw (p10 lite) and it's working without issues...

maybe a problem with patched magisk for a-only?
[P8 Lite (2017) Development] amonpaike:
No I do not think it is related to magisk, the fact is that this problem does not appear immediately, the second time it took two weeks to re-emerge ... to solve the problem I simply restored the "DATA" partition with twrp, but obviously this does not it is a good solution.

my phone is a was-lx1a that if I am not mistaken it means that it is the version with 4 gb of ram

edit: i just read the siberia kernel thread, and version 302 came out with some fixes with sfs and sdcard .. now i try to install it and see what happens, it could be that it is related to sfs, since the break emerged after a reboot, but it's just my guess and I really hope to be right.

Changelog : 4.4.302

Upstreamed to v4.4.302

Refactor f2fs

Refactor sdcardfs

Disabled Some log spam
[P8 Lite (2017) Development] GizmoTheGreen:
I couldn't get 302 to work yet. bootloop even if I wipe data (tried wipe/format in erecovery, format in twrp, wipe in twrp.) let me know if you get it working... and how. I hate this device is so sensitive... look at it wrong and it bootloops haha
[P8 Lite (2017) Development] 11spqr:
I've got stock working, thats it, anything more fails.

Bests,

P.
[P8 Lite (2017) Development] amonpaike:
yes I also had bootloops, because I had not read the comments of the Siberia Kernel thread and I had not seen that there were problems and we needed the "stock" version but I saw that you already liked my comment on the other thread, so I know you know already the solution.
[P8 Lite (2017) Development] buteo:
Hello.

I downloaded and flashed

Huawei P8 Lite 2017 PRA-LX1 PRA-L11 hw eu HLRCF Prague-L31 8.0.0.402(C432) Firmware 8.0.0 r1 EMUI8.0 05014FFV [androidhost.ru]

It was the only v.402 file on the site, for the right area C432

After successful flashing I end with version 8.0.0.046(0OXY) (NOT .402, wrong area code).

In this state ROM boots and stucks at crdroid logo (the same with Lineage) for a long time, then reboots to erecovery.

I tried to reflash EU oeminfo, but it doesn't seem to help. Tried do install

Huawei Honor 8 Lite PRA-LX1 PRA-L31HN hw eu HLRCF Prague-L31HN 8.0.0.375(C432) Firmware 8.0.0 r1 EMUI8.0 05014GNH [androidhost.ru]
but it fails.

Any advice?

Some info I can get:

$fastboot oem get-build-number
(bootloader) :System 8.0.0.046(0OXY)
$ fastboot oem get-product-model
(bootloader) PRA-LX1
$ fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :PRA-LX1C432B170
[P8 Lite (2017) Development] buteo:
There are no sounds or ringtones in the ROM image, right?

So I installed "LineageOS_Sounds.zip" from within TWRP and, even if sound files are in/system/media/audio/* directories ringtones are not selectable from CRdroid UI.

Ringtones appear only if copied in Internal memory Ringtones directory.

What do you think I made wrong?
[P8 Lite (2017) Development] hamedsolo:
I have problems with v314

1-camera has delay

2- screen mirror and hotspot with software like xender not working

3- Qr code scanners not working

4- access to sd card has problems

how can I dirty update this rom from v314 to v315?

I have magisk 22 and gapps.
[P8 Lite (2017) Development] 11spqr:
Hi,

Because of SU app change IMHO dirry update is not possible.

I had problems with Mixplorer with root permisions and SU app itself after dirty update(reboot to twrp, clean cache, dalvik/cache, reboot to bootloader, flash system img). I am not usig Magisk on this rom dough.
[P8 Lite (2017) Development] Ozzwi77:
Escuse me, how to how to resize system partition?
[P8 Lite (2017) Development] AltairFR:
You can resize system partition in TWRP
[P8 Lite (2017) Development] amonpaike:
Will this crdroid get any updates?
[P8 Lite (2017) Development] MrBrowseGierza:
thanks for this info i was finally able to work it with my Huawei Hono 6X
[P8 Lite (2017) Development] traversone:
hi all,

this ROM works in P10lite as per given instructions.

However, as in LeaOS, the mobile data continuously toggles between ON/OFF like the network signal is not stable !

please suggest some workaround, thank you
[P8 Lite (2017) Development] moitreker:
AltairFR

Hi.

La sélection de sonnerie ne fonctionne pas, erreur de soundpicker. Cette méthode n'a pas aidé( apex / com.android.media / etc / seccomp_policy / mediaextractor.policy Comment y remédier?
[P8 Lite (2017) Development] AltairFR:
You can't, use leaos. Crdroid don't have my source patch to fix this issue
[P8 Lite (2017) Development] Iconium_:
bootloop *doesnt go into boot*. goes into erecovery super quickly.
[P8 Lite (2017) Development] DooSHeK:
Is there a way to make VoLTE working in this rom?
[P8 Lite (2017) Development] kimhauk:
</Enter>
[P8 Lite (2017) Development] xc112:
sir, can i have your github source to rebuild this rom, i think they updated it to pass safety net
[P8 Lite (2017) Development] AltairFR:
On the github iceows
[P8 Lite (2017) Development] xc112:
this is only the list on your github sir

lineage_build_leaos

aosp_build_leaos

arrow_build_leaos

cant find crdrom
[P8 Lite (2017) Development] DooSHeK:
So no VoLTE fix?

I have a second problem.

After charging and disconecting rom charger, phone won't go to deep slepp. I have to reboot phone to be able to go to deep sleep.
[P8 Lite (2017) Development] DooSHeK:
I understand that after the latest Google Droid Guard update, the ROM needs to be signed with release keys, otherwise it's impossible to pass the Play Integrity check. Are there any plans to release a signed ROM or provide assistance with building and signing it?
[P8 Lite (2017) Development] AltairFR:
The LineageOS 20.0 for Huawei p20 light have release Keys,.. i can make version for p8 lite
[P8 Lite (2017) Development] DooSHeK:
That would be great. This is the only rom that works flawlessly (well, almost, VoLTE doesn't work :)) LeaOS has problems with Data corruption
[P8 Lite (2017) Development] xc112:
how to sign it, i been building for honor6x but i do not know how to do it, thanks
[P8 Lite (2017) Development] DooSHeK:
Is anything happening on this topic?
[P8 Lite (2017) Development] amirarsalan_rm:
I did all the steps, but it gets stuck on this screen. I had already installed this ROM on this phone, but now it doesn't work anymore. Honor 8 lite phone model.
[Google Pixel 6 Pro] rav101:
Hi all,

This may be in the too soon to tell or no one knows category of question but "Does anyone know if there will be GCam mods on the Pixel 6Pro GCam to further improve it's capabilities like is the case with the ports to other phones?"
[Google Pixel 6 Pro] 96carboard:
Correct me if I'm wrong, but aren't the gcam mods there to enable software features that are not-authorized for older or off-brand phones? Wouldn't really give you anything for the P6 since its the newest and has all the new super magic features already.
[Google Pixel 6 Pro] rav101:
Yeah I'm not sure if what they do with gcam takes any of its features and dials up the scale to eleven and therefore would add value on the main Pixel device of the time.

I'm happy either way because as you say, the latest pixel already has amazing goodies!
[Google Pixel 6 Pro] ThoroSOE:
I loved the modded GCAM on my Pixel 3, because it allowed me to dial down the noise reduction and sharpening for the JPEGs. As the Pixel 6 is again guilty of, the stock JPEGs do not even come close to the level of detail the DNG files allow. But with those tweaks, I did not need to go to lightroom with most pictures, that I deemed important. 95% came out great with the modded GCAM.

I really cannot wait for someone to make this possible for Pixel 6. Such great hardware, such a baaad set up JPEG engine.
[Google Pixel 6 Pro] Gnaius:
I put this on similar threads; it's important that as many people as possible make themselves heard. All of you concerned about the jpeg over-processing issue, please weigh in here, so that Google can see our complaints: https://issuetracker.google.com/issues/208860802

The more people who post, the more likely the complaint will be noticed. (Sorry if this appears to be spam; it's strategic.)
[Google Pixel 6 Pro] 96carboard:
I honestly don't think that gooble gives a damn. There are issues in that system that are over a decade old with tens of thousands of responses that have not been addressed.
[Google Pixel 6 Pro] fards:
There's a gcam mod for pixel devices only that works very well.

Has lovely b&w mode and swaps to zoom cam.

https://www.celsoazevedo.com/files/android/google-camera/dev-MWP/f/dl14/
[Google Pixel 6 Pro] Golf c:
And your Aosp Is better?
[Google Pixel 6 Pro] Gnaius:
You may be right, but you may not. That page *seems* to be monitored: someone, for instance, has established a hierarchy of priorities. Is this smoke and mirrors? Maybe. But Google gets their bug reports from somewhere, and why wouldn't this be the place?

Also, this new report gives me a tiny bit of hope. On the list of 100 or so fixes in the December update you find this one, specific to the Pixel 6 and 6 Pro:

General image quality improvements in camera preview/capture.

(@Golf c — I had to look up that acronym. I take it you're referring to the American Society of Orthopedic Professionals?)
[Google Pixel 6 Pro] benleonheart:
"produces an output comparable to" does not mean "produces an output of"

This said, though, a 50MP un-binned option in the camera settings would've been cool
[Google Pixel 6 Pro] kevinireland11:
Dude I think you just need to buy an DSLR pal lol
[Google Pixel 6 Pro] Solomon M:
Or, yall could hold these clearly capable companies, to the quality you expect from them.... And unless you do, & many more, do you think they have incentive to put all we want and need in a single device?:

IRDA current optimized for mobile

Wi-Fi a,b,g,n,ac,ax or current hotspot etc etc

Cellular 1,2,3,4,5G

Bluetooth ...that is current tech

Indestructible

Easily repairable for minimal loss to recycle / replace

Etc

A camera [ ...that is current tech and enough pixels that the other binned method could be used in low light or set to max resolution as in "un-binned" which is not just software. Google please give us a capable, quality, customizable camera (like you did with the Pixel 2), then plenty of options to be able to get the image we desire. ]

Etc

NFC etc

FM radio

AM radio

Fm & AM Transmitter

Built-in compatibility for universal Bluetooth keyboard/mouse HID for universal function without dongle...

I dream too big right.... Least I'm not asking for a clear foldable sheet of plastic that is 30 +yrs from now.

Realistically all this capable hardware could be easily implemented into a single device... Even the psp 1000 had IRDA ...

Like whoever holds these patients preventing this hardware from being given to the consumer, a real device capable of what science has to offer (dream bigger with the device you use everyday, and make it know you'd like a feature like ip68, 1080p, but what about all the rest... Where is the build your own cell phones? ...Some people might not like what weight is required for each component:

Image a Google kiosk where you'd like to upgrade your phone:

1: You use you current phone to pay when you get there with nfc

2. You insert your phone.

3. Select the on screen available components and watch it remove the back and upgrade it with robotic arms as you commit the changes.

4. Spits back out your newly upgraded device, same screen if you didn't choose to replace it etc etc.

https://www.onearmy.earth/project/phonebloks

https://en.m.wikipedia.org/wiki/Project_Ara

... one that has a magnet in a coil like those flashlights so to charge you shake it..... Come on people let the ai build it test it in the lab then after multiple continued test release the device to manufacturing... The human brains should start pioneering after they correctly test the ai to their knowledge for integrity. Other than how to see the connections upon all the branches of science to one another shouldn't be hard with access to the resources an ai would.

GOOGLE AND ANYONE ELSE: COVID-19 IS OVER: GET BACK TO BEING SERIOUS ABOUT YOUR QUALITY OF WORK. WE ALL DEPEND ON EACH OTHER TO SURVIVE.

The fact is if we really wanted some futuristic technology in our hand, we have to start requesting it, and not buy otherwise.

We have cool stuff now, I'm excited to see what options we will have when I'm old.

Consider these two:

https://en.m.wikipedia.org/wiki/LG_Voyager (Nov 2007)

https://www.samsung.com/us/smartphones/galaxy-z-flip4/ (current)

Great improvement but while looking at current trends doesn't look like much from the Fold3 & 4.