yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] DragonFire1024:
[MENTION=5749760]ggow[/MENTION] I feel him. I never lost hope. If anything it motivated me further, hence all the tricks and hacks I've been able to perform and continue to do. Besides a few select handful of us who, for whatever reason can't get enough of these things, everyone else gave up. So much so people started to beg those who continued on. Though our corner is small, I can't thank you guys enough for the work you've put into and continue to put into these things. If it weren't for the dedication of you guys, I would've put my fire 7 in a drawer 4+ years ago.
[Fire Original Android Development] DB126:
Me thinks radio adaptation will be easier on karnak (2018 HD 8) as FireOS v6 is based on Android 7.12. Seems a natural for Lineage 14.1.
[Fire Original Android Development] eric93se:
ggow everthing has been great with my Fire Ford. :)

One suggestion for the original post. Next to Unlocked Boot loader add " (NEW 2019) " maybe in red, since people are making the mistake it seems.

Actually the only problem I've had is Magisk Manager crashing.
[Fire Original Android Development] ggow:
Although I have karnak booting with the stock 6300 kernel binary on lineage-14, unfortunately getting wifi and bluetooth is not going to be straight forward. We don't have the kernel source for 6300 and the 6301 kernel source won't boot for some reason. Need time to investigate properly.
[Fire Original Android Development] DB126:
Drat. I believe you alluded to this awhile back; for some reason I though 63xx kernel source had been sourced. Too many grey hairs (err...all of them); the one surviving brain cell is having a hard time keeping up.
[Fire Original Android Development] brunnen153:
My MAC address changed after updating to the latest build from the december one on my Austin. Is this intended?
[Fire Original Android Development] srnoth:
Updated to this new "unlocked" version after running one of last year's versions for a long time. Zero issues and if anything feels more snappy. Great work and thanks for keeping breathing new life to this 3 year old (and only $50 at the time) tablet.

By the way for those that like to tinker... Unlocked bootloader means we can now mess with the boot.img in Android Kitchen. First thing I did was edit the fstab file to remap the entire /data to my SD card (formatted as ext4), disabled the zram and made the /cache partition be swap space instead. So far so good. Pretty sure a half decent sd card is faster than the internal memory on these things anyway. Not to mention my internal storage now reports as 64gb :D
[Fire Original Android Development] DB126:
Regardless of card specs external storage will be slower than internal due to usb2 interface constraints (yes, also applies to SD card slot). At best you may score 50% of the IOPS relative to internal storage based on previous testing with a 5th gen Ford. I also suggest leaving a small ZRAM allocation which will speed boot times. Regardless of swap configuration be sure to dial back swappiness (suggest 10-25) and properly prioritize multiple swap spaces (defaults will likely be opposite what you actually want).
[Fire Original Android Development] srnoth:
Yep I'm getting about half the read speeds (~50MB/s vs ~100) but write speeds seem to be capped at ~20 MB/s on both. I've settled on my SD card mounted to /data and the internal data partition mounted to /data/data. I figure that way when launching apps it can read the actual app file (apk/art cahche) from the SD card while simultaneously loading the app data from internal, maximizing use of both. Two simultaneous streams of slow IOPS better than just one?

Re: swap/zram I've only got one swap partition (the previous cache partition) so no need to prioritize. I figure no zram = less work on the CPU compressing/decompressing pages as they are swapped in and out. Don't really care about boot times in this thing - so long as it's less than a minute that's fine. Still messing with optimal swappiness setting. The /cache didn't appear to be used for anything and I haven't noticed any ill effects with it gone.

Here is my current fstab.mt8127:

# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#/dev/block/platform/mtk-msdc.0/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc wait,check,resize,encryptable=footer
/dev/block/platform/mtk-msdc.1/mmcblk1p1 /data ext4 noatime,nosuid,nodev,noauto_da_alloc wait,check,resize,encryptable=footer
/dev/block/platform/mtk-msdc.0/by-name/userdata /data/data ext4 noatime,nosuid,nodev,noauto_da_alloc wait,check,resize,encryptable=footer
#/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc wait,check
/devices/platform/mtk-msdc.0/mmc_host auto vfat defaults voldmanaged=sdcard0:emmc@fat,noemulatedsd
#/devices/platform/mtk-msdc.1/mmc_host auto vfat defaults voldmanaged=sdcard1:auto,noemulatedsd
/devices/platform/mt_usb auto vfat defaults voldmanaged=usbotg:auto
#/dev/block/zram0	nome	swap	defaults	zramsize=67108864
/dev/block/platform/mtk-msdc.0/by-name/MISC /misc emmc defaults defaults
/dev/block/platform/mtk-msdc.0/by-name/cache none swap defaults 0 0

