yashsingh1/xdaforums huggingface dataset:
[Nexus 10 Android Development] Axel85:
Hi , soreading all the posts Can anyone confirm magisk is working? I need it to virtually unplug hdmi so sky Go would not detect nexus 10 connected to tv . Anyone tested micro hdmi ? Right now I'm running remix os but magisk can't work correctly on lollipop
[Nexus 10 Android Development] ThePx:
Magisk is working for me.
[Nexus 10 Android Development] _Misfit_:
Hi!

Which exact version of the linked Netflix APK did you user?

These are all ARM64 APKs and the Nexus 10 is just ARM.

When I used the SAI method I got the error that the device is incompatible and with the TWRP install method, the installation went without errors but after a reboot Netflix app didn't show up in my system.

Thanks!
[Nexus 10 Android Development] Narcoticx:
No more updates?
[Nexus 10 Android Development] ThePx:
THIS is the last version I'm using. It's a bundle so it contains ARM64 and ARM as well.

I had that same error with the first kernel version, the only Netflix apk supported was an old one provided by Netflix itself, but it didn't allow downloads.

After updating the kernel (3.4.71) I've been using the APKs provided in that thread without any problem.
[Nexus 10 Android Development] _Misfit_:
great, thanks for the link!

I already had the 3.4.71 kernel, but with this netflix ARM version it works. :)
[Nexus 10 Android Development] n0j0e:
Can anyone describe a proper how-to-installation please?

The 5. "Download the boot.img" url is dead on Gdrive.
[Nexus 10 Android Development] ThePx:
Try the one in THIS post.
[Nexus 10 Android Development] Axel85:
Can you confirm that magisk hide it's not working? It doesn't stick after an app closing or reboot
[Nexus 10 Android Development] andynx1:
Hi all,

I'm currently using lineage 16, based on android 9.

The USB post on my nexus 10 doesn't work, and I charge with the pogo connector on the side. But the pogo connector is only good for charging, not for any data connection.

Therefore, I can't wipe everything and connect to a PC. I have twrp installed. Can I download this ROM to my nexus 10, and flash from here? Or do I need to wipe everything and connect to a PC (which I can't do).

Thanks.
[Nexus 10 Android Development] ThePx:
Magisk Hide is working for me, except for one bank app but it didn't work since before I tried this ROM.

I haven't connected my Nexus 10 to a PC in a while. I downloaded all the files and wiped everything with TWRP, except for the internal storage, after that I flashed those files and that's it. All in the same "session" of TWRP.
[Nexus 10 Android Development] andynx1:
Thanks.

It's just that the instructions say to wipe everything, and that memory gets repartitioned.

I'll give it a try.
[Nexus 10 Android Development] andynx1:
OK, so thanks again, it worked just fine. Installed the ROM last night, and have been trying it out.

First problem was a bit bizarre, there was no way to install widgets. So I installed Nova launcher, and its OK now.

Do others have location working? Doesn't work for me, unfortunately. I have high accuracy selected, which also uses wifi - but nothing. [MENTION=8165603]DragonFire1024[/MENTION] mentions this and says he has a fix, which would be good. Location is used by loads of apps, eg IMDb, weather, maps etc.

But, the cameras work, which is great, and the general feel is smooth and stable. Just need to get location working.

Thanks for a great ROM.
[Nexus 10 Android Development] Axel85:
Hide feature it's not doing anything , it's not working because if you close magisk ( clear from recent apps) or reboot the tablet , the setting won't stick and revert to not hided . This is the same problem I have in remix os
[Nexus 10 Android Development] ThePx:
If the hide feature is important for you maybe you should try Xposed + RootCloak, or even try SuperSU.

The combo SuperSU + Xposed + RootCloak worked for me on LOS, I haven't tried it with this ROM or with Magisk but hey, this is an old tablet, maybe it works better with old software.
[Nexus 10 Android Development] n0j0e:
Hi, i'm with Magisk 20.4 on the kernel which you are released after some weeks ago (image-new.img 5,33MB).

Now after flashing your new boot.img (16MB) and trying to flash Magisk 20.4 again i get..

