yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] csolanol:
Get 5.0.1 firmware from this post: http://xdaforums.com/showpost.php?p=62986665&postcount=3 and follow [MENTION=4410674]lovejoy777[/MENTION] steps from above post.

The slim 5.1.1 is android 5.1.1, amazon is labeling fireos in the same way. Slim label has nothing to do with fireos one.
[Fire Original Android Development] lovejoy777:
no luck yet on layers, ive added the commits but it breaks everything ?? just get a black screen with back button and notifications, no homescreen or settings. woops
[Fire Original Android Development] StackOverflow13:
Deleted wrong thread
[Fire Original Android Development] Sblood86:
[MENTION=2511007]csolanol[/MENTION] I just wanted to mention I figured out what was causing my initial build issue.

Because y'all have the command to create the dir for KERNEL_OBJ/usr in the vendorsetup.sh it only runs when you source build/envsetup.sh, anytime you run a clean or clobber that dir is deleted and you either have to re-source build/envsetup.sh OR do mkdir manually.

Obviously that shouldn't be necessary to perform a clean build so I'm wondering if it might be safe to move that into one of the makefiles instead?

Edit: the current method also means that if you have the ford device tree in your repo you will always have an out dir created for it when you source build/envsetup.sh even if you are intending to compile for another device.
[Fire Original Android Development] csolanol:
Yup, no problem if it creates the folders before using it.
[Fire Original Android Development] thx1138az:
Kindle Reader app and Play Store

I was able to solve the Kindle Reader app issues and enhanced the app availability in the Google Play Store. The Kindle Reader app is broken because the build.prop file's "ro.product.manufacturer" and the "ro.product.brand" is set to "amazon". Amazon must do this so that we don't "accidentally" use the wrong version of Kindle Reader on their Fire. I used Build Prop Editor by JRummy to edit the the build.prop file. I set the "ro.product.manufacturer" to "asus", the "ro.product.brand" to "google" and the "ro.product.model" to "Nexus 7".

I also used the Market Helper app to get around the "This app is not compatible with this device" for many of the apps I wanted in the Play Store by emulating the the Nexus 7 tablet.

I hope this is helpful.
[Fire Original Android Development] csolanol:
Fixed it in sources but didn't upload a new build. Will do soon.

Commit: https://github.com/csolanol/device_amazon_ford/commit/f34a52a699cab60ddcbb09b29eceeabc727d8e44
[Fire Original Android Development] t3chwizard:
Is 5GHz WiFi not supported by the antenna in the device?
[Fire Original Android Development] csolanol:
Tablet specs says it supports 802.11b/g/n
[Fire Original Android Development] t3chwizard:
Does that mean it does or doesn't?
[Fire Original Android Development] lovejoy777:
lol

edit: i don't know either by the way ??
[Fire Original Android Development] csolanol:
https://en.wikipedia.org/wiki/IEEE_802.11n-2009
[Fire Original Android Development] t3chwizard:
[MENTION=2511007]csolanol[/MENTION] Both my phone and tablet are running SlimLP. It could be a signal range issue due to how cheap the tablet was but I cannot see any 5GHz networks in my neighborhood and my phone detects that there are 2 of them. On top of that in the settings for WiFi there is no option to change the frequency band like there is on my phone. From the link you posted it appears the tablet should support 5GHz networks due to whatever specification that codename means so I am a bit confused.
[Fire Original Android Development] :
I don't think this tablet has 5ghz antenna, I think its only 1 band which is 2.4ghz

---------- Post added at 06:28 PM ---------- Previous post was at 06:24 PM ----------

Nope, check this link https://developer.amazon.com/appsan...ications/01-device-and-feature-specifications
[Fire Original Android Development] fastcar22:
can some please help me, i tried to install CM 12.1 from slim rom using flashfire, i was on amazon 5.1.1 stock rom and now i am stuck with cyanogen mod logo while booting, i cannot go in to recovery using vol-up plus power button it just gets stuck at amazon logon, and when i try vol-down plus power it goes to fastbootmode and i tried several different commands in fastboot but nothing worked. can someone please help me to get back to slimrom?
[Fire Original Android Development] :
I hope someone with a good heart can come along and help.
[Fire Original Android Development] blueberry.sky:
5Ghz is optional in 802.11n / not all wifi n devices will support 5Ghz.
[Fire Original Android Development] nd4spdviper:
I liked it better when this thread was about SlimLP
[Fire Original Android Development] :
Still is a slimlp thread, why?
[Fire Original Android Development] nirogu325:
I think that user got confused with the CM thread which kind of derailed the other day.
[Fire Original Android Development] lovejoy777:
mine is very temperamental at going into recovery too. ive found if i hold power and volume up until i see the a. azon logo, then release it seems to goto recovery every 4/5 attempt. hope this helps as i can't see how you could have just lost stock recovery
[Fire Original Android Development] csolanol:
Op and 2nd post updated. v2.3 is discontinued in favour of official SlimLP sources plus some added features explained in the op.

