yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] wjcroft:
Thanks again @ggow, very impressed. Working great.

[Skip to update below.] Here's one oddity for those with knowledge of different charger compatibility with this Fire. Previously when using FireOS, I could plug into either the Amazon charger (rated 1 amp at 5 volts), or my Motorola charger (rated 2 amp at 5 volts); both worked fine.

Now with Lineage 16 running, it does not like the 2 amp charger, it constantly beeps at me. (Same one-time beep sound as when attaching to a charger, but repeats every second or so.) But if I plug into the Amazon 1 amp charger, no beeps; it likes it. Weird. Neither of these clunky chargers would be considered a modern 'fast' charger. I attached an mp4 showing the Settings / Battery screen when it was beeping.

[Update on August 8, 2021: I figured out the source of the beeping. It was my long USB cord from the charger to the Fire. Replaced that with a one meter cord, and now all is fine, no beeps with either the 2 amp or 1 amp charger. My guess is that the Lineage charge monitor code is doing more current monitoring than FireOS did. And is trying to alert in the case of anomalies detected, such as unexpectedly low amperage. With the short cord and the 2 amp charger, I indeed am getting about 8 to 9 watts charge power (by my usb meter) with Lineage. No issues.]
[Fire Original Android Development] ggow:
Hello all, I have had a flood at our house. My workstation, some tablets were amongst the fallen items. House is not inhabitable still. Waiting for building repairs etc.
[Fire Original Android Development] detesto:
Hopefully it was just material things, glad you're ok
[Fire Original Android Development] wjcroft:
re: question on safety of flashing latest Magisk zip over @ggow 's Lineage 16

I followed the unlock, TWRP and install process that @ggow described on an earlier post:

Fire 7 (2019, mustang) unbrick, downgrade, unlock & root

Make sure to read this guide completely before starting. You will lose all data on the tablet, make a backup of important data before you start. What you need: - a Linux installation. Don't use a VM! Use a live USB, if you don't have Linux...

xdaforums.com

However that specific thread above was related to a FireOS downgrade (Android 7.1) and TWRP / Magisk install. Since the Magisk linked there was targeted at Nougat, I skipped the Magisk install and just flashed the Lineage 16 instead.

Is it safe to download and flash the latest Magisk zip and have TWRP flash that on top of my existing Lineage 16?

I do understand that this particular TWRP has a patch specific to Fire 7, and so any future upgrades of Magisk need to happen from TWRP and not the Magisk Manager.

Installation

The Magic Mask for Android

topjohnwu.github.io

How to Install Magisk on your Android Phone

Magisk is a powerful tool that can help you customize some aspects of your phone or even grant you root access. Here's how you can install it!

www.xda-developers.com

Is anyone on this thread successfully using Magisk with Fire 7 [mustang] Lineage 16?

