yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] emeister2:
I still get this error on Austin after clean install with 20190731:

Camera error: Can't connect to the camera.

I also tried 20190730 with same result. 20190524 works though.

I have a logcat capture from 20190731 but I can't figure out how to attach it to my message. Below are some highlights. Thanks for your work!

mediaserver's remote binder Camera object died

Received error 100 from the Camera1 ErrorCallback

Camera open failure: HIST_ID0_-1_1_502_204_204_101_102_204_HEND

Received device exception:

java.lang.RuntimeException: getParameters failed (empty parameters)

at android.hardware.Camera.native_getParameters(Native Method)

at android.hardware.Camera.getParameters(Camera.java:1984)

at android.hardware.camera2.legacy.RequestThreadManager$5.handleMessage(RequestThreadManager.java:840)

at android.os.Handler.dispatchMessage(Handler.java:98)

at android.os.Looper.loop(Looper.java:135)

at android.os.HandlerThread.run(HandlerThread.java:61)
[Fire Original Android Development] platypoid:
I have 5th generation that was Flashfire 12.1 version long time ago and tried to update to Lineage awhile back and that is when there were all the problems with it not working so had to flash back to original then put in Cyanogen 12.1 version again. I finally got the gumption to do the new TWRP unlock method with bricking to older version . To make a long story short I couldn't get the raspberry pi to do that job - ended up cracking the screen taking the back off - still couldn't get pi to work so went to laptop with Linux Mint and it all worked perfectly. ( I wouldnt have had to take back off ) I sideloaded this newest July version, and the newest gapps, and Magisk and it all booted up fine - screen is okay even with the crack. What really surprised me is that all my old settings and apps are still in there even after all that - guess cause I never did any wipes ? Anyway thanks for the updates !
[Fire Original Android Development] DragonFire1024:
I've had data remain before several times when flashing stock. Its been mentioned before and no one seems to know how or why.
[Fire Original Android Development] ggow:
Could you a try a full wipe + format system and data?
[Fire Original Android Development] llamasking:
That message is from May, before the May 24 release. It works after that release.
[Fire Original Android Development] Rortiz2:
Nope. Austin here.
[MENTION=5749760]ggow[/MENTION] Clean flash + latest ROM + G-APPS and neither camera and video are working. It's not a hardware issue since in FireOS they work.
[Fire Original Android Development] ggow:
Strange, send me a logcat please.
[Fire Original Android Development] emeister2:
I wiped all and formatted system and data. I still get the camera error. I wiped all and formatted again and installed 20190524, still get the error! 20190524 worked at some point. I need to track it down. Seems unlikely but maybe my back camera broke. Open Camera app allows me to switch to front camera and works but back camera gets error. Built in app just fails.
[Fire Original Android Development] emeister2:
Update: Not a H/W problem. I just installed FireOS Revamped and both cameras work.
[Fire Original Android Development] ggow:
Could you connect your device up to the PC, you will will need adb and root access on your device enabled.

do the following at a terminal or windows command prompt:

adb shell
su
idme print device_type_id
idme print productid2
idme print board_id

Send me the output
[Fire Original Android Development] ggow:
Is anyone with ford having any issues with the camera?
[Fire Original Android Development] Reynald0:
Photo is taken from both frontal and rear camera, video is recorded and saved, fast scrolling logs I only see one permission denied thing:

smi_bw_ctrl_set(): vendor/mediatek/proprietary_mt8127/platform/mt8127/hardware/bwc/bandwidth_control_port.cpp@83: Open SMI(/dev/MTK_SMI) driver file failed.:Permission denied

emi_bw_ctrl_set(): vendor/mediatek/proprietary_mt8127/platform/mt8127/hardware/bwc/bandwidth_control_port.cpp@228: fail to open mem_bw_ctrl driver file

del.dog / adacugafoc.md
[Fire Original Android Development] ggow:
Thanks, is this from austin or ford?
[Fire Original Android Development] Ziona:
Preview:

Is the latest 12.1 ford download removed ? There is no June 30 download file only much older version there @ downloads link ! Also well the lineage team or who managers the 12.1 OS for the fire tablet be putting the SBC XQ BT PATCH For better quality Bluetooth audio what's already found in 14.1 an above ?:confused:
[Fire Original Android Development] Reynald0:
Ford, latest ROM.

Regards.