Using flashfire should work if you come from fireos. No idea if you come from CM...

Enjoy.
[Fire Original Android Development] abacabie:
I used flashfire coming from cm12.1 with this version as i have the locked bootloader , no problems to report, it went silky smooth, just like the rom itself, thank you for doing this.
[Fire Original Android Development] :
Just came from cm and everything seems working great on your beta release. I see you took out theme layer that's good for those using flashfire because a theme that crashes system ui is a softbricks for us on 5.1.1 using flashfire because twrp doesnt work on 5.1.1 and only option for us is flashfire and flashfire doesn't have a recovery that we can go to take out the bad theme causing system ui crashing. Thanks
[Fire Original Android Development] laofan:
I learned the layer issue on v2.3 in a hard way.. Need to reflash fire os 5.1.1 and then root, flashfire everything again.
[Fire Original Android Development] :
You see how bad is theme layer for us on 5.1.1, and people kept telling me to use twrp but that doesnt work for people like us on 5.1.1. So we screwed with the only option returning back to stock and start from scratch
[Fire Original Android Development] t3chwizard:
I also have noticed this. My device will only enter recovery every few attempts. It is very odd but seems to work.

---------- Post added at 10:26 PM ---------- Previous post was at 10:24 PM ----------

[MENTION=4410674]lovejoy777[/MENTION] could you possibly take up the ART optimized builds? I think myself and many others would really appreciate it if these weren't just discontinued.
[Fire Original Android Development] csolanol:
Did u try 0.14?. You should try and test if you notice any performance difference in comparison with v2.3 :)
[Fire Original Android Development] :
I love 0.14 better than v2.3 its less crowed and i tested the speed and what I can say its more speedy than v2.3
[Fire Original Android Development] anselmo884:
Question, can the new beta be dirty flashed over the old 2.3? Or would i have to wipe everything? Runing 2.3 SlimLP flashed over from stock 5.1.1.
[Fire Original Android Development] :
Dirty flashing is when you flash without wiping nothing

Yes you can dirty flash if you pleased but I don't dirty flash I rather wipe everything
[Fire Original Android Development] csolanol:
I recommend clean flashing but you can try doing it dirty. Wipe cache, dalvik cache & system and flash rom + gapps.
[Fire Original Android Development] Bib_x:
I searched some explanations of art optimization, but i still don´t know, what this will do.

Will a rom with art be faster? Will it run smoother? Will it have some more settings? What is the great benefit of art optimization?
[Fire Original Android Development] csolanol:
art is the default vm for LolliPop. You can read some info about the optimizations you are talking about here and here

Basically changes are to build.prop:

dalvik.vm.image-dex2oat-filter=everything

dalvik.vm.dex2oat-filter=everything
[Fire Original Android Development] Bib_x:
Ok, thank you.

So, in theory, a rom with art optimizations should be faster and run smoother? But user experience here in this thread told us the opposite?!

And the advantage of a non-art-rom is, that i can use xposed framework with this new version.

So i will not see any big difference in every day use, if this rom is with art or without it?
[Fire Original Android Development] csolanol:
v2.3 has older sources than 0.14. My recommendation to everyone is to move to 0.14 branch. And yes you can use xposed with 0.14 but do it on your own if you get any issue.
[Fire Original Android Development] bradrel:
v0.14 Version Number

Hello, I flashed version 0.14 over 2.3 (wiped system), however the Slim version shows "Slim-5.1.1.build.2.3-csolanol-20151218" in the About tablet setting. Is this correct or should I start over? --Thanks
[Fire Original Android Development] csolanol:
Something went wrong. It should say Slim-5.1.1-beta.0.14-UNOFFICIAL...
[Fire Original Android Development] Earthsape:
Firstly, many thanks to [MENTION=2511007]csolanol[/MENTION] for the ongoing work on this ROM. I've just been testing Slim-5.1.1-beta.0.14-UNOFFICIAL and hit a problem installing Google Calendar, I've tried over and over again including full wipes and I constantly get a -505 error during installation from the Play store. I've now reverted to Slim-5.1.1-beta.0.13-UNOFFICIAL and Google Calendar has installed fine. Any ideas what could be causing this?
[Fire Original Android Development] x_x1_x:
Is it possible to move apps to SD card, as the stock ROM?
[Fire Original Android Development] blueberry.sky:
Try installing it from apk mirror.

