Develop Bugs

Viper4Android Help

I've been trying to get Viper4Android driver installed but it keeps failing.
I've tested CM11 and Stock but no go when I hit install driver. I'm guessing it may have something to do with SE Linux as I have to set it to permissive but haven't had any luck with trying to change it as apps do not detect it.
Just looking to see if anyone else had any luck with the app on their Fire Phone?

I had it working without problems on CM-11. SELinux is disabled on that ROM, so no drawback here, no need to change anything...
Before I annoy you with more stories, tell us which file you used exactly to install V4A on your device.
I had to use SELinuxModeChanger on other devices (they used "enforcing") because they didn't offer a setting to change the SELinux mode.

Bingo Bronson said:
I had it working without problems on CM-11. SELinux is disabled on that ROM, so no drawback here...
Before I annoy you with more stories, tell us which file you used exactly to install V4A on your device.
Click to expand...
Click to collapse
I've reviewed the following thread
http://forum.xda-developers.com/showthread.php?t=2191223
I've tested 2.4.0.1 & 2.3.4.0 but can't install the driver. I have BusyBox Pro installed and running and reviewed the logs in SuperSU but i have no idea whats going on when I try the driver install.
Screenshot of Super SU Log: http://postimg.org/image/wdhvthr73/
I am currently back on CM-11 if you have any steps for me to try...

Kerrona said:
I have BusyBox Pro installed and running [...] I am currently back on CM-11 if you have any steps for me to try...
Click to expand...
Click to collapse
Hm, well that's interesting... I also used Stericson's busybox (non pro) and it worked right away... (I also used "ViPER4Android_FX_v2401_A4.x-A6.x.apk")
Maybe reinstall busybox... why isn't it able to find the "toolbox" / why is it calling the path with failsafe?
I see you have some security / privacy / permission tools running... can't really vouch for a hassle free install in such an environment.
You could try to flash this zip from safestrap recovery, this worked for me on other devices and the driver is already integrated, no need for a separate install from within the app.

This has something to do with superSU Binaries updated from normal method, if you have updated super su from playstore then you have to wipe the system partition reflash the rom and latest superSU zip. Otherwise you can flash the pre-build V4a zip as suggested above.

Thanks guys.
I got the driver installed and enabled now with the flash version.
Will probably wipe and start fresh and try the apk again.

Using Supersu with LineageOS (Q).

Hi.
I have a question regarding how supersu installs on LineageOS.
I recently flashed LineageOS ROM over OnePlusOne cyanogenMod.
With the help from members in Q&A forum I successfully flashed supersu.
Upon completion, the settings in Developer Option showed 2 options for Root access.
1. ADB-only 2. Disable (see screenshot). I selected adb-only. Installed root checker and Titanium backup and was able grant root permission and execute Titanium bkup.
I was under the impression, you must choose (adb and apps) for root access, but as you see on my screenshot that option is not available.
(Q): How did I get supersu root access for apps using adb-only?
Installation Performed:
After several failed attempts trying to install supersu, I went to my original TWRP backup and did a full restore of LOS and GAAP.
Copied supersu zip from PC to Phone internal storage, selected, Install and rebooted. (did not wipe).
When finish, selected adb-only (as I stated above) and supersu worked. (see screenshot).
I am aware there is a LOS extras patch available to install, having Root access (adb and apps) option, but I cannot understand why it worked with the option I choose.
Does LOS have an internally supersu root (all) flag built in their release that can be triggered by adb-only? I tried selecting adb-only and failed having Sultans LOS zip installed, before doing a full TWRP restore of my files as a last option.
The LOS build I used was 14.1-201707703-Nightly bacon.
The Supersu I installed was Update-Supersu-v2.82-20170528234214.
Thanks.
TC.

@tomx2x
I prefere LOS's addonsu.

Out of interest, why SuperSU? Have you given Magisk a try?

vikashhero said:
Out of interest, why SuperSU? Have you given Magisk a try?
Click to expand...
Click to collapse
Is there any advantage besides that safetynet thing?

kurtn said:
Is there any advantage besides that safetynet thing?
Click to expand...
Click to collapse
Modules

vikashhero said:
Modules
Click to expand...
Click to collapse
Mostly looks like solutions for problems which I don't have as long as I don't install magisk.

