yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] shelleyfrank:
Austin 7th gen rom:

A gather that external sdcard write permission is preconfigured in this rom, which is convenient if you don't want the "grant write permission to sdcard" dialog to pop up for every app. However, some apps have issues. In Opera browser when you save a download there is no sdcard option, as in the attached Screenshot included here. Same goes for a backup app I've been using called Apps backup and restore, where the sdcard doesn't show up in storage options.

[Edit] sorry, this is solved by eject and remount.
[Fire Original Android Development] shelleyfrank:
Kind request to developer: Is it possible to build a release with selinux set to enforcing please.
[Fire Original Android Development] ggow:
Just tested the stock camera on the latest build, seems to be fully functional here.
[Fire Original Android Development] ggow:
Fixed... Will be included next release.
[Fire Original Android Development] shelleyfrank:
Thank you for checking but I still get the same issue. I've just done a fresh install from a fresh download, md5 matching. Opened the camera, works fine for back camera, switching over to back camera gives error, can't connect to camera. To make the camera work again I have to clear data on app. As long as I don't switch to back camera everything works fine. I am getting the same error on two tablets as I mentioned before.
[Fire Original Android Development] ggow:
That is strange, I tested multiple times switching between back and front camera and no problems here. Can you post logs and I'll take a look.
[Fire Original Android Development] nirogu325:
Dev needs logs. Use the SysLog app after the error to provide him what he needs.
[Fire Original Android Development] shelleyfrank:
OK, so, I ran the camera app, switch camera to front camera, got the error, closed the dialog and saved this syslog. See attachment.
[Fire Original Android Development] ggow:
Have you installed any apps at all that modify the system frameworks (ie. xposed)?

Something seems to have interfered with the binder process relating to the mediaserver.

Could you try the following method for clean install:

1. Go into TWRP

2. Factory reset

3. Wipe system partition

4. Install ROM zip only

5. Reboot

6. Report back with regards to the camera

Also, is anyone else having similar issues?
[Fire Original Android Development] DB126:
No issue here w/latest build on Ford (5th gen) rocking Xposed and SuperSU 2.82 SR5. Toggled between cameras multiple times.
[Fire Original Android Development] shelleyfrank:
It's no use. Here is what I've done. In TWRP I wiped dalvic/art cache, cache, data, internal storage, system. Formatted data partition by typing yes. Installed los 12 austin only, without open-gaps or anything else, from external sd. Wiped cache and dalvic/art again. Rebooted. Gone through setup, skipping wifi.

OK, so here I am in a nice fresh install. Open camera app, take a picture with back camera. Fine. Take a video clip. Fine. Swap camera to front facing. Error: can't connect to camera.
[Fire Original Android Development] ggow:
Can you send me a full logcat and kernel log of bootup and a logcat including when the camera fails to connect using your clean setup.
[Fire Original Android Development] shelleyfrank:
Attachments are:

1. Syslog from boot-up

2. Syslog shortly after having started camera app and switching to front to produce error.
[Fire Original Android Development] shelleyfrank:
sorry, these ones are no-root. I will send again..
[Fire Original Android Development] shelleyfrank:
1. Syslog boot-up

2. Syslog camera fail.
[Fire Original Android Development] ggow:
That is the strangest behaviour.

There seems to be numerous i2c data transfers failing, resulting in the front camera sensor not being seen.

I honestly at this point do not understand why that might be.

Could it be damaged hardware, damage to the sensor?

I have two fords and two austin's here with both cameras working fine.

I am in the UK and bought all of the devices at different times, so I don't think it's a batch thing.
[Fire Original Android Development] shelleyfrank:
Very strange.

I've got two fords and two Austin here too! Chips! Both cameras are working fine on the fords and both austins have got this bug, even though the tablets were bought separately at different times, the one is an 8gb model and the other a 12gb number.

I'm not a programmer so I'm pretty much in the dark here. Can it be something that was caused during Bootloader unlocking and custom recovery installation? I used the latest scripts by k4y0z.
[Fire Original Android Development] ggow:
I wouldn't have thought the bootloader exploit could cause this, but I could be wrong... @k4y0z what do you think of this issue?

[MENTION=3306735]shelleyfrank[/MENTION] can you remember which version of fireos you started with prior to unlocking?
[Fire Original Android Development] shelleyfrank:
Phew.. The latest version end of May. I can't say exactly, but it was up to date when I applied the hack.