There are apps which will do that for you.
[Fire Original Android Development] anselmo884:
Ok so I went ahead with the dirty flash but was I supposed to flash supersu? I don't seem to have root access and I think its causing all the apps I had moved to my SD card with Link2SD to not appear in the app tray & Play services keeps crashing. Is there a fix to this or should I restore to stock and start over again? Thanks
[Fire Original Android Development] :
I always flash supersu but supposedly slimlp has supersu integrated already. If anything you needed to flash/ROM/supersu.zip/ gapps

---------- Post added at 08:36 AM ---------- Previous post was at 08:30 AM ----------

Any idea How to fix the SD card not showing up after setting dpi? It disappeared and I cant even move apps if its not forcing it to SD card.
[Fire Original Android Development] anselmo884:
I know this question is slightly unrelated to the thread but would using Tom's Supertool be able to root me while on SlimLP 0.14? Or is it time to start over? Lol
[Fire Original Android Development] :
To be honest sometime I forget to add supersu.zip to flashfire and I have no choice to root it with rootjunky supertool and it works great. Open supertool then open amazon 5th generation and wait to it to detect your device then put 7 which is root amazon fire then wait to load and then put 2 which is root fire on 5.1.1 and wait for tablet to reboot and inject root files and to boot normally and boom you have root and a supersu icon on app drawer.... Lol I know I just like to write the steps even though you know already how to
[Fire Original Android Development] gsmyth:
Is it ok to flash this rom coming from stock 5.0.1 firmware? Can I use flash fire to wipe and flash the rom?
[Fire Original Android Development] :
Supposedly flash fire works for those who accepted firmware 5.1.1. And can't use twrp to flash but if you were to flash yeah i think you can 5.1.1 over 5.0.1 but never downgrade firmware or you have a hard bricked tablet
[Fire Original Android Development] csolanol:
If you are con 5.0.1 the best way is use twrp recovery method explained in the op.
[Fire Original Android Development] t3chwizard:
I'll give it a go soon.

[MENTION=2511007]csolanol[/MENTION], theoretically if I wanted to add the ART optimizations all I have to do is change those values in the build.prop?
[Fire Original Android Development] hp420:
so xposed finally works on the newest build, or what?
[Fire Original Android Development] csolanol:
The right version should work on 0.14...
[Fire Original Android Development] csolanol:
I think so, you should reboot and wipe cache and dalvik.
[Fire Original Android Development] :
Lol
[Fire Original Android Development] atayal:
Need new gapps link pls. Anyone have a tutorial for dirty flash?
[Fire Original Android Development] anselmo884:
Not to deter you from trying a dirty flash but I wouldn't recommend it, if you do go ahead with it make sure to flash supersu because I didn't and I didn't have root access plus some really weird app crashes and the play services crashing constantly. It might work for you though. link: http://www.apkmirror.com/apk/google...es-8-4-89-2428711-230-2-android-apk-download/
[Fire Original Android Development] lovejoy777:
i haven't managed a dirty flash yet ? something flips out every time I have tried. the latest going from my build to 0.14 had google services errors which i could sort without a full clean wipe.
[Fire Original Android Development] :
Really need Tutorial for dirty flashing? All you do is flash ROM/supersu.zip/gapps without wiping anything. That's dirty flash. And idk about others but I had root access oafter clean install without flashing su
[Fire Original Android Development] lovejoy777:
awesome work by the way guys. new build running smooth as silk. thanks ? i might resync and try again with layers.
[Fire Original Android Development] anselmo884:
Has anyone gotten the GNL to work on 0.14? I've uninstalled and reinstalled but it won't show up as an option to make a my default launcher...:confused:
[Fire Original Android Development] lovejoy777:
yes, dont dl from ps, i downloaded an old version which worked fine then update on ps. ill find you a link. sec
[Fire Original Android Development] lovejoy777:
[MENTION=7165018]anselmo884[/MENTION] https://www.dropbox.com/s/jxzu1a4cughp7hf/com.google.android.launcher-1.1.0.1167994.apk?dl=0 delete ps version 1st, then install this one, then after setting as default goto "my apps" in ps and update it
[Fire Original Android Development] csolanol:
Guys having problems dirty flashing, are you flashing over 0.13 or over v2.3 and do you use twrp or flashfire?. SuperSU is backed into the flashable zip and shouldn't need to flash it. The right way to dirty flash is wipe cache, dalvik cache and system and flash ROM + gapps. Note that you need gapps mini, not the add-on, only the mini gapps package linked in the op. If you flash the add-on you will get play services fc. There is a video around that show the procces flashing the add-on and it's wrong.