This is honestly the best this tablet has ever run.
[Fire Original Android Development] DB126:
Unlikely the low-end controller can efficiently handle "simultaneous streams"; more likely some form of round robin. 20 MB/s is about right for external writes but is ⅓-½ what internal should read. Either read-ahead is way off (unlikely) or the mounted SD is artificially capping writes. You will want to do some further testing if looking to fully optimize performance.

A small ZRAM will not burden the CPU if swappiness is throttled back. It will be much faster than eMMC/SD I/O and won't prematurely trash the latter or trigger excessive garbage collection on the former. There is a method to the madness; it wasn't hank the hacker pulling hunks out of his hinney. Might want to reference the previously linked thread for additional guidance.
[Fire Original Android Development] DragonFire1024:
Looks like the fire 7 is getting a much needed hardware boost https://www-cnet-com.cdn.ampproject...-7-tablet-with-faster-processor-more-storage/

Upgrades include ability to use voice assist/Alexa. Storage from 8gb to 16.
[Fire Original Android Development] nirogu325:
It's 2019 and it'll release with the same 1GB RAM...yuck.
[Fire Original Android Development] DragonFire1024:
I don't suspect their tablets will go too much above that. There are 10 inch I think was there only exceptions thus far and so far they haven't given it a refresh and I'm not surprised. At least it will be able to gained some of the features the other devices have that will be a plus for sure.
[Fire Original Android Development] llamasking:
I've gotten SafetyNet to pass! Device is certified.

I used MagiskHide Props Config with Improved Hiding on and using the fingerprint of a Google Nexus 7 2012 WiFi.
[Fire Original Android Development] DB126:
That's pretty impressive!
[Fire Original Android Development] DragonFire1024:
There was a point, and I for the life of me cannot recall how I did it, but I had no modules installed or anything to manipulate the market, but at one point I was certified and passed safety net. I don't know how it happened. I suspect it has to do with play protect, I had scanning turned on too. With selinux permissive in the kernel, and flashing BusyBox, the only thing stopping auto updates, is because I have yet to be able to repeat the process. And knowing me of course I had to go and try. And it really is a pain to set Google assistant up again unless of course you're installing it from flashing a ROM build or something to that effect.
[Fire Original Android Development] llamasking:
I'm actually pretty shocked it worked at all, considering this device has probably never seen even a pass on FireOS.
[Fire Original Android Development] Android Adam:
Is there a way to get the amazon appstore on it?
[Fire Original Android Development] DragonFire1024:
I believe the 'underground' app store works, but as for the regular? I'm pretty sure that's no.
[Fire Original Android Development] DB126:
You will need to use the underground variant and not all functionality will work. Also a bit of a resource hog unless tamed via Greenify or similar.
[Fire Original Android Development] brunnen153:
Can MAC address randomization be disabled?
[Fire Original Android Development] DB126:
https://xdaforums.com/amazon-fire/orig-development/rom-fire-nexus-rom-lmy49f-t3300714/post79556598
[Fire Original Android Development] brunnen153:
Ahh, so it actually is a bug, gotcha, thanks for the update!
[Fire Original Android Development] Android Adam:
Update: Nevermind I got it working.

Unmounting/removing the SD card fixed the problem

How do I do that. I know how to sideload apks so where is the apk. Also i sideloaded the normal appstore and it works except Minecraft which always fails. It's the exact same apk that works for my phone so is it just incompatibility
[Fire Original Android Development] DB126:
Not necessarily a "bug"; better described as a known characteristic. :)
[Fire Original Android Development] TECHNOFAB_11:
For me it works kinda good.

One problem are quite some random reboots, kinda annoying. I just want to use it as a Wall Smart Home Dashboard, but with these restarts the app seems to get weird too (Fully Kiosk Browser)
[Fire Original Android Development] black.kahder:
Just now bluetooth crashed on me again. I think this is the forth or fifth crash I have seen. This time no keyboard was attached, nor had been attached during this boot.

Here is the interesting part from logcat

