[discontinued][ROM][unlocked][ford,austin] Fire Nexus ROM [26 MAY 2019]

Status
Not open for further replies.
Search This thread

ajislav

Senior Member
Apr 1, 2011
412
212
Thanks, this didn't work. Not sure if it is because I am using a Family account on the device (kid under 13 account). Rebuild it is.
Thanks for the info. What other google accounts were on the devices? (as I understand it, there was only one child account on each device right?) My takeaway, so far, is that the ROM does not support dirty flashing (i.e. no data wipe) when only the child account is used on the device.
(as a side note, I hightly doubt that this has anything to do with ggow changing the ROM to support the unlocked bootloader only, but I could be wrong)
 

leaskovski

Senior Member
Mar 31, 2006
489
20
Thanks for the info. What other google accounts were on the devices? (as I understand it, there was only one child account on each device right?) My takeaway, so far, is that the ROM does not support dirty flashing (i.e. no data wipe) when only the child account is used on the device.
(as a side note, I hightly doubt that this has anything to do with ggow changing the ROM to support the unlocked bootloader only, but I could be wrong)

Correct, there was no other account on the device.

I have two devices, and I upgraded both. One device got broke that I had to rebuild, the other I managed to rescue by reinstalling gapps again on to the device and only wiping davlik. After reboot, all was fine.
 
  • Like
Reactions: ajislav

DB126

Senior Member
Oct 15, 2013
15,259
10,037
Amazon Fire HD 8 and HD 10
Google Pixel 4a
Correct, there was no other account on the device.

I have two devices, and I upgraded both. One device got broke that I had to rebuild, the other I managed to rescue by reinstalling gapps again on to the device and only wiping davlik. After reboot, all was fine.
As a side note davlik is automatically rebuilt after flashing system, even with 'dirty' updates. That said, there is no harm invoking a manual wipe from twrp and no time savings either way.
 

Rortiz2

Senior Member
Mar 1, 2018
2,034
1,241
Barcelona
Logcat when trying record video:
Code:
I/CameraService( 5463): CameraService started (pid=5463)

D/AMZ-MtkCam/module( 5463): [mtk_camera_module_methods_instantiate] module_api_version:0x203


D/AMZ-MtkCam/Utils/Property( 5463): [clear] pid/tid=5463/5463


D/AMZ-MtkCam/module( 5463): [mtk_camera_module_methods_instantiate] 00: getProperty


D/AMZ-MtkCam/module( 5463): [mtk_camera_module_methods_instantiate] 01: setProperty


I/CameraService( 5463): Loaded "MediaTek Camera Module" camera module

D/AMZ-MtkCam/MtkCamUtils( 5463): [CamDevMetaInfoMap::clear] pid/tid=5463/5463


D/AMZ-SeninfDrvImp( 5463): [getInstance][getInstance] 

D/AMZ-SeninfDrvImp( 5463): [SeninfDrvImp][SeninfDrvImp] 

D/AMZ-SeninfDrvImp( 5463): [init][init]: 0 

D/AMZ-SeninfDrvImp( 5463): [init][init]: X 

D/AMZ-SeninfDrvImp( 5463): [setTg1PhaseCounter][setTg1PhaseCounter] pcEn(1) clkPol(1)

D/AMZ-ImgSensorDrv( 5463): [impSearchSensor]SENSOR search start 

D/AMZ-ImgSensorDrv( 5463): [impSearchSensor][impSearchSensor] m_fdSensor = 14  

D/AMZ-ImgSensorDrv( 5463): [impSearchSensor]impSearchSensor search to sub

D/AMZ-ImgSensorDrv( 5463): [impSearchSensor]set sensor driver id =10000

I/art     (  839): Explicit concurrent mark sweep GC freed 124019(6MB) AllocSpace objects, 4(58KB) LOS objects, 40% free, 17MB/29MB, paused 2.325ms total 204.364ms

D/AMZ-ImgSensorDrv( 5463): [getCurrentSensorType][getCurrentSensorType] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getSocketPosition][getSocketPosition]:[1][1] 