If you come from v2.3 I recommend a clean flash. Too many changes from v2.3 to 0.14.
[Fire Original Android Development] lovejoy777:
[MENTION=2511007]csolanol[/MENTION] i tried exactly as you described, im using flashfire as i got the dreaded upgrade to 5.1.1. in flashfire it only gives me option of "system app data" and not a full system wipe. am i missing something? i was on 0.13
[Fire Original Android Development] anselmo884:
I tried flashing 0.14 over 2.3 the dirty way, and I followed what you told me and I made sure I had the mini gapps(I used the same ones to do a clean flash afterwards it works great) I wiped cache, dalvik cache, and system and then flashed the rom & gapps with flashfire(also made sure wipes went before flashing as for whatever reason the default was to flash then wipe). After I rooted with the supertool and I still kept getting the play services fc so I just clean flashed.:D
[Fire Original Android Development] csolanol:
This is what I see here:

https://www.dropbox.com/s/wwy6b2m48ud02vu/Screenshot_2016-01-10-00-35-41.png?dl=0
[Fire Original Android Development] csolanol:
Maybe coming from v2.3 and flashfire doesn't pair too well [emoji17]
[Fire Original Android Development] lovejoy777:
yep, thats what i got ? just wandered if the pro version had some extra features i was missing.
[Fire Original Android Development] atayal:
is there any other way to get your stuff back onto the tablet, it took me a long time to set it up the way i wanted it.

BTW: I am going to use flashfire (from 2.3) if that changes your thoughts
[Fire Original Android Development] :
Hey [MENTION=2511007]csolanol[/MENTION] can you fix the issue where we select a DPI in display setting and the tablet reboots to take effect but afterwords SD card disappeares and I can move apps to SD because is not showing up. Only option is to force move to SD card. Thanks
[Fire Original Android Development] csolanol:
If you reboot, no soft reboot, SD works again?
[Fire Original Android Development] :
No doesn't work i even started using DPI changer on GP to see if that fixes the problem and the app rewrites the built.prob with the DPI setting I set then I reboot tablet and no change happens so when I go to display setting it shows my default is 200 but really its pointed on 160dpi so when I click on 200dpi the system automatically reboots and then it takes effects but with SD card disappeared I can't do nothing I tried connecting to PC and doesn't show up there neither
[Fire Original Android Development] csolanol:
Not sure if I understand you...

Change DPI from settings, it will soft reboot and SD isn't working. If you reboot again problem still remains?
[Fire Original Android Development] anselmo884:
Well, you can back up your stuff in FlashFire in case something does go wrong, and you can back up your apps and etc. to the Google servers and restore your apps after you clean install. I tried with Flashfire and it didn't work out, it seems as OP told me Flashfire and jumping from 2.3 to 0.14 doesn't work well together.

Option 1: Back up in FlashFire and attempt dirty flash if it fails restore backup, make sure you leave backup on external SD in case something really goes wrong.

Option 2: Clean flash and restore your apps during tablet setup if you have backup your apps to Google.
[Fire Original Android Development] anselmo884:
Trying to enable ART on 0.14

So I'm using Build Prop Editor by JRummy to try and add the two lines to the build prop to enable to ART but what should I put as "Predefined Properties", "Property name", and "Property Value"? Sorry kinda of a noob on modding the build prop lol

BTW: Play Games won't install on 0.14 I get the "-505" error not a big deal but you know? lol
[Fire Original Android Development] :
Omg thank you [MENTION=2511007]csolanol[/MENTION] that full reboot did that trick. Sorry you can discard my other post
[Fire Original Android Development] Earthsape:
Looks like there is a -505 on two apps so far, I have the same issue on Google Calendar, does anyone have any ideas why this is?
[Fire Original Android Development] Avasta:
Google Launcher on Slim Rom