Inviato dal mio unknown utilizzando Tapatalk
[Fire Original Android Development] emeister2:
As requested:

shell@austin:/ # idme print device_type_id
idme print device_type_id
A1J16TEDOYCZTN
shell@austin:/ # idme print productid2
idme print productid2
0642FFFFFFFFFFFFFFFF
shell@austin:/ # idme print board_id
idme print board_id
0037001080000017

Thanks for looking!
[Fire Original Android Development] ggow:
Thanks and no worries, will take a look into it.
[Fire Original Android Development] sterbaya:
No camera issue on my ford with the 2 last ROM (07/30 & 07/31).
[Fire Original Android Development] newinnov:
Hi, Tested today there is no camera issue, dirty flashed. All basic functionality seems to work fine except auto mode in live display does not work, (based on time of day) User has to manually toggle.

Request: Please port/update resurrectRemix rom too. It was the best rom few years back when I tried. Now that we have boot unlock. Only if it's not require huge amount of commitment from your side... in that case please leave it to be as this device is almost obsolete.
[Fire Original Android Development] Ziona:
[MENTION=5749760]ggow[/MENTION] thanks for the update its working on Q :silly:;)

Do you think you can apply the SBC XQ Bluetooth patch by valkiss to improve the fires audio he made free patch's for ROM Dev like yourself to use , I found out that they are already used (His patches) in Lineage 15 & 16 roms now ! There's also mention some where that you can even decompile the Bluetooth default. so found in system / lib/ hw to make changes to increase its bit rate higher an so on . are you aware of any of this . If you even decide to guess you can either patch the ROM or tweak the Bluetooth. so they would be Fire :good::)
[Fire Original Android Development] ggow:
Could you send me a link to the patches and I'll take a look. I wasn't aware that they existed.
[Fire Original Android Development] Ziona:
This is one ! https://m.habr.com/en/post/456476/
[MENTION=685332]ValdikSS[/MENTION]
[Fire Original Android Development] shelleyfrank:
On Austin latest ROM, 31/07/19, my front camera is still not working, on two tablets, both Austin.

On the 22/04/19 build i have both cameras working, no video.

[MENTION=5749760]ggow[/MENTION] Here's another difference I've noticed between April build and all subsequent releases:

I am using defiant07's swapit script to add a swap file to expand virtual memory to 500mb ( https://xdaforums.com/showthread.php?t=2359182 ) An init.d script is run to attach a swap file at boot time. In the April build, the script isn't run at boot time, but it can still be run from a terminal. It is working fine in all the later releases. That is, after bootup you'll find that the zram is increased by x MB equal to the size of the swapfile.

I was going to use the 22/04/19 release to make use of the front camera (for Skype), but on account of low memory issue I decided to use the latest release instead and ditch the camera for now, since the tablet performs much better with a larger swap. The default here is 64 MB. Adding 449 MB swap makes it a nice 512 MB.
[Fire Original Android Development] prisoner1969:
Quick question. I have one of the tablets that was with the old firmware that was easy to flash with twrp. I haven't used my tablet in a long time. The last version of Lineage I flashed was from January of 2018. Obviously a clean flash is what I'm going to do but is there anything special I need to do? I see the unlocked bootloader needed since January of 2019. Can I just flash with the fastboot of twrp like I normally did? Thanks in advance. Mine is a Ford kffowi
[Fire Original Android Development] k4y0z:
The short answer is no, if you want to flash the current builds, being able to boot into TWRP is not enough, you will need an unlocked bootloader , this will also give you permanent access to TWRP without needing to use a PC.

This is required, since the current builds use a custom boot-image (instead of hijacking the boot-process like it used to be necessary with locked bootloader).

Given that you have a ford (KFFOWI/ 5th gen) the procedure is actually pretty simple and does not require you to open the device.

You will have to use amazon recovery to downgrade to version 5.0.1, which will put your device in a specific bricked state, which will allow you to run the unlock-procedure without opening the device. Be sure to read the guide completely before attempting, but TLDR, given that you have set up your linux environment as advised, in your case you will follow the downgrade route and have a fully unlocked ford with TWRP and your favorite custom ROM by [MENTION=5749760]ggow[/MENTION] in no time.

Good luck.
[Fire Original Android Development] prisoner1969:
Unfortunately I did follow the directions but during the process of using the script to unlock the bootloader my USB cable came loose now it won't turn on at all. Guessing it's a paperweight now.
[Fire Original Android Development] k4y0z:
I have replied to you on the other thread, let's keep it there.