vikashhero said:
Out of interest, why SuperSU? Have you given Magisk a try?
Click to expand...
Click to collapse
kurtn said:
Is there any advantage besides that safetynet thing?
Click to expand...
Click to collapse
Some people prefer Coca-Cola, others prefer Pepsi. The nice thing is that there are choices, and we can use whatever solution we like (I use SuperSU, myself, as I've not encountered a situation where I'd need Magisk).

My preference is beer. But in AEX they only served that brown lemonades.
tomx2x said:
(Q): How did I get supersu root access for apps using adb-only?
Click to expand...
Click to collapse
Did you try to run SuperSU without adb-only? I think, these buttons are only beer bottle openers for addonsu. Thy have no effect on your lemonades. AEX has no built-in opener at all.

kurtn said:
Mostly looks like solutions for problems which I don't have as long as I don't install magisk.
Click to expand...
Click to collapse
Well there's modules, and the fact that it's open source whereas SuperSU is not. If Chainfire still owned it, I'd worry less, but I'd want some transparency behind a third party application used to handled root access on such a personal device.
I'm not suggesting that CodingCode is doing anything dodgy with SuperSU, but it does give me peace of mind using something open.

vikashhero said:
Well there's modules, and the fact that it's open source whereas SuperSU is not. If Chainfire still owned it, I'd worry less, but I'd want some transparency behind a third party application used to handled root access on such a personal device.
I'm not suggesting that CodingCode is doing anything dodgy with SuperSU, but it does give me peace of mind using something open.
Click to expand...
Click to collapse
Did anyone try the open source alternative pph's SuperUser?
Looks like the LOS addonsu is open source: https://review.lineageos.org/#/q/project:LineageOS/android_system_extras_su

kurtn said:
Did anyone try the open source alternative pph's SuperUser?
Looks like the LOS addonsu is open source: https://review.lineageos.org/#/q/project:LineageOS/android_system_extras_su
Click to expand...
Click to collapse
phh's one was good, yeah
The LOS one works fine too, as you'd imagine. That's the one I'm currently using, but if I need to use Android Pay (on some weekends I do make use of it) then I'll switch over to Magisk.

Best OOS kernel ?

Hi, i'm looking for the best kernel for battery/performance ratio.
Already used stock but i wonder if there is something better.

I would say the best one is blue spark kernel

saucissemanger said:
Hi, i'm looking for the best kernel for battery/performance ratio.
Already used stock but i wonder if there is something better.
Click to expand...
Click to collapse
use blue_spark kernel good for performance and batrery.
using it since first beta out.

vk_singh said:
use blue_spark kernel good for performance and batrery.
using it since first beta out.
Click to expand...
Click to collapse
Will do , thanks

vk_singh said:
use blue_spark kernel good for performance and batrery.
using it since first beta out.
Click to expand...
Click to collapse
Hi one question there are some settings to applied or just flash and profit ?

