yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] frankslade:
Hi guys !

My son don't want do an hard reset to install Lineage OS 14 so we can stay on 12... but I don't want unlock the "little" FORD to install the last release of 12.

Now we are on april 2018 and I would like install the last 12 before unlock:

lineage-12.1-20181218-UNOFFICIAL-ford.zip

that release are not yet downloadoble from GGOW anrdoidfilehost... there is anyone can upload or send it to me please ?
[Fire Original Android Development] mrmazak:
I might still have this one. I will check. But need [MENTION=5749760]ggow[/MENTION] permission to mirror it he has taken down the original.
[Fire Original Android Development] Kramar111:
[MENTION=1109872]frankslade[/MENTION]

lineage-12.1-20181218-UNOFFICIAL-ford.zip is #1 in folder Ford on androidfilehost from OP
[Fire Original Android Development] frankslade:
[MENTION=5728225]Kramar111[/MENTION]

Yes thanks, but in Italy android file host for this file can't find any mirror to let me download the file...

Do uou have tried to download it ?

---------- Post added at 06:51 PM ---------- Previous post was at 06:50 PM ----------

[/COLOR [MENTION=5728225]Kramar111[/MENTION]

Yes thanks, but in Italy android file host for this file can't find any mirror to let me download the file...

Do uou have tried to download it ?
[Fire Original Android Development] Kramar111:
[MENTION=1109872]frankslade[/MENTION]

Hmm... Yes...

"OOPS!

no mirrors found."

Earlier downloaded without problem
[Fire Original Android Development] DragonFire1024:
If anyone is interested, the new Google Go app, the lighter google app, has a hidden Google Assistant activity. It works on low-ram devices. There are no settings for it, but you can use 'Activity Runner/Manager' to launch the activity. Pretty much full google assistant without the user interface.
[Fire Original Android Development] frankslade:
Thanks to all guys !

lineage-12.1-20181218-UNOFFICIAL-ford downloaded few minutes ago fron androidfilehost canada mirror !!!

Have a good week-end !
[Fire Original Android Development] vanzan:
Forgive me but I can't use the Gmail app....won't work with my Google Account. I presume this is a known issue? Searched the thread for "gmail" and saw nothing though. I did a full wipe and fresh install of the latest austin and gapps 7.1. Made sure I wiped System, data etc.

:edit: I installed the Outlook email app and that works fine so I suppose it doesn't matter! :)
[Fire Original Android Development] nirogu325:
GApps for Android 7.1? This is Lineage 12.1 which is Android 5.1.
[Fire Original Android Development] Nazo:
What's the proper way to root the 12.1 version? I decided I do need access to the MicroSD card, so I backed up my 14.1 (so I can flash the update to it whenever it supports MicroSD) and wiped to do a clean install of 12.1. Of course I enabled the setting in the developer options, but there seems to be no addonsu for 12.1. They have 14.1 on up on the official site and I found a mirror that had 13.0, but nothing for 12.1 so far. I decided to try the old SuperSU addon (took some digging, but it seems some people still use it for some things) and flashed that with no errors, but there is no root access in anything after booting up. If I try to run su in a terminal it says su not found. For lack of a better idea I even tried copying the files from the arm folder of the SuperSU flash zip file into /system/bin and chmod 755 them and when I booted back up the system insisted they didn't exist anyway. (Should it have been armv7?) The interesting thing is that when I flash SuperSU the app to manage it seems to be happy as if everything is properly installed even though still nothing can get root, but when I try any other method the app complains that the su binary needs to be "updated." So it's as if it does see something even though nothing else does.
[Fire Original Android Development] fmc000:
MicroSD works perfectly on 14.1, it seems that you missed a few posts...
[Fire Original Android Development] Nazo:
Would you care to point me to whatever I missed? Nothing I've found in this thread so far seemed to disagree with my own result of it not actually working in 14.1 -- including the author's response to my question.
[Fire Original Android Development] fmc000:
Because you have to look in the 14.1 thread, not in this one.
[Fire Original Android Development] barcia99:
Page 12 in the 14.1 thread boot IMG for the Ford model.

---------- Post added at 09:46 PM ---------- Previous post was at 09:43 PM ----------

Page 11 for the Austin model in 14.1 thread. Both were for SD card fix in 14.1 until ggow rolls it out in the next update.
[Fire Original Android Development] Nazo:
When I have proper Internet again (I'm burning through very limited data right now) I'll dig through that thread and try to figure out how to get SD access working. In the meantime, I'll have to return to my previous question and ask what the proper way is to get proper root access that apps will recognize in the 12.1.
[Fire Original Android Development] DB126:
Flash SuperSU 2.82 SR5 with Lineage. Works fine (everytime).
[Fire Original Android Development] fmc000:
Lineage has integrated root access under developer options, no need to flash anything else. Just enable it and it simply works.
[Fire Original Android Development] DB126:
Correct and generally the preferred solution. Poster says that's not available under DO which can happen if root extension is not included in Lineage build (unlikely) or there is a perceived conflict with a prior root solution. Hence suggestion to use SuperSU 2.82 SR5 which is dead nuts reliable on Android 5.1 base for this device.
[Fire Original Android Development] vanzan:
Oh my God I've been in the wrong thread as well!!!! Didn't even realise there was another thread for the 14.1 Austin.
[Fire Original Android Development] DB126:
Yep - easy to miss as posted in the 'wrong' section (subtopic).
[Fire Original Android Development] Nazo:
Another part that is confusing about it is 14.1 seems to be almost unofficially added. It's on the same link and etc but only one build buried under a ton of 12.1 builds. The implication in my mind at least was that there was no official 14.1 thread yet and it was just based under this one during its early initial release. In fact, many threads start out with one thing and then later change over officially rather than start a new thread. At the time the 14.1 thread didn't seem to be visible when I initially looked in this forum, so I had simply assumed something like that was the case. And yes, you caught me, I didn't go through multiple pages or anything looking for it. I guess there are just a myriad of reasons for the confusion in the end. None of them are really particularly anyone's fault, just the way things often go.

To be clear, I did say I had used the option in developer settings and then tried installing SuperSU with both failing to provide a working su. The curious part is that they seemed to apply properly but then su simply wasn't present. It almost made me wonder if something weird was going on like a fuse mount overriding whatever was physically written to the system partition or something.

Well, moving on, I'm not sure why all that turned into some kind of personal attack before (and just for the record I want to point out that simply saying "here is the solution: [link]" is not only more constructive than just "you're wrong" but it actually saves both parties a lot of time and frustration in the end) I searched through the 14.1 thread and on page 4 (not everyone has the same forum settings btw -- another reason why a post link is better) I found the modified boot image. It does indeed seem to work and I have SD access on my Fire 7 with 14.1 now. As far as I could really determine the only thing other than that that that 14.1 seems to do worse than this 12.1 is longer boot times (no big deal) so I'll go ahead and use that and forego trying to further troubleshoot the rooting issue on 12.1. Though it was a bit roundabout, thanks anyway for the help with that.

(And side note, I'm happy to say that I got my Internet back before I completely used up all my data. Whew. Time to start installing a ton of apps on my Fire 7 and good riddance to that awful FireOS.)
[Fire Original Android Development] fmc000:
The one in developer options works just fine without needing anything else. Just enable and select "apps and adb". If you flashed SuperSU you may have to wipe /system and reflash the ROM.

FWIW I have the 14.1 running on my two Fire devices along with all the Ziona's addons and the boot.IMG that enables the sdcard usage. Both have the built-in root and both work just fine.
[Fire Original Android Development] DB126:
Kinda funny. I have four of these gizmos (well three; one died), all early Fords. Never experienced root drama...native (when available) or SuperSU when I opt for that solution. Not to mention numerous Amazon devices dating back to 2nd gen HD. All rooted. Must have pulled the lucky straw. :rolleyes:

I do enjoy lengthy, finger wagging posts from those seeking assistance. Tata.
[Fire Original Android Development] Marauder0408:
Hello all, I managed to root my Fire 7 2017 and flashed the latest version of Lineage OS 14.1. Unfortunately the front camera wouldn't work so I went to the latest version of 12.1, and still the front camera doesn't work. I read in the thread and there was some previous discussions on this but I didn't see a final solution.

Can any provide some recommendations or a version of 12.1 where the camera works? I just want to use it as a wall mounted tablet with Wallpanel or Fully kiosk browser.

Thanks!
[Fire Original Android Development] ntd252:
I had used the method in this post https://xdaforums.com/amazon-fire/development/unlock-fire-t3899860 to flash the 12.1 ROM 2018 version for my Fire 7 2017. So to flash the Aug 2019 version, do I need to do those steps again? If I don't need to do it, how can I install TWRP for my device? Thank you!
[Fire Original Android Development] platypoid:
if you do the procedure in your link successfully it will install TWRP on your Fire. Then you can install this or other suitable Roms using TWRP which is on your Fire - no need to install it again because it is on there . Just boot to recovery.
[Fire Original Android Development] ntd252:
edit: I press the wrong button, sorry!

----------------------------------------------------

Yes I did the exact procedure and was able to boot to recovery and flash the 2018 ROM version, but now when I try to power off the device, then press volume up + power button, it doesn't boot into recovery. How to check if I installed TWRP? As I see the procedure on that link just "trigger" the device to boot into recovery mode, not sure if it was installed. I just followed the exact steps at that day.
[Fire Original Android Development] platypoid:
You can also use the adb command adb reboot recovery
[Fire Original Android Development] ConnCarl:
Thanks, OP! Nice clean ROM.

Just curious, I did read about the camera issues. I have the 8-23 release running on a Fire 7 5th gen, and there is no selection at all for video. Still camera works fine. Is that expected behavior?
[Fire Original Android Development] danieljawatson:
Ive been having a problem where sometimes when I wake the tablet the brightness dims drastically and even when I bring the brightness all the way up I doesnt get brighter until a reboot. Anyone know why or have a fix? Thanks
[Fire Original Android Development] aarem:
I don't know if this is the correct place to ask this question but I am considering buying an used 7th gen. Amazon Fire HD 8 for $25. I will install LOS. But I was wondering if there is any chance of getting a more recent LOS than 12.1 (I am wondering about something like Nougat or later). Is that in the works, or is it not conceivable in the near future. I ask because the 8th gen. is available from Amazon for $50 right now, both 16GB, but I don't want to support Amazon.
[Fire Original Android Development] TECHNOFAB_11:
Does the Kernel support tap to wake? I would like to use this for my Fire which should go on the wall as a dashboard. But motion detection with a camera and stuff isnt good, so it would be great If there was a way to turn on the screen when the screen is tapped once (or twice, but once would be awesome) :)
[Fire Original Android Development] DB126:
Stock kernel does not support T2W.
[Fire Original Android Development] TECHNOFAB_11:
With stock you mean the Fire 7's stock kernel or the kernel of this ROM? If you mean the one of this ROM, is there a way to get T2W into it myself? Never have done anything like that, but maybe coding exp will suffice. If not, is there any ROM I could flash onto the Fire 7 to get T2W? Idc about the rest, as long as the fully kiosk browser runs on it :)
[Fire Original Android Development] DB126:
To the best of my knowledge the archive does not contain any bootloader/kernel mods. Just an adaptation of Lineage 12.1 leveraging the stock kernel for hardware support.
[Fire Original Android Development] lestatlestat:
not able to sign in google account, no google service framwork id

Hello,

i have succesfully installed the Rom lineage 14.1 austin together with open-gapps nano 7.1.

But when I try to sign in to my google account over the play store app or settings/accounts i get the answer:

"Couldn t sign in, There was a problem communicating with google servers. Try again later."

Then i read about the registration from not official devices over the google registration site.

My problem ist, that I can not find the google framework id. When I try the command "adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db "select * from main where name = "android_id";"' the output is blank.

Also when I try it with the app device id.

Where is my problem? Grateful for any advice.

lestatlestat
[Fire Original Android Development] platypoid:
You maybe want to ask over on the 14.1 forum topic or search over there for answer on past posts - this one is for older 12.1 version.

https://xdaforums.com/amazon-fire/orig-development/rom-lineage-14-1-t3962457
[Fire Original Android Development] Black Swift:
hello! im getting the error 7 on TWRP when flashing lineage 14.1 for austin, im runing a fire 7 7th gen (SRO43KL) and the bootloader is alredy unlocked.
[Fire Original Android Development] Black Swift:
oh thanks.....didnt realized i was on the wrong one
[Fire Original Android Development] mc510:
Play Store problems

Finally bit the bullet and did the new bootloader unlock so that I could switch from Nexus to Lineage 12.1; mostly smooth but I'm having some problems with Play Store. Mind to review what I've done; let me know if I messed up or what? So, after completing the bootloader mod and getting TWRP, I wiped everything including system, then adb pushed Lineage 12.1, gapps pico 5.1, and Magisk zip to the device, then used TWRP to install them one at a time, in the order shown, and then rebooted only after completing installation of all three. So far so good? After going through device setup and Google account login, I'm now ready to install apps from Play Store. First Play Store quit on me a couple of times, then it wanted me to pay for apps that I've already purchased, and now it seems to have settled down but I get stuck at "waiting for download" on everything. I did clear Play Store cache in settings, as suggested elsewhere; no joy. (Oh, and little thing: I've turned off typing sounds in device settings, but Play Store blasts out clicks at full volume.) Advice?
[Fire Original Android Development] platypoid:
maybe try the newer 14.1 ?

https://xdaforums.com/amazon-fire/orig-development/rom-lineage-14-1-t3962457
[Fire Original Android Development] narum:
Hello, today i unlocked my bootloader and installed the new lineageos 14.1 with GApps (ARM | 7.1 | pico). Everything works fine except the youtube apps. I see the preview Images, hear the sound but the Video still keeps black. If i use the browser to watch videos on youtube there is no problem with the video. Do you have an idea how i can fix this problem? Because youtube and youtube Kids was the mainreason to flash this tablet. Kindly regards

//Edit: Found the Solution here: https://xdaforums.com/showpost.php?p=80167249&postcount=26
[Fire Original Android Development] JT1510365:
wrong thread buddy:)
[Fire Original Android Development] mc510:
Yeah; I was hoping to be able to stick to the more mature Lineage 12 ROM, but oh well. Tried Lineage 14 today and Play Store works great on it.
[Fire Original Android Development] SageWilliams:
Hey all,

Having used my Fire in well over a year. Had a 2018 version of this OS on it and used TWRP 3.0.2 to wipe and installed the latest 12.1 version with Pico GaPPs 5.1 ARM but constantly getting bootlooped at the Amazon logo. I can get back to TWRP but not sure what to do. Any advice?
[Fire Original Android Development] Rortiz2:
Hi,

Sounds like you have a locked Fire with 5.0.1 bootloaders.

Are you booting into TWRP tought fastboot?

Regards.
[Fire Original Android Development] SageWilliams:
Yeah I was booting through fastboot
[Fire Original Android Development] barcia99:
Was wondering if you could help me with safety net again. I'm on 14.1rom have props config and busy box by 0smosis module's installed. I know you can spoof with the google nexus 7 WiFi 2012. Per your post. I do that but have both basic integrity and CTS false. Not sure how to turn on improved hiding on. What am I doing wrong. Any help's appreciated
[Fire Original Android Development] llamasking:
I mean, Google might have patched that safety net bypass. I handed off the tablet to my sister and don't have access to it to verify.

Is hardened magiskhide on in Hide Props?
[Fire Original Android Development] barcia99:
Not sure how to check hardened magisk hide on. Thanks
[Fire Original Android Development] llamasking:
Sorry, improved hiding and hardened magisk hide are the same thing. I think the name just changed at some point. It also seems that it was removed as a whole and is just on by default, looking at the settings on my main phone.

You could try tracking down SafetyPatch. That module might be able to get it to work. Props can only really get CTS to pass. If BasicIntegrity isn't passing, it can't help.
[Fire Original Android Development] barcia99:
Cool, thank you for your help. I'll check the safety patch
[Fire Original Android Development] danieljawatson:
Can microg be used on this ROM instead of gapps. I tried the one on magisk but gsmcore was unchecked. I would like to get rid of gapps and use microg so is it possible?
[Fire Original Android Development] Wootrefresh:
I found my Amazon Fire 5th gen 7" tablet that I forgot I had bought and thus, late to the party. It is on 5.0.1 and I used RootJunky's SuperTool to root the device, disable OTA updates, install Google play store, remove lock screen ads and install Nova Launcher. Overzealous, and well, I should have installed a recovery and custom rom after rooting, so I just want to make sure I have everything correct.

I should

1) Fastboot TWRP recovery via Here

2) Unlock bootloader here via Here