TLDR, it's not a paperweight, no worries.
[Fire Original Android Development] DragonFire1024:
The battery trick does not always work. The USB ports on Amazon tablets are quite sensitive. So much as knocking the plug in the wrong direction just enough to bend anything inside, causes the USB port to just stop working altogether. It happened on my first HD 10 which ended up being stripped for the rest of the parts. It also happened on another one of my friends fire 7. However the battery trick is not working this case. I'm attempting to replace the port but it is secured to the board quite well and tearing it off too quick or in the wrong way well easily break the board or at least damage it beyond repair. They have those things soldered in there right through to the other side. If I can manage to get that off it's as easy as just flipping the port up and unplugging it and replacing it. You can just resolder the casing back onto the board or use a small amount of glue.and if it is indeed dead as a doc you can always look for other broken or damaged tablets on eBay and other places and simply just replace the board. You can get some of the broken ones online for as cheap as 4 bucks.
[Fire Original Android Development] prisoner1969:
Got it working. The one question I have is that on an old version of the rom I got VUDU (walmart streaming service) to work. Now it won't let me even log in. Vudu works fine and without an account I can view trailers and such. I use the exact same credentials as my phone but it won't let me login. Says invalid email address or password. Yet they are exactly the same on my xbox, computer, cellphone, and tv. I'm not at the max devices. Has anyone got Vudu to work with this rom?
[Fire Original Android Development] FabMue:
do the following at a terminal or windows command prompt:

adb shell
su
idme print device_type_id
idme print productid2
idme print board_id

Send me the output[/QUOTE]

Here is my output (if still necessary):

adb shell
shell@ford:/ $ su
root@ford:/ # idme print device_type_id
A2M4YX06LWP8WI
root@ford:/ # idme print productid2
0
root@ford:/ # idme print board_id
0025001050010015

AND

shell@austin:/ $ su
root@austin:/ # idme print device_type_id
A1J16TEDOYCZTN
root@austin:/ # idme print productid2
0641FFFFFFFFFFFFFFFF
root@austin:/ # idme print board_id
0037001080000017

I never had a camera issue on my ford. I bought my austin a few weeks ago which is not able to connect to my camera.
[Fire Original Android Development] q4q9x:
Updating

Just to be sure, to update from 24 May 2019 to 31 July 2019 is it necessary to wipe first, or can I just flash 31 July over an existing 24 May?
[Fire Original Android Development] ggow:
Yes, dirty flash should work fine.
[Fire Original Android Development] Ziona:
[MENTION=5749760]ggow[/MENTION]

Hey thought I should mention this in case it helps anyone , that the latest july update breaks MircoG features to link your Google account , you won't be able to sign in anymore , thou if you dirty flash it will keep signed in but all sync functions will stop eg... YouTube won't save videos you watch an so with other google apps you run ! May 24 update still runs perfectly !

---------- Post added at 12:41 AM ---------- Previous post was at 12:41 AM ----------

