• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][unlocked][ford,austin] Lineage-14.1 [17 JAN 2021]

Search This thread

klamation

Senior Member
Apr 28, 2011
136
16
Nokia Lumia 820
Nokia Lumia 920
I feel like I must be missing something...

I've installed this rom half a dozen times and I'm still facing the same issue. sifting through this thread I haven't quite found an answer.


Problem:
  • WIFI will not connect. SSID says "Saved" underneath. Clicked on it brings a pop-up with options "Forget" "Cancel" or "Connect", when I tap "Connect" the word "Saved" disappears for a split second and comes back. No "Connecting" or "Obtaining IP" or any messages other than "Saved".

What I've done so far:
  • After getting TWRP up and running, I flashed the ROM, gapps, and magisk. Everything seemed to work fine except WIFI, so I started looking further into this thread and found the "Fixes" post. I flashed the newest wifi fix "nvram-test.zip" rebooted, and the "NVRAM" error in the list of wifi ssid's was gone, so I tried connecting to my ssid again, and it just said "Saved" and would not connect.
  • Wiped tablet in TWRP with the format option, and just to be safe, the advanced option with everything but my SD card and USB OTG checked. I installed the ROM again without anything extra except the wifi fix. Same issue.
  • Wiped again, same way, this time after flashing the ROM I let the tablet boot the system. Same issue as described, so rebooted to TWRP, flashed newest fix, wiped cache, and booted the system. Still same issue.
  • Did the same as above step, but used the older "NVram_fix_by_ziona.zip", and still seeing the same issue persist.
If I could get some help from someone that might know what I'm doing wrong or what I'm missing, that would be awesome! Thanks in advance!
Maybe it's an obvious troubleshooting step, but how many different SSIDs have you tried connecting to? Can you test another?

I actually didn't install any fixes when I installed this rom. It was just the ROM and the gapps. I've installed on a few devices and each one is able to connect to my router, which runs both 2.4Ghz and 5Ghz with the same SSID. Since the ford doesn't support 5Ghz, I know it's going to the 2.4Ghz network. I've also been able to get it connected to multiple routers' SSIDs without any issues.
 

Wizzzzard90

New member
Jul 26, 2021
2
1
Germany
I have been trying to understand this, on my austin the snapshot and video camera are working perfectly. It should just work out of the box so to speak, could you send a logcat?
First of all thank you very much for still putting work into this project
I've been trying for hours to fix it now, all the suggestions from this post didn't work to fix the camera issue...
I sent you a logcat via PM
 
  • Like
Reactions: Teknonono

Solarean

Member
Aug 28, 2020
21
9
Thanks for all the work you've (and the others) have done to get this working. I really loathed FireOS, so seeing this device I've had for years (7th Gen) boot up into LineageOS for the first time was amazing.

I've not noticed anything wrong yet that hasn't already been documented. But if I see something I'll mention it.

Thanks again!
 

dwl99

Senior Member
Sep 22, 2008
762
88
Yup, the last ROM I had on it was cm-12.1-20161122-UNOFFICIAL-ford - it's definitely a 5th gen
 
May 21, 2021
5
1
My 7th gen is not showing up in Windows explorer. On the device it is set for usb file transfer. Does anybody have any reccomendations?

Edit: Problem solved. Fix below for anyone else.

Device manager>(device)>Properties>Driver>Update Driver>Browse for Driver>Pick From List>Portable Devices>MTP USB Device
 
Last edited:
  • Like
Reactions: mrmazak

kelemvor33

Senior Member
Mar 6, 2012
54
2
Howdy,
I have a 5th gen Fire 7 tablet running Nexus something 5.1.1. Can I use this ROM to upgrade my tablet to v7.x or is this specific to something that goes in a car? I want to use my tablet as a normal tablet but just get it more current than it is now.
Thanks.
 

Teknonono

Member
Feb 4, 2021
7
0
Howdy,
I have a 5th gen Fire 7 tablet running Nexus something 5.1.1. Can I use this ROM to upgrade my tablet to v7.x or is this specific to something that goes in a car? I want to use my tablet as a normal tablet but just get it more current than it is now.
Thanks.
Hi, Lineage 14 is android 7 so will give you more compatibility with your apps. I have issues with the camera (not something I use much), and as some people have mentioned battery life drains quicker. Otherwise it’s been working fine for over a year for me. I think just ensure you do a full clean flash rather than a quick upgrade, as I think this managed to solve Netflix issues for me. Good luck!
 