Regards, William
[Fire Original Android Development] Michajin:
yes, just dont update from magisk.
[Fire Original Android Development] Nazo:
So I just decided to do a clean install because I want to do a MicroG only build this time around and I grabbed the most current version (dated March 12.) I think this is the same one I had installed before actually. After installing, the only difference from the previous install would, therefore, be that I did not flash OpenGapps. (I haven't attempted installing any MicroG stuff yet.) When I boot it up for the first time, after doing the initial setup stuff (LAN and etc) I get a warning that SELinux is not enforcing. I really don't remember it being off before and certainly I received no warnings about it being such, so I'm wondering if I just somehow missed it being off before or if something somehow went wrong during this specific installation. I know it was signed with testing keys, but shouldn't SELinux still be able to function?

Was it just always disabled and I just simply never saw it before? I get that it's signed with test keys, but does that mean SELinux can't be set to enforcing at all?

Have you checked the voltage output? In many cases with a power supply, if it's not at all under load (and below 50% can potentially qualify -- especially if it is not well made) its voltage will be higher versus when it is under load. The Fire 7 isn't really designed to make heavy usage of fast charging functions nor heavy current usage, so even under full load likely doesn't push a 2 amp power supply very hard. It occurs to me that it may be exceeding the amount of tolerance and it might be activating voltage protection, cutting off the charge. I haven't measured its actual current usages, but I suspect it's actually well below 1a really.

PS. Sorry to hear about the flood. I hope everything has worked out ok.
[Fire Original Android Development] wjcroft:
[see my edited original post with the beep video above, original date July 12. Issue was solved.]

Hi Nazo, thanks for the thoughtful reply. However my 5V 2A charger is a quality unit. OEM charger from Motorola / Lenovo. It charged the Fire 7 just fine when it was running the original Fire OS from Amazon. Only started beeping like this when the Fire 7 was converted to Lineage OS 16. So I very much doubt is an issue with voltage. May be that the newer OS does not limit current, whereas Fire OS did.

I also have a duplicate of this charger, same exact specs. It causes beeping similarly now. Whereas before it did not with FireOS.

As soon as I use the original Amazon 5V 1A charger, beeping stops.

William
[Fire Original Android Development] Nazo:
I didn't mean to imply (and tried very hard not to) that quality was the only determining factor in voltage output of a power supply, though things like brand/etc aren't actually a guarantee of quality either. (It's about how it's actually built. I've seen some very reputable brands produce some not very good power supplies including one that literally smelled like something burning when I used it by Samsung.) It's worth noting they generally don't even have the means to make their own power supplies and they actually rebrand something made by another company for them. Anyway, I was merely hypothesizing a possible explanation. You can check the actual voltage output to see what it's doing if you're curious -- or not as you will. It may not be that at all, just it is a common thing in power supplies as a whole. As for the ROMs, it may be the stock ROM manages voltage via QC or etc better, whereas this just gets the default generic USB output (which isn't even guaranteed to be accurate above 500mA by original standards) without any management.

EDIT: I got curious and tested it. It seems with the screen on and battery charging (but without pushing things hard in other ways) the current was only about 400mA. That definitely could be a fair bit lower than a power supply intended for fast charging would expect.
[Fire Original Android Development] hoppi05:
Hi all, I am new to the frustrations of this fire tablet HD7 we have bought but not to Andriod and rooting etc. all be it this seems to be the most complicated root process yet... I am wanting to know if my assumption is right and save myself a lot of time, my version details are below and i am assuming this is one of the newer generation ones that cannot be rooted and stock android flashed?

Tablet Codename: mustang

FireOS Version: 7.3.1.9

Android Version: 9.0

Security Patch: 2018-10-05

Chipset: MT8163

If anyone knows if it is possible to root and flash a new rom on this spec device i will start to read up and do so.

thanks in advance all.
[Fire Original Android Development] Nazo:
This isn't really the thread for that, but in a worst case the Mustang model is vulnerable to a hardware exploit, so it should be moddable one way or another.
[Fire Original Android Development] thebigphatmaster:
So, and I'm probably being a total nOOb, because its been like 3 years since I got / rooted my Mustang F7, but I just need to:

- titanium and nandroid backup (though there is no backup button in my version of TWRP for some reason);

- factory reset;

- flash los16 via TWRP (from a USB OTG card)

- then re flash magisk (via twrp) to keep root;

- then flash gapps via twrp?
[Fire Original Android Development] Nazo:
Two things: it's best when flashing an OS to wipe the system partition too, not just data and cache. Factory reset won't wipe the system partition. Basically that would be an upgrade in the form of a "dirty flash" but without any data, so kind of pointless anyway. In an ideal world it's probably best to never dirty flash except when it's a stable line of updates with very few changes though of course we all have to do it so we don't have to redo everything from time to time anyway, but regardless if you're not saving data then there's no point. Basically you can just do an advanced wipe and erase everything but internal storage and external storage if you have a memory card in.

Don't flash Magisk until after you boot it for the first time or it can get stuck on boot. Go ahead and flash gapps before you boot that first time though. You can keep things simpler if you want though. Up to Lineage 16.0 you could simply flash a su binary directly into the ROM: https://download.lineageos.org/extras (ARM, not ARM64.) This adds considerably less complexity, but doesn't have any of the extras of Magisk, so it depends on what your needs are, but this ROM doesn't pass SafetyNet or anything like that anyway, so many of the benefits of Magisk are wasted on it. There are some things Magisk can do that you can't do via root alone much like the Xposed Framework, so depending on your needs you have either option with this one, but if you don't do any of those things it might be good to keep the ROM just that much cleaner.

BTW, I have no idea why you wouldn't have a backup button at all. I think the latest version for Mustang is 3.3.1-0 (at least the highest I could find) if that helps narrow down among which ones are available. Make sure there is a storage available. You may have to do a reformat (advance "wipe") of the storage partition if all else fails perhaps (bear in mind this erases everything in the internal "sdcard" storage, so back it up via mtp or adb first if you want to do that.) Internal storage should be formatted as ext4. You should also be able to use an external sdcard for backup. Make sure one of them is actually mounted. Also, if it does that whole thing with the swipe bar to enable modifications obviously you want to swipe to allow them (I forget if this one even does that.)
[Fire Original Android Development] thebigphatmaster:
Thanks, that's really helpful.

I'm really interested in doing the minimum, I only use su rights for termux from time to time, and maybe tasker.

Yes, no backup on this version of TWRP.

The attached picture is what my TWRP looks like
[Fire Original Android Development] Nazo:
Yeah, there is a lot to be said for keeping things minimal. Magisk can do a lot of powerful things, but on a Fire 7 a lot of those things are less applicable to the way most of us probably use such a device. After all, this is no high end machine and most of us are using them for simple things like reading. I recommend Magisk for a lot of things, but most of what at least I personally do with my Fire 7 benefits more from keeping everything as minimal as possible for maximum battery life. In fact, next time I flash mine I'm going to a MicroG setup, but YMMV of course.

And yeah, that's an older TWRP build with fewer options from earlier on in this model's hacking timeline. Here's a newer build with more features and compatibility: https://xdaforums.com/t/recovery-mustang-twrp-touch-recovery-fire-7-2019-9th-gen.3949114/ You should be able to just flash the img from TWRP itself I think.
[Fire Original Android Development] thebigphatmaster:
Thanks for the link, my limited google-fu didn't turn that up

My F7 predominantly gets used these days as a way to distract the little one on the changing mat, though am interested in some heavier use. Surprisingly it runs Zoom (Amazon version?) more reliably than anything else I have, so Zoom with a split termux / emacs window for notes will be a prime use-case

So, to recap for my own benefit, actually now I need to:

- Ti Backup [done]

- Termux / emacs backup

- nandroid backup (in case I want to go back to stock)

- flash latest Mustang Twrp

- full wipe

- flash lineage16

- flash su and gapps before rebooting

- profit!

Forgive my noob-ness but when you say a micro-g build, do you mean microg rather than gapps, or the lineage micro-g fork? I find the idea of a microg build attractive of its lighter
[Fire Original Android Development] Nazo:
Yes those are the right steps except, just to be 100% clear, you don't have to format internal storage or the external SD of course in that full wipe.

As for MicroG, the LineageOS fork is just the normal LineageOS with MicroG stuff already installed, configured, and conveniences around it (like F-Droid given the privileges it needs to automatically update) just already setup for you. There is no true difference from manually doing those same things yourself, just a convenience. Unfortunately, as the Fire 7 lacks any official LineageOS builds, you won't find official MicroG convenience builds already available either. There may be some build with it available around here somewhere, but it's probably behind this one and with a device like this you definitely want the latest builds you can find. In the end though it's no different from just doing it yourself. The only key difference is just you don't flash the gapps package and then after initial setup you install and configure the MicroG apps yourself.
[Fire Original Android Development] thebigphatmaster:
Thanks @Nazo and @ggow for your help and development. Everything went smoothly.

I flashed 16 and it looks lovely. For now I've hopped over to 14 for working cameras and YT support.

I'm just re-flashing 14 because the play store won't get past "pending" and I've tried everything else (clearing data, cache, rebooting etc) hopefully that'll work out fine

Thanks again
[Fire Original Android Development] Nazo:
How strange. The Play store should work on this one. Can't do much about the rest though.
[Fire Original Android Development] thebigphatmaster:
Play store all fine after a fresh flash (14)
[Fire Original Android Development] slacka123:
I've tried to use this 16.0 image as my daily driver, but the lack of video playback is a deal breaker. Any hacks or work arounds? Media consumption is my primary use, so I had to go back to 14.1.

I had a question about using Nano GApps and other ideas to free memory on 14.1. Is it OK to post about 14.1 here? @ggow I'm sure you got real-world to focus on now. Until your life has recovered from the flood, could you re-open that thread, if you don't want it discussed here?
[Fire Original Android Development] detesto:
I decided to give this a try since I had to hand down my daily driver tablet to my daughter and this was just collecting dust in a drawer.

Since my main use is media consumption, mostly on YouTube, I tried that first and it wasn't working (black screen), so I loaded Newpipe and changed the video format to webm. After that, for some reason the main YouTube app started working, so I now can watch videos there instead. This will hold out until I catch a deal on another tablet.
[Fire Original Android Development] thisisnotatest:
Just wondering, in terms of privacy how does flashing this rom differ from using the latest version of fire Toolbox (v.23) since you can stop telementary and freeze apps
[Fire Original Android Development] Rortiz2:
Everything differs, keep in mind LineageOS is an "open source operating system".
[Fire Original Android Development] thebigphatmaster:
Just a quick bit of info on the video issue if it helps:

(1) the failure to play back is also present in BBC iplayer app;

(2) choosing webm in newpipe (latest 0.21.9) works for most, but not all videos there are some videos, mostly from less popular channels, which just error out with "Unrecoverable player error occured";

(3) youtube Vanced doesn't play at all; and

(4) as detesto has noted, for some reason the main YT app (with all its ads and annoyances) works just fine

**EDIT**(5) when wind down is set to greyscale, the screen goes predominantly green
[Fire Original Android Development] donk165:
Thank you for this new build, I have flashed it onto one of our work tablets, I will be updating the remaining 39 tablets in the next week. All appears to work great, its nice that the black screen issues from the old LOS14 build are gone now :)