Is there anyway to get google launcher to be the default launcher in slim rom?
[Fire Original Android Development] csolanol:
It's a known issue, cm has it too. Download both apks from apkmirror.com and install them by hand.
[Fire Original Android Development] lovejoy777:
read back a page or two
[Fire Original Android Development] :
You can install google play games off the internet, works great

Recommended, slimlp mini gapps for calendar play,ect
[Fire Original Android Development] Pond-life:
Surely it doesn't come with the rom, isn't it part of G(oogle)Apps, so depending on which Gapps is used will change what's installed.
[Fire Original Android Development] :
Well if you read the first post it says recommended slimlp mini gapps and that's what I used and yes It has google calendar.
[Fire Original Android Development] Pond-life:
That doesn't make it part of the rom so you were still wrong.

Talking of reading, if you tried that you'd see that I wasn't the one that had an issue with calendar, so I've not done anything without reading.

Also one said anything was your fault. You are coming across as quite a tit in that post.
[Fire Original Android Development] :
Well ok ill take the reading part back my bad, now back to ROM

Well nothing of google comes with the ROM I didn't say it did so in what part I was wrong? I said I flashed slimlp mini gapps and it came with calendar so basically being part of the ROM in other words

---------- Post added at 06:04 PM ---------- Previous post was at 05:53 PM ----------

I'm still right, and your thought about me being wrong was wrong.

1) flashing gapps becomes part of system aka ROM

if you factory defaults your tablet you still have the gapps installed why? Because it became part of the rom, duh

2)i never said that calendar comes with ROM or was part of it. thats only if you don't flash the gapps obviously you won't have calendar,playstore, ect.
[Fire Original Android Development] csolanol:
Google calendar isn't part of slim mini gapps.
[Fire Original Android Development] piercecn:
OK in have a quick question. I have 2.3 on my tablet right now and i was thinking about flashing 0.14. Now I have been reading a lot about this flash fire, I still use abd to reboot into recovery, so what is flash fire and do I need it or can I use abd pc connection to reboot into recovery? I have been away for a while trying to get myself updated lol.
[Fire Original Android Development] csolanol:
Use twrp recovery. Flashfire is for people with 5.1.1 firmware who can't boot into twrp.
[Fire Original Android Development] :
Well how come i have it? Only thing I did is flash latest slimlp mini gapps beta
[Fire Original Android Development] csolanol:
Aosp calendar is part of the rom, not google calendar.
[Fire Original Android Development] :
Holly s*** I thought it was google calendar dam it looks alike. Sorry folks i apologize, feel like a d*** now. Hey it still works like a gp calendar same o thing :good:
[Fire Original Android Development] sd_shadow:
if you have the 5.0.1 bootloader, you can boot twrp or use flashfire

Flashfire doesn't require a PC.
[Fire Original Android Development] Earthsape:
Wow, I really didn't mean to put the cat amongst the pigeons over the differences between the built in calendar and Google Calendar, but it is an understandable mistake. [MENTION=2511007]csolanol[/MENTION] you are correct manual install does work fine, thanks for the tip.
[Fire Original Android Development] :
Yeah I been a punk lately ever since my son passaway. My apologies to everyone who reacted over my nonsense. My mind as of now is low forgive me all.:eek:
[Fire Original Android Development] rdfry:
Wow so sorry to hear that. All the best to you.
[Fire Original Android Development] :
Thank you so much [MENTION=625679]rdfry[/MENTION] I didn't expect any replys :)
[Fire Original Android Development] lovejoy777:
[MENTION=2511007]csolanol[/MENTION] im struggling building. i did a full repo sync to a new local folder and now when I make bacon it says "no rule to make target" i tried alsorts, any ideas where im going wrong?
[Fire Original Android Development] csolanol:
Make a clean repo sync from official slim github first and when it's done add the local_manifest.XML and sync again
[Fire Original Android Development] lovejoy777:
mmm thats what i did. it took me 8 hours to sync too as my internet is so slow. the thought of having to do it again ??

??
[Fire Original Android Development] diegocr:
Only remove 2 lines with android_build, sync, . build/envsetup.sh & lunch.

After add csolanol android_build and sync angain.
[Fire Original Android Development] csolanol:
Remove the local_manifest.xml and sync again. Then add it again and resync.
[Fire Original Android Development] lovejoy777:
thanks guys, all sorted. building again at last. i had to remove /. repo/projects/build. git too thanks again Steve
[Fire Original Android Development] csolanol:
Good luck with layers Steve!
[Fire Original Android Development] lovejoy777:
ill get it, in the end ?