Just to add, I've just tested your nexus rom and I get the same error there. Perhaps I caused damage to the camera somehow, but I find it strange that I could've done it to two tablets in a row. I need to add that the camera is recognised in DevCheck. Open camera says "serious camera error" when switching to front cam.

However, if this can't be solved it it the least of my worries, since I do actually use the tablet as a book reader and I cannot remember when, or if at all, I've taken a selfie with it. 0.3mp is not quite my style. I will keep my eye on this post though. Thanks for your concern.
[Fire Original Android Development] black.kahder:
Rear camera works fine for me on pictures in the stock app. It crashes on movies per previous comments but works in Open Camera.

Front camera works in the stock app, but I just noticed that the image saved is mirrored (left/right flip). I don't know if that's supposed to be that way... I imagine not. This is the same in both Open Camera and the stock app.

---------- Post added at 17:34 ---------- Previous post was at 17:22 ----------

I do have a complaint regarding this ROM, but I don't know if it is worth looking into.

The stock CM/Lineage File Manager app won't run in root mode for me. I imagine that this is because it is incompatible with Magisk, and whatever test it does to determine root capability is Dependent upon SuperSU or Lineage SU. Magisk probably did not exist or was not popular when this app was written.
[Fire Original Android Development] emeister2:
For me BOTH cameras work with Austin and 4-22 release. BACK facing camera fails with 5-24. All tests with stock app.
[Fire Original Android Development] shelleyfrank:
Ok, just out of curiosity, I rolled back one of my austins to kindle stock. Right now I've got Fire OS 5.6.4.0 running on it, and the front camera is working fine. So, NO, there is no damage to the hardware. I was starting to worry that maybe I roasted the circuits when I applied the short...:silly: But it turns out I didn't. So, when I get to flash the cm12 os again, which will be very soon, I will report back about this bug over here. Cheers.

---------- Post added at 12:15 PM ---------- Previous post was at 12:12 PM ----------

Yes, I agree, the 4-22 release has got both cams working. How is it that the BACK facing camera fails in your case and the FRONT facing camera fails in my case? Random.. :confused:
[Fire Original Android Development] shelleyfrank:
OK, so from fire os 5.6.4.0 I'm back in lineage 12 os. Guess what? The front facing camera isn't working. I guess that clarifies things a bit.

Just one more thing when I opened the kindle back cover this morning I accidentally unplugged the back facing camera (circled in red in the attached pic) so when I tested the camera it wasn't working at first, until I replugged it. How daft is that?

This is it for now. I'll probable use the April release for the time being since both cameras do work in that release. Till later cheers.
[Fire Original Android Development] Rortiz2:
In my austin and ford, front camera doesn't work..
[Fire Original Android Development] Reynald0:
I saw the file manager try to detect /system/xbin/su and being removed I think that is why not detect it anymore, I think the default file manager could be fixed in some ways or changed with another OpenSource alternative like this: openintents/filemanager.

About the frontal camera I tried see inside the logs of my device, but I don't see anything strange happening, I tried the frontal camera and it works fine.
[Fire Original Android Development] chimera533:
I'm also having front camera problems. Can you dirty flash from the May release to the April release?
[Fire Original Android Development] tegan1110:
Hey you knowledgeable lot!

I'm close to flashing lineage on my Fire 7 7th gen... (Most downloads done, Ubuntu installed on old laptop for BL Unlock etc etc.) I'm just gathering all the files I'm gonna need for flashing lineage....but struggling a little with gapps... There's loads of different versions of gapps! Is any one in particular recommended for lineage?

TIA!
[Fire Original Android Development] Rortiz2:
arm/5.1/pico
[Fire Original Android Development] DB126:
opengapps.org

arm/5.1/nano (read the pop-up descriptions to decide between nano/pico)
[Fire Original Android Development] chimera533:
To answer my own question, it does seem that you can dirty flash back to the April release (at least for my purposes). I'm only using the Fire to run the Wallpanel app and turn on the screen when the camera detects motion. So far so good and my previous camera problems seem to be fixed.
[Fire Original Android Development] mrbfrank:
Ford USB 2.0 issue

Tested the May release on Ford, Windows 10 does not recognize the tablet as portable storage when plugged into USB 2.0, but works on USB 3.0 port.
[Fire Original Android Development] DB126:
Works fine here; fix your drivers.

