Related
Good Day Folks.
I'm a Noob in need of help and i'm hoping the more experienced among us might be able to assist. I have an issue with disappearing phone storage. Over the course of a week I realized that I was losing about 1MB a day. My phone would basically be dormant and I would still see my storage space dropping by this amount everyday.
Cache cleaning didn't work. Later I realized that Android creates a bunch of log files in Data/System/Dropbox that was responsible for the disappearing phone storage trick I've been seeing for a while now.
I know now that Google has incorporated into Android as of the 2.2 iteration, a DropBox Manager that's responsible for logging all of the events that take place during the course of a running Android session. Everything from what took place at boot to force close details.
I understand that this is used for debugging purposes but I'm no developer . So my question is.... Can this DropBox Manager be disabled....somehow.
I really don't need all these files (and its A LOT OF THEM) being created as they serve no practical purpose for me. Not sure if anyone else might have noticed this but I'm hoping to receive some help. Even if it means pointing me in the right direction so I can work on it myself.
I really don't have a clue on how to start. Any help will be appreciated....Seriously...
Currently using G1 with CM6 Magpie running on EZTERRY's 2.6.34.7 kernel.
Its perfect except for this annoying problem.......
NB: I've posted this before in the general discussions area but should have posted it here first....Sorry about that....
Hi there all
I have an important question. As I have never been a huge fan of Gapps, and currently using 2 devices with Android, I have 2 questions regarding safety on those devices.
1st one: AOSP Rom, 4.4, no Gapps or anything Google's installed, just the open source F-droid, and sometimes downloading an app via Google Play download sites. I regularly update my Firefox web browser, but since I dont have any Google apps such as Play Services, does that mean that I wont get any important safety updates for my device?
Does this mean that, using any "not the latest" Android device without Google Play Services is a dangerous device? Do I really need it?
2nd device, Android 4.2 with Gapps installed (no custom rom), but with all Gapps deleted or disabled, including Play Store and Services. Also using the open source F-droid. Same question: is this device vulnerable?
I suppose they are vulnerable even with the latest Firefox installed, as Android bugs are not repaired at all. Is there anything I could do to make my devices safer? My 4.2 device is not able to be rooted as it is an unknown brand. My 4.4 device is the Sony Xperia T phone.
I only use my devices to check email, read the newspapers, do some Facebooking and Whats-apping and have some medical apps installed.
Many thanks for reading.
@ruben112 , not sure if this would be helpful , and you may have already seen ; but is an informative thread.
http://forum.xda-developers.com/showthread.php?t=2960077
"err on the side of kindness"
mrrocketdog said:
@ruben112 , not sure if this would be helpful , and you may have already seen ; but is an informative thread.
http://forum.xda-developers.com/showthread.php?t=2960077
"err on the side of kindness"
Click to expand...
Click to collapse
Thanks a lot for the thread, I had looked for some tutorials but hadnt found them yet! So newer Androids dont per se bring better security? And with some of those apps the security bugs get fixed too?
as i understand things AOSP is less intrusive than what some custom roms are based on. as far as android versions go , "stagefright" is a vulnerability that just got patched in lollipop (i think). but i believe there are sometimes tradeoffs , i.e. the newest may give more security while at the same time taking more control over an OS.
i am really hoping someone more knowledgeable will chyme in :what:. as far as apps go ; just look at what permissions are asked for by the app , some are quite unreasonable to say the least.
i personally never install gapps.
sorry i dont really know more.
"err on the side of kindness"
mrrocketdog said:
as i understand things AOSP is less intrusive than what some custom roms are based on. as far as android versions go , "stagefright" is a vulnerability that just got patched in lollipop (i think). but i believe there are sometimes tradeoffs , i.e. the newest may give more security while at the same time taking more control over an OS.
i am really hoping someone more knowledgeable will chyme in :what:. as far as apps go ; just look at what permissions are asked for by the app , some are quite unreasonable to say the least.
i personally never install gapps.
sorry i dont really know more.
"err on the side of kindness"
Click to expand...
Click to collapse
Thanks. That is exactly what Im wondering: I almost use no apps so they might have security issues but there should not be that many, OS updates on the contrary could in theory make your phone much safer, but do they do it and could the issues not be patched otherwise?
if you have way more knowledge than me about coding and such then you might be.able to patch it yourself.
i personally do not know any other way. but there probably is.
"err on the side of kindness"
It seems that contributing to LOS building ROM is not anymore tolerated, this post is deleted.
Maybe @Scavenger87 wants to take a look here ;-)
I guess it's better to have an own dedicated thread.
Thanks for setting up a distinct thread. Things were getting confusing!
john_matrix said:
Maybe @Scavenger87 wants to take a look here ;-)
I guess it's better to have an own dedicated thread.
Click to expand...
Click to collapse
Hey John great idea with opening a new Thread because i also think its really confusing already
john_matrix said:
@Scavenger87: Steel01 advised to let 15.1 (I think he is right because it's too old and because lot of changes have been done between 15.1-16.0)
Also have found this during LOS 16.0 debugging and when application is crashing:
Starting from Android 9, LMK can be implemented in userspace and needs new optimization settings:
Low Memory Killer Daemon | Android Open Source Project
source.android.com
Will see if this new userspace LMKD can be tuned.
@Trevor_g: can't say... I don't have an Nvidia controller to test.
Click to expand...
Click to collapse
Ok yeah i think he's right for multiple reasons
- 15.1 had still unsolved issues aside of broken omx like the crashing nv games app and not working screen mirroring which is working so far on 16.0
- 16.0 is Android 9.0 based which is the same as the actual Software for the Shield TV. That means there is maybe a chance they can use some Codes or even Apps like the Shield Accessories to makes things like the First Controller working again over WIFI.
I even found a lot Nvidia OEM Apps here on APK Mirror : https://www.apkmirror.com/apk/nvidia/
I think i start testing around with those apks as soon i installed the lasted 16.0 build
@Trevor_g
For your question i have to check that again on 16.0 with the old Controller but i think its still only working over a OTG Adapter.
Like i mentioned above maybe the Shield TV Accessories App is working.
mirhl said:
https://gist.github.com/webgeek1234/8ef1bd105d2add3aa9c29028c2befbb0
https://github.com/vartom/drivers-kernel-nvidia-49/tree/smaug49/drivers/hid
https://github.com/devmapal/nvidia-shield-controller-driver
Click to expand...
Click to collapse
Someone even mentioned this Linux Driver for the Controller
But to be honest dont suspect too much on lets say all this bonus functions because first the LOS Team have to work on the base build to make it stable and running right
Ok i installed the latest build (4/1/21) yesterday on my LTE Tablet over sideload because i had no extra SD Card to format it to FAT32 and with the new TWRP 3.5-9.0.
I installed also the Pico Gapps and then TWRP said when i was about to Restart that there's now OS installed.
But thats seems to be a bug with TWRP itself because after the restart there was the LineageOS screen waiting for me and after a freeze for about a minute or two i was able to complete my installation.
After this i now can say its the most stable LOS 9.0 Rom so far !
It has very less apps crashing so far i only had to start them twice sometimes and also the hw acceleration working now most of its time at Chrome and on the Youtube App.
I can really see there has going again a lot of work into this Rom and its really a pleasure now to see how it get more stable everytime.
Big thanks to @Steel01, @npjohnson, the whole LineageOS Team and of course to @john_matrix
Btw @john_matrix did you change anything on the partitions you mentioned earlier on this build ?
@Trevor_g
I did a short test yesterday with the controller and as suspected it doesnt recognize by the tablet. I soon test out those Android 9.0 based Accessories App from the Shield TV
Thank you for the rom
Can I just flash this over Lineage 14.1 or do I need a factory wipe?
Did anybody test gamepass streaming yet?
danielandross said:
Thank you for the rom
Can I just flash this over Lineage 14.1 or do I need a factory wipe?
Did anybody test gamepass streaming yet?
Click to expand...
Click to collapse
Yes you have to wipe the device first in TWRP to install this rom.
Maybe a little general guide for everyone here who want to try this build in this early state and help tracking bugs
For an clean Installation its important to wipe the device first with TWRP like shown on the first Screenshot.
After this go to Advanced and choose everything choosen on the second Screenshot.
Now you shutdown the Tablet and insert the SD Card or plug in the cable for sideloading.
After turning on the Tablet and choose Recovery Mode again, first install the Rom of course then choose Wipe cache/dalvik.
Now you have to install Gapps if you want to use it. Its recommend to use only the Pico Package.
Wipe cache/dalvik again and restart the device.
If you use Sideload it might says in the Shutdown Menu :
No OS installed !
Which is a bug in my opinion of the new TWRP 3.5-9.0 Package but please use this Version of TWRP in any case that the basement of the installation is everywhere the same !
This is IMHO the way to install a Rom in a clean way and helps tracking down bugs better when everyone used the same methodes.
@john_matrix
I installed the Rom today on a K1 16GB with the methode i described above and did it with my regular SDCard i use in all my Tablets. In comparsion to installing over sideload it didnt get the No OS installed! message at TWRP and i didnt had that 1 minute freeze at begin of the install-wizzard after the LOS Logo.
Also the Rom seems to be same stable as the one on the 32GB model.
But i have to test it a bit more side by side to make valid statements
Also Nvidia Games working nice as you can see on the Screenshots
Hi guys, so, long story short i got scammed on a dutch advertising portal and ended up with one of them shield tablets which were recalled a few years ago. Yep, those with the defective battery that may burst in flame one day
Anyways, i figured that since it hasnt happened until now, i might just be lucky and give it a shot.
Its great to see that there is still some active development of this device! flashed this rom and i gotta say im positively surprised. Its running nice and smooth and even though it crashed on me a few times after the first boot, but a few reboots later and its running like a charm! i didnt bother with gapps, root or anything yet though. really great job devs!
Scavenger87 said:
I installed the Rom today on a K1 16GB with the methode i described above and did it with my regular SDCard i use in all my Tablets. In comparsion to installing over sideload it didnt get the No OS installed! message at TWRP and i didnt had that 1 minute freeze at begin of the install-wizzard after the LOS Logo.
Also the Rom seems to be same stable as the one on the 32GB model.
Click to expand...
Click to collapse
My tablet was completely wiped with no OS so I just pushed the ROM, pico gapps, and magisk over USB onto internal storage with MTP/TWRP. Flashed it all from there and it worked fine. No issues or errors. I don't think it's at all necessary to sideload to use an external SD.
Jackill said:
Hi guys, so, long story short i got scammed on a dutch advertising portal and ended up with one of them shield tablets which were recalled a few years ago. Yep, those with the defective battery that may burst in flame one day
Anyways, i figured that since it hasnt happened until now, i might just be lucky and give it a shot.
Its great to see that there is still some active development of this device! flashed this rom and i gotta say im positively surprised. Its running nice and smooth and even though it crashed on me a few times after the first boot, but a few reboots later and its running like a charm! i didnt bother with gapps, root or anything yet though. really great job devs!
Click to expand...
Click to collapse
In this Thread beginning from here i share my informations so far about the two type of batteries and changing them out if you interested:
Finding Replacement Battery in 2017?
Anybody know where to find a battery that will fit in the Shield Tablet? I know there are several threads online (here on xda, on GeForce forums, and other places) that discuss replacing the shield tablet battery and a few different part numbers...
forum.xda-developers.com
airtower said:
My tablet was completely wiped with no OS so I just pushed the ROM, pico gapps, and magisk over USB onto internal storage with MTP/TWRP. Flashed it all from there and it worked fine. No issues or errors. I don't think it's at all necessary to sideload to use an external SD.
Click to expand...
Click to collapse
I did these two type installation because @john_matrix mentioned to use a SD Card which is formated with FAT32 instead of exFAT. I didnt had one lying around so i used sideload this time.
Thank you everyone and Scavenger87 for your feedback! ;-)
About stability, I guess the culprit is the fact I have played with the new userspace LMK but for me it's not stable enough to be used as daily.
For example, Youtube often continue to play videos greeny and blocky and this is annoying
I will try to fine tune the best settings for LMK.
About battery, I have changed mine too with this one:
https://fr.aliexpress.com/item/32807531204.html
It works good but require to use the board of the original battery.
Seems to be going well so far for me, battery life seems good and for the general use I have had time to do it's worked well.
One crash that caused a reboot, after testing the hdmi output the tablet rebooted when I unplugged the hdmi cable from the tablet.
john_matrix said:
Thank you everyone and Scavenger87 for your feedback! ;-)
About stability, I guess the culprit is the fact I have played with the new userspace LMK but for me it's not stable enough to be used as daily.
For example, Youtube often continue to play videos greeny and blocky and this is annoying
I will try to fine tune the best settings for LMK.
About battery, I have changed mine too with this one:
https://fr.aliexpress.com/item/32807531204.html
It works good but require to use the board of the original battery.
Click to expand...
Click to collapse
Ok that means there is still some kind of memory leak problem with our tablets or is the memory managment on android 9 and higher not really suited for our low ram devices ?
I also read something about drawbacks with the in-kernel LMK as you can see here :
Drawbacks of in-kernel LMK driver
Android deprecates the LMK driver due to a number of issues, including:
Low-RAM devices had to be tuned aggressively, and even then would perform poorly on workloads with large file-backed active pagecache. The poor performance resulted in thrashing and no kills.
The LMK kernel driver relied on free-memory limits, with no scaling based on the memory pressure.
Because of the rigidity of the design, partners often customized the driver so that it would work on their devices.
The LMK driver hooked into the slab shrinker API, which wasn't designed for heavy operations such as searching for targets and killing them, which slowed down the vmscan process.
Is the zRam function now activated by standart on Android 9 and higher to compress amount memory is needed ?
I try to stresstest it today with a website that have a lot pictures sadly i cant use instagram anymore because you need a account now
Shield Tablet can't be considered as a "low ram device" as Google defined them with up to 512MB (Android Go?)
Android Performance Optimization | Android Open Source Project
source.android.com
I also have devices with 2GB that are currently performing Lineage 17.1 very well (Sony Z3C and Nexus 4)
I don't know if zRAM is activated by default in Android but you still have the choice to activate it or no (in the kernel or in the fstab.
Additionnally, I don't know what is the policy to activate zRAM (my Mi9 have 6GB RAM and have zRAM activated by Xiaomi so...)
Another thing about zRAM is there are lot and lot of options you can activate such as compression, lz4, clear caching, etc... depending of your needs and I am not skilled enough to say exactly what will be the consequences of these options (but it cost nothing to try).
You also have to keep in mind that zRAM will consume more CPU times (as KSM).
Similarly, you can fine tune the CPU governor and IO scheduling (often I see CFQ by default but on the other way I have saw that Noop and Deadline gives best results).
Feel free to share your experience and if you have other ideas on what you would like to integrate in this ROM (as the best possible).
You are right to stress test the OS, you can also debug the memory and the weight attributed on the processes.
Ok but 2GB is really not much these day also this article from android source is really old i think i read there something about kitkat or so
But your right i also was suprised to see that my xperia z3 compact i have lying around is able to run lineageos 17.1 and even is supported by the LOS Team
Which leads me to the question is the memory managment on the Qualcomm SOC so much better ? Ok the Ram there is on the SOC itself instead of external like on our Tegra based devices.
I think i install tonight Triodexes 15.1 with zram to compare the effect it has.
I also noticed the hw acceleration crashes the most on the firefox browser like i told in the 15.1 Thread you can start one video and it runs if you leave everything untouched but your not able to start a second one even with autoplay.
Btw about the LMK i know its maybe a dumb question but did you try the original settings from the Oem Rom ?
Edit : The original values in minfree are: 18432,23040,27648,32256,36864,46080
And zRam is already activated on the LOS 16.0 Build with 511MB same like the oem rom
Scavenger87 said:
I did a short test yesterday with the controller and as suspected it doesnt recognize by the tablet. I soon test out those Android 9.0 based Accessories App from the Shield TV
Click to expand...
Click to collapse
Thanks SO much for looking into this for me! You mentioned later that the controller wasn't recognized by the tablet, however I'm also curious if the Accessories app from the ShieldTV might help. Thanks again, in advance!
Fwiw, there's a bunch of framework patches needed for the wifi direct controller to work. I've yet to get them all straight. Haven't had that working since cm-12.1. See the incomplete set for 16.0 here:
https://review.lineageos.org/q/topic:shield-blake-p
That's on top of:
https://review.lineageos.org/q/topic:nvidia-shieldtech-p
And there's no nvidia pairing app that works with a touch interface. It's a mess atm. I did get blake to pair to foster on 15.1, but only while the pairing wizard was open. As soon as I hit back to close it, the autonomous group goes down and the connection is lost. And now, it's close to impossible since nvidia didn't release the nvwifi prebuilt jar to link against. And the one from O doesn't work on P.
Hi @Steel01
Thank you for keeping us updated on your work with the controller and also for your work for this device in general
I already tought its not easy to bring wifi support back for the old controller but i think also there is no high priority since the second gen is working fine over bluetooth and they already cheap to buy used.
Other than this the rom is suprisingly good running for this early stage and most of the stuff is working
Is there something that needs special attention for testing at the moment to help you developing ?
Like i mentioned in a other Thread i have every generation of the Shield Tablet and Controller. Only on my LTE Modell the SIM Card Reader is unfixable broken
But i still hunting for a fully working device.
Before I flash this Rom: Why do I habe to wipe internal storage?
danielandross said:
Before I flash this Rom: Why do I habe to wipe internal storage?
Click to expand...
Click to collapse
Well i dont know if its really needed to wipe the internal storage but i think by the reason we testing here a new Rom in a really early stage we should give it the cleanest basement as possible to exclude problems that might caused by left over data that interference with the Rom
Hi everyone,
I've been away from the ROM scene for a few years and was pleasantly surprised to find out that even a MediaTek phone these days can be flashed with a ROM different from its original. With a lot of bumps and information from this thread and others, I was able to test the Lineage, Havoc, and Treble ROMs, flashing through adb commands on fastbootd on unsigned xiaomi drivers. The one with the best compatibility so far is an older ROM, the Treble 10 GSI bundled with go gapps. Treble 11, the latest, doesn't have a working "recent apps" button (multitasker/app switcher). I'm not using this phone as a camera phone, but I did install an older Gcam (Gcam 2.3, I think) by googling the phone's mediatek processor, Helio G25.
On stock android, I do feel like the phone is much improved from the MIUI OS's bloat. I feel that Xiaomi as of late is putting too much adware, a far cry from when I bought my first phone from them (A Redmi 1S).
I would like to thank everyone here for the recovery files, twrp, etc.
I'd love to know how you accomplished this, as an otherwise decent phone is, I feel, crippled by MIUI's ridiculous bloat.
Bludwurst said:
I'd love to know how you accomplished this, as an otherwise decent phone is, I feel, crippled by MIUI's ridiculous bloat.
Click to expand...
Click to collapse
Hi @Bludwurst ... I'll see if I can write something semi-coherent about it. Please give me a few days. But the general method was pretty similar to flashing other treble-based ROMs, the important thing is that the phone boots into FASTBOOTD ("elevated" fastboot) and the rom you're flashing is the correct architecture with some Google Go apps (if you want it to be easier to set up). They update every few weeks, so depending on the progress, it may even be feasible to try out the other more popular ROMs. Lineage was 2nd best in my experience, and Android 11 to boot with its own recovery, but it doesn't come bundled with Google Go apps, you'll have to flash the Google apps yourself.
Major caveat about the treble GSI i'm using though -- the Gcam with HDR on has a chance of shutting down (exiting). It's less of an issue when the setting is off. I do have a separate primary camera phone so that wasn't an issue to me.
I've had the phone for about 3 weeks now. I think the biggest difference between this ROM and the MIUI OS is that the MIUI OS is very aggressive about killing my VPN (Ad blocker) and other background apps. With this Treble GSI (Android 10, not 11), I won't claim that my mediatek phone suddenly became a snapdragon, but there's no unexpected app-killing, which is very important for Blokada to stay alive.
**Has any other app crapped out (crashed/exited) since I changed ROMs?**
I don't run games on this phone, so I can't say if there's a difference between MIUI and Treble, but most of the productivity stuff is running okay (time tracker, markdown editor, pdf viewer, etc.) there IS some slowdown when running mobile youtube on my browser (yes, i don't run the youtube app... there may be an improvement if you're using a dedicated app.
I bought this phone as my work tracker phone. Before, with the MIUI stuff, it would stutter after a few apps were loaded. This is improved, but under heavy loads (10+ tabs, video playing), the phone is likely to complain.
**How's the battery life**
I bought this phone for the battery life, so I'd say I'm pretty satisfied on that front. The difference between the MIUI and the Treble GSI.... there's some small improvement with the Treble GSI. But it is (after a few weeks of use) not as much of a "battery boost" as I initially thought. Maybe this is because MIUI keeps killing background apps that now stay on? Can't tell.
**Any other issues**
I had to fix brightness and I think the headphone bug. I still have the commands somewhere, I'll dig it up.
Next, I am not sure if this phone will get security issues moving forward, or if i'll have to keep reflashing to a later GSI. I haven't checked if there's a way to sideload kernel security patches.
**Worth it to switch?**
Yeah, absolutely. Not having to reload apps is a huge deal, and not losing working data while typing helps. Tradeoff is camera hdr and security.
This all sounds very interesting.
I've admittedly not kept up with the Android scene (to call it something), so I'm a bit lost regarding Treble ROMs and such; I'll try to catch up a bit.
Take your time, I can wait.
(It goes without saying that, should I not like the results, I can always bail and reinstall an official Xiaomi ROM for this device, no?)
Yes, MIUI is extremely aggressive killing apps, and getting it to stop is rather confusing (it's not enough to turn off battery optimizations... You need to dig into Settings).
I managed to stop it from killing Netguard, at least...
I also don't play games or otherwise make extremely heavy use of the phone; I also don't care much for camera apps, so such disadvantages aren't dealbreakers for me.
Thank you for your reply
can you tell what gsi did you install? tkss
Luelu said:
can you tell what gsi did you install? tkss
Click to expand...
Click to collapse
You should use arm32_binder64-ab variants for this device, and you should flash an image that is THE SAME ANDROID VERSION you currently have or 1 version above. Example if you have Android 11, Flash Android 11R version, if you have Android 10 only flash ANDROID 10Q versions, etc.
To find out what GSI image should you use, this app makes it easier, it recommends you which one to download. https://play.google.com/store/apps/details?id=tk.hack5.treblecheck&hl=&gl=US --
#Another mirror:
https://www.apkmirror.com/apk/hacki...lease/treble-info-5-0-6-android-apk-download/
2 Years later, i made a guide on how to flash it , maybe it can be useful to you.
Xiaomi Redmi 9A 9i 9AT 10A
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
s_code said:
Hi everyone,
I've been away from the ROM scene for a few years and was pleasantly surprised to find out that even a MediaTek phone these days can be flashed with a ROM different from its original. With a lot of bumps and information from this thread and others, I was able to test the Lineage, Havoc, and Treble ROMs, flashing through adb commands on fastbootd on unsigned xiaomi drivers. The one with the best compatibility so far is an older ROM, the Treble 10 GSI bundled with go gapps. Treble 11, the latest, doesn't have a working "recent apps" button (multitasker/app switcher). I'm not using this phone as a camera phone, but I did install an older Gcam (Gcam 2.3, I think) by googling the phone's mediatek processor, Helio G25.
On stock android, I do feel like the phone is much improved from the MIUI OS's bloat. I feel that Xiaomi as of late is putting too much adware, a far cry from when I bought my first phone from them (A Redmi 1S).
I would like to thank everyone here for the recovery files, twrp, etc.
Click to expand...
Click to collapse
by the way can you share the links you used to download those roms? I wanna try em out too
Hello, fellow hackers! I am the proud owner of a Samsung Galaxy S10 and a Samsung Galaxy Tab A 10.1 (2019 Edition). However, I've been having problems with updating my tablet, and after uninstalling a whole bunch of apps, this has made it where I can install the system updates. Apparently, one or more apps have some sort of bug that affects the OS and causes it to not update.
In my quest to figure this out on my own, I was wondering if there was an OS update log or list somewhere stored on my devices. Since they are not rooted, I would have to pull such a file using ADB, but I can do it. This would be useful for my S10 too, since I am considering installing some of the same apps to it.
I know about logcat, but the output is far too lengthy, and I'm not sure how to get it to focus only on OS updates. What I'm wondering if there is a log or other file which stores information about each time I update my tablet, very much similar to logs stored by Linux or Windows.
Any help on this would be great; I have scoured the web for this, but to no avail. To clear any confusion, no, I am not concerned about when apps are installed and updated, only Android OS updates. This can include minor updates that only update the security of my devices.
I may should point out that during the time that I wasn't able to update, some of my apps hung, even the system UI hung and was unresponsive.
All I want to do is find out about a record of system OS updates. It may help me figure out what went wrong.
Interesting, seems like I posted on this before: https://forum.xda-developers.com/t/t510-consistent-lag-and-update-issues.3990799/#post-83194013
Seriously? No one has an answer to my question? Surely there are other logs stored by Android other than what is pulled by adb logcat!
I did discover on my own that there are recovery logs that you can see, but they can't be pulled using adb pull because it says that permission is denied. However, I can view them if I boot to recovery. Would this help me find out what app(s) may have prevented the updates from happening? I'm not sure exactly what I'm looking for.
What, really? Absolutely nothing? Never mind, I'm pretty sure I've solved this problem already.