D/AMZ-ImgSensorDrv( 5463): [impSearchSensor]found <0x2355/gc2355mipiraw/SENSOR_DRVNAME_GC2355_MIPI_RAW>

D/AMZ-ImgSensorDrv( 5463): [impSearchSensor]MAIN sensor found:[0]/[0x10000]/[0]/[1] 

D/AMZ-ImgSensorDrv( 5463): [impSearchSensor]set sensor driver id =10001

D/AMZ-ImgSensorDrv( 5463): [impSearchSensor][impSearchSensor] Err-ctrlCode (I/O error) 

D/AMZ-ImgSensorDrv( 5463): [getCurrentSensorType][getCurrentSensorType] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getSocketPosition][getSocketPosition]:[1][1] 

D/AMZ-ImgSensorDrv( 5463): [impSearchSensor]sensor ID mismatch

D/AMZ-ImgSensorDrv( 5463): [impSearchSensor]set sensor driver id =10002

D/AMZ-ImgSensorDrv( 5463): [impSearchSensor][impSearchSensor] Err-ctrlCode (I/O error) 

D/AMZ-ImgSensorDrv( 5463): [getCurrentSensorType][getCurrentSensorType] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getSocketPosition][getSocketPosition]:[1][1] 

D/AMZ-ImgSensorDrv( 5463): [impSearchSensor]sensor ID mismatch

D/AMZ-ImgSensorDrv( 5463): [impSearchSensor]set sensor driver id =10003

E/AudioService(  462): Media server started.

D/AMZ-ImgSensorDrv( 5463): [impSearchSensor][impSearchSensor] Err-ctrlCode (I/O error) 

D/AMZ-ImgSensorDrv( 5463): [getCurrentSensorType][getCurrentSensorType] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getSocketPosition][getSocketPosition]:[1][1] 

D/AMZ-ImgSensorDrv( 5463): [impSearchSensor]sensor ID mismatch

D/AMZ-ImgSensorDrv( 5463): [impSearchSensor]m_pstSensorInitFunc[i].getCameraDefault is NULL: 4 

D/AMZ-ImgSensorDrv( 5463): [impSearchSensor]impSearchSensor search to sub

D/AMZ-ImgSensorDrv( 5463): [impSearchSensor]set sensor driver id =20000

D/AMZ-ImgSensorDrv( 5463): [impSearchSensor][impSearchSensor] Err-ctrlCode (I/O error) 

D/AMZ-ImgSensorDrv( 5463): [getCurrentSensorType][getCurrentSensorType] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getSocketPosition][getSocketPosition]:[2][-1] 

D/AMZ-ImgSensorDrv( 5463): [impSearchSensor]sensor ID mismatch

D/AMZ-ImgSensorDrv( 5463): [impSearchSensor]set sensor driver id =20001

D/AMZ-ImgSensorDrv( 5463): [impSearchSensor][impSearchSensor] Err-ctrlCode (I/O error) 

D/AMZ-ImgSensorDrv( 5463): [getCurrentSensorType][getCurrentSensorType] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getSocketPosition][getSocketPosition]:[2][-1] 

D/AMZ-ImgSensorDrv( 5463): [impSearchSensor]sensor ID mismatch

D/AMZ-ImgSensorDrv( 5463): [impSearchSensor]set sensor driver id =20002

D/AMZ-ImgSensorDrv( 5463): [getCurrentSensorType][getCurrentSensorType] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getSocketPosition][getSocketPosition]:[2][-1] 

D/AMZ-ImgSensorDrv( 5463): [impSearchSensor]found <0xb310/gc0312yuv/SENSOR_DRVNAME_GC0312_YUV>

D/AMZ-ImgSensorDrv( 5463): [impSearchSensor]SUB sensor found:[2]/[0x20002]/[1]/[-1] 

D/AMZ-ImgSensorDrv( 5463): [impSearchSensor]set sensor driver id =20003

D/AMZ-ImgSensorDrv( 5463): [impSearchSensor][impSearchSensor] Err-ctrlCode (I/O error) 