- Checking ramdisk status
Loading cpio: [ramdisk.cpio]
! Boot image patched by unsupported programs
! Please restore back to stock boot image
- Unmounting partitions
Prozess Updater endete mit FEHLER: 1
I:Install took 2 second(s).
Fehler beim Installieren von ZIP '/sdcard/#Lager/Android 6.0/Magisk-v20.4(20400).zip'
[Nexus 10 Android Development] ticky33:
Unable to install magisk with the new kernel 3.4.84
[Nexus 10 Android Development] DragonFire1024:
I believe if I recall correctly, I don't have any devices with magisk but I have used it before oh, you have to actually flash original boot image from the ROM to the device flash magisk and then update the kernel if I'm not mistaken. to do that you would have to unpack your boot image with the ROM or the boot image with magisk using something like Android image kitchen or if you have Linux mkbootimg. If this becomes too much for any of you guys then when I get home in the morning I will go ahead and make a fresh boot image from the ROM that includes the new kernel.
[Nexus 10 Android Development] DragonFire1024:
another user had the same problem I'm pretty sure you have to restore the original boot image then update the kernel and then flash magisk. when I get home I will go ahead and make a fresh boot image with the brand new updated kernel, and it will be an unrooted boot image so that should work with installing magisk. If not you will have to grab the original boot image from the ROM, and the boot image from my post above, unpack them using Android image kitchen or if you use Linux, mkbootimg, go into the split image folder and replace boot.img-zImage with the same file from the updated boot image I posted above.
[Nexus 10 Android Development] DragonFire1024:
I've been trying to find thermal support for the kernel for quite some time. turns out the reason why I haven't been able to find it is because the drivers are not supported until version 3.6.x :(

Also if you have a problem with your tablet constantly changing WiFi Mac addresses, some people have that feature set up other routers to monitor it, only way to shut off the randomization or at least let the router recognize your device as being the same one every time it reboots is to set the net hostname. you can have your device be named whatever you want and you have to add this to the build prop:

net.hostname=YourDesiredName

Then open terminal emulator on your device or use ADB and set the prop manually

adb shell
su
setprop net.hostname YourDesiredName
[Nexus 10 Android Development] n0j0e:
Didn't work. Same error.
[Nexus 10 Android Development] DragonFire1024:
It does say in the error that you have to reflash the stock boot image. So you have to take the boot image from the ROM when you installed it (that means extract it from the zip file in OP), flash it in Recovery, Flash magisk and reboot the system. Make sure you have proper root. Then open a shell or terminal emulator on your device:

su
dd if=/dev/block/mmcblk0p3 of=/sdcard/boot.img

This will save a copy of your boot image in your internal storage. Then go to this link and download Android image kitchen for Windows or Linux depending on which OS you use. Follow the instructions to set it up then copy the boot image from your internal storage to your PC. Unpack the boot image and in the Split Image folder copy boot.img-zImage and paste it somewhere safely on your PC that's out of the way for now. Now take the boot image from this link (this has the currently updated kernel that I just posted about) and place it into the Android image kitchen folder and run the cleanup script and then the unpack script. Copy and paste boot.img-zImage to the unpacked boot image that came from your device. You can delete the old zImage from that folder or overwrite it with the new one. Run the repack script, move the new boot image to the device and Flash it in TWRP all should be good and you should still have root.
[Nexus 10 Android Development] n0j0e:
If i replace the boot.img-zImage in unpacked stock boot.img (MantaM_twrp-flashable.zip) with the new boot.img-zImage from new boot.img i get freezing phone service and can't do anything except reboot to recovery. But flashed Magisk v20.4 in twrp without error! :D

ps: didn't read your post above before this post. I understand what you mean with Magisk patched stock boot image and will try it if Manta accu is full of charge again. :o
[Nexus 10 Android Development] DragonFire1024:
Do you still need the fix for location services? Go here and download the framework https://drive.google.com/open?id=1b7u4Up6nxCUX3uAXeiUFNIldgci79gPL and Keep it in your downloads or place it in your desktop folder or your home folder if you're on Linux (as long as that folder has access and is able to use ADB), navigate to the folder you just placed it in, and type the following below using ADB. You must use ADB to do this.

adb root
adb remount
adb push framework-res.apk /system/framework/framework-res.apk
adb reboot
[Nexus 10 Android Development] andynx1:
Thanks for replying, I really appreciate it.

Unfortunately I can't do that, as my USB port is not working. I'm using the side connector to charge, but this doesn't carry data.

But, thanks anyway.
[Nexus 10 Android Development] DragonFire1024:
if you have a quick enough finger you can try doing it through a file explorer like Root explorer, or you can attempt to do it through twrp. Just in my experience I never seem to be able to do that properly or at least it doesn't work for me but that doesn't mean you can't try. Just make sure you backup your framework before you go moving things around. Aside from that I don't see why it shouldn't work oh, but I'm more comfortable with using ADB then I am with doing it manually.
[Nexus 10 Android Development] Axel85:
Yes I will try thank you . The problem for me is to find a balance between performance and sky go working . Sky go is very restrictive on root or other modifications , and I'm trying to find a way to hide those things to it . Elsewhere Nexus 10 still is a great tablet for multimedia contents
[Nexus 10 Android Development] DragonFire1024:
I sent you a message regarding something that has to do with the Google play store. it may or may not be of assistance to you I have no idea I have never actually tried to see if this had any effect. But it would be nice to get a second opinion.
[Nexus 10 Android Development] n0j0e:
Flashed new boot.img with Magisk 20.4 successfully!

Do i need the ramdisk-new.cpio.gz after repackimg ?

/system/etc/init.d/swapon didn't work for me. Permissions are ok.

Looking for another solution like Franco Kernel Manager with the script start @ boot feature or /data/adb/service.d/

EDIT: /data/adb/service.d/swapon.sh works here.
[Nexus 10 Android Development] DragonFire1024:
Weird maybe try creating a su.d folder in /system placing a copy of the swapon file there while leaving one in init.d give it the same for missions and do a reboot and see if it works that way. But if your way works that's equally as well. I had found after using it for an extensive period On several devices that apps2sd although useful, can go crazy and wreak havoc on older devices with its scripts. And just has a habit of causing more problems than good in terms of performance. Also glad to see you got the kernel to work successfully.

I have been able to make further upgrades to the kernel, up to 3.4.99. before I continue trying to go any further does anybody know if I can upgrade further to 3.5.x? the next patch I'm having a lot of trouble with 3.5.1-2 (3.5.100 is alpha one but I'm not in front of my pc at the moment so it could possibly be 3.4.100) and it will take some time for me to work on it and figure out the commits I need to cherry pick out of the patch in order for it to properly patch the kernel. That's of course assuming I am able to do so.
[Nexus 10 Android Development] n0j0e:
All fine now! New kernel + Magisk 20.4 + swap.file + swapon.sh are working.

