yashsingh1/xdaforums huggingface dataset:
[Nexus 10 Android Development] DragonFire1024:
UPDATE:

I have been tirelessly trying to figure out if there was any possible way, any tiny little hack or any kind of trick to get something working, not only to build this ROM, but also to get the camera working as well as other things. Some of these things can be easily fixed by moving a file from one place to another. In some cases it just needs a helping hand. Other times no matter what I do and how many times I try and fix the air it will pop up in other places that it normally didn't show up before.

A significant portion of these errors seem to revolve around a specific area 'videodev2_exynos'. Everything there after falls apart which has to do with media files in general and it tears apart everything from the camera to the codecs and if you're lucky enough to get some of Library files to build, they're usually corrupted. Anyway sometimes it's a typo sometimes it literally is a missing apostrophe or a (. It took me two weeks to figure out I had to update a few lines of code replacing an equal sign with a ':' I kid you not. An entire build process will stop or things will not work when or if it finishes. Anyways I wish it were that easy in this case. The downside about patching older devices especially when it comes to a colonel it can be a very slow process. Luckily with just a few additions to the configuration file, appears to suggest that another memes has been found to turn the camera on. This is where the time-consuming part comes in because I have to add these configurations manually to the lineage and standard Manta deconfig as opposed to updating them in a terminal by means of an actual patch. So I will start adding these configurations in and hopefully this will fix the majority of the problems that I have been having at this exact point. If so it looks like I will be able to get a whole bunch of stuff to work again without little more to do. So in theory I should be able to apply a significant portion of these configurations to the Android configuration and it should work. Fingers crossed.

[Manta] [PATCH 1/2] UBUNTU: [Config] Enable the Samsung related camera configs to get the camera to work
[Nexus 10 Android Development] andynx1:
Talking of typo's! Spell checkers, don't you love them?

Thanks for the update, I really appreciate your efforts, hope it works out.
[Nexus 10 Android Development] DragonFire1024:
My Google assistant is ultimately out to destroy me. I don't get it because it will display the word properly as it should be then when I put a period at the end, half of the sentence gets spelled wrong.

Might have to build the kernel on its own and command it over as a prebuilt. Lineage is weird they make their own deconfig. So I can't just do a make xx_deconfig because then the source won't be clean and lineage will complain about it all the way through. While stopping the build process for no apparent reason other than the fact that doesn't like it. I've still got some experimenting to do but some of the errors I were hoping would cleanup did not, while a significant portion of other ones did clean up.

I guess before I continue to figh, does anyone know if there is any specific reason video4linux (v4l and or v4l2) is needed? If not how can I remove it because I cannot do so in any kind of menu configurations as it seems to be a permanent selection but I can't find where in any configuration files it is set.
[Nexus 10 Android Development] TiggaZ:
Hi [MENTION=8165603]DragonFire1024[/MENTION],

your dedicated work is much appreciated and thanks for the continued work. Sorry I con not help you in the process as I have no experience in building a ROM or kernel in any way.

Keeping the Nexus 10 alive is the best thing we can hope for and love to see you spending your time on it.

Saying that do you have an updated flashable boot.img for kernel 3.4.99? I do not understand to process of how to accomplish that and it would be much more efficient to have one provide the ready to use boot.img.

If anyone else already made a flashable boot.img please feel free to share it as well.

Thanks for your help and kudos for the continuous work.
[Nexus 10 Android Development] DragonFire1024:
I can make one but I have to use the stock boot image. Which isn't a problem but generally I make instructions like this because people use different methods of rooting and make their own preferences and settings in their boot images and this saves the trouble of them having to redo all of that work. But yes anyone who requests an actual image to flash it's very easy to make and I have no problem doing that. You will have to wait until tomorrow thoigh. I am at work all night so when I get home I will be able to do that.
[Nexus 10 Android Development] TiggaZ:
Your help is much appreciated.

Thank you
[Nexus 10 Android Development] DragonFire1024:
we had a lot of really bad weather today and was without electricity for a good portion of the day so I wasn't able to get anything done. Hopefully tomorrow mother nature will be more cooperative.
[Nexus 10 Android Development] DragonFire1024:
here is the stock boot image from the marshmallow rom, not rooted with supersu or magisk and updated kernel to 3.4.99. just extract the boot.img and flash in twrp and reroot.
[Nexus 10 Android Development] DragonFire1024:
Android 7.1

Well I got a ROM built, Lineage 14.1. I haven't tested/installed it yet, so I have no idea if it boots or works. I need someone to test it. You will need to boot to twrp, wipe everything, reboot device back to twrp, plug tablet into PC and copy and paste the zip below, to storage. Then download and place in tablet storage, OpenGapps for ARM, android 7.1, nano. Download Magisk and move to tablet storage. flash ROM, OpenGapps, magisk and reboot system. Like I said, no clue if this is working or not so make sure TO BACK UP ANYTHING IMPORTANT before installing in case you need to go back to the ROM in the OP.