rtyperic

New member
Oct 16, 2021
1
1
@ggow

FORD & AUSTIN FIXES DOWNLOAD PAGES LIST

FLASH THEM VIA TWRP

OMX VIDEO FIX VIDEO PLAYBACK ISSUES (zip file below)

NVRAM FIX ( for error Issue on wifi scan dialogue )
https://forum.xda-developers.com/showpost.php?p=81992843&postcount=548 . lastest

https://forum.xda-developers.com/showpost.php?p=80166385&postcount=25


Build Prop edit & flash tool For ford , Note; Austin users will have to change the buildprop file within the zip with their own first to use.
( Just edit buildprop within the zip an flash via recovery page #5
Only needed for stubborn build prop edits that don't stick on reboot. https://forum.xda-developers.com/showpost.php?p=80207471&postcount=50

Custom ggow Tribute Fire Reborn Boot Animation zip on page #10 https://forum.xda-developers.com/showpost.php?p=80383683&postcount=91

Nougat Battery Saver Plus ( Force Doze ) on Page #10 https://forum.xda-developers.com/showpost.php?p=80396199&postcount=100

CAMERA WORKAROUND APP Page #13
https://forum.xda-developers.com/showpost.php?p=80420517&postcount=121

AUTO ROTATION FIXES , ON PAGE # 15 app & PAGE # 25 fix zip
https://forum.xda-developers.com/showpost.php?p=80630501&postcount=241

LATEST FOR AUTO ROTATION ISSUES
https://forum.xda-developers.com/showpost.php?p=81731259&postcount=460

New Fix - FASTER BOOT START-UP SPEED PLUS SD CARD FIX - FORD & AUSTIN ON PAGE #22

Ford - https://forum.xda-developers.com/showpost.php?p=80584099&postcount=214

Austin - https://forum.xda-developers.com/showpost.php?p=80590927&postcount=219

HARDWARE ACCELERATION TWEAK PAGE #27
https://forum.xda-developers.com/showpost.php?p=80670111&postcount=267

TITANIUM BACKUP SUPPORT PAGE # 26
https://forum.xda-developers.com/showpost.php?p=80658833&postcount=260

SDCARD TO ROOT WRITE ACCESS FOR SOME APPS
https://forum.xda-developers.com/showpost.php?p=82208665&postcount=1 . Lastest

https://forum.xda-developers.com/showpost.php?p=82039601&postcount=564

LITE PIXEL LAUNCHER PAGE # 20
https://forum.xda-developers.com/showpost.php?p=80554187&postcount=198

OTG SUPPORT PAGE # 35
https://forum.xda-developers.com/showpost.php?p=80794079&postcount=343

NEW BOOT ANIMATION FIRE SKULL PAGE #36
https://forum.xda-developers.com/showpost.php?p=80812161&postcount=352

SMARTKERNEL AUDITOR
https://forum.xda-developers.com/showpost.php?p=80586217&postcount=217

MICRO-G INSTALLER
https://forum.xda-developers.com/showpost.php?p=80620189&postcount=234

LATEST FORD BOOT IMAGE WITH ADD-ONS
https://forum.xda-developers.com/showpost.php?p=81762183&postcount=484

LATEST AUSTIN BOOT IMAGE WITH ADD-ONS
https://forum.xda-developers.com/showpost.php?p=81771963&postcount=491

NEW WIFI SLEEP POLICY PATCH For battery savings.
https://forum.xda-developers.com/showpost.php?p=82077939&postcount=1

DEVELOPER OPTIONS ENABLER
https://forum.xda-developers.com/showpost.php?p=82187235&postcount=1

UPDATED 07/04/2020

if you liked all the help Please hit thanks
@Ziona - Do you know if any of these fixes are included in ggow's latest (17 Jan 2021) image from the first post?

Edit: Removed the accidental extra quote.
 
  • Like
Reactions: DigitalSnow

ljward

New member
Oct 26, 2021
1
0
Is there any chance you can post the "roomservice.xml" (or whatever XML you use to add the necessary addition repos to the lineage build?) that you used to build this ROM? I would like to rebuild it with the kernel patched to support OTG and Charging at the same time. Thanks!
 

savanzi

Member
Mar 1, 2016
9
3
Hi there! I have a 5th generation device.
I successfully downgraded bootloader and then initiated the sudo ./bootrom-step.sh process.
Unfortunately the usb cable disconnected right in the middle of the process... 😭 here's the output:

[2021-11-14 18:29:37.168076] Init crypto engine
[2021-11-14 18:29:37.232762] Disable caches
[2021-11-14 18:29:37.234168] Disable bootrom range checks
[2021-11-14 18:29:37.261538] Load payload from ../brom-payload/build/payload.bin = 0x45D0 bytes
[2021-11-14 18:29:37.268369] Send payload
[2021-11-14 18:29:38.162426] Let's rock
[2021-11-14 18:29:38.163471] Wait for the payload to come online...
[2021-11-14 18:29:38.773566] all good
[2021-11-14 18:29:38.774313] Check GPT
[2021-11-14 18:29:39.068375] gpt_parsed = {'KB': (2048, 2048), 'DKB': (4096, 2048), 'EXPDB': (6144, 35584), 'UBOOT': (41728, 2048), 'boot': (43776, 32768), 'recovery': (76544, 32768), 'MISC': (109312, 1024), 'LOGO': (110336, 7168), 'TEE1': (117504, 10240), 'TEE2': (127744, 10240), 'system': (137984, 2457600), 'cache': (2595584, 512000), 'userdata': (3107584, 12162271), '': (0, 1)}
[2021-11-14 18:29:39.068904] Check boot0
[2021-11-14 18:29:39.273662] Check rpmb
[2021-11-14 18:29:39.483073] Clear preloader header
[8 / 8]
[2021-11-14 18:29:39.857165] Downgrade rpmb
[2021-11-14 18:29:39.859385] Recheck rpmb
[2021-11-14 18:29:40.753236] rpmb downgrade ok
[2021-11-14 18:29:40.753799] Flash lk-payload
[5 / 5]
[2021-11-14 18:29:41.063839] Flash tz
[2244 / 2244]
[2021-11-14 18:30:29.236605] Flash lk
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 501, in read
'device reports readiness to read but returned no data '
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "main.py", line 156, in <module>
main()
File "main.py", line 130, in main
flash_binary(dev, "../bin/lk.bin", gpt["UBOOT"][0], gpt["UBOOT"][1] * 0x200)
File "main.py", line 34, in flash_binary
flash_data(dev, data, start_block, max_size=0)
File "main.py", line 25, in flash_data
dev.emmc_write(start_block + x, data[x * 0x200:(x + 1) * 0x200])
File "/home/pi/Downloads/amonet/modules/common.py", line 210, in emmc_write
code = self.dev.read(4)
File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 509, in read
raise SerialException('read failed: {}'.format(e))
serial.serialutil.SerialException: read failed: device reports readiness to read but returned no data (device disconnected or multiple access on port?)


What could I do know? If I try to power off the fire by holding the POWER button for about 40secs and then re-starting from step 2, it doesn't recognize the device and keeps saying "Waiting for bootrom" :/

Can anybody help me?
 

Graysters

Member
Dec 2, 2013
6
4
Hi All,

I'm trying to get to the bottom of the camera issues that some austin devices are having.
To be clear, I am not a developer, but I do happen to have two notionally identical austin tablets.
Both tablets' cameras (still and video) work perfectly under FireOS. but under LOS14.1 their behaviour differs:

  • Austin Tablet A: both still (not video) cameras function correctly in @ggow 's latest 14.1LOS build
  • Austin Tablet B: Neither still (nor video) cameras function correctly in latest 14.1LOS build. (crashes camera app)

This is with an identical clean LOS14.1 install on both devices... really odd.

Having taken the back off the tablets I made an interesting discovery:

It seems that austin tablets have different camera modules installed! (may be true of Ford too)

this would probably explain the behaviour differences people (myself included) are seeing with the cameras on these tablets.

Anyway, if anyone's interested

Tablet A with the working camera has the following written on the rear facing camera:
Austin_Tablet_A_Camera.jpg


BLX2509H-
A1916-B
V1.0 5.6


Tablet B, the one with non-working cameras has the following written on the rear facing camera:
Austin_Tablet_B_Camera.jpg

G7P2-ZA
1916BHQ-
2355N
V2


I've only checked the rear facing camera, as they're the easiest to access, but I expect the same is true for the front facing one too...

I suspect @ggow has a tablet similar to my Tablet A, and hence has setup the LOS14.1 ROM to work with the camera modules in that, but the modules in TabletB, are sufficiently different for this not to work. Just to prove the point, I temporarily swapped the rear camera from TabletA and put it in Tablet B, and that works fine in the camera app!

I expect there must be some configuration data required that's either not being read correctly (or at all) from the camera EEPROM, or not being passed to the camera app correctly.

From the logcat (snippet below, let me know if you want to see this) I've just dumped from Tablet B when the camera app crashes, the backtrace points at
Code:
/system/lib/lib3a.so
which seems to be related to camera settings...

Code:
[ 12-01 10:21:05.321  2836: 2836 F/DEBUG    ]
    #00 pc 000101a6  /system/lib/lib3a.so (_ZN4NS3A6AeAlgo19getAEPLineMappingIDE15LIB3A_AE_MODE_TP10eAETableIDi+217)


[ 12-01 10:21:05.321  2836: 2836 F/DEBUG    ]
    #01 pc 000102cd  /system/lib/lib3a.so (_ZN4NS3A6AeAlgo9setAEModeE15LIB3A_AE_MODE_T+84)


[ 12-01 10:21:05.321  2836: 2836 F/DEBUG    ]
    #02 pc 00014b05  /system/lib/lib3a.so (_ZN4NS3A6AeAlgo6initAEEPK18AE_INITIAL_INPUT_TP11strAEOutputP15AE_STAT_PARAM_T+220)



It's at this point that my limited knowledge runs out...

Is there anything I can extract from TabletB running FireOS that can be grafted into a LOS14.1 image to get it working?

Or can lib3a.so be patched to do the right thing with different cameras?

Happy for pointers in the right direction!

Cheers,

Graysters
 
Last edited:
  • Like
Reactions: DigitalSnow

DigitalSnow

Senior Member
Mar 23, 2012
60
7
@Ziona - Do you know if any of these fixes are included in ggow's latest (17 Jan 2021) image from the first post?

Edit: Removed the accidental extra quote.
Having this same question myself, this is what I have found in reading back on this thread for a while.

Yes, a couple of them are still needed it seems. In Ziona's post there is links to latest Ford and Austin boot images which have a release date after the latest Jan 17th image date. In those posts they include the SDCARD FIX and QUICKBOOT FIX (boot.img).

Rortiz2 says that the fixes should not be needed here:

Rondadon says that they needed the rotate fix here:

So it sounds like, install the latest, but add Ziona's boot.img for the SDCARD and QUICKBOOT. Then add anything else only if needed. That is what I am currently trying...

Update: On my ford, first installed the latest image, Ziona's boot.img, and gapps pico, but it just hung on the loading screen after reboot. Then tried, just the latest image and gapps pico and everything is working great so far (wifi, camera, screen rotation all good).

Update 2: correction on screen rotation. It only works for a while and then quits working. May try the screen rotation fix if I feel like installing Magisk.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Hi there! I have a 5th generation device.
    I successfully downgraded bootloader and then initiated the sudo ./bootrom-step.sh process.
    Unfortunately the usb cable disconnected right in the middle of the process... 😭 here's the output:

    [2021-11-14 18:29:37.168076] Init crypto engine
    [2021-11-14 18:29:37.232762] Disable caches
    [2021-11-14 18:29:37.234168] Disable bootrom range checks
    [2021-11-14 18:29:37.261538] Load payload from ../brom-payload/build/payload.bin = 0x45D0 bytes
    [2021-11-14 18:29:37.268369] Send payload
    [2021-11-14 18:29:38.162426] Let's rock
    [2021-11-14 18:29:38.163471] Wait for the payload to come online...
    [2021-11-14 18:29:38.773566] all good
    [2021-11-14 18:29:38.774313] Check GPT
    [2021-11-14 18:29:39.068375] gpt_parsed = {'KB': (2048, 2048), 'DKB': (4096, 2048), 'EXPDB': (6144, 35584), 'UBOOT': (41728, 2048), 'boot': (43776, 32768), 'recovery': (76544, 32768), 'MISC': (109312, 1024), 'LOGO': (110336, 7168), 'TEE1': (117504, 10240), 'TEE2': (127744, 10240), 'system': (137984, 2457600), 'cache': (2595584, 512000), 'userdata': (3107584, 12162271), '': (0, 1)}
    [2021-11-14 18:29:39.068904] Check boot0
    [2021-11-14 18:29:39.273662] Check rpmb
    [2021-11-14 18:29:39.483073] Clear preloader header
    [8 / 8]
    [2021-11-14 18:29:39.857165] Downgrade rpmb
    [2021-11-14 18:29:39.859385] Recheck rpmb
    [2021-11-14 18:29:40.753236] rpmb downgrade ok
    [2021-11-14 18:29:40.753799] Flash lk-payload
    [5 / 5]
    [2021-11-14 18:29:41.063839] Flash tz
    [2244 / 2244]
    [2021-11-14 18:30:29.236605] Flash lk
    Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 501, in read
    'device reports readiness to read but returned no data '
    serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)

    During handling of the above exception, another exception occurred:

    Traceback (most recent call last):
    File "main.py", line 156, in <module>
    main()
    File "main.py", line 130, in main
    flash_binary(dev, "../bin/lk.bin", gpt["UBOOT"][0], gpt["UBOOT"][1] * 0x200)
    File "main.py", line 34, in flash_binary
    flash_data(dev, data, start_block, max_size=0)
    File "main.py", line 25, in flash_data
    dev.emmc_write(start_block + x, data[x * 0x200:(x + 1) * 0x200])
    File "/home/pi/Downloads/amonet/modules/common.py", line 210, in emmc_write
    code = self.dev.read(4)
    File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 509, in read
    raise SerialException('read failed: {}'.format(e))
    serial.serialutil.SerialException: read failed: device reports readiness to read but returned no data (device disconnected or multiple access on port?)


    What could I do know? If I try to power off the fire by holding the POWER button for about 40secs and then re-starting from step 2, it doesn't recognize the device and keeps saying "Waiting for bootrom" :/

    Can anybody help me?
    1
    Hi All,

    I'm trying to get to the bottom of the camera issues that some austin devices are having.
    To be clear, I am not a developer, but I do happen to have two notionally identical austin tablets.
    Both tablets' cameras (still and video) work perfectly under FireOS. but under LOS14.1 their behaviour differs:

    • Austin Tablet A: both still (not video) cameras function correctly in @ggow 's latest 14.1LOS build
    • Austin Tablet B: Neither still (nor video) cameras function correctly in latest 14.1LOS build. (crashes camera app)

    This is with an identical clean LOS14.1 install on both devices... really odd.

    Having taken the back off the tablets I made an interesting discovery:

    It seems that austin tablets have different camera modules installed! (may be true of Ford too)

    this would probably explain the behaviour differences people (myself included) are seeing with the cameras on these tablets.

    Anyway, if anyone's interested

    Tablet A with the working camera has the following written on the rear facing camera:
    Austin_Tablet_A_Camera.jpg


    BLX2509H-
    A1916-B
    V1.0 5.6


    Tablet B, the one with non-working cameras has the following written on the rear facing camera:
    Austin_Tablet_B_Camera.jpg

    G7P2-ZA
    1916BHQ-
    2355N
    V2


    I've only checked the rear facing camera, as they're the easiest to access, but I expect the same is true for the front facing one too...

    I suspect @ggow has a tablet similar to my Tablet A, and hence has setup the LOS14.1 ROM to work with the camera modules in that, but the modules in TabletB, are sufficiently different for this not to work. Just to prove the point, I temporarily swapped the rear camera from TabletA and put it in Tablet B, and that works fine in the camera app!

    I expect there must be some configuration data required that's either not being read correctly (or at all) from the camera EEPROM, or not being passed to the camera app correctly.

    From the logcat (snippet below, let me know if you want to see this) I've just dumped from Tablet B when the camera app crashes, the backtrace points at
    Code:
    /system/lib/lib3a.so
    which seems to be related to camera settings...

    Code:
    [ 12-01 10:21:05.321  2836: 2836 F/DEBUG    ]
        #00 pc 000101a6  /system/lib/lib3a.so (_ZN4NS3A6AeAlgo19getAEPLineMappingIDE15LIB3A_AE_MODE_TP10eAETableIDi+217)
    
    
    [ 12-01 10:21:05.321  2836: 2836 F/DEBUG    ]
        #01 pc 000102cd  /system/lib/lib3a.so (_ZN4NS3A6AeAlgo9setAEModeE15LIB3A_AE_MODE_T+84)
    
    
    [ 12-01 10:21:05.321  2836: 2836 F/DEBUG    ]
        #02 pc 00014b05  /system/lib/lib3a.so (_ZN4NS3A6AeAlgo6initAEEPK18AE_INITIAL_INPUT_TP11strAEOutputP15AE_STAT_PARAM_T+220)



    It's at this point that my limited knowledge runs out...

    Is there anything I can extract from TabletB running FireOS that can be grafted into a LOS14.1 image to get it working?

    Or can lib3a.so be patched to do the right thing with different cameras?

    Happy for pointers in the right direction!

    Cheers,

    Graysters
  • 41
    Disclaimer
    Code:
    /*
    * I am not responsible for bricked devices, dead SD cards, thermonuclear war,
    * or you getting fired because the alarm app failed.
    * Please do some research if you have any concerns about features included
    * in the products you find here before flashing it!
    * YOU are choosing to make these modifications.
    */
    LineageOS needs no introductions. This version of LineageOS-14.1 is a highly customised version solely for the ford and austin models of the Amazon Fire 7"

    - EVEN MORE IMPORTANT: This ROM only works on devices using the bootloader hack. See <<< HERE >>> to unlock your devices.

    - IMPORTANT: Do not update Magisk via the Magisk Manager App, your device will enter a bootloop if you do. Instead update Magisk via TWRP only. If you do this by accident then it is recoverable by just flashing the latest version of the ROM again (with gapps etc as required).

    Rules
    - Please search the thread before asking questions
    - Please try to stay on topic, I know it's not always possible
    - Please report bugs here
    - Report only one issue per bug report
    - When reporting bugs please post a logcat and/or dmesg containing pertinent information regarding the issue...

    Prerequisites for Installation
    - Unlocked Bootloader
    - TWRP Installed

    Downloads
    *** Please do NOT create any mirrors ***
    Lineage-14.1 for Amazon Fire 7"

    Source Code

    - ROM Source: LineageOS
    - Kernel Source: https://github.com/ggow/android_kernel_amazon_mt8127-common
    - Common Tree: https://github.com/ggow/android_device_amazon_mt8127-common
    - Device Tree: https://github.com/ggow/android_device_amazon_ford
    - Device Tree: https://github.com/ggow/android_device_amazon_austin

    Thanks
    - @k4y0z and @xyz` for the bootloader hack
    - LineageOS

    NOTE
    Here is the link to all available fixes for Austin & Ford. Will be updated when anything new is introduced. Questions about mod add-ons you can ask me @Ziona
    https://forum.xda-developers.com/showpost.php?p=80167249&postcount=26


    XDA:DevDB Information
    mt8127_LineageOS-14.1, ROM for the Amazon Fire

    Contributors
    ggow, Ziona
    ROM OS Version: 7.x Nougat
    ROM Kernel: Linux 3.10.x
    ROM Firmware Required: Unlocked Bootloader
    Based On: LineageOS
    22
    @ggow

    FORD & AUSTIN FIXES DOWNLOAD PAGES LIST

    FLASH THEM VIA TWRP

    OMX VIDEO FIX VIDEO PLAYBACK ISSUES (zip file below)

    NVRAM FIX ( for error Issue on wifi scan dialogue )
    https://forum.xda-developers.com/showpost.php?p=81992843&postcount=548 . lastest

    https://forum.xda-developers.com/showpost.php?p=80166385&postcount=25


    Build Prop edit & flash tool For ford , Note; Austin users will have to change the buildprop file within the zip with their own first to use.
    ( Just edit buildprop within the zip an flash via recovery page #5
    Only needed for stubborn build prop edits that don't stick on reboot. https://forum.xda-developers.com/showpost.php?p=80207471&postcount=50

    Custom ggow Tribute Fire Reborn Boot Animation zip on page #10 https://forum.xda-developers.com/showpost.php?p=80383683&postcount=91

    Nougat Battery Saver Plus ( Force Doze ) on Page #10 https://forum.xda-developers.com/showpost.php?p=80396199&postcount=100

    CAMERA WORKAROUND APP Page #13
    https://forum.xda-developers.com/showpost.php?p=80420517&postcount=121

    AUTO ROTATION FIXES , ON PAGE # 15 app & PAGE # 25 fix zip
    https://forum.xda-developers.com/showpost.php?p=80630501&postcount=241

    LATEST FOR AUTO ROTATION ISSUES
    https://forum.xda-developers.com/showpost.php?p=81731259&postcount=460

    New Fix - FASTER BOOT START-UP SPEED PLUS SD CARD FIX - FORD & AUSTIN ON PAGE #22

    Ford - https://forum.xda-developers.com/showpost.php?p=80584099&postcount=214

    Austin - https://forum.xda-developers.com/showpost.php?p=80590927&postcount=219

    HARDWARE ACCELERATION TWEAK PAGE #27
    https://forum.xda-developers.com/showpost.php?p=80670111&postcount=267

    TITANIUM BACKUP SUPPORT PAGE # 26
    https://forum.xda-developers.com/showpost.php?p=80658833&postcount=260

    SDCARD TO ROOT WRITE ACCESS FOR SOME APPS
    https://forum.xda-developers.com/showpost.php?p=82208665&postcount=1 . Lastest

    https://forum.xda-developers.com/showpost.php?p=82039601&postcount=564

    LITE PIXEL LAUNCHER PAGE # 20
    https://forum.xda-developers.com/showpost.php?p=80554187&postcount=198

    OTG SUPPORT PAGE # 35
    https://forum.xda-developers.com/showpost.php?p=80794079&postcount=343

    NEW BOOT ANIMATION FIRE SKULL PAGE #36
    https://forum.xda-developers.com/showpost.php?p=80812161&postcount=352

    SMARTKERNEL AUDITOR
    https://forum.xda-developers.com/showpost.php?p=80586217&postcount=217

    MICRO-G INSTALLER
    https://forum.xda-developers.com/showpost.php?p=80620189&postcount=234

    LATEST FORD BOOT IMAGE WITH ADD-ONS
    https://forum.xda-developers.com/showpost.php?p=81762183&postcount=484

    LATEST AUSTIN BOOT IMAGE WITH ADD-ONS
    https://forum.xda-developers.com/showpost.php?p=81771963&postcount=491

    NEW WIFI SLEEP POLICY PATCH For battery savings.
    https://forum.xda-developers.com/showpost.php?p=82077939&postcount=1

    DEVELOPER OPTIONS ENABLER
    https://forum.xda-developers.com/showpost.php?p=82187235&postcount=1

    UPDATED 07/04/2020

    if you liked all the help Please hit thanks
    18
    Hi, hope you're all well,


    Just a quick note, I was planning to do some stuff on this but have not had enough time for everything. Covid hit and work has gone crazy busy so not much bandwidth. I have had time to do some stuff for Kindle HDX, a little suez and that's all.
    15
    New Build is Up

    Dated 17 January 2021

    - Special thanks to @Ziona for all the great support provided
    - Fix external sdcard access
    - Fix OMX and media playback
    - Fix microphone
    - Setup zram with 0.5GB
    - Fixed cameras for ford and austin
    - Fixed screen off rotation animation for ford
    - Tested youtube and Newpipe
    - Tested amazon prime video
    - Tested clash of clans
    - Tested wired headphones
    - Tested microphone with sound recorder
    - Tested Spotify
    - Video cameras do not work
    13
    TODO

    - nvramAgent and media_policy service looping resulting in longer boot time
    - sdcard access, needs investigating - does it work the same as in lollipop - guessing not
    - OMX not working
    - NVRAM warning in WiFi settings Post #9
    - austin: Camera won't connect Post #9
    - ford: screen off animation orientation
    - ford: screen rotation sensor not working
    - ZRAM not working
    - Netflix not working