05-21 15:14:42.418 W/art ( 532): Long monitor contention event with owner method=void com.android.server.am.BroadcastQueue.processNextBroadcast(boolean) from Broadcast
Queue.java:553 waiters=0 for 534ms
05-21 15:14:42.445 E/BTEventHandler( 7326): A4WP is not supported
05-21 15:14:42.474 W/ctxmgr ( 1139): [TimeFilter.Builder]startTimeMillis must be >= 0. Clamping to 0.
05-21 15:26:47.516 I/EventLogChimeraService( 5890): Aggregate from 1558475805720 (log), 1558475805720 (data)
05-21 15:30:21.009 D/BluetoothAdapterState( 7326): CURRENT_STATE=PENDING, MESSAGE = START_TIMEOUT, isTurningOn=true, isTurningOff=false
05-21 15:30:21.009 E/BluetoothAdapterState( 7326): Error enabling Bluetooth
05-21 15:30:21.009 D/BluetoothAdapterProperties( 7326): Setting state to 10

Googling for 'E/BTEventHandler "A4WP is not supported"' gives quite a few interesting results, including some existing commits.

---------- Post added at 20:38 ---------- Previous post was at 20:35 ----------

I have yet to witness a random reboot on my austin/Gen7 device. I have been using/testing it about three hours a day every day for the last two weeks.

---------- Post added at 20:56 ---------- Previous post was at 20:38 ----------

Yes, the 802.11 MAC address changing on each boot is a bug. Some embedded wifi devices like this one don't have a MAC written into the hardware itself and expect the driver to set a MAC in software. The MAC address it is supposed to use is probably in a partition somewhere (misc?). If the location of the MAC address can be found, this is easy to fix in Android's init.rc file or possibly the linux device tree if this kernel is new enough to support it (probably not).

I looked briefly in the Amazon Fire OS files for a clue as to where this might be set, but I didn't find it. I did not look too hard though.

As a temporary fix you can write a "ifconfig wlan0 hw ether" command in init.rc or the init.d files, but that's kind of advanced for most users.
[Fire Original Android Development] DragonFire1024:
Running netcfg in a shell will give you a list of available connections and or ability to connect via p2p, wlan0, and what not. It also displays Mac addresses. Not sure if that's static or not.
[Fire Original Android Development] black.kahder:
EDIT: Some info in this post is old. Some bugs have been fixed. Read on.

I have been using this device and the Lineage OS ROM for two weeks now. Here's everything I've learned and some of my notes. Most of this is probably already known by all. New users might find this useful.

Issues and Annoyances

Camera crashes when shooting video on custom ROMs. Known issue. No fix yet.

Bluetooth has been seen sometimes crashing. A reboot is required to get it working again. No fix yet.

No 5Ghz 802.11a without importing firmware files. Well-known issue. Easy to fix.

There are no charging/low-battery/notification indicator LEDs. Minor annoyance.

The 802.11 MAC address changes on each boot. Likely be fixed in the near future.

No light sensor means no display auto-brightness adjustment; manual adjustment required. Annoying.

sh/bash shell job control not working properly. This is fixed in later versions of Android.

I have experienced two instances where I selected a reboot in LineageOS 12 to the recovery partition. Instead of rebooting, the system simply powered down instead. Minor annoyance.

Device Specifications

https://developer.amazon.com/docs/fire-tablets/ft-device-and-feature-specifications.html

This SoC has no encryption acceleration (AES-NI) support.

If you format your sdcard with ext4, make sure it doesn't use unsupported features.

sudo mkfs.ext4 -O ^64bit,^metadata_csum /dev/sdc1

MediaTek serial/debug cable

http://www.stevenhoneyman.co.uk/2014/11/mtk-mediatek-debug-cable.html

https://xdaforums.com/amazon-fire/development/bootloader-unlock-ideas-t3289721

Power-on key combos

Hold Power button down for 3 seconds = Power device on normally. Boot /system.

Hold Power button down for 13 seconds. = Force power off.

Hold Power-on and Vol-Down during boot (Vol-down = corner, away from audio jack) = Boot into Recovery. (TWRP or Amazon system recovery)

5GHz 802.11 doesn't work fix

https://xdaforums.com/showpost.php?p=79202917&postcount=3

Magisk

There have been some reports of Magisk causing LineageOS builds to stop booting.

Works for me. Don't install Magisk from within Magisk Manager; only use TWRP.

For OpenGApps, use Platform "ARM" and Android "5.1".

Dark themes

Currently using blazze11's Euphoria Dark.

