XRN5Pro New Camera Blobs beta
The patch for the firmware toold
blobs camera, which replaces them new ones
. Useful, for example, if you are on firmware blobs with old and want to put Patch for aging
of the cap, which is based, just the same, in the new. Archive is not a conflict, ie after it you can use any patches / fashion, but only those for new blobs. Oh yes .. everything in your
own risk :)
- Needed with older firmware blobs camera (Seriously? ...)
- Be sure to put the core of the new libami (markednewcam or the like). Any, of your choice.
- Set file attached below from under rekaveri.
- If an error occurs "Unable to connect to camera" (Should not, in theory), the We go in and rekaveri vaypaem caches .
Stitched archive, by tradition, will automatically create a backup file of runoff (ie those that are currently in the firmware) to the internal memory, in BlobsBackup folder with preservation of structure. Nuancesbetaversions:
And I really would advise you to put it.
all patches for the camera, which we have, do not work out of Magisk
(No 20.4 or 20.1 - do not waste time on it, it has nothing to do with it). But regularly working those modes that are put out of rekaveri, ie with specific files are replaced. Again, there is nothing stopping to steal files from of your fashion and shove them directly in the replacement - they will work. If anyone has ideas on how this fixed a time, and even better if someone would explain why it is so - I ask in the QMS
. Curator clean theme from offtopic - a pleasure.I test all this onHavoc-OS-v3.5-20200516-whyred-Azimxv-Edition (On older firmware blobs) and the core ExtOC-EAS-NEWCAM-V39.2-by-Darkness (On the new kernel).
Patches that i test itPatch for aging (Version rekaveri) and patch on frontalku for new Lieb (manually pushed in).
Excuse me, I'm writing the scripts / firmware development / Patching libraries do not have any education or relationships, I'm just an enthusiast. I do as I can, thank you for your attention.Post has been editedMoonpwr - 18.05.20, 20:12