Ford | 20190524 | Win10x64b1809 | USB 2.0 & 3.0
[Fire Original Android Development] ggow:
My Austin device is now exibiting the cannot connect to camera issue that some of you were reporting. Will try to fix that before making another release.
[Fire Original Android Development] DragonFire1024:
I think SU comes preinstalled. I know it does in the Fire Nexus ROM. The only thing I had to do was download the SuperSU app. I haven't tried the lineage build on this tablet yet. Both ROMs are based on Lollipop of the same version, 5.1.1.
[Fire Original Android Development] DB126:
- LineageOS has an integrated root manager; enable under developer options

- SuperSU can be flashed if desired but is not required or recommended

- [MENTION=8165603]DragonFire1024[/MENTION]: please do not respond with speculation; hard enough keeping differences between ROMs sorted w/o mudding the waters with unintentional misinformation
[Fire Original Android Development] EtoileLabrie:
[MENTION=5488402]Davey126[/MENTION] Thank you..... so much. Now finally everything is fine. running Lineage 12.1!
[Fire Original Android Development] DragonFire1024:
Just want to clear up, I didn't say to flash SU. Just to have downloaded and installed SuperSU app. There is an option in the settings that asks to respect Android's root option.
[Fire Original Android Development] nirogu325:
Not only that, I've never had an issue with SuperSU in either of my two Fires, not in Lineage, or CM in the past, or Fire Nexus. Yes, no issues whatsoever even in the latest build and I use lots of root apps in both Fire tablets.
[Fire Original Android Development] DB126:
There have been numerous problems reported with recent SuperSU builds v2.80-2.82; v2.79 appears safe) on Lollipop based ROMs including bootloops and device instability. Fortunately, it does not appear the ROMs for this device are impacted as we would certainly have seen more noise in the forums as Play Store updates are automatic for many. I run SuperSU on numerous devices and -have- experienced the problem on one device. Easy fix with TWRP and a recent backup. Not fun at all without these resources.
[Fire Original Android Development] DragonFire1024:
I had one issue, back when those versions came out, on my phone when it had KitKat. It was pre bootloader unlock, and it was and still sometimes is tough to get ride of Kingroot. Most my issues stems from not fully removing a Kingroot root. That aside, I'm most familiar with just using the app and not flashing SU.
[Fire Original Android Development] t3chwizard:
It shouldn't make a difference. Either one should work.
[Fire Original Android Development] NeuromancerInc:
I've found a few issues with this custom ROM but the most annoying one is that when I set the USB computer connection to "Charge only", there is no way to re-enable MTP mode from Settings. When you go to Settings > Storage > Tap on options in top right > USB computer connection, it just shows a popup notification at the bottom of the screen saying "USB is now disconnected".

Thankfully, I found a way to re-enable MTP by entering

setprop sys.usb.config "mtp"

in the Terminal app then selecting the USB option from Settings as normal but it is an issue.

Another issue is related to the lockscreen shortcuts. After setting both lockscreen shortcuts to none, it still shows the Phone icon in the bottom left. It doesn't do anything obviously but it still shows up.

The Buttons section of Settings shows options for a number of irrelevant items considering there is no way for the navbar buttons to wake the device. Same for the number vibration related Settings items.

Not to mention the CyanogenMod related branding still peppered through the ROM.

I know a lot of work has already been put into the ROM and I really appreciate that. I just wanted to make sure these issues were listed.
[Fire Original Android Development] DB126:
Reflects characteristics of generic LineageOS core based on an aging version of Android (and defunct CM) designed to run on a wide variety of devices most of which are phones. Personally I'm happy developer has not invested scarce resources customizing this ROM beyond the essentials required for stable installation/operation on this non-mainstream device. But everyone likes their tea differently.
[Fire Original Android Development] NeuromancerInc:
I'm not demanding anything of ggow and have said how I'm grateful for the work done already. The USB MTP mode issue though is still a problem.
[Fire Original Android Development] steve8x8:
I've installed Lineage 12.1 on a Fire that came with 5.3.1 - and I'm impressed. I can compare this one directly to another device running 5.1.1 - battery life looks like an order of magnitude better, fireOS had been eating battery like crazy even in sleep and airplane mode. Wow. Haven't checked all built-in stuff yet, but couldn't find a single glitch. Trying to enable SU though I made the same mistake as many others: It takes a reboot after changing the setting in DevOptions :/