[/COLOR [MENTION=5749760]ggow[/MENTION]

Hey thought I should mention this in case it helps anyone , that the latest july update breaks MircoG features to link your Google account , you won't be able to sign in anymore , thou if you dirty flash it will keep signed in but all sync functions will stop eg... YouTube won't save videos you watch an so with other google apps you run ! May 24 update still runs perfectly !
[Fire Original Android Development] ggow:
Will put this on my list of issues
[Fire Original Android Development] chimera533:
I still have what seems to be the same problem with the camera. If I'm off charger for a while it will stop functioning until I restart the device. As long as I stay on charger it works.
[Fire Original Android Development] ggow:
New Build is Up

Dated 23 August 2019

- August 2019 ASB patches (sec. string 2019-08-05)

- Additional (backported) security patches from AOSP branch 'nougat-mr2-security-release

- Privacy Browser updated to version 3.2

- SetupWizard rebranded to LineageOS
[Fire Original Android Development] MZGSZM:
Hello!

Just wanted to pop in and say thank you for your efforts on this ROM. I just flashed it earlier this evening. I'm very impressed with how responsive this is compared to the stock Fire OS and how bug free (relatively speaking) it is. I would've expected a ROM for such a niche install base to be a fair bit less stable, excellent work!

~MZ
[Fire Original Android Development] DB126:
I have been appreciating [MENTION=5749760]ggow[/MENTION]'s work for years. They are (usually by a wide margin) the most refined and stable custom ROMs for Amazon devices. That doesn't happen by accident. Professional characteristics I seek out IRL.

Specific to this device, the latest builds targeting unlocked bootloaders have brought new life to an aging platform with limited resources. I actually enjoy using my early release Fords once again for targeted tasks that fit within the performance profile. Don't ask too much and the device and [MENTION=5749760]ggow[/MENTION]'s ROMs will deliver a very satisfactory experience.
[Fire Original Android Development] thechosenone43:
[MENTION=1531770]ggw[/MENTION] HELP please!

Ok I fu... up my Fire by flashing something wrong with flash fire.

Then I got my device bricked so I needed to flash stock Rom ( look SS please)

Now I'm on Stock and device got booted.

But I can't flash TWRP and Lineage OS over it.

It always get back to Bootloop and bricked...

What do I get wrong?

Could somebody explain me step by step by flashing TWRP correctly over the Stock Rom and that TWRP stays there?

Please any help appreciated.

Thanks guys
[Fire Original Android Development] thechosenone43:
Additional information about my last Post
[Fire Original Android Development] DB126:
This is not a hardware recovery thread. You will need to unlock your device to install the latest ROM builds. Flashfire is no longer relevant and should not be used.

Start here: https://xdaforums.com/amazon-fire/development/unlock-fire-t3899860
[Fire Original Android Development] Rortiz2:
[MENTION=5749760]ggow[/MENTION]

Latest build, Amazon Fire 7 2017 aka austin: Privacy Guard keeps spamming and it's disabled. I saw that this happened before but IDK if it has fix.

Regards!
[Fire Original Android Development] Ziona:
@ggow

[MENTION=5749760]ggow[/MENTION]

Hey Bud do you have any idea if this latest August update is compatible with MircoG !
[Fire Original Android Development] ggow:
It should be. Are you having issues?
[Fire Original Android Development] Ziona:
[MENTION=5749760]ggow[/MENTION]

Haven't tried it as yet wanted to make sure it was OK from you to flash first .

Thanks !
[Fire Original Android Development] ggow:
You'll have to flash it and find out. I don't use anything gapps related on my tablets.
[Fire Original Android Development] Ziona:
OK [MENTION=5749760]ggow[/MENTION]

Yeah I wouldn't either if it wasn't for YouTube which I use daily an its the only way I know that app can login to a account ! :good:
[Fire Original Android Development] glate:
Odd question. I have been running custom roms since this device (Ford) was first launched; however, my device fell off my shelf when I first got it and the USB port works to charge but not to connect. Am I now SOL when it comes to new ROMs? Seems that I need USB to unlock the boot loader? Thx!
[Fire Original Android Development] Rortiz2:
Yep you need usb for unlock so no new ROMS. But if you are running FireOS 5.0.1-5.3.1 you still can install OLD ROMS with locked BL usinf FlashFire.
[Fire Original Android Development] glate:
That's what I figured. Sadly the FlashFire ROMs are pretty old at this point from what I could see :crying:
[Fire Original Android Development] DB126:
Old but reliable and functionally equivalent to unlocked peers w/exception to the recently released Lineage 14.1. Certainly better than FireOS.
[Fire Original Android Development] vanzan:
I was on the 30th July build and just dirty flashed the latest. It's been stuck on the LineageOS boot thingy for over 10 minutes now.

Did a factory reset and it booted....have to start from scratch again though sadly.
[Fire Original Android Development] k4y0z:
Technically if you have root, it should be possible to flash the unlock without USB.

It's not without risk though and should something go wrong you'd have no way to recover without USB.

You could open the device and try to fix the usb-port though likely one or both of the data-pins just got detached from the fall.
[Fire Original Android Development] Rortiz2:
Is amonet flashable by flashfire?
[Fire Original Android Development] k4y0z:
No, I don't think so, could manually flash it using dd though.

This is becoming OT, further questions regarding this should go in the unlock thread.
[Fire Original Android Development] Ziona:
Hey guys can anyone send me a copy of their boot.img an possibly these three file's from -

system/bin/ qp

system/bin/ sdcard

system/bin/ vold

Thanks in advance
[Fire Original Android Development] sandman512:
So, after much trials and issues(and help) I was able to flash this ROM. I have been out of the game for a little while, so excuse the stupid question. There are NO "google apps" installed, so how do I go about installing them again? Once again, thank you!
[Fire Original Android Development] platypoid:
Go to open gapps and download smaller version( nano or micro ) for arm 5.1 ( I think I have that right ) , put it on Fire and flash it using TWRP

https://opengapps.org/
[Fire Original Android Development] ldeveraux:
Why not install 14.1 instead? Did you require external SD card?
[Fire Original Android Development] sandman512:
So, there is an external SD card, but I really don't need it. Can I just download 14.1, wipe and flash. If so, where should I put 14.1 on the device after I DL? Thank you.
[Fire Original Android Development] ldeveraux:
TWRP can see the SD card, so put it on there. Also grab the latest nano opengapps for 7.1, as I had numerous force closes with 5.1. Reboot to TWRP (please tell me you have it installed!) install 14.1, install opengapps, reboot, profit.
[Fire Original Android Development] sandman512:
OK, tried to install lineage and the screen was black. Also tried to install that, that gapps, no luck, it said it's not compatible. Had to back to 12.1
[Fire Original Android Development] Oco:
Did you wipe ALL in TWRP?

---------- Post added at 10:50 PM ---------- Previous post was at 10:44 PM ----------

7.1 Gapps for LOS 14.1
[Fire Original Android Development] sandman512:
No, didn't wipe. Would you mind expanding on what has to be wiped?

I'll try 7.1. Which version? LOS?
[Fire Original Android Development] DB126:
Wipe system first (leaving data intact) if you wish to preserve personal apps/content. On exiting TWRP you should be prompted to wipe cache & dalvik; accept the offer. If that fails you'll need to wipe all partitions except internal storage before updating to LOS 14.1. Also note apps installed under 12.1 may need to be updated. Usually a comprehensive wipe is the best option when jumping between major Android versions.
[Fire Original Android Development] sandman512:
Thank you, that worked. Now I just have to load gaaps.
[Fire Original Android Development] DB126:
LOS is sensitive about loading GAPPS after initial ROM boot. You may have to reflash 14.1 concurrent with your desired Google package (recommend nano). Try an independent flash first; you'll know pretty quickly if things aren't working correctly.
[Fire Original Android Development] sandman512:
Just tried to install nano after ROM, no luck, got an error message.Just tried to install them concurrent, no luck.
[Fire Original Android Development] ldeveraux:
Are you sure the Gapps you're downloading are for ARM (not ARM64), Android 7.1 (not 5.1), and either nano or pico?
[Fire Original Android Development] sandman512:
Success! Thank you. Yes, it was 64.

Quick question, when ever I go to download something in the PLAY STORE, it says, waiting for download and either takes for ever or never downloads?
[Fire Original Android Development] buletini:
Thanks so much ggow! For the first time, the Kindle Fire 5th goes to level 7.1.2. It's a revolution.

But there are some problems:

sd card not recognized; the video does not work on Facebook (Stories), Instagram and Youtube.
[Fire Original Android Development] DB126:
Yep - known defect in recent GApps packages that ensnares low end devices. No good solution other that toggling WiFi or 'flight mode' which often relieves the constipation.
[Fire Original Android Development] Nazo:
Is there any chance 14.1 might have SD card support relatively soon-ish? I really don't want to have to use 12.1 as Android 7.1 has always been many times better for me in just about every single way versus its predecessors and otherwise runs and works just great on the Fire 7, but I really would like to be able to have stuff like my music collection that takes up a good bit of space available.

BTW, is there any particular reason quite a large number of fairly simple and ordinary apps are "unsupported on this device" in the App Store? Just as an example, the Google Assistant basically needs nothing more than an Internet connection and a microphone to function yet still shows up as one of those. (Well, I probably don't really want the Google Assistant on here, but it's an easy to remember and easy to find example of those seemingly random apps that have practically no real requirements to function yet show up as unsupported.)
[Fire Original Android Development] ggow:
I'm just completing a bring up of nougat for the mt8173 platform. Then ill have the same platform for all of the tablet devices i work on. Looking into issues like the sdcard access can then come, I'm sure its fixable.
[Fire Original Android Development] Nazo:
Oh thanks for your work on this. All of this is very much appreciated. It's a convenient cheap little system, but the stock OS is so horrible it's almost physically painful to use.