Manta Lineage 14.1
[Nexus 10 Android Development] Narcoticx:
supports the camera?
[Nexus 10 Android Development] DragonFire1024:
I don't know. I haven't tried it. I've been fixing things as I see them, or at least trying to. With that said, I will try the build above and one that's just fresh as of an hour or two ago. Several things things I have noticed, nothing is/was updated to work past marshmallow. It seems they managed to get the cameras working working with each update until M. Then it stopped. Lineage did a little work, but most of the edits and commits were done when CM was still cranking, so they ported most stuff over rather than update it. So the good thing: I didn't notice any errors in the camera department. I think there's a good chance I managed to update, properly, the make files that should get it to work. NFC is going to be tough to predict. I have not managed to make much progress there and if I had to guess, I would say it's a no go. But seeing as I haven't tried either build yet, I am just speculating based on visually watching certain parts of the building process.

In a nutshell, I went through each hardware section by section RE camera, NFC, sensors. In some cases, overwriting the source files with the master branch of 7.1 (14.1), was enough to get a lot of the errors to vanish. In other cases, doing that made things worse so I picked apart the Android.mk files and manually updated the major ones (camera, NFC, sensors) and finally was able to get builds to pop out one after another. So I spent time hunting down each alleged incompatibility, and hunting down the errors related to them. Either tonight or in the AM I will test them and see if they even boot first lol!
[Nexus 10 Android Development] Narcoticx:
Perfect, great job you're doing with our beloved Nexus 10, we'll be open to your advances.
[Nexus 10 Android Development] DragonFire1024:
I will finally have a couple of days to try the ROM and see if it works sorry but it's just been one crap show after another here. If it's not a virus then it's riots. If it's not that then it's bad weather. Just haven't been able to win too much lately. I will try and see what I can get done in the next two days so look out for some updates
[Nexus 10 Android Development] DragonFire1024:
Well the ROM works. NFC appears to work, but I have no way of actually testing it to see if it does. But everything functions as it should as it did in prior versions. I have not looked at any logs that would be my next step. The camera only half works. I don't think this is a hardware problem I think this is a codec and module problem. It doesn't crash and the app doesn't force close when you try opening the camera. All it does is black screen. There's just nothing there. If you try switching up the app, then the camera force close over and over. I haven't figured out which file yet but if you switch out the library files that are part of the camera, with any other ones from the same device but older versions of Android, the device will not boot. Even if you replace the remove library files the device will not boot and you have to start all over reflash the ROM, rom, root etc. so I am almost pretty sure this has something to do with all OMX or something along those lines. We have a very eerily similar problem with our Amazon tablets. Amazon has put most of their tablets on lollipop, so are ROMs for this device are for lollipop and for Android 7. The cameras along with the headphone jack don't work properly, if at all. Video, whether it's live or an actual clip, will not play and if it does it's often very poor quality and has no sound. We have managed to fix the video issue buy flashing additional OMX codecs in TWRP. So far as I know the cameras are still an issue. And we know our cameras work on the Nexus 10 because they work on every Android until 7. The same pretty much goes for the Amazon fire tablets. I think regardless of who the company is, they somehow coincidentally misplaced blobs or kodak's or make them incompatible with certain versions just to ruin our fun.

With a Nexus 10 there is a catch and there is a way around the issue I just have to find it. Essentially they have in the past but able to overcome the camera issue by instead of using the platform camera (camera.exynosX. The x being exynos 4, 5, etc) they were able to build the ROM and or kernel by directing them to use instead Samsung's cameras or the code that would make them operational. Now I have found what appears to be that particular code, but I have yet to be able to complete a successful build of a ROM using them.however that's not bad news because I think this latest issue is my own fault because I've come across it before and I don't remember what I did to fix it LOL. But if that is the least of my worries with all the work I have done so far on this tablet, I consider that to be pretty darn good. So for now you can enjoy the luxuries of having a brand new updated ROM, which by all means everything works with the exception of the camera, or wait until I come up with a solution to the camera issue or give up either way I will keep you updated.
[Nexus 10 Android Development] locuturus:
Has anyone managed to flash Magisk? I haven't been able to with 20.4; the script complains: 'boot image patched by unsupported programs' and then ends with error 1.

