Related
for some reason i have been getting a prompt about every few hours that says
"BatteryStatus Today-Plugin"
"this is shareware and you can use it "as is" and as long as you want!
thank you for using BatteryStatus Advanced!"
i have Open Touch v3.0 Biggy WM 6.1 that was just flashed last week w/no problems (only this little one).
any one have a solution for this?
thanks
DK
I have the same exact issue, it just started this morning. It used to do it before, too, and it took another flashing to get rid of it. It looks like the cook used an incorrect version of BatteryStatus.
From the BatteryStatus Author's site:
I have a nag-window sometimes. How can i remove that?
A registration system is currently in testing state. If you want a nag-free version (for a while) you need to register at xda-developers and use one of the versions provided there.
:'(
so where does this leave us
orochidp said:
I have the same exact issue, it just started this morning. It used to do it before, too, and it took another flashing to get rid of it. It looks like the cook used an incorrect version of BatteryStatus.
From the BatteryStatus Author's site:
I have a nag-window sometimes. How can i remove that?
A registration system is currently in testing state. If you want a nag-free version (for a while) you need to register at xda-developers and use one of the versions provided there.
:'(
Click to expand...
Click to collapse
alright, its not just me. so what now? i really don't want to flash again. i am already registered here, so how do i get/install an "xda version"?
let me know if you have any ideas.
I just installed the BatteryStatusExt.1.05.UPXed.build_0290.CAB from this thread:
http://forum.xda-developers.com/showthread.php?t=270751
So far it seems like my issue has been fixed. I hope it works for you, too.
I had the pop up since this morning too. I did a soft reset, and since then there hasn't been a prompt yet
thanks for the searching
orochidp said:
I just installed the BatteryStatusExt.1.05.UPXed.build_0290.CAB from this thread:
http://forum.xda-developers.com/showthread.php?t=270751
So far it seems like my issue has been fixed. I hope it works for you, too.
Click to expand...
Click to collapse
I followed the thread and it says on the first paragraph that the BatteryStatusExt.1.05.UPXed.build_0290.CAB could damage your device.
this has me skeeved out. i might just give it a day or two, and if it continues, i'll just flash to Open Touch v4.0 Biggy. i just got this phone a month ago and i don't want to kill it yet. thanks for the suggestion
DK
hmmmmm
Jerommeke said:
I had the pop up since this morning too. I did a soft reset, and since then there hasn't been a prompt yet
Click to expand...
Click to collapse
i wonder if this is a coincidence? i bet that this pop up is scheduled at the end of every month or something like that.
digitalknoll said:
I followed the thread and it says on the first paragraph that the BatteryStatusExt.1.05.UPXed.build_0290.CAB could damage your device.
this has me skeeved out. i might just give it a day or two, and if it continues, i'll just flash to Open Touch v4.0 Biggy. i just got this phone a month ago and i don't want to kill it yet. thanks for the suggestion
DK
Click to expand...
Click to collapse
EVERY version of BatteryStatus can hurt your device if you use it incorrectly. For example, overclocking to above 260 is not smart and will shorten the life of your device. It could just freeze up and stop altogether. It's nothing specific to that version, just that overclocking in general is pretty risky stuff if you push it.
i did not know that...
orochidp said:
EVERY version of BatteryStatus can hurt your device if you use it incorrectly. For example, overclocking to above 260 is not smart and will shorten the life of your device. It could just freeze up and stop altogether. It's nothing specific to that version, just that overclocking in general is pretty risky stuff if you push it.
Click to expand...
Click to collapse
cool, well thanks for that info. i have seen a lot of people clocked at 247 and up, and i tried that, but i swear the back of my phone was getting hot. i switched it over to 234, and it runs just fine for me. i don't think i would be able to tell the difference anyway. great, then i will open that cab up and see what happens. thanks for the info orochidp.
DK
Jerommeke said:
I had the pop up since this morning too. I did a soft reset, and since then there hasn't been a prompt yet
Click to expand...
Click to collapse
This pop-up is incredibly annoying.
i hate the latest version and this still pops up. how do i fix please?
I soft reset and it still no work.
Thanks
Hey guys, I want to first apologize for this post being a little out of place. Being a new user I dont have access to development forums so Im posting this here because this is the phone I have. I downloaded both of the last 2 super one click versions to try and root my phone. after following the process all the way to before rooting, int he top right you are supposed to switch the tab from psneuter to rageagainstthecage. When I click that box however there is no rageagainstthe cage option for either verstion, it is gingerbreak or psneuter. I tried clicking psneuter once and it stated and got to a point where it more or less froze, after 20 min i just alt f5 it and my phone still works. I tech savy guy when it comes to windows but know virtually nothing about linux accept a few terms. I dont want to do something to brick the phone and not entirely sure if I have messed up something so that there is no rageagainstthecage option. Also I was wondering, if you root the device are there updates that still download? For instance if i root by my os is still the stock and they finally come out with gingerbread what happens? Sorry again for misplacement of this thread, I have just been trying to find the answers online for 3 days and there hasnt been any information dealing with this type of problem that I have found. Thanks again
Edit: So I had checked this thread 2 days ago for my answer, and after posting and looking again it looks like a post from yesterday may have some answers, ill have to check when I get home to see if it works from me. Sorry again, I am very litteral so when Im told to do a step and it simply isnt there, it causes me concern, especially when skipping it doesnt work.
Hi There,
I would really appreciate some help with rooting my HTC Sensation XL which runs Android version 4.0.3.
I am not too sure if I have posted this in the right section so my apologies if I haven't.
OK so I have been trying for about 6 weeks now to ROOT my HTC. The only reason that I wish to do so is so that I can delete the apps that can not be deleted from the phone IE Facebook,Twitter & similar apps. I don't use them any more and because of this I would like them off the phone.
I have spent many of hours trawling the net to find guides and step by steps on how to do this. I wouldn't say I know/understand a lot of what it asks me to do but at the same time I have a little knowledge so that I am not completely in the dark.
But after reading several step by steps,reading about all the files I need,I end up getting lost and very confused half way through so I decided that perhaps an app that does it for me would be best.
I have seen SuperOneClick recommended several times so I thought I couldn't go wrong with it.
I downloaded the file from CNET.It is version 2.3.3. I extracted it,plugged my phone in via usb (made sure it was in debugging mode) and then clicked "RUN AS ADMINISTRATOR" on the actual SOC icon. It brought up the box and I clicked "ROOT". It scrolled and it looked like it was going well until step 7 where it hangs and just states "WAITING FOR DEVICE".I gave it some time but after an hour of it not changing from this,I guessed that something was wrong. Then when I try and click on the window,it becomes unresponsive and I have to force close it.
I have searched for solutions to this,one forum even suggested that I download an older version of SOC which I did. But it pretty much did the same thing,just a different message.
As I said,all I want to do is delete these apps so if anyone can shed some light on the problem I am having and how I can actually root the phone in the most simplest terms (talk to me as if I was your Nan!) then I would be very grateful.
Thank you for your time
Crystal
If any one could help or have any ideas I would be very grateful. Really desperate to do this.
Thanks
Try this: http://forum.xda-developers.com/showthread.php?t=1625841
Or this: http://forum.xda-developers.com/showthread.php?t=2093082
Sent from my GT-N7105 using xda premium
I have a couple 5th Gen Kindle Fires. I have installed the Google Play Store on one, but still need some additional functionality--I would like to add widgets, for instance, which I understand I can get by rooting the device, but I also need some additional control over sound options--the option to route alarms through the headphone jack, for instance, and perhaps a couple other options.
I've also got a few troubleshooting issues to go through (Google hangout messages no longer play sounds, for instance, or provide "pop ups" when the screen is sleeping).
So I guess I'm not sure what is best...should I go ahead and root the device and go through the exercise of adding widgets that way, and hope my other issues can be solved one by one as development continues, or should I just wait for a custom ROM?
I am not in a huge rush, but don't have much experience with the android world, but I've done a fair bit of jailbreaking on Apple devices so could probably root the device now. I just don't know what to expect on android devices, like is there a big bang for your buck in installing a custom ROM vs. rooting the device, and if I root it now will it complicate my life later when custom ROMs are available?
jwbohrer said:
I have a couple 5th Gen Kindle Fires. I have installed the Google Play Store on one, but still need some additional functionality--I would like to add widgets, for instance, which I understand I can get by rooting the device, but I also need some additional control over sound options--the option to route alarms through the headphone jack, for instance, and perhaps a couple other options.
I've also got a few troubleshooting issues to go through (Google hangout messages no longer play sounds, for instance, or provide "pop ups" when the screen is sleeping).
So I guess I'm not sure what is best...should I go ahead and root the device and go through the exercise of adding widgets that way, and hope my other issues can be solved one by one as development continues, or should I just wait for a custom ROM?
I am not in a huge rush, but don't have much experience with the android world, but I've done a fair bit of jailbreaking on Apple devices so could probably root the device now. I just don't know what to expect on android devices, like is there a big bang for your buck in installing a custom ROM vs. rooting the device, and if I root it now will it complicate my life later when custom ROMs are available?
Click to expand...
Click to collapse
ggow wrote that the stock bootloader/kernel will not support kexec, which means that what can be done with custom roms is very limited
There is no reason not to root your device now.
Rooting will not negatively effect your ability to install custom mods if we are able to do that in the future.
jwbohrer said:
I have a couple 5th Gen Kindle Fires. I have installed the Google Play Store on one, but still need some additional functionality--I would like to add widgets, for instance, which I understand I can get by rooting the device, but I also need some additional control over sound options--the option to route alarms through the headphone jack, for instance, and perhaps a couple other options.
I've also got a few troubleshooting issues to go through (Google hangout messages no longer play sounds, for instance, or provide "pop ups" when the screen is sleeping).
So I guess I'm not sure what is best...should I go ahead and root the device and go through the exercise of adding widgets that way, and hope my other issues can be solved one by one as development continues, or should I just wait for a custom ROM?
I am not in a huge rush, but don't have much experience with the android world, but I've done a fair bit of jailbreaking on Apple devices so could probably root the device now. I just don't know what to expect on android devices, like is there a big bang for your buck in installing a custom ROM vs. rooting the device, and if I root it now will it complicate my life later when custom ROMs are available?
Click to expand...
Click to collapse
If you don't root before getting the 5.1.1 update, there's no root method found for that update as of yet so you could be waiting a long time if you wait.
Sent from my Slim ROM'd Amazon Fire
Joshmccullough said:
If you don't root before getting the 5.1.1 update, there's no root method found for that update as of yet so you could be waiting a long time if you wait.
Sent from my Slim ROM'd Amazon Fire
Click to expand...
Click to collapse
There is now
http://forum.xda-developers.com/amazon-fire/orig-development/root-t3272362
Pond-life said:
There is now
http://forum.xda-developers.com/amazon-fire/orig-development/root-t3272362
Click to expand...
Click to collapse
I received my Fire with stock 5.1.1 and tried to root according to that link
Confirmed, working:
- Enable ADB-Debugging in Developer Settings, then:
Code:
adb reboot-bootloader
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot continue
adb wait-for-device && adb shell
Click to expand...
Click to collapse
After the first fastboot command, the device just hangs on "=> FASTBOOT mode..."
And the terminal on my Linux machine is hanging on "<waiting for device>"
Any help to resolve this? The device isn't bricked. I can reboot to stock just fine.
That sounds like a driver problem rather than a Fire issue and my knowledge of linux is round about nil I'm afraid.
Pond-life said:
That sounds like a driver problem rather than a Fire issue and my knowledge of linux is round about nil I'm afraid.
Click to expand...
Click to collapse
Hmm, not sure. I was able to successfully use adb to install the google play store and run the commands to (temporarily) hide the ads. Plus, "adb devices" shows me the Fire.
I can try from a different machine.
Roti2000 said:
Hmm, not sure. I was able to successfully use adb to install the google play store and run the commands to (temporarily) hide the ads. Plus, "adb devices" shows me the Fire.
I can try from a different machine.
Click to expand...
Click to collapse
What about "fastboot devices" when the tablet is hung on "=> FASTBOOT mode..."
Pond-life said:
That sounds like a driver problem rather than a Fire issue and my knowledge of linux is round about nil I'm afraid.
Click to expand...
Click to collapse
Pond-life said:
What about "fastboot devices" when the tablet is hung on "=> FASTBOOT mode..."
Click to expand...
Click to collapse
I did some investigating . It DOES appear to be a drivers issue. Fastboot has different drivers than ADB. I'll have to get that cleared up and give it another try
EDIT: I got my drivers squared away on Ubuntu by editing the udev file. Rooted!
Pond-life said:
There is now
http://forum.xda-developers.com/amazon-fire/orig-development/root-t3272362
Click to expand...
Click to collapse
Well.....learn something new every day. Thanks for the correction
EDIT: It does look like there's a fair amount of hard/permanent bricking of Fires posted in that forum, even as recently as this past week; the methods being discussed seem a little 'touch and go' at the moment, but it also looks like the forum's hopping with people working on making the method(s) more stable, so hopefully perma-root and even a permanently flashable recovery aren't too far off.
Joshmccullough said:
Well.....learn something new every day. Thanks for the correction
EDIT: It does look like there's a fair amount of hard/permanent bricking of Fires posted in that forum, even as recently as this past week; the methods being discussed seem a little 'touch and go' at the moment, but it also looks like the forum's hopping with people working on making the method(s) more stable, so hopefully perma-root and even a permanently flashable recovery aren't too far off.
Click to expand...
Click to collapse
None from rooting. Perma root is there, done and dusted stable as anything.
Just two from trying one method to get twrp access back and one from another attempt, was expected to be risky. TWRP recovery on the device still seems unlikely.
Flashfire is letting people change to some custom roms
I purchased my first Samsung tablet today after a long, loving relationship with Asus Transformers (wanting something smaller). To my surprise OEM Unlocking was not available in Dev Mode. Having not owned a Samsung device since my S5 I searched high and low on Google and nothing worked. Tons of suggestions for S8's/9's but nothing for my new little SM-T380. I tried variations of everything I found and when none of them worked, started back at the top of the list. I FINALLY GOT LUCKY.
TL;DR - Today's date is 12/1/2018, time was 9:32pm (central).
I toggled my date/time to manual.
I manually set my date to 11/1/17. (YES, ONE YEAR AND ONE MONTH EARLIER)
Before wifi had time to reconnect after the date change I manually checked for updates and it errored out.
Without pressing anything else, I held the power button and restarted.
After restart I checked to see if OEM Unlocking was there and it wasn't.
I then adjusted the date back farther to a random interval. (Ended up being 03/1/17)
Manually check for updates again.
Selected dev options on the left again and OEM Unlocking finally appeared!!!!!1
Notes:
SM-T380
7.1.1
ARB3 build
B1G7r33! said:
I purchased my first Samsung tablet today after a long, loving relationship with Asus Transformers (wanting something smaller). To my surprise OEM Unlocking was not available in Dev Mode. Having not owned a Samsung device since my S5 I searched high and low on Google and nothing worked. Tons of suggestions for S8's/9's but nothing for my new little SM-T380. I tried variations of everything I found and when none of them worked, started back at the top of the list. I FINALLY GOT LUCKY.
TL;DR - Today's date is 12/1/2018, time was 9:32pm (central).
I toggled my date/time to manual.
I manually set my date to 11/1/17. (YES, ONE YEAR AND ONE MONTH EARLIER)
Before wifi had time to reconnect after the date change I manually checked for updates and it errored out.
Without pressing anything else, I held the power button and restarted.
After restart I checked to see if OEM Unlocking was there and it wasn't.
I then adjusted the date back farther to a random interval. (Ended up being 03/1/17)
Manually check for updates again.
Selected dev options on the left again and OEM Unlocking finally appeared!!!!!1
Notes:
SM-T380
7.1.1
ARB3 build
Click to expand...
Click to collapse
What's the REAL difference between what you did today and what we did days ago.? Is the same thing we came up with 3 days ago.. Just your version of the same thing..
Three days ago?
This didn't work for me. Neither have any of the other similar date-spoofing methods people have suggested or linked to on this forum. I'd be happy to be wrong, but there doesn't seem to be a legitimate way to trick this tablet into letting you bypass the 7 day wait for OEM Unlock to appear.
@B1G7r33!, if your method actually works, can you replicate the process and prove it? Can you wipe your data, flash back to stock firmware, go to Settings>About tablet>Status, and take a screenshot that shows the "Up time" of the tablet, go through your suggested date-spoofing method, then if OEM Unlock appears, take another screenshot of your tablet's up time, and one screenshot of your developer options menu.
I'm not calling you a liar, it's just that this and similar methods haven't worked for me and haven't been confirmed as working by anyone else yet. If it actually works, then great, but it's not working for me, so I'd like to pinpoint the problem and solve it.
B1G7r33! said:
Three days ago?
Click to expand...
Click to collapse
actually starting on 14th November 2018, 07:17 PM and ending about 4 days ago.. with ptballers solution.
post 118 was the beginnings of it on the thread: https://forum.xda-developers.com/ga...10-02-2018-t3747564/post78159074#post78159074
but even THAT came from earlier works that weren't detailed enough and reconstructed.
the builds seem to be way different here in the solution, i had luck with what we came up with but have only done that once so far.
I am using build NMF26X.T380DXU1ARB3 myself, what about you?
we need to figure out what ptballer is using and everyone else too as we confirm stuff so we know what to do with tablets based upon builds.
seems there is no single solution yet, and that's what we really need too keep confusion cut down to a minimum.
---------- Post added at 06:16 PM ---------- Previous post was at 06:12 PM ----------
Evul1 said:
This didn't work for me. Neither have any of the other similar date-spoofing methods people have suggested or linked to on this forum. I'd be happy to be wrong, but there doesn't seem to be a legitimate way to trick this tablet into letting you bypass the 7 day wait for OEM Unlock to appear.
@B1G7r33!, if your method actually works, can you replicate the process and prove it? Can you wipe your data, flash back to stock firmware, go to Settings>About tablet>Status, and take a screenshot that shows the "Up time" of the tablet, go through your suggested date-spoofing method, then if OEM Unlock appears, take another screenshot of your tablet's up time, and one screenshot of your developer options menu.
I'm not calling you a liar, it's just that this and similar methods haven't worked for me and haven't been confirmed as working by anyone else yet. If it actually works, then great, but it's not working for me, so I'd like to pinpoint the problem and solve it.
Click to expand...
Click to collapse
did you clear out your storage cache after changing the date and then turn on developer options?
what build are you working with btw.
Trying this on round two after root yielded no results. I also tried the clear cache method from your post I found which has a MUCH more consistent process to follow and still got nothing.
Perhaps starting from the bottom would be beneficial here.
Flash stock with odin --> find method that works --> add to root process.
It adds two more steps but that seems like a small price for consistency.
This is f***ing infuriating.
7r33
capriorn1971ad said:
did you clear out your storage cache after changing the date and then turn on developer options?
what build are you working with btw.
Click to expand...
Click to collapse
Yes, I tried that as well and it didn't work. Are you suggesting that this has worked for you? If so, can you reset your tablet right now and try it again to confirm?
I'm using the same build you are using, NMF26X.T380DXU1ARB3
Evul1 said:
Yes, I tried that as well and it didn't work. Are you suggesting that this has worked for you? If so, can you reset your tablet right now and try it again to confirm?
I'm using the same build you are using, NMF26X.T380DXU1ARB3
Click to expand...
Click to collapse
thats quite a bit of work to do, but yes it worked for me.
I was planning on writing a guide on rooting this and what to do if and when it fails in laymans terms and utilizing this, but if it isn't working for everyone.. if it isn't the cache then what is causing it to show for some and not others?
to do the guide i was going to start from a failed installation so i could write part 2 first and finish with part 1 (the actual initial rooting), which would require me to reset the tablet but if this isn't working right.. then i need to hold off on that idea.
maybe i should just do it and spend my day tearing around on that, sounds fun and all but i have to go to Burbank tomorrow to sign up at Central Casting (they are actually looking for someone like me right now, i am going with inside information) and it will be an all day endeavor, tuesday would be much better for me in truth, that allows me to use that tablet while i wait, and i will have hours to wait, but of course with my luck they will call me wednesday and null and void that.
B1G7r33! said:
Trying this on round two after root yielded no results. I also tried the clear cache method from your post I found which has a MUCH more consistent process to follow and still got nothing.
Perhaps starting from the bottom would be beneficial here.
Flash stock with odin --> find method that works --> add to root process.
It adds two more steps but that seems like a small price for consistency.
This is f***ing infuriating.
7r33
Click to expand...
Click to collapse
when you flash stock, restart the device and set the date back 2 months, then do a factory reset AFTER that and it will work.
after rooting it DO NOT reboot it until the OEM unlock shows up again, you can't rely on a method to bypass the second 7 days that requires rebooting, it null and voids the rooting by doing such.
this tablet is awefully touchy, i lost root 2 1/2 weeks after rooting and being able to reboot having OEM unlock showing and all.. but i didn't set up magiskhide..
don't know how the tablet detected it and figured it out..
yes it is infuriating, least you have company to work on it with..
capriorn1971ad said:
thats quite a bit of work to do, but yes it worked for me.
I was planning on writing a guide on rooting this and what to do if and when it fails in laymans terms and utilizing this, but if it isn't working for everyone.. if it isn't the cache then what is causing it to show for some and not others?
to do the guide i was going to start from a failed installation so i could write part 2 first and finish with part 1 (the actual initial rooting), which would require me to reset the tablet but if this isn't working right.. then i need to hold off on that idea.
maybe i should just do it and spend my day tearing around on that, sounds fun and all but i have to go to Burbank tomorrow to sign up at Central Casting (they are actually looking for someone like me right now, i am going with inside information) and it will be an all day endeavor, tuesday would be much better for me in truth, that allows me to use that tablet while i wait, and i will have hours to wait, but of course with my luck they will call me wednesday and null and void that.
Click to expand...
Click to collapse
It shouldn't be that much work at all if your method to get OEM Unlock to display actually works, as your bootloader will then be unlocked and you can immediately re-root, re-flash TWRP, and restore a nandroid backup. Rooting this tablet [flashing TWRP and su and/or magisk and/or a nandroid image] is actually quite simple and can be done in 5 minutes once you have OEM Unlock displayed.
You certainly wouldn't need a whole day just to try this. But I understand. Samsung's security nonsense makes the initial root of this tablet rather fragile if you don't know all the potential roadblocks beforehand. And a comprehensive root guide that explains all of this would certainly help people looking to root this tablet, so I don't want to rush you.
capriorn1971ad said:
when you flash stock, restart the device and set the date back 2 months, then do a factory reset AFTER that and it will work.
after rooting it DO NOT reboot it until the OEM unlock shows up again, you can't rely on a method to bypass the second 7 days that requires rebooting, it null and voids the rooting by doing such.
this tablet is awefully touchy, i lost root 2 1/2 weeks after rooting and being able to reboot having OEM unlock showing and all.. but i didn't set up magiskhide..
don't know how the tablet detected it and figured it out..
yes it is infuriating, least you have company to work on it with..
Click to expand...
Click to collapse
I found out the reboot after root no-no the hard way, lol.
After playing with it all day today, I think you're on the right path with it being application based. If we could log which run before and after, the chances of finding it and being able to adb uninstall/disable would be significantly increased.
So what can be used to low-level log WITHOUT root?
B1G7r33! said:
I found out the reboot after root no-no the hard way, lol.
After playing with it all day today, I think you're on the right path with it being application based. If we could log which run before and after, the chances of finding it and being able to adb uninstall/disable would be significantly increased.
So what can be used to low-level log WITHOUT root?
Click to expand...
Click to collapse
don't think we can really.
trial and error..
thought i was on the right path earlier, but if it didn't work for you then it isn't the solution, cause the solution will work for everyone.
has to be some small thing were overlooking i would assume.
I worked for Metricom through Verso Technologies back in the late 90's, the first coast to coast wireless provider, had dealings with the big wigs and all, but they always opted for less security and more accessibility in most everything pertaining to networking, always afraid to give up backdoors.
i need to go back to what you said too and see what slight differences there are, did you have any luck this time around? was it repeatable?
sucks to know i am going to have to root to cause a failure to try to bypass and root again only to cause a second failure to verify, and to get it right it is going to take that really, the bypass has to be repeatable, i think setting the date back before the systems restore is key to it, but i could be wrong.
if you would lose root and be able to get it pass the first 7 days OEM unlock then your good, because even if you can't get the second, and something goes wrong to where you need it, your gonna have to wipe anyways, which means you just wipe, set date back and then do the factory reset, not being able to reboot afterwards until the OEM unlock appears and not being able to advance it through the last 7 days means little so long as the root is good and right, funny thing really, took me a while to realize that, there is no real need to rush the second 7 days, only the first 7, but it would be nice to be able to reboot it again afterwards, the same day, and not have to worry about it anymore, but like i said earlier, i got detected somehow and lost root still., wish i knew how.
that's alot of my problem though, i do things and try to document them afterwards rather than as, and i am not 20 years old anymore with a mind like a razor, it's just a serrated steak knife now at almost 50, wish i wasn't like that, because i lose bits and pieces as i go.
so if my tablet auto updates to Oreo 8.1 ... then i'm SOL huh?