Thanks again @ggow !
[Fire Original Android Development] thebigphatmaster:
@donk I'm curious about the black screen issues. Was that where there was a freeze which needed a soft reset?
[Fire Original Android Development] donk165:
TBH, this was a year ago or so, back on the LOS14.1 builds from another thread, yeah the screen used to go black and the device didnt respond, you had to hold the power button to power cycle it back into life. It didnt always happen, and there were some patches made by @Ziona to address the issue.

Are you experiencing this on the LOS16 builds?
[Fire Original Android Development] thebigphatmaster:
That's exactly what I was experiencing, didn't seem well documented. I literally went out and bought another tablet.

No it was just on 14.
[Fire Original Android Development] ggow:
I'm still not moved back into our house yet (since beginning of June) after the flood we had. Will continue with mustang development when possible.
[Fire Original Android Development] thebigphatmaster:
That's sad to hear man, hope everything is going as well as it can for you. Thanks so much for your work with this device. Even the current version of 16 with no cameras etc is fantastic compared with the OEM OS.
[Fire Original Android Development] Crigges:
I did a full wipe and a fresh install on my 9th Gen. Fire 7 (M8S26G) with the Version from the Mar 12, 2021.

However, Bluetooth keeps crashing even when turned off, see attached tombstones.

Anything I am doing wrong?

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***LineageOS Versi - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