D/AMZ-ImgSensorDrv( 5463): [getCurrentSensorType][getCurrentSensorType] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getSocketPosition][getSocketPosition]:[2][-1] 

D/AMZ-ImgSensorDrv( 5463): [impSearchSensor]sensor ID mismatch

D/AMZ-ImgSensorDrv( 5463): [impSearchSensor]m_pstSensorInitFunc[i].getCameraDefault is NULL: 4 

D/AMZ-ImgSensorDrv( 5463): [impSearchSensor]SENSOR search end: 0x7 /[0x2355][0]/[0xb310][2]

D/AMZ-ImgSensorDrv( 5463): [init][init] mUsers = 0

D/AMZ-ImgSensorDrv( 5463): [init][init] m_fdSensor = 14  

D/AMZ-ImgSensorDrv( 5463): [init][init]: m_LineTimeInus[0] = 27

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getCurrentSensorType][getCurrentSensorType] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getCurrentSensorType][getCurrentSensorType] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getCurrentSensorType][getCurrentSensorType] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getCurrentSensorType][getCurrentSensorType] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getCurrentSensorType][getCurrentSensorType] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getCurrentSensorType][getCurrentSensorType] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getCurrentSensorType][getCurrentSensorType] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getCurrentSensorType][getCurrentSensorType] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getCurrentSensorType][getCurrentSensorType] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [uninit][uninit] mUsers = 1

D/AMZ-ImgSensorDrv( 5463): [init][init] mUsers = 0

D/AMZ-ImgSensorDrv( 5463): [init][init] m_fdSensor = 14  

D/AMZ-ImgSensorDrv( 5463): [init][init]: m_LineTimeInus[1] = 26692308

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getCurrentSensorType][getCurrentSensorType] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getCurrentSensorType][getCurrentSensorType] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getCurrentSensorType][getCurrentSensorType] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getCurrentSensorType][getCurrentSensorType] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getCurrentSensorType][getCurrentSensorType] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getCurrentSensorType][getCurrentSensorType] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getCurrentSensorType][getCurrentSensorType] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getCurrentSensorType][getCurrentSensorType] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [getCurrentSensorType][getCurrentSensorType] 

D/AMZ-ImgSensorDrv( 5463): [getInfo][getInfo] 

D/AMZ-ImgSensorDrv( 5463): [uninit][uninit] mUsers = 1

D/AMZ-SeninfDrvImp( 5463): [uninit][uninit]: 1 

D/AMZ-SeninfDrvImp( 5463): [setTg1PhaseCounter][setTg1PhaseCounter] pcEn(0) clkPol(0)

D/AMZ-MtkCam/MtkCamUtils( 5463): [CamDevMetaInfoMap::add] pid/tid=5463/5463 size:1, OpenId:0


D/AMZ-MtkCam/MtkCamUtils( 5463): [CamDevMetaInfoMap::add] pid/tid=5463/5463 size:2, OpenId:1


D/AMZ-MtkCam/MtkCamUtils( 5463): [CamDevMetaInfoMap::add] pid/tid=5463/5463 size:3, OpenId:255


D/AMZ-MtkCam/devicemgr( 5463): [enumDeviceLocked] iSensorsList=0x00000007, i4DeviceNum=2


D/AMZ-MtkCam/devicemgr( 5463): [enumDeviceLocked] [0x00] orientation(wanted/setup)=(90/90) facing:0 metadata:0x0 DeviceVersion:0x100


D/AMZ-MtkCam/devicemgr( 5463): [enumDeviceLocked] [0x01] orientation(wanted/setup)=(270/270) facing:1 metadata:0x0 DeviceVersion:0x100


D/AMZ-MtkCam/devicemgr( 5463): [enumDeviceLocked] [0xff] orientation(wanted/setup)=(0/270) facing:0 metadata:0x0 DeviceVersion:0x100


D/AMZ-MtkCam/Utils/Profile( 5463): {CamProfile}[CamDeviceManagerImp::enumDeviceLocked] : (0-th) ===> [start-->now: 268 ms]