3) Flash Lineage-12.1 via TWRP along with latest gapps and supersu.

Is there anything I am missing? I presume I don't need FlashFire since I am still on 5.0.1. Thanks in advance

Edit: My apologies.
[Fire Original Android Development] DB126:
Asking the same question (cut|paste) in multiple threads is considered poor form and will usually result in a non-response. Answer here: https://xdaforums.com/amazon-fire/help/help-thread-question-noob-friendly-t3205441/post81858365
[Fire Original Android Development] blakegriplingph:
Is this stable enough as a daily driver? I'm getting tired of Amazon trying to shove things up my throat and having to manually block them intrusive apps.
[Fire Original Android Development] platypoid:
No way of knowing if it is good enough as your daily driver but you will have zero Amazon stuff if you use this rom .
[Fire Original Android Development] DB126:
Rock solid on Ford/Austin. That said, still constrained by hardware and Lollipop base. Adding a small static swap file (and adjusting swapiness) helps but it will still lag badly at times. 1G RAM (868MB available) just doesn't cut it unless you're a serial single tasker.
[Fire Original Android Development] blakegriplingph:
Yeah I can tell. It works fine from what I can tell, but my only beef is that some apps such as the World Rally Championship app won't work due to Lineage being flagged as an unauthorised ROM. The presence of busybox is seemingly ignored based on the latest RootBeer sources, but test-keys is flagged.
[Fire Original Android Development] blakegriplingph:
Also, the ROM tends to lag with even some basic games and/or apps such as WellieWishers, Asphalt Nitro and WRC, as it appears to be having choppier frame rates compared to stock. Any way to smooth it out besides the swap file?
[Fire Original Android Development] DB126:
Try twiddling LMK values paying particular attention to empty apps. Start with 16/24/32/48/64/128 and tune from there. Don't go too high; you only have 850MB or so to play with. It is unlikely such tweaks will fully address lag and poor frame rates as kernel integration ('drivers') have not been optimized for performance. As is often the case, nothing beats stock if one is looking for performance/reliability/stability.