Next time an upgrade is released, I'll try to get rid of GApps completely - most apps I'm using are old ones, and side-installed, or can be loaded and maintained via FDroid. I presume that would make the install a "fresh" one ...

Thanks [MENTION=5749760]ggow[/MENTION] for your work!
[Fire Original Android Development] ggow:
I'll fix the mtp mode issue in the next release
[Fire Original Android Development] iknight8:
I just got the fire tabletwith 5.4.0.1. Can i unlock the bootloader and remove fire os and install vanilla Android?
[Fire Original Android Development] t3chwizard:
I found there is another odd issue. Occasionally if there already is a persistent notification, the notifications sometimes will get stuck (that's the best I know how to explain it) and the drawer with the quick settings will slide down and cover them but only the latest notification will show even if there are others. Appears to have been fixed after a reboot however so I'm not sure what that could have been. I'll see if the issue persists.
[Fire Original Android Development] yakov116:
Nope there is no way
[Fire Original Android Development] ms372591:
At this time nothing 5.3.2.1 and above can be rooted or unlocked.
[Fire Original Android Development] iknight8:
Damn it... why is the damn tablet even popular than! Craplet needs to disappear.

Can I still install Titanium Backup and remove the bloatware and sideload APKs?

---------- Post added at 04:10 PM ---------- Previous post was at 04:09 PM ----------

Can I downgrade the tablet to that version?
[Fire Original Android Development] t3chwizard:
I don't think downgrading is possible unless you want to brick the device due to the locked BL.
[Fire Original Android Development] iknight8:
How about as far as side loading apps? Like the Play Store, Titanium Backup, etc.
[Fire Original Android Development] Rortiz2:
[MENTION=5749760]ggow[/MENTION] In latest release none of two cameras are working and adb doesn't work too. (austin).
[Fire Original Android Development] chimera533:
Putting this here in case it helps diagnose what's causing the problem. For me, I only have problems when I take the device off the charger. If I keep it on the charger, the camera will always work. The reason I know this is that I'm only using this device as a touch panel to control my home automation. I'm using the WallPanel app which turns on the screen when it sees movement through the camera. Kind of a ghetto motion detector. If I keep the tablet on the charger, it will turn on every time. If I take it off the charger, it will stop waking up after a short time. If I try to open the camera I'll get an error related to the camera. If I restart the device and keep it on the charger it will go back to working all the time.

I have the problem with every ROM I've tried: both the April and May Lineage releases here, the May Fire Nexus release, and the July RC1 Fire OS Revamped release. This is on austin. Not sure if my case is unique but I hope this information helps.
[Fire Original Android Development] tf101crasher:
flashed the latest images with TWRP, the latest 2 images do not seem to work with Amazon Fire 7 5th gen the tablet keeps rebooting

since I used to flash other tablets too, lineage-12.1-20170720-UNOFFICIAL-ford.zip works okay.
[Fire Original Android Development] llamasking:
On my Ford, I dirty flashed from 22 April 2019 to 24 May 2019 with just a cache clearing. The video recording works fine.

Is your bootloader unlocked? It sounds like you're flashing from the old TWRP. Wiping?
[Fire Original Android Development] tf101crasher:
I wiped several times.

TWRP_Fire_2.8.7.0_adb

- lineage-12.1-20190524-UNOFFICIAL-ford.zip / failed

- lineage-12.1-20190416-UNOFFICIAL-ford.zip / failed

- lineage-12.1-20170720-UNOFFICIAL-ford.zip / ok

well I'm fine with the old one since I'm only running some custom application on it anyway.
[Fire Original Android Development] k4y0z:
You're not unlocked.

The new ROMs only work with unlocked bootloader.
[Fire Original Android Development] barcia99:
Anyone having a problem with magisk showing cts profile false on this lineage 12.1 for 5th gen fire. Any help would be appreciated. Thanks
[Fire Original Android Development] llamasking:
Use the MagiskHide Props Config module and spoof the Google Nexus 7 2012 WiFi.

As shown here, it works.
[Fire Original Android Development] barcia99:
Awesome, worked great. Thanks for your help. Still can't get spectrum app to work DFE-1012 error. They suck. Totally off subject can apps be downloaded straight to SD card. Like Google play, etc
[Fire Original Android Development] tamojit_ray:
[MENTION=5749760]ggow[/MENTION] can this rom be ported to FIRE TV STICK 2. It has got same soc.

And does this rom got Widevine L1/L3 support?
[Fire Original Android Development] ggow:
It's a possibility, definitely worth trying.
[Fire Original Android Development] tamojit_ray:
Need help from u. I got some questions.

Does this rom support Widevine L1? If not then how to add it.

How to set the resolution of Fire Stick ?
[Fire Original Android Development] N6ML:
Play Store "Download pending..."

Firstly, thanks to those involved with making these images available!

I'm running the 20190524 builds on a ford and an austin.

In both cases, when I choose to install an app from the Google Play Store, it seems to get stuck in "Download pending...." for several minutes (like about 5 mins), before proceeding and eventually successfully installing the app. Other Android devices on the same WiFi network do not exhibit any delay. Any known issue here? Apologies if I missed something - I did try to search this thread, but didn't find anything.
[Fire Original Android Development] ggow:
The short answer is i don't know. I'm not an expert in cross porting existing ROMs to other devices. All the stuff I do is built from source.
[Fire Original Android Development] FabMue:
I am facing the same "issue" on my ford. I just sticked to it because I am just using a bare minimum of apps on this devices. Anyways, I am open for solutions to test. ;)
[Fire Original Android Development] tamojit_ray:
Can u please create a post writing the full procedure of how to build LOS rom for fire tablet/tv.
[Fire Original Android Development] Rortiz2:
Please don't spam the thread. PM me, I can guide you for port the ROM.