D/AMZ-MtkCam/Utils/Profile( 5463): {CamProfile}[CamDeviceManagerBase::getNumberOfDevices] : (0-th) ===> [start-->now: 268 ms]
It says: Can't connect to camera.
 

secerko

New member
Dec 11, 2010
4
1
Can t install rom on ford (2015). I get following (twrp /install zip)
amonet Remove boot patch...
amonet OK
detected filesystem ext4.....
script succeeded: result was /system
amonet Install boo patch...
amonet OK
amonet Install recovery patch....
amonet ALREADY_INSTALLED
Updating partition details.....
...done

Rom Is stored on device (same occurred with sideloding previos version of rom) and with sideloading lp rom

When rebooting to system i get message “no os installed”


Sent from my iPhone using Tapatalk
 

secerko

New member
Dec 11, 2010
4
1
Can t install rom on ford (2015). I get following (twrp /install zip)
amonet Remove boot patch...
amonet OK
detected filesystem ext4.....
script succeeded: result was /system
amonet Install boo patch...
amonet OK
amonet Install recovery patch....
amonet ALREADY_INSTALLED
Updating partition details.....
...done

Rom Is stored on device (same occurred with sideloding previos version of rom) and with sideloading lp rom

When rebooting to system i get message “no os installed”


Sent from my iPhone using Tapatalk



Flashing boot.img from rom’s zip (it is posted at end of first post) has worked, rom is now loading and it is darn fast!


Sent from my iPhone using Tapatalk
 

klamation

Senior Member
Apr 28, 2011
132
12
Nokia Lumia 820
Nokia Lumia 920
Bluetooth issue

Hey guys, I recently installed this Fire Nexus ROM (26May2019 image) on some 2015 Kindle Fire tablets, and am super-impressed with the performance and stability of it, considering the hardware. I did notice a problem, though, so I hope this is the best place to bring it up.

I set up my Google account as the "owner" on the tablet, and set up my son's Google account as a secondary User on it. I can enable Bluetooth on my side, but whenever he goes to enable Bluetooth, the switch will flip to on, then go back to off within a few seconds, and he cannot use Bluetooth at all.

Any thoughts on what else I need to do to troubleshoot this, gather logs, or possibly fix it? Or is it really a bug in the image?
 

DB126

Senior Member
Oct 15, 2013
15,259
10,037
Amazon Fire HD 8 and HD 10
Google Pixel 4a
Hey guys, I recently installed this Fire Nexus ROM (26May2019 image) on some 2015 Kindle Fire tablets, and am super-impressed with the performance and stability of it, considering the hardware. I did notice a problem, though, so I hope this is the best place to bring it up.

I set up my Google account as the "owner" on the tablet, and set up my son's Google account as a secondary User on it. I can enable Bluetooth on my side, but whenever he goes to enable Bluetooth, the switch will flip to on, then go back to off within a few seconds, and he cannot use Bluetooth at all.

Any thoughts on what else I need to do to troubleshoot this, gather logs, or possibly fix it? Or is it really a bug in the image?
I generally find that one user per device is 'best practice' with custom ROMs, especially on Amazon HW. I realize this is not popular nor the response you were looking for. That said, I have never been one to cut across the grain or swim upstream unless the benefit significantly outweighed the effort. These things are relatively inexpensive; get your little one his own device and lock it down as needed. :)
 

klamation

Senior Member
Apr 28, 2011
132
12
Nokia Lumia 820
Nokia Lumia 920
I generally find that one user per device is 'best practice' with custom ROMs, especially on Amazon HW. I realize this is not popular nor the response you were looking for. That said, I have never been one to cut across the grain or swim upstream unless the benefit significantly outweighed the effort. These things are relatively inexpensive; get your little one his own device and lock it down as needed. :)

I get what you're saying, and expected a response like this. This isn't a shared device between users; all of my kids have their own Fire tablet. For the younger ones, I'm using a limited user account that doesn't connect to a gmail account, has a subset of apps, and Bluetooth works fine on these systems. It's simply a way to use a single Google account to manage all of these devices (so I can use Find My Device to locate them, etc), but to allow the kids access to their own Google account and apps on it. It's only a problem where multiple Users/Google accounts are in place.
 