Some dark themes are theming the Play Store incorrectly, causing fonts to become invisible. Beware.
[Fire Original Android Development] buletini:
Where can I find the release of 21 May 2019?
[Fire Original Android Development] DB126:
There is no such release; latest is 22 April 2019.
[Fire Original Android Development] DragonFire1024:
Just discovered nova launcher allows custom icon packs. Got a total dark theme using nova, custom all around dark icon pack, and custom wallpaper for home and lock screen. Amazon did a good job of making a custom dark theme easy.
[Fire Original Android Development] Reynald0:
For OpenGApps may I suggest what I used before, this tiny app from F-Droid:

OpenGApps Downloader
[Fire Original Android Development] ggow:
On the change log, I keep a running log of what I'm working on when updating. I was going to make a release on the 21 May but then decided to look into the MAC address issue. I have changed it to be WIP instead.
[Fire Original Android Development] buletini:
Thank you! I'm glad you're working to fix the video recording problem:good:
[Fire Original Android Development] BXM500:
Will the Android 5.x be te latest for this device or will it be possible to see newer Androids running on Fire?
[Fire Original Android Development] ggow:
We can go higher, but we need to be able to build some userspace drivers from source so things can have a chance of working. Primarily bluetooth and wifi. I have started looking into this.
[Fire Original Android Development] Klaus R:
Great job, ggow, Thanx a lot
[Fire Original Android Development] jratt:
I have the 5th gen fire tab 7, ruining Nov 9 2018 build of lineageOS, I had to use flashfire to install new builds because of newer bootloader.

Will I Have to open this tablet to do the bootloader hack and install newer builds?
[Fire Original Android Development] Rortiz2:
No need to open it. Just downgrade to 5.0.1 to enter bootrom mode.
[Fire Original Android Development] jratt:
I thought going below 5.1.2 would brick my device and that is why I couldn't use TWRP?
[Fire Original Android Development] fmc000:
Please read this thread, especially the first post.
[Fire Original Android Development] ggow:
New Build is Up

Dated 24 May 2019

- ASB May 2019 patches (sec. string 2019-05-05)

- Privacy Browser updated to version 3.0.1

- System Webview M74

- Fixed video recording

- WiFi: Use hardware MAC address

- Bluetooth: Use hardware MAC address
[Fire Original Android Development] Rortiz2:
Any chances to update Fire Nexus ROM? I use it as daily driver.

Thanks!
[Fire Original Android Development] tyderian:
https://xdaforums.com/amazon-fire/orig-development/rom-fire-nexus-rom-lmy49f-t3300714
[Fire Original Android Development] black.kahder:
I just updated to the 24 May 2019 (lineage-12.1-20190524-UNOFFICIAL-austin.zip) image.

No /data wipe, wiped caches/dalviks.

Added OpenGApps pico and Magisk.

Nothing obviously broken. System seems to be working like previously.

Verified MAC address in ifconfig/ip link matches idme print mac_addr. MAC address issue is fixed.

I tried the built-in camera app and it's still crashing when switching to video mode. However I used OpenCamera and it took a video successfully.

I had to re-associate my bluetooth keyboard. No crashes yet.

I've observed that when the LCD screen is off, 802.11 still works, but it's very slow and not possible to maintain and audio stream. This is not a new issue.
[Fire Original Android Development] ggow:
I just tried the built in camera app again, for video capture seems to work fine here on austin and ford.

Could you post a log of when you switch to video mode?

For 802.11 it probably amazon's aggressive power profile in the kernel. When I next look at the kernel I'll do some digging.
[Fire Original Android Development] Rortiz2:
lol I know that but I mean if he can add MAC fix to the Fire Nexus ROM...
[Fire Original Android Development] ggow:
I'm working on Fire Nexus ROM, takes longer to update this one.
[Fire Original Android Development] t3chwizard:
Is this only applicable to the 2017 (austin) fire?
[Fire Original Android Development] black.kahder:
I only have an austin/Gen7, but to the best of my knowledge the comments will be relevant to both ford/Gen5 and austin/Gen7 since the hardware is so similar.

The day after I posted that a new ROM was released which fixes the MAC/BT address issues mentioned. The in-ROM/Lineage camera app is still crashing for me but it looks like other camera apps may be fine.
[Fire Original Android Development] BenX10mini:
Hi, I unlocked the bootloader of my 5th gen (Ford) Fire 7 using the method found in the other thread.

I then flashed linage-20190422 + gapps nano after wiping both caches + data, coming from stock 5.3.1. Again, everything running perfectly fine for me, except video recording (known bug).