ElementalX is my best choice, so far - have been using it for a few days. To me it seems as fast as blu_spark, and it has the sound settings too (which I need for playing loud enough on the fitness center's music equipment - where I work). Battery life seems to be great, but I cannot report on that until i've used it more.

Again?!? There is no"best" kernel. What works good for me may not work as well for you. There are variables. Signal, apps installed, usage patterns. Try them all and find the "best for you" kernel.
Sent from my ONEPLUS A5010 using Tapatalk

jmtjr278 said:
Again?!? There is no"best" kernel. What works good for me may not work as well for you. There are variables. Signal, apps installed, usage patterns. Try them all and find the "best for you" kernel.
Click to expand...
Click to collapse
+1.
From my point of view, the most important is : stability / smoothness / security fixes / wireguard
For me, the kernel that best suits my needs is Flash Kernel, thanks a lot to nathanchance for its really great work :good: !!

How do I get back to the stock kernel if I do not like another one?
It's easy?
I want to install another kernel but be able to return to the stock if I do not like it

Princeland said:
How do I get back to the stock kernel if I do not like another one?
It's easy?
I want to install another kernel but be able to return to the stock if I do not like it
Click to expand...
Click to collapse
You simple flash your OOS fullzip ROM.

re_endymion said:
You simple flash your OOS fullzip ROM.
Click to expand...
Click to collapse
Then I lose everything? My applications, my data... etcetera

Nope. Just don't wipe anything but dalvik&cache.

szymko1995 said:
Nope. Just don't wipe anything but dalvik&cache.
Click to expand...
Click to collapse
OK thanks. One more question ... I have a system notification to update my Op5t to the latest Oxygen OS 5.1.2, how should I do to update, what steps should I follow? I download the full ote and install and then wipe cache and dalvik from twrp or should I go back to the recovery stock? I've never used the twrp to update and it's my first time with a One plus ... Now I'm with Oxigen OS 5.1.1 android 8.1 stock .... Greetings

I'm using RenderZenith and I personally think it's both smoother & snappier/more responsive than stock kernel. Battery life seems very comparable to stock kernel, possibly a bit better. Unfortunately, I cannot give a comparison of stock vs RZ kernel as far as battery life goes as my day-to-day usage is too irregular to give an accurate comparison.
---------- Post added at 07:17 PM ---------- Previous post was at 07:01 PM ----------
Princeland said:
OK thanks. One more question ... I have a system notification to update my Op5t to the latest Oxygen OS 5.1.2, how should I do to update, what steps should I follow? I download the full ote and install and then wipe cache and dalvik from twrp or should I go back to the recovery stock? I've never used the twrp to update and it's my first time with a One plus ... Now I'm with Oxigen OS 5.1.1 android 8.1 stock .... Greetings
Click to expand...
Click to collapse
If you're rooted you'll want to download the full OTA. Easiest way to do that is through Settings>Software Update. If you're rooted it will automatically detect you're rooted and flash a pop up saying "hey you're rooted, and because of that, we'll download the full Zip file" (along the lines of that).
Once downloaded, disable and uninstall any substratum themes (if you have any), & boot to recovery. Once you're in TWRP, follow these steps:
1. Wipe > Dalvik/Cache only
2. Click Install, from there you'll want to navigate to sdcard/.ota, the update should be located in this folder
3. Flash the ROM update.
4. Flash Magisk (ensure you're not using 16.4) The Magisk version you flash should be the version you were previously using on 5.1.1. Do not try to update Magisk while also updating ROM.
5. Wipe Dalvik/Cache (I always do for good measure, not really necessary)
6. Reboot, & enjoy 5.1.2.

crashazz3 said:
I'm using RenderZenith and I personally think it's both smoother & snappier/more responsive than stock kernel. Battery life seems very comparable to stock kernel, possibly a bit better. Unfortunately, I cannot give a comparison of stock vs RZ kernel as far as battery life goes as my day-to-day usage is too irregular to give an accurate comparison.
---------- Post added at 07:17 PM ---------- Previous post was at 07:01 PM ----------
If you're rooted you'll want to download the full OTA. Easiest way to do that is through Settings>Software Update. If you're rooted it will automatically detect you're rooted and flash a pop up saying "hey you're rooted, and because of that, we'll download the full Zip file" (along the lines of that).
Once downloaded, disable and uninstall any substratum themes (if you have any), & boot to recovery. Once you're in TWRP, follow these steps:
1. Wipe > Dalvik/Cache only
2. Click Install, from there you'll want to navigate to sdcard/.ota, the update should be located in this folder
3. Flash the ROM update.
4. Flash Magisk (ensure you're not using 16.4) The Magisk version you flash should be the version you were previously using on 5.1.1. Do not try to update Magisk while also updating ROM.
5. Wipe Dalvik/Cache (I always do for good measure, not really necessary)
6. Reboot, & enjoy 5.1.2.
Click to expand...
Click to collapse
Thank you very much for such detailed information. I will follow your instructions
Regards

Princeland said:
How do I get back to the stock kernel if I do not like another one?
It's easy?
I want to install another kernel but be able to return to the stock if I do not like it
Click to expand...
Click to collapse
If you have root you can use the apk on playstore called flashify. It makes a backup of the stock kernel, if you don't like the result you simple have to restore the stock one.

[ROM+Kernel][MAY 16, 2020] AOSP direct, Marshmallow 6.0 & NEW kernel, version 3.4.99

[ROM+Kernel][MAY 16, 2020] AOSP direct, Marshmallow 6.0 & NEW kernel, version 3.4.99
****UPDATE****
As of May 16, 2020, If you already have this ROM installed, please see this link for an updated kernel to version 3.4.99 with other various editions and Extras. If you are downloading and installing this ROM for the first time download the ROM and Flash it, and finish setting up your device before updating the kernel. You will have to flash Superuser or Magisk again (or whatever your root preference is) after installing the ROM or boot image regardless of whether you're coming from a fresh installation or updating the kernel.
The number of ROMS for the Nexus 10 has dwindled, and those that do remain, have too many bugs and not everything works. I spent a couple weeks looking for a good ROM and finally found one. I did NOT build this ROM, however I DID build the kernel from scratch.
What you get:
- Android 6.0, Marshmallow ROM built directly from the AOSP source code. (built by Dmitry.GR)
- Freshly updated kernel from 3.4.67 to 3.4.99, built by Me from source. I used the Manta kernel source (3.4.67) from Omnirom's android-6.0 branch and applied the official kernel patches 3.4.67-68 through 3.4.98-99. SELinux in the boot image provided by the ROM is disabled. Standalone updated kernel/boot image is permissive). Kernel in its original form, would not allow for a permissive selinux so the only option was to disable it.
- In the updated boot image, ADB is insecure (ro.adb.secure=0 and ro.secure=0). This allows for an automatic root shell when running 'adb shell'. It also allows you to remount the filesystem RW through ADB, using the command 'adb remount'.
- No swap or zram options on the original kernel because it was not performing properly. This is fixed on the standalone upgrades to the kernel I have been doing.
What doesn't work:
- Location services may or may not work. If they don't, let me know as I do have a fix for that. For some reason, com.google.android.gms was removed from the framework-res (android system apk). Some apps won't recognize the device GPS and may tell you location is turned off when it actually isn't.
- The camera work however oh, there is an issue with the flash. Every time you use flash the camera will crash after snapping the photo. This wouldn't be a problem except the photo doesn't get saved. I don't know what's causing it and until I can figure that out you can't use the flash on your camera.I have a suspicion or two but I haven't looked into it because I don't use the camera often enough and when I realized the problem I'm never at home to look.
Installation requirements and instructions:
Required:
1. Unlocked bootloader
2. TWRP custom recovery
3. PC with either Windows or Linux
Instructions:
1. You need to wipe the device completely. Boot to recovery, select wipe, format data and type yes and confirm. When done, tap home, wipe, advanced wipe, select all and swipe to confirm. Tap home, reboot, reboot recovery.
2. Once booted back to recovery, plug your tablet into your PC. It should be recognized.
3. Download Open Gapps, ARM, 6.0, Pico and place it on the tablet's internal storage.
4. Download the TWRP flashable zip that contains the ROM and place it on internal storage.
5. Download the boot.img which contains the new Kernel, place in storage.
6. Download SuperSU zip and place in storage.
7. Once done, tap the home button then install. Select the TWRP flashable ROM zip and install it. When done tap home again, install, install image and select image-new.img and install.
8. When finished tap home and install and install Open Gapps. When finished install SuperSU then reboot system when finished.
Kernel installation and updates ONLY
1. Download and extract the zImage from the provided zip at the end of the post.
2. You need to unpack the boot image from the ROM above. You can do this on Windows Linux or your own Android device with the Android image kitchen by XDA developer @osm0sis. After unpacking the image, open the folder named 'split image' and locate boot.img-zImage. make a copy of it and put it somewhere safe, then delete it from the split image folder.
3. Now take the zImage you extracted earlier and put it into the split-image folder, and rename it to boot.img-zImage. Repack your boot image which when done, will be default named to image-new.img.
4. Reboot the device into TWRP or the bootloader and flash your new boot image and reboot.
Screen shot below. You now have an awesome Marshmallow ROM and brand new Kernel for your Nexus 10!!
****Change Log****
February 10, 2020: Updated kernel version from 3.4.69 to 3.4.71. kernel patches not fully cooperating with the disabling of SELinux so I had to re-enable it. Simply placing a small script into /system/su.d (or locate wherever your su folder is and inside will be a su.d folder) to set selinux permissive on boot works perfectly. Create a text file called permissive.sh and copy and paste text below and save it to that folder with permissions: 777. If no su.d folder exists, create one in /system with permissions 755.
Code:
#!/system/bin/sh
setenforce 0

Can I dirty flash this with LineageOS15?

ong14 said:
Can I dirty flash this with LineageOS15?
Click to expand...
Click to collapse
I am going to take a guess and say no. Partition layout changes in Android 8 and 9 so probably won't work. I compiled the kernel with AOSP 6.0 gcc toolchain and I have no idea if this kernel can even support 8 or 9. I have to read further on updating the kernel as this is as far as I can update it for now. Any further patches say they're already added so I have to figure out what I am doing wrong. Also need to figure out how to update security patches.

ong14 said:
Can I dirty flash this with LineageOS15?
Click to expand...
Click to collapse
I am testing out another option. I will know soon enough whether or not it will work.

ong14 said:
Can I dirty flash this with LineageOS15?
Click to expand...
Click to collapse
No luck on the other option. Drats!

I'm charging my nexus right now and I'm gonna try this. I'll report in a few hours.

Update:
February 10, 2020: Update kernel from 3.4.69 to 3.4.71.
Download the zip, extract the zImage. use any one of the various tools in existence to unpack the boot image for the device and in the split-image folder delete boot.img-zImage and replace it with the zImage file and rename it to boot.img-zImage. Repack the the boot.img and flash in twrp or reboot to bootloader and flash in fastboot.
Sent from my Google Nexus 10 using XDA Labs

So I've been using this for a day now and I gotta say I'm loving it. It is stable no crashes or reboots. So thank so much for bringing this out. I've attached some screenshots for those curious.View attachment 4946929View attachment 4946931
Sent from my AOSP on Manta using Tapatalk

Kaleshwar said:
So I've been using this for a day now and I gotta say I'm loving it. It is stable no crashes or reboots. So thank so much for bringing this out. I've attached some screenshots for those curious.
Click to expand...
Click to collapse
Glad to hear. I have tried numerous ROMs on that device and all of them have some kind of flaw or another on a serious level. Either random reboots would occur, random shutdowns, extreme loss of memory and various other things. I got quite excited when I found this one online, with a working download link. Honestly it's exactly what I was looking for straight from AOSP. The stock ROM is also quite good, but it needs to be a bit more recent than lollipop. Because I was so used to stock AOSP on it already I was glad I can continue using AOSP. Never have been a big fan of lineage since they took over cm.and as the days go on it seems I like them less and less.
On a side note once I I'm able to update the kernel to a more recent version, then I will start experimenting with adding features. With that having been said I found it very hard to do so with this kernel. However I'm sure it can't be any more difficult then having to go through failed patches to remove commits and differences that screw up the build. Cherry picking on a whole new level. The only way I can figure out what patches do not work are by patching it and seeing which ones fail. That makes the process very timely.

Kaleshwar said:
So I've been using this for a day now and I gotta say I'm loving it. It is stable no crashes or reboots. So thank so much for bringing this out. I've attached some screenshots for those curious.
Click to expand...
Click to collapse
PS I just caught your screen shot. Awesome home screen! I've also included mine as well as a screenshot of the device has info for the kernel version. In the meantime, kernel auditor works awesome on this device. Especially the entropy settings. This tablet seems to pay on it a bit and increasing the read and write variables a bit, does give this device a new feel.
Sent from my Google Nexus 10 using XDA Labs

I had been using LOS for a long time thinking it was the most "stable" option, but after trying this... WOW, I feel that my Nexus has been reborn. It is fluid, the boot is quite fast, battery performs quite well and so far I have not had any unexpected reboot issues, which in LOS it was a every day thing.
The only thing I miss is being able to use Magisk, but I will survive.
Thank you!

ThePx said:
I had been using LOS for a long time thinking it was the most "stable" option, but after trying this... WOW, I feel that my Nexus has been reborn. It is fluid, the boot is quite fast, battery performs quite well and so far I have not had any unexpected reboot issues, which in LOS it was a every day thing.
The only thing I miss is being able to use Magisk, but I will survive.
Thank you!
Click to expand...
Click to collapse
The saying goes they don't make them like they used to. I have found myself consistently returning to older devices and finding new means to bring brand new life into them. It's not often I get to get a case like this where the difference is so drastic. I literally turned a technically ancient device into what will soon be my new daily driver tablet. Best $50 investment ever.

One thing: the selinux script is working fine, but when I patch the new kernel it get stuck in a boot loop. I have followed your instructions using the Android image kitchen without luck, any idea?
BTW I've noticed that your configuration screen is dark, which theme engine are you using?

ThePx said:
One thing: the selinux script is working fine, but when I patch the new kernel it get stuck in a boot loop. I have followed your instructions using the Android image kitchen without luck, any idea?
BTW I've noticed that your configuration screen is dark, which theme engine are you using?
Click to expand...
Click to collapse
Not sure I'm using the same z image. I'll test it when I get home and see what happens it's the same one I pulled off of mine so I know it works. I don't believe it'll work on the stock ROM so I'm pretty sure you have to be on the marshmallow ROM in the OP. Other than that I'll have to test it and see what happens. You could also use any other tool that unpack and repack boot images, that just happens to be the one I use.
If you look at APK mirror, you can grab an APK for substratum that works on marshmallow ROMs. You're pretty limited in the theme number of themes for it, and there are a few good ones that still exist but are still quite limited. I use PureZ material dark. It won't turn every app into dark mode, including some Google apps, so just download 'dark mode' from the play store which takes advantage of accessibility services to darken most every other app.
Sent from my Google Nexus 10 using XDA Labs

ThePx said:
One thing: the selinux script is working fine, but when I patch the new kernel it get stuck in a boot loop. I have followed your instructions using the Android image kitchen without luck, any idea?
BTW I've noticed that your configuration screen is dark, which theme engine are you using?
Click to expand...
Click to collapse
Sorry it took so long. Busy time at work these days. I honestly don't know what was wrong everything work fine on my end so here's what I did. Instead of using the actual zImage I went ahead repacked it to the stock boot.img from the ROM in OP. That should work but you will have to reflash SuperSU or magisk if you have systemless root.
Managed to add a few features but it's nothing much yet. Added all governors such as powersave, ondemand and userspace, etc. Disabled SELinux again, added debug info and options for GPU, and kernel same page merging (can be deactivated at boot by using kernel auditor or Franco kernel). Also deactivated the option that told the kernel it was using a "fake platform GPU". trying to get some kind of GPU options selectable inside one of the kernel applications. Let me know if it works and I will update the OP with the updated file. Just backup your current boot image and flash the new one in TWRP or push it in fastboot.
Sent from my Google Nexus 10 using XDA Labs

DragonFire1024 said:
Sorry it took so long. Busy time at work these days. I honestly don't know what was wrong everything work fine on my end so here's what I did. Instead of using the actual zImage I went ahead repacked it to the stock boot.img from the ROM in OP. That should work but you will have to reflash SuperSU or magisk if you have systemless root.
Managed to add a few features but it's nothing much yet. Added all governors such as powersave, ondemand and userspace, etc. Disabled SELinux again, added debug info and options for GPU, and kernel same page merging (can be deactivated at boot by using kernel auditor or Franco kernel). Also deactivated the option that told the kernel it was using a "fake platform GPU". trying to get some kind of GPU options selectable inside one of the kernel applications. Let me know if it works and I will update the OP with the updated file. Just backup your current boot image and flash the new one in TWRP or push it in fastboot.
Sent from my Google Nexus 10 using XDA Labs
Click to expand...
Click to collapse
3.4.71 working with the new image, thanks!
No problems so far, I'll update if I find something.

While unpacking boot.img I don't get split-image folder!! Seems the procedure described needs some clarity

ranandi said:
While unpacking boot.img I don't get split-image folder!! Seems the procedure described needs some clarity
Click to expand...
Click to collapse
See this link https://forum.xda-developers.com/showpost.php?p=81747927&postcount=15 flash boot image in TWRP or in bootloader mode. reboot your device then reboot back to recovery and flash magisk or whatever superuser you use. This is a clean boot image from stock so it is not rooted.
Sent from my Google Nexus 10 using XDA Labs

DragonFire1024 said:
See this link https://forum.xda-developers.com/showpost.php?p=81747927&postcount=15 flash boot image in TWRP or in bootloader mode. reboot your device then reboot back to recovery and flash magisk or whatever superuser you use. This is a clean boot image from stock so it is not rooted.
Sent from my Google Nexus 10 using XDA Labs
Click to expand...
Click to collapse
Yes, I could flash new boot image, following two issues:
(1) Camera sometimes shows 'not connecting', but sometimes it works fine.
(2) In clock when trying to set times of mother international zones, clock is not working error.

ranandi said:
Yes, I could flash new boot image, following two issues:
(1) Camera sometimes shows 'not connecting', but sometimes it works fine.
(2) In clock when trying to set times of mother international zones, clock is not working error.
Click to expand...
Click to collapse
1) I can look into the camera. I may know why that happens, though I never had a problem.
2) you may need to install another clock. I didn't stick with the one on the ROM. But try going to /data/used/0 and deleting the folder com.google.androud.deskclock (com.androis.deskclock?) and the contents and reboot and try again. I discovered while I've been testing kernels, that when flashing gapps, it doesn't always update the data files for Google related apps in that directory and causes some of the applications to force close, or not function at all. Also check the SD card Android/data as well and do the same.

[UNOFFICIAL][ROM] crDroid 5.12 for Galaxy Tab E [SM-T560NU][Pie]

I am not responsible for any bricked devices. Install at your own risk!
This is experimental so please post any bugs you find.
SCREENSHOTS
What doesn't work:
I haven't found anything so far that seems to be broken. Doesn't mean it's bug-free though.
How to install:
1. Factory Reset
2. Format Data
3. Flash rom <-- Download
4. Flash GAPPS
5. Flash Magisk [optional]
6. Reboot to system
Enjoy.

I tried to install the ROM to my SM-T560NU, it boots with no issues. It's very laggy to use, so I mess around with crDroid settings and I changed the scrolling cache setting (Settings->crDroid Settings->User Interface->Animations->Scrolling Cache) from Default enable to Default disable, it fixed the laggy issue.
I also tried to flash Vince2678's overclock kernel and it boots with no issues.

This is the Bomb. I have a Tab E TM-560NU. I failed miserably trying to install other roms. But yours went in 1st shot. Nice work!
Question is I'm thinking about putting Magisk, But do I really need it? Is that like SU? Probably a very dumb question.

This rom is for Android 7?

zeovani said:
This rom is for Android 7?
Click to expand...
Click to collapse
>Android Pie
Sorry bud this an android 9 rom lol

edwardnizz said:
This is the Bomb. I have a Tab E TM-560NU. I failed miserably trying to install other roms. But yours went in 1st shot. Nice work!
Click to expand...
Click to collapse
I've experience of flashing my tablet so I can flash my tablet without issues. Since it's too laggy to use, so I switched to LightningFastROM 17.1, for now.
If you had issues of flashing the ROM, I recommend to use this version of TWRP:
https://msm8916.com/?view=downloads&dist_name_short=TWRP&codename=gtelwifiue
edwardnizz said:
Question is I'm thinking about putting Magisk, But do I really need it? Is that like SU? Probably a very dumb question.
Click to expand...
Click to collapse
It's your choice whenever you want to use Magisk or not. If you want Busybox, ViPER4Android FX,etc... or other apps that requires root then you'll need to flash Magisk in order to use it.

Tickbaby said:
I am not responsible for any bricked devices. Install at your own risk!
This is experimental so please post any bugs you find.
SCREENSHOTS
What doesn't work:
I haven't found anything so far that seems to be broken. Doesn't mean it's bug-free though.
How to install:
1. Factory Reset
2. Format Data
3. Flash rom <-- Download
4. Flash GAPPS
5. Flash Magisk [optional]
6. Reboot to system
Enjoy.
Click to expand...
Click to collapse
download link for the rom is broken :/

Fruse said:
I've experience of flashing my tablet so I can flash my tablet without issues. Since it's too laggy to use, so I switched to LightningFastROM 17.1, for now.
If you had issues of flashing the ROM, I recommend to use this version of TWRP:
https://msm8916.com/?view=downloads&dist_name_short=TWRP&codename=gtelwifiue
It's your choice whenever you want to use Magisk or not. If you want Busybox, ViPER4Android FX,etc... or other apps that requires root then you'll need to flash Magisk in order to use it.
Click to expand...
Click to collapse
I just installed liightningfast. It turns out, I forgot to wipe data the first time i tried. Thanks a bunch. Now i have a few choices! Dude your the BOMB!!

One Questions Dev's and Fellow members Can this rom be flashed on SM T561 too ?

running on the sm-t560nu well. no lag issues, doesn't pass safety net though. not that big of deal, was just hoping magisk hide worked. Did you by chance add in the patch (or is this even applicable) found here: https://github.com/kdrag0n/safetynet-fix/tree/master/patches/9/sys

malfuncion said:
running on the sm-t560nu well. no lag issues, doesn't pass safety net though. not that big of deal, was just hoping magisk hide worked. Did you by chance add in the patch (or is this even applicable) found here: https://github.com/kdrag0n/safetynet-fix/tree/master/patches/9/sys
Click to expand...
Click to collapse
i used super su to root

I have found a bug. When using stock screen recorder with puting only record internal audio, if u have headphones connected it freaks out. Plz don't mind the video, I clicked on it for representation of the issue.