pastebin.com

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***LineageOS Versi - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

pastebin.com
[Fire Original Android Development] douginoz:
For those wondering if they can install this on their latest tablet, I had the latest stock Fire OS rom, 7.3.2.1 installed on a Fire 7 version 9, M8S26G model.

I used the hw method to unlock the tablet, then installed twrp 3.3.1-0, lineage-16.0-20210312-UNOFFICIAL-mustang.zip, and gapps.

The latest (as of this writing) gapps, namely

open_gapps-arm-9.0-nano-20211028.zip

open_gapps-arm-9.0-mini-20211028.zip

open_gapps-arm-9.0-stock-20211028.zip

Don't work with this ROM, but the previous one from 20211021 (at least, the nano (speed good), stock (unusably slow), and mini ones) do.

I'll continue testing but so far, the setup app is working ok.
[Fire Original Android Development] douginoz:
A couple of things I noticed missing from the Settings app. When you enable developer mode, the developer menu item doesn't appear. Also, the Multiple Users menu item isn't there. Both can be searched for within Settings.

I also tried installing Plex but no videos play even though I used that other app to enable WebM as default. I suspect Plex ignores that anyway. I also tried configuring Plex to use an external video player and installed vlc. Nothing played.

This is on Lineage-16.0 12 Mar 2021 version.
[Fire Original Android Development] monsieur goonie:
hello, was wondering what it would take to port this Los version to ford version of Amazon fire 7.