(waiting for annoying posts from custom ROM fanboys unable to differentiate bloat from core and think the word kernel always prefaces sanders ...)
[Fire Original Android Development] Rortiz2:
Agreed with you. Playing with LMK helped to improve the performance in my austin running LineageOS 12.1. But as you said, if you want a fully-stable/quick ROM you should switch back to FireOS (debloating it obviously).

lol.
[Fire Original Android Development] ajislav:
Can you post your optimal values please? What was the logic behind your adjustments (will depend on your use case, obviously)
[Fire Original Android Development] blakegriplingph:
I can tell lol. Not unless ggow decides to spend more time optimising the kernel and/or drivers even further, which I know is no easy task to pull off.

There are however some instances where the WRC app does smooth up a little as what I can tell with the loading animation - it used to be choppy but now it appears far less laggy. I guess I can live with that for now, short of installing one of those ported ROMs Rortiz is raving about.

Also, hotspot support seems to be either missing or broken. Will that be fixed in a future update, especially as some file-sharing apps need it?
[Fire Original Android Development] DB126:
Hotspot support has never been a thing with Fire ROMs; not sure stock even supports it. I wouldn't get your hopes up (limited interest) unless someone adopts the challenge.
[Fire Original Android Development] blakegriplingph:
Yeah I can see that. I did try another Unity game from 2014 and it did perform well, all things considered, not to mention that I was able to patch out the root check on WRC which allowed me to log in to my live rally racing subscription. As a matter of fact this runs circles over that crappy Verizon tablet my uncle got from his relatives in the states which used a Marvell PXA1L88. Doubt there's even a custom ROM scene around it as there's not much info for said SoC.
[Fire Original Android Development] PianoGuy628:
Hey, so I installed the Amazon Appstore for Android apk a while back, and every time I try to install Minecraft, it keeps failing. All other apps install fine, but Minecraft won't for some reason. If anyone's got a solution it would be greatly appreciated.

---------- Post added at 03:19 AM ---------- Previous post was at 03:17 AM ----------

I can't remember what it was called, but I swear I came across an app in the Play Store that worked, even on the stock Fire OS. I'll have to check to see what it was called though.
[Fire Original Android Development] Copro:
I also need to unlock the bootloader if I am coming from an older Fire Ford running the fastbooted TWRP installed CM 12.1 build from the thread "UNOFFICIAL CM-12.1 22 Nov 2016"