I flashed the latest build yesterday (just wiped cache + dalvik) and everything seems perfect, including video fix !

Thanks a lot !!
[Fire Original Android Development] Reynald0:
Not only you, I experience same issue with AudioFX, without changing anything. Regards.
[Fire Original Android Development] black.kahder:
I don't recall if anyone noted it previously but the change which fixed the Wifi MAC addresses also fixed the Bluetooth MAC, which was also not being previously applied.

This change will cause all of your existing bluetooth device associations to be broken. You will probably need to delete them all and re-associate. No big deal, but worth mentioning.
[Fire Original Android Development] Xates:
[MENTION=5749760]ggow[/MENTION] can you enable support for signature spoofing on this ROM, in order to successfully install and use microg? Flasing NanoDroid through the modified TWRP gives an error...
[Fire Original Android Development] ggow:
Signature spoofing is already included, go into Developer options->Apps and enable "Allow signature spoofing" option.
[Fire Original Android Development] newinnov:
Hi,

the nightlight feature's automatic setting is not working. Manual toggle works, but in automatic mode, it never gets activated.

Is it working fine with others? or its just me?

apart from it everything is working fine.
[Fire Original Android Development] black.kahder:
This device does not have an ambient light sensor.
[Fire Original Android Development] newinnov:
And you doesn't have context. Lineage LiveDisplay auto works based on the time of day. No sensors required!
[Fire Original Android Development] DB126:
Exactly; ambient sensor is irrelevant.
[Fire Original Android Development] t3chwizard:
[MENTION=5749760]ggow[/MENTION] this might be a stupid question, but someone modified VLC a while back to compensate for the non square pixels in the Fire 7 2015 (Ford)

https://xdaforums.com/amazon-fire/themes-apps/modified-vlc-media-player-5th-gen-fire7-t3674541

Do you have any idea if it would be possible to add such a modification to this ROM or even have a flashable zip or magisk module for it so that we can have the same impact except system wide?

---------- Post added at 04:45 PM ---------- Previous post was at 04:42 PM ----------

Additionally, lately my Fire 7 2015 (Ford) keeps telling me that the SD card was removed randomly. I'm not sure why, but I'm going to try troubleshooting it.
[Fire Original Android Development] Lava1000:
This is currently not working. It sets up then it crashes and gives a black screen then I have to force shutdown. Installed with TWRP with cleared data, system, cache, and dalvik cache. Also installed with OpenGApps (ARM,5.1,nano) and SuperSU.

Device: Amazon Fire Tablet 5th Generation
[Fire Original Android Development] BobPony:
Any progress on this? Just curious because Android 5.1.1 is starting to feel dated, would be nice if it would be possible to get the Android Pie or at least Android Nougat working on here. :D
[Fire Original Android Development] black.kahder:
I once had a failed SD card which would do this. The filesystem would go read-only and sometimes Android said that it had been ejected. I replaced it and the problems went away.

---------- Post added at 23:59 ---------- Previous post was at 23:55 ----------

Try flashing just the system ROM alone. Then go from there. The fact that you have TWRP installed and working means you are in good shape. You just need to get the system working. FYI most people use Magisk today instead of SuperSU, but that's up to you. Good luck.
[Fire Original Android Development] Lava1000:
I reinstalled it without gapps or supersu and I reach the setup for 1 second then a flashing black screen.
[Fire Original Android Development] mrmazak:
Boot to twrp, do complete wipe including system , and try again

Also verify you have a non corrupted download of rom
[Fire Original Android Development] Lava1000:
I did a complete wipe of the system before I installed the rom last time before this post and the rom is not corrupted.
[Fire Original Android Development] shelleyfrank:
Hi, I've got the austin rom installed on two tablets and I've got the same issue on both. Camera app works fine for back facing camera, but front facing camera causes an error and wouldn't work. Is the a known issue and is there a fix for it? Thanks a lot.
[Fire Original Android Development] ggow:
I'll look into it. Which camera app are you using? What's the error you are seeing?
[Fire Original Android Development] shelleyfrank:
Stock camera gives an error popup saying "Camera error : Cannot connect to the camera".

Camera fv5 simply crashes when switched over to front facing camera. Thanks
[Fire Original Android Development] l3ullseye:
Gesture Typing not working...

Gesture Typing not working, in the 24 May release, it is enabled in the settings but when doing a gesture on the keyboard nothing happens, does anyone else have this problem?

Thanks in advance...