I started with Super SU then tried flashing Magisk before removing Super SU, after removing Super SU, and again after updating to the 3.4.99 kernel.
[Nexus 10 Android Development] DragonFire1024:
You're going to have to restore the stock boot image from the original zip file of whatever ROM you installed then flash magisk.
[Nexus 10 Android Development] DragonFire1024:
Once you restore the stock boot image you're going to have to learn a crash course on either building a kernel or unpacking a boot image to insert a new kernel. it's actually quite easy, but I'm not going to waste the time discussing it if you already know how to do it. So let me know and we'll go from there. There are several ways of doing it that minimize requirements.
[Nexus 10 Android Development] freshlysqueezed:
The kernel that dragonfire posted a few days ago seems to work with magisk 20.4.

https://xdaforums.com/showthread.php?p=82690921
[Nexus 10 Android Development] locuturus:
I was thinking, at the time, that it was implied I was on the ROM you supplied in the OP but I see now I could have specified that better. So to be clear I have been using the 6.0 ROM from your OP the whole time, and I started with the boot image you provided in the same post. I do know something about how to unpack a boot image with osm0sis's tools, that is how I upgraded to 3.4.99*, but I do not know how to build a whole kernel.

*I see now you recently provided a stock, unrooted, 3.4.99 kernel so I suppose I could just flash that? Or is there an advantage to unpacking and making some tweaks in there myself?
[Nexus 10 Android Development] DragonFire1024:
I just find it to be easier in most cases to provide the instructions and tools to complete the job given the many different methods and work people do to their specific devices. I don't use magisk unless I have no other choice. Other than that all devices I own and that are rooted are with SuperSU. I don't know why Magisk cries about needing and original boot image. I know there's some kind of obsession with not having to touch as much of it as you absolutely have to but the reality is it mirrors itself on the boot image with everything that's on the system so what difference does it make. Anyways there is no benefit one way or the other it just depends on your level of technical advantage.
[Nexus 10 Android Development] n0j0e:
here with latest kernel and Magisk 20.4 ready..
[Nexus 10 Android Development] locuturus:
I guess we just like what we are used to (: I like using certain modules, and on my Pixel Magisk allows OTAs and DRM and so on with (usually) minimal trouble. I guess it makes little difference to something as old as Manta.
[Nexus 10 Android Development] DragonFire1024:
Well so far as I know modules are not supported on this device or in its kernel. Though the option is added later on in one of the patches it never actually uses any modules. But that doesn't mean it won't in the future or didn't in the future, I still am working on this as we speak. there's an annoying problem I run into sometimes and it's frustrating and it sets me back quite a bit even though it never should. Even after make cleaning the build directory sometimes there are still phantoms left over and it usually doesn't fix itself until I clear the cache. which is now what I generally go to first since that is fixed to each time in the last couple of days that I've been able to sit down and work on this. I've also been able to reseat my memory cards and add some additional ones and I'm glad I actually did that because my memory cards were not properly inserted. And they've been like that for quite some time before I noticed them and when I say quite some time I mean over a year at least LOL that would explain a great deal of many other things and problems I was having before. Anyways off to work!
[Nexus 10 Android Development] DragonFire1024:
Update.

So the ROM I posted here, everything is smooth and I didn't know that tablet could go faster. Wifi seem much improved. The camera is another story. I've been having trouble getting another biuild through but not for any problems that I can't fix, I am trying to push the source code to the limits and giving me as much space as possible on this thing. And I just get barely to the wire and it shuts me out every time. So I'm going to have to go back down to what the original specs say because unfortunately none of the updated ones that show the amount of space some of these images is supposed to have will cause nothing to be flashed.

secondly I'm trying to hunt down exactly where the problem exists with the camera whether it is on a kernel level or on more of a software level in terms of the board. It's not it's definitely not a kernel problem. Because I took the kernel out of a failed ROM and replaced it with the one I linked In the paragraph above, and everything worked as it should have except for obviously the camera. secondly although the camera app does not crash when you open it, various hardware apps clearly show there isn't even a module being registered. This is the very first ROM I spit out and it was just a test and for a test it works pretty good

third everything with NFC seems to be in place but because I have no means to actually test it if anybody has a way to pay through Google pay and use NFC I would like to have it tested because I would like to see if it's working. other than that everything else is bright to go and actually I'm impressed with this being my first actual working ROM on any device.

tomorrow I am back at the drawing board and it takes about two hours maybe three if I don't touch anything for a complete build to spit out. Hopefully we will have more answers tomorrow when we see if the modules I found build properly. Until then enjoy
[Nexus 10 Android Development] DragonFire1024:
All right this is what has got me convinced that I may have fixed the camera. We'll find out in a few hours hopefully now that I have made the corrections that I intentionally broke in the first place. Here's a snip of the little bit of code from the Android make file that may get them working again:

# HAL module implemenation stored in
# hw/<COPYPIX_HARDWARE_MODULE_ID>.<ro.product.board>.so
LOCAL_MODULE_PATH := $(TARGET_OUT_SHARED_LIBRARIES)/hw

And

LOCAL_CFLAGS += -DSAMSUNG_EXYNOS5250
[Nexus 10 Android Development] DragonFire1024:
Okay I ran into some issues. And I'm not sure where they're at so I have to go and look through everything piece-by-piece and figure out what's going on. for some reason something in the system is causing it not to flash properly. It's not a kernel issue because that works fine. could be something in the kernel that's not allowing the system to flash properly which is likely the fstab. I don't know I'm going to have to download a zip of the repo and look over the files and see what I'm missing and replace it. I'm also going to have to resync the sources and see if that does anything. As of now when I flash it all I get is a black screen. The device does not reboot it does not go back into recovery it just sits at that black screen. I find it very odd that the very first ROM that I built for this thing worked perfectly so far except for the things we suspected, but I'm having so much trouble now. Oh well more work to do tomorrow. ☹️
[Nexus 10 Android Development] DragonFire1024:
Okay whatever I did I have fixed. Now for a little bit of an update. I'm pretty sure I can get the SEC camera module to build and install on the tablet but, the air message "cannot connect to camera" has now arrived. Which I don't know if that's better or worse than before. Still still working on it.

Secondly, without a modified TWRP, to change the partition layout, f2fs is unavailable for this device. That was the problem I had before as it was trying to create f2fs images, but could not do so due to lack of space. So ext4 it is, and I'm not sure how much further on Android that can go before it changes again.

I'm going to take the next day or so to try and fool around with the camera modules a bit more to see if I can get anything working. The thing I'm confused about is there is libcamera and libcamera2. The second, libcamera2 has the build files for exynos5 camera, and the Hal files I found have SecCamera in libcamera. The module builds when removing libcamera2 but no application builds. ??
[Nexus 10 Android Development] DragonFire1024:
Ok so...it doesn't look like the SecCamera will work, unless I can find the "universal" hardware/device tree or the "common" tree. You can't mix and match the files unless it uses some already. It appears back the days of KitKat they got this to work but through the kernel. So I added USES_CAMERA_STUB :=true which should direct the board to not use the platform/hardware camera. But without all the proper files, it doesn't even build a module. I will post a screenshot later of both camera modules on the 6.0 ROM because it's kind of messed up how it's listed. Then I need to install stock again and see the camera modules on hat one. I won't say what it is I suspect until I checked that cuz I don't want to jinx it.
[Nexus 10 Android Development] DragonFire1024:
Okay here is the screenshot of the list of camera modules on the ROM 6.0. I don't know what they are. I also provided a screenshot of the first Hardware page which doesn't seem to show any of the camera modules but I could very well be wrong. So the question is how should we proceed from here? All the hardware modules such as the hardware composer and whatnot will have to be switched to the common tree if I can find it.
[Nexus 10 Android Development] DragonFire1024:
Okay update on the camera situation. I think I've discovered the problem why they won't work on any of the devices on recent builds past 6.0. The source files in the repos are for ExynosCamera. On this marshmallow ROM, the camera is ExynosCameraHAL2. Without the proper files in the repo and if build files don't exist, then it doesn't look like they will ever work on anything past marshmallow. I will contact the developer and hope he can shed light on how he got HAL2 to even work. It also doesn't appear the common tree will work on this either just based on the above observation. So I find the right source files, we may have a chance. If not, no dice. Sorry guys I spent a lot of time tracking down every error and this is the unfortunate case. This is due most certainly because the code never got updated and once CM died, so did development on fixing the issue which back then, would've been relatively easy to do.
[Nexus 10 Android Development] DragonFire1024:
One other thing to note I believe I've also for the most part solved the problem of the tablet powering down at almost exactly 20% saying there is zero battery left. All it required was a simple change in the framework to allow for automatic power modes to operate by changing the value from false to true. That seems to have pretty much fixed that issue all together. I tested out a few more things and I think it's good to go so the next few days I'll release a framework and a guide to install it. Couple of added features as a result so nothing too exciting though.
[Nexus 10 Android Development] DragonFire1024:
Well hopefully some good news to come out of the camera issue it appears I may have found the proper blobs (source files). Google has tucked them away and tagged them in an archive, that's not publicly displayed, but is publicly accessible. Turns out I've been looking in the wrong spot. If these are the right files which I have hopes they are, they were tucked away underneath the archive for a "preview of Android m" specifically for exynos5. I don't think it was anything they did intentionally in terms of trying to hide the source rather than because it never made it to the manufacturing point they simply placed it into an archive before the entire source went public and never updated their table of contents in the process.

https://android.googlesource.com/pl...g_slsi/exynos5/+/refs/tags/android-m-preview/

this is actually frustrating because I could not find any of these files on any of the prior searches I've done without actually looking up the specific camera module name and I was only able to figure that out while reading logs on the device.