regards
[Fire Original Android Development] dathappy:
Thanks for making LineageOS work on the Fire 7. It's so much faster now.

@ggow

Since you already fixed the cameras, I was wondering if there's any chance to get a release with this fix?

I'd love to use it with the motion detection feature of the fully kiosk browser.
[Fire Original Android Development] illfell58:
Hi, I also have the same tablet hardware version as you with fire os 7.3.2.1. I've been trying to perform the hardware unlock method with the contact point suggested in the main post but the script gives me an error every time. Did you use one of the other three pads?

The full terminal message I get is:

sudo ./bootrom-step.sh

[2021-11-25 00:15:12.317302] Waiting for bootrom

[2021-11-25 00:15:22.883141] Found port = /dev/ttyACM0

[2021-11-25 00:15:22.922628] Handshake

* * * If you have a short attached, remove it now * * *

* * * Press Enter to continue * * *

Traceback (most recent call last):

File "main.py", line 161, in <module>

main()

File "main.py", line 82, in main

load_payload(dev, "../brom-payload/build/payload.bin")

File "/mnt/SEAGATE2000/Android Files/Android Custom ROMs/Fire 7 2019 Unlock/amonet-mustang/modules/load_payload.py", line 99, in load_payload

dev.write32(0x10007008, 0x1971) # low-level watchdog kick

File "/mnt/SEAGATE2000/Android Files/Android Custom ROMs/Fire 7 2019 Unlock/amonet-mustang/modules/common.py", line 147, in write32

self.check(self.dev.read(2), b'\x00\x01') # arg check

File "/mnt/SEAGATE2000/Android Files/Android Custom ROMs/Fire 7 2019 Unlock/amonet-mustang/modules/common.py", line 84, in check

raise RuntimeError("ERROR: Serial protocol mismatch")

RuntimeError: ERROR: Serial protocol mismatch

It seems to work for a second after the "Press Enter to continue" message but then it spits out an error once I press the key.
[Fire Original Android Development] Rortiz2:
This isn't the correct place to discuss about the unlock. You should ask for help here.

RuntimeError: ERROR: Serial protocol mismatch

Means the tablet was in Preloader Mode (08ed:2000) when you tried the script so probably you have a patched (HW) revision which prevents you from triggering bootROM mode.
[Fire Original Android Development] illfell58:
Directly asking the person who seemed to have hands on experience sounded like the fastest option, my bad. Since I imagined that the hardware method wouldn't work I was surprised to see another person with seemingly the same device having gotten the exploit to work. I'll ask there too.

Do I have any other option? From your post it sounds like I'm out of luck. Any guesses as to how douginoz managed to get it to work if the devices have the same model number though? Or is the model number kept even after the hardware undergoes a revision?
[Fire Original Android Development] Rortiz2:
Im not sure if model number has something to do actually. But yeah, if it's a patched HW revision nothing can be done (at the moment). If it's not a patched HW unit, all I can say is keep trying and make sure you're shorting the correct pin + you're using something conductive.
[Fire Original Android Development] illfell58:
I see. Any way to definitively identify which hardware revision I have? The only information the PCB has on it says "A1926_MB_PCB_V7" on top of the battery connector.
[Fire Original Android Development] dathappy:
I had issue with notifications being delayed. Since I don't use messaging on the tablet I can't say if the messaging app would be affected too. For me it was Home Assistant and my Doorbell.

I tried disabling the battery saving feature for those two apps as well as some other system apps which sounded like it could help. I also checked via ADB to make sure the apps are whitelisted.

Unfortunately it did not work, so I disabled deep sleep altogether (adb shell dumpsys deviceidle disable).

Now notifications come in as expected and battery drain did not increase noticeably.