Enviado desde mi Mi A2 mediante Tapatalk
[Fire Original Android Development] tamojit_ray:
I want to build LOS from source as this rom was build. This build is different from other phones custom rom.
[Fire Original Android Development] ggow:
Everything needed to build this ROM is linked in the OP.
[Fire Original Android Development] ggow:
New Build is Up

Dated 30 July 2019

- ASB July 2019 patches (sec. string 2019-07-05)

- System Webview M75 - updated to 75.0.3770.101

- Fixed Keyboard Swype functionality

- Front and rear cameras on ford and austin fixed and tested working
[Fire Original Android Development] Reynald0:
Tried dirty update, and clean flash, cannot mount SD-card.

Inviato dal mio ONEPLUS A5010 utilizzando Tapatalk
[Fire Original Android Development] ggow:
I'll look into this evening.

What filesystem are you using on the sdcard?

Did it work in the previous build?
[Fire Original Android Development] Reynald0:
Hi, it happened with FAT32, I am trying if I can replicate the same with exFAT.

In the previous build FAT32 was mounted ok.

Inviato dal mio ONEPLUS A5010 utilizzando Tapatalk

---------- Post added at 02:15 PM ---------- Previous post was at 02:11 PM ----------

Unfortunately it happens the same, plus the initial language selection dialog is missing on clean install.

Regards.

Inviato dal mio ONEPLUS A5010 utilizzando Tapatalk
[Fire Original Android Development] ggow:
I did a 2 clean installs on austin and ford and the initial language selection came up for me. Very strange. Has anyone else seen this?
[Fire Original Android Development] ggow:
It's working for me taking videos and pictures on both cameras on both austin and ford. Can you post a logcat?
[Fire Original Android Development] ggow:
I think I have found the issue. I will do another release shortly.

I'll set my PC clock forward by a day then we can have a new build early :)
[Fire Original Android Development] FabMue:
Just dirty flashed today's release via twrp on my ford. Seems like everything is working properly (including camera). :)

Will try it on my austin tomorrow.
[Fire Original Android Development] ggow:
New Build is Up

31 July 2019

- Fix external sdcard not mounting correctly

- I tested the fix on both devices

- Moved my PC clock forward a day to get a uniquely dated build out today :)
[Fire Original Android Development] ggow:
[MENTION=8500234]Reynald0[/MENTION]

Let me know if this fixes the issue for you
[Fire Original Android Development] Reynald0:
New build ok ggow, for the language no problem, it is different from old cyanogenmod based, it is just a tap inside settings select language, maybe new.

Thanks ggow

Inviato dal mio ONEPLUS A5010 utilizzando Tapatalk
[Fire Original Android Development] Rortiz2:
[MENTION=5749760]ggow[/MENTION] And camera?? :/

Enviado desde mi Mi A2 mediante Tapatalk
[Fire Original Android Development] ggow:
https://xdaforums.com/showpost.php?p=79985120&postcount=1400