rktr2019

New member
Jan 16, 2019
1
0
Alexa?

Any way to achieve Alexa hands free with a Ford device? Not with third party apps like Reverb or others. At least can we get Alexa app as we can with the stock firmware?
 

DB126

Senior Member
Oct 15, 2013
15,259
10,037
Amazon Fire HD 8 and HD 10
Google Pixel 4a
I get what you're saying, and expected a response like this. This isn't a shared device between users; all of my kids have their own Fire tablet. For the younger ones, I'm using a limited user account that doesn't connect to a gmail account, has a subset of apps, and Bluetooth works fine on these systems. It's simply a way to use a single Google account to manage all of these devices (so I can use Find My Device to locate them, etc), but to allow the kids access to their own Google account and apps on it. It's only a problem where multiple Users/Google accounts are in place.
Yep - multiple accounts generally behave in the expected fashion when operating autonomously on the end point. Things get more interesting (and convoluted) when addressing multiple host accounts. Level of refinement/segregation just isn't there. At least on older Android foundations. Actually, I'm surprised you didn't get a few home brew responses that are rarely stable in the wild and take 88 steps plus a prolonged prayer session to implement. Hence my previous response.

Good luck with whatever path you choose to pursue.
 
Last edited:
  • Like
Reactions: J-Lindo and ggow

klamation

Senior Member
Apr 28, 2011
132
12
Nokia Lumia 820
Nokia Lumia 920
Yep - multiple accounts generally behave in the expected fashion when operating autonomously on the end point. Things get more interesting (and convoluted) when addressing multiple host accounts. Level of refinement/segregation just isn't there. At least on older Android foundations. Actually, I'm surprised you didn't get a few home brew responses that are rarely stable in the wild and take 88 steps plus a prolonged prayer session to implement. Hence my previous response.

Good luck with whatever path you choose to pursue.

Thanks, it's all good. I just figured this would be the best place to report what seems to be a bug, but if it won't get fixed, I can deal with that.
 

mrsteveman1

New member
Aug 16, 2019
1
0
What would be involved in enabling USB tethering on this ROM ? Not for internet sharing, but purely for the IP connection.

I'm using a Fire 7 as the display for an Arducopter drone ground station, the Fire is connected to a Raspberry Pi running OpenHD, which handles the air<->ground communication link. Connecting them with WiFi causes a lot of problems (unpredictable latency and interference from other devices regardless of which WiFi band is used, also causes interference to the air<->ground link). USB tethering is apparently the best option, it's just not always enabled on Android tablet ROMs.

I've been a software engineer for a decade, and I've written in-house kernel code for work, so building a kernel with changes to the config isn't a problem. I'm just curious what other changes would have to be made, either to the existing ROM or during the build process for it.

I assume it's not something that most people would generally need so I'm not requesting it be added (and may not be a one-line trivial change either), just interested in some pointers in the right direction.

Thanks :)
 

sandman512

Senior Member
Nov 12, 2007
861
77
So, I have been running this ROM on my tablet for a little while now. The tablet seems to be extreme slow and non responsive at times. I have been out of the loop for a while on "flashing" and all. What are my options? Thanks!
 

ldeveraux