swapon.sh: Maybe Magisk service with /data/adb/service.d/

I have absolutly no skill about kernel compiling etc. sry!
[Nexus 10 Android Development] TiggaZ:
Hi, thanks for the great work and the latest kernel.

How are the chances that the kernel will also work with other Marshmallow ROMs like Omnirom or LineageOS?

They have later releases and probably more (securitiy) fixes as the original AOSP ROM from dmitrygr.

I will now check on the AOSP mostly because all later ROMs are too slow and not swappy.
[Nexus 10 Android Development] andynx1:
Hi again, and thanks.

Finally plucked up the courage, and replaced my framework-res.apk with the one in your link. I used root explorer, and as soon as the new file was in place, my phone went into a bootloop. I copied it over, and chose 'replace' the file.

Using TWRP I was able to restore the backed up framework-res.apk, rebooted, and everything was fine. Couple of questions:

Should I have replaced framework-res.apk, with yours?

Your framework-res.apk is about 7mb, the original is about 15mb. Is that OK?

Thanks.
[Nexus 10 Android Development] DragonFire1024:
Just how apktool recompile that I suppose. Not sure but I do know it has to do with compilation of the APK. This happens on other devices I work on as well. Then I suppose the only way to do it is to use ADB. Using ADB by remounting the device and pushing APK automatically sets the permissions without you having to set them manually. That seems to be an issue on this device for some reason and your experience is one of the saying that I had when first trying it on this one. as long as you were able to restore your original framework then you are okay nothing should be lost but it may take an extra minute or two for the device to reboot.
[Nexus 10 Android Development] DragonFire1024:
Was wondering how the internet connection has been for anyone who is installed the new kernel?
[Nexus 10 Android Development] TiggaZ:
WLAN is kind of wonky. Sometimes very good speed then suddenly very slow. I recognized this while watching Youtube which starts with a good resolution (720p) then reduces to low res (144p).

I thought is is an old issue with Nexus WLAN and CCMP connection (old android bug). I tried it to fix with TKIPPER but it didn't solve it completely.
[Nexus 10 Android Development] DragonFire1024:
Okay then that about describes the issues I had. All right give me a few hours and I will see what I can do with posting the latest update I did which was to 3.4.99. I couldn't say exactly what was causing the issues but I kind of figured they might have started to happen on other devices after working pretty good. I know it's something to do with the network settings I just can't remember which one I had Deconfigured. So I started out with a fresh platter, applied all the patches and re-added options and features when that was complete and the problem whatever it was no longer persist in fact I would say it probably improves the Wi-Fi quality or Internet overall. I like to run new kernel builds for at least a week or so before posting updated versions here in case anything goes terribly wrong along the way. So I apologize if it seems like that's why it's taking me so long to update the versions.

I may have fixed the hardware issue for building Android 7.1. so it appears that it is something to do with HAL and HAL2 and incompatibilities with the code which builds the modules which build the library files which make the camera work. I've spent several days tinkering with the directories and files and folders on both the official AOSP and lineage repos. Trying to fix as many of the problems as I could to at least get the library files to build and it appears I have been successful with that. Now the only problems I seem to be having are some of the vendor proprietary files will not properly extracted from the device so I have to wait for each of those errors to pop up, which sometimes take as long as a half hour to 45 minutes before the build process halts because one file isn't where it is supposed to be and I have to physically extract it from the device and place it into the proper area in the vendor directory. So until all of those files are properly put into place I won't get a clean build.everything was going good right up until I had to leave the house to go to work when it aired out again so I don't know what had happened and I won't know until I get home. But if all goes as well as it has been the last several hours then hopefully I will be able to test a build in the next few days or less.
[Nexus 10 Android Development] DragonFire1024:
What's New?

- Update to version 3.4.99

- Fix various issues with Wi-Fi being a bit wonky and probably actually improving it a bit.

- Patch files related to Mali ARM GPU to prep it for upgrade. Arm has updated gpus for this device. The problem is I have to rewrite the whole script in order for the main patch to apply correctly. This update adds additional settings and profiling options to the GPU for this upgrade to be added later on if possible. It is a full version upgrade so I hope I can get this working. For now if you can find a good kernel tuning application that can properly hook into the profiling settings you can tweak Mali GPU. I have to hunt down additional build files for adding advanced settings which do not appear to Build properly or adds the drivers that are required for it to work.

- Various other tweaks and performance improvements

Installation is the same as before. Download this tool to use on Linux, Windows or on your own Android device to unpack and repack your boot image. I am rooted with SuperSU so you're going to have to restore your stock boot image if you are rooted with Magisk, before updating your kernel. Download the attached zip and extract the boot.img-zImage. Unpack your Restored stock boot image and in the split image folder copy and paste your boot.img-zImage to somewhere safe in case you need it again. Then copy and paste the new boot.img-zImage into the split mage folder. Repack the boot image which will be named 'image-new.img' and flash in TWRP and reflash root.
[Nexus 10 Android Development] DragonFire1024:
Future?

- Thermal controls and modules are added in later versions of the Linux kernel. I don't know why they haven't been implemented earlier but when I get brave enough I will try and see if I can apply them to the current version I have updated our kernel to so far.

- Update (try) GPU versions. Device has a dev/debug version, whereas the ARM update is standard, but a whole version upgrade from v5 to v6. this requires rewriting a lot of the script mostly just to change version numbers. Because the script is written only for the standard GPU I have to change certain lines that relate to standard, to recognize the 'dev' so an update can be patched.

- other drivers are missing for various other settings and toggles for CPU related functions such as power. I still have not been able to figure out what is causing the device to power off with 20% battery left. It doesn't happen all the time but when it does it happens at the worst time. I have continued to tweet the power modules with seemingly no effect but that does not mean anything as there are still some drivers that are not being applied to the places they should be because the files do not exist to build them. Which means I have to play a game of hunting.

- I believe that lineage OS has updated or supply the proper scripts and build files 2 properly build the HAL components, or I am just that good at fixing things ;) but if true, and the module function properly that would mean sensors and camera should also function properly as well. the only reason why I haven't recommended any other available ROMs for this device is because most of them do not have a functioning camera. Not that that's a deal-breaker on necessarily all devices because the current tablet I am using now to post this, does not have a functioning camera yet it is my daily driver for the moment. The reason why I do not want to recommend a rhyme for this device without a working camera is because of the simple fact that this is one of the few devices that have a pretty darn good camera for a tablet.
[Nexus 10 Android Development] n0j0e:
Respect! :good: :laugh:

Thanks for your hard work!

So we can see a 7.1 build near future?
[Nexus 10 Android Development] DragonFire1024:
It's not that a ROM won't build, but with the amount of errors that being created it nearly disabled much of the features this tablet has. So there really wasn't any kind of point in building one if they weren't going to work and I know that much of code on all devices is never updated regularly or even properly in some cases. One issue I think I am having the most trouble with is different compilers were used between the versions of Android from 6 to 7. That makes it a bit more difficult to build with library files that weren't designed or built with the intentions of going on any Android device higher than lollipop. Some of the files just won't build. But they won't build not because the hardware is not compatible but so far in my experience with trying to fix the issues specific to this device when it comes to building a ROM, that it's a matter of fixing code that has not been updated or is broken because of the updates and therefore doesn't work because too much of it needs to be manually updated which can be frustrating. Is that and I also believe some of the proprietary files were not in place properly and also posing a problem for some of the sensors to build properly. The problem with building directly through AOSP is it doesn't tell you those things and you have to search for hours in some cases on the internet for answers and sometimes it's very simple and other times it's very complicated. Basically I'm hoping I can build through lineage and then transfer some of the files from their repo over to AOSP to complete the build process over there. Honestly this was an experiment that I wasn't expecting to work so I'm kind of excited and hopeful. I don't like lineage I never have and probably never will and much prefer to build a through AOSP direct.