Senior Member
  • Nov 20, 2008
    2,410
    875
    So, I have been running this ROM on my tablet for a little while now. The tablet seems to be extreme slow and non responsive at times. I have been out of the loop for a while on "flashing" and all. What are my options? Thanks!

    I flashed the LineageOS 14.1 a week ago and it's absolutely terrific so far. It's pretty speedy, though no external SD support. It will come soon though!:good:
     

    sandman512

    Senior Member
    Nov 12, 2007
    861
    77
    Thanks for the reply. So, I am not sure what I did, BUT it's stuck in a loop(when it starts up this ROM). I think I can get it into Amazon Recovery Mode. Any advice? It's been a while since flashing ROMS. Thanks!
    UPDATE: So, I thought I bricked the device BUT I found a video by ROOTJUNKY and was able to restore it to an Amazon Device. Now, need to flash another ROM(I can't stop).
     
    Last edited:
    Status
    Not open for further replies.

    Top Liked Posts

    • There are no posts matching your filters.
    • 177
      Code:
      [COLOR="gray"]
      /*
       * 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.
       */
      [/COLOR]

      Information + Features
      - Pure AOSP Experience
      - Also ideal for customisation through Xposed

      - EVEN MORE IMPORTANT: As of January 2019 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...
      - Saying something isn't working without proper explanation will not attract any attention.

      Prerequisites for Installation
      - Unlocked Bootloader
      - TWRP Installed

      Downloads
      *** Please do NOT create any mirrors ***
      - Fire Nexus ROM for Amazon Fire 7"

      Source Code
      - Kernel Source: https://github.com/ggow/android_kernel_amazon_mt8127-common

      Credits
      - Google / AOSP
      - Lineage
      - CAF
      - Temasek

      XDA:DevDB Information
      lp-fire-nexus-rom, ROM for the Amazon Fire

      Contributors
      ggow
      ROM OS Version: 5.1.x Lollipop
      Based On: AOSP

      Version Information
      Status: Beta

      Created 2016-01-25
      Last Updated 2019-05-26
      54
      Change log / Release Notes

      [tbd] August 2019
      - ASB August 2019 patches (sec. string 2019-08-05)
      - Update Chromium WebView to 76.0.3809.111
      -

      26 May 2019

      - ASB May 2019 patches (sec. string 2019-05-05)
      - Fixed video recording
      - WiFi: Use hardware MAC address
      - Bluetooth: Use hardware MAC address
      - Fixed swype functionality when using AOSP keyboard

      03 May 2019

      - Fix certificate store issue which prevented connections to google servers.

      01 May 2019

      - ASB Apr 2019 patches (sec. string 2019-04-05)
      - Upstreamed kernel to 3.10.108
      - Add support for Austin Fire 7 7th Gen
      - Updated webview
      - Removed AOSP Calculator
      - Tested with Latest OpenGapps Pico
      - Tested with Magisk 19.1
      - Unlocked bootloader only
      - Gapps no longer included
      - Root no longer included
      - Enjoy!

      02 June 2018
      - ASB May 2018 patches (sec. string 2018-05-05)
      - Android System Webview updated to M66

      05 May 2018
      - Port relevant security patches up to April 2018
      - Update chromium-webview: 59.0.3071.92 -> 65.0.3325.144

      17 December 2017
      - Port relevant security patches to up December 2017

      02 December 2017
      - Port relevant security patches to up November 2017
      - Switch to using FireOS 5.4.0.0 update-kindle-37.5.7.9_user_579225620 binaries and boot.img
      - Fixed backlight becoming stuck on minimum setting. This needs more users to test. It works for me so far :)

      02 October 2017
      - Port relevant security patches to up September 2017
      - Includes all bluebourne patches
      - Standalone build is now available in the same download location
      - First standalone filename is "lp-fire-nexus-rom-ford-standalone-20171002.zip"

      22 July 2017
      - Upgrade ROM base LMY49M
      - Port security patches up to July 2017
      - Integrate Prebuilt webview.apk from CM-14.1
      - Compile ROM using Snapdragon LLVM 3.8.8
      - Upgrade to open_gapps-arm-5.1-nano-20170702.zip
      - Tested flashing from Lineage-12.1 -> Fire Nexus ROM via FlashFire 0.57
      - Tested upgrading from 08 FEB version to this via FlashFire 0.57

      08 February 2017
      - Switch to using FireOS 5.1.4 update-kindle-37.5.4.4_user_544271020 binaries and boot.img
      - Fix Miracast
      - Fix-up camera and video camera connect and recording problems.
      - Re-tested:
      • Snapshot Camera
      • Video Camera
      • Google Services
      • VLC
      • Miracast
      • Video Playback
      • Audio Playback

      02 February 2017
      - Fixed bug causing google play services to repeatedly crash
      - Fixed supersu.apk disappearing
      - Updated SuperSU to 2.79
      - Updated gapps to open_gapps-arm-5.1-nano-20170202.zip

      Older HIstory
      24 November 2016
      - November 2016 AOSP Security Patch Level
      - Switch to using lastest FireOS 5.3.2 - update-kindle-global-37.5.6.0_user_560177220 binaries and boot.img
      - Fix Video Recorder bug [Cannot connect to camera]
      - Fix bug in OMX causing freeze of video

      04 November 2016
      - October 2016 AOSP Security Patch Level
      - Fix x265 video playback - Thanks @jeromeof

      23 September 2016
      - September 2016 Security Patch Level
      - Updated integrated gapps to open_gapps-arm-5.1-nano-20160923
      - Switch to using lastest FireOS 5.3.1 - update-kindle-global-37.5.5.2_user_552153420 binaries and boot.img

      12 August 2016
      - August 2016 Security Patch Level
      - Updated integrated gapps to open_gapps-arm-5.1-nano-20160812
      - Fix audio lag issue in games - thanks @$ideWinder

      28 July 2016
      - July 2016 Security Patch Level
      - Fixed SuperSU update binary problem
      - Updated integrated gapps to open_gapps-arm-5.1-nano-20160728
      - Upgrade SuperSU to 2.76 Stable

      15 June 2016
      - June 2016 Security Patch Level
      - Added CIFS Support (Instructions here)
      - Fix Swipe for stock keyboard
      - Fixed failure to mount /system partition error due to change in build system
      - Switch to using lastest update-kindle-37.5.4.4_user_544271020 binaries and boot.img

      19 May 2016
      - May 2016 Security Patch Level

      20 April 2016
      - Add app name to "Android is Upgrading..." dialog
      - Fix sdcard write access
      - Enable Bluetooth LE

      05 April 2016
      - Includes April 2016 Security Patch Level
      - Update to android-5.1.1_r37
      - Switch to using lastest update-kindle-global-37.5.4.2_user_542168620 binaries and boot.img

      29 March 2016
      - Includes 01 March 2016 Security Patch Level
      - Upgrade SuperSU to 2.65 Stable

      29 Feb 2016
      - Fixed Downloads App Crash
      - Updated integrated gapps to open_gapps-arm-5.1-nano-20160228

      09 Feb 2016
      - Fixed AOSP Keyboard Swype functionality
      - Location Services Fixed
      - Screen Rotation Glitches Fixed

      07 Feb 2016
      - Built in SuperSU
      - Updated codebase to android-5.1.1_r34
      - Includes 01 February 2016 Security Patch Level
      - Upon installation open SuperSU and update binary via the Normal Method following the prompts

      27 Jan 2016
      - Fix Screenshot capture by rotating memory buffer according to ro.sf.hwrotation
      - Fixed camera/media/stagefright issues causing inability to save images
      - Fixed sdcard access, tested from ES File Explorer

      25 Jan 2016
      - Initial Release
      41
      New Build is Up

      - Dated 22 July 2017
      - Upgrade ROM base LMY49M
      - Port security patches up to July 2017
      - Integrate Prebuilt webview.apk from CM-14.1
      - Compile ROM using Snapdragon LLVM 3.8.8
      - Upgrade to open_gapps-arm-5.1-nano-20170202.zip
      - Tested flashing from Lineage-12.1 -> Fire Nexus ROM via FlashFire 0.57
      - Tested upgrading from 08 FEB version to this via FlashFire 0.57
      20
      Progress for Next version

      - I'm working on an update which should fix up the previous borked release.
      - This ROM relies on gapps been included to work correctly so will not be releasing without it
      - I've fixed a bug in one of the last security updates I back-ported. Google services using the latest gapps now seems stable.
      - I wanted to check over a few more things and do some testing before release.
      - Hopefully should be done within the next couple of days.
      18
      New Build is Up

      - Dated 17 December 2017
      - Port relevant security patches to up December 2017