yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] shokka9:
Yes, best £34 (Tescos) I've spent in a while.

The ROM seems pretty quick, quicker than the stock offering. I've downloaded some purchases from 2010! Beautiful Widgets Pro, and a few others.

I can't believe I paid for them!
[Fire Original Android Development] Joshmccullough:
Thank you!!! Just ordered one of these on Black Friday, can't wait to get it and make a real Android tablet out of it :)
[Fire Original Android Development] nowseewhatudid:
Just wondering if anyone else has had bootloop after xposed framework install
[Fire Original Android Development] blueberry.sky:
Which xposed files did you install, the xposed-v78-sdk22-arm.zip one? And how did you install, flashfire, recovery?
[Fire Original Android Development] t3chwizard:
Try using Wanam's Xposed. On my phone running SlimLP that was the only one that worked as the regular Xposed caused a bootloop for me. I said this earlier in the thread http://xdaforums.com/showthread.php?p=64040259. Please search the thread next time.
[Fire Original Android Development] blueberry.sky:
That's what I was getting at. But didn't want to assume he used the wrong one.
[Fire Original Android Development] diegocr:
slimlp + ezio mod have some art optimizations, xposed won't work
[Fire Original Android Development] BigMosley:
This ROM is sick! Everything is so much smoother then the stock tablet. The camera not working kinda sucks, not so much for taking pictures but to scan barcodes in MyFitnessPal, fingers crossed getting the camera to work is achievable ? Awesome work thus far!

EDIT: I'm an idiot, the camera works in the MFP app, just not the stock. ?
[Fire Original Android Development] t3chwizard:
Bluetooth bug was fixed today so hopefully more fixes are to come.
[Fire Original Android Development] BigMosley:
Yup I saw that and can also confirm it works ? my Fitbit thanks you.
[Fire Original Android Development] SageWilliams:
Does Multiuser work on Slim?
[Fire Original Android Development] blueberry.sky:
I'd like multiuser as well.
[Fire Original Android Development] Pond-life:
Weird thing for it to do, they still worked though?
[Fire Original Android Development] Coslaw:
Not able to move apps to sd card...

So far this rom is running fantastic, my only issue is that I am unable to move apps to my sd card, it says "Couldn't move app. Not enough storage space", though it is a clean 32 gbs. Due to the tablet having low internal storage as it is, not being able to store apps on it makes the tablet kind of limiting. Is anyone else having this issue?
[Fire Original Android Development] Chief_Nodnarb:
I'm a little late to the party but I just picked up 2 of these tablets. First thing I did was backup stock via TWRP and flashed this ROM. So far so good. Nice work [MENTION=2511007]csolanol[/MENTION], keep up the awesome work.
[Fire Original Android Development] laofan:
Try use "Link2SD" or other similar apps to move your apps.

The limit here is your search ability, not tablet here. No offense but it is a XDA rule to search before ask .
[Fire Original Android Development] Coslaw:
Well to be fair good sir, I did try that, even if the app moves over with the app, it will not lower the amount of storage on the internal memory.... I was just asking if other have this issue.

---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------

Well to be fair good sir, I did try that, even if the app moves over with the app, it will not lower the amount of storage on the internal memory.... I was just asking if other have this issue.
[Fire Original Android Development] t3chwizard:
You can use this app instead of paying for Link2SD. It has all the features in it and it is free https://play.google.com/store/apps/details?id=in.co.pricealert.apps2sd. I set it up and use it and it works great. If it happens to tell you that the mount script didn't work on boot what I have found to work is to wipe the data of the app and then open it again then restore the backup of the database when it asks and then open the link apps menu and it will ask me to specify the partition filesystem etc.... Works great for me.
[Fire Original Android Development] andynx1:
[MENTION=2511007]csolanol[/MENTION] Don't know if you celebrate Christmas, but if you do - I hope it's fantastic!

We've given my daughter a Fire tablet for Christmas, with your ROM. Its performing flawlessly, and it is her favourite gift.

Thank you!
[Fire Original Android Development] Katschunga:
Meanwhile I switched to CM.

At first I had the same brightness bug. In the second or third post of the CM thread there is a FAQ which addresses this issue. You have to install a specific app to change brightness. This somehow activates the systems brightness settings and you can uninstall the app thereafter.

Maybe this helps if someone has a similar issue.

The latest kindle app is working flawless on CM. No need to install kindle 4.2

I realised that the device name in the not working kindle app is "fire". In version 4.2 it's simply something like "android device".

On CM the device name in the latest kindle release also is "android device". Perhaps this is a hint to find the bug in SlimLP.

Though I have to say SlimLP to me seems to run a bit faster and smoother than CM. If the kindle problem gets solved sometime I think I'm going to change back.
[Fire Original Android Development] csolanol:
We are on winter holidays spending time with family. Thanks for the report, will look into it.
[Fire Original Android Development] Katschunga:
There's no hurry!

Happy holidays!

Gesendet von meinem KFFOWI mit Tapatalk
[Fire Original Android Development] t3chwizard:
This ROM is amazing.
[Fire Original Android Development] rummyPPG:
Hi,

I flashed CM 12.1 first with FlashFire but am having issues with gapps size and system partition there. Wanted to try SlimLP instead, but when trying to use FlashFire on CM to install SlimLP it goes through the process but CM stays installed. Anyone successfully went from CM 12.1 (via FlashFire) to this ROM?

Thanks,

\Peter
[Fire Original Android Development] Chief_Nodnarb:
Are we able to safely use stock recovery to wipe and start again or will this mess things up?
[Fire Original Android Development] sd_shadow:
not a good plan,

factory reset just wipes data,

Rom will be the same
[Fire Original Android Development] Pond-life:
Yeah was one of the first things done, so it was an older version of CM admittedly.

You will still have similar GApps size issues though.

http://xdaforums.com/showpost.php?p=64286367&postcount=2
[Fire Original Android Development] OscarDiggs:
Big thanks to everyone involved. Your work is greatly appreciated.
[Fire Original Android Development] switchy85:
Didn't see this anywhere in the thread yet, but has anyone else had an issue with the softkeys disappearing each reboot? I can go into settings and disable, then re-enable them again, but was wondering if anyone elsenbhad it happen. Probably going to re-flash the rom to see if that helps
[Fire Original Android Development] rummyPPG:
Yeah, it was just once I had CM 12.1 I couldn't do anything; overlay smaller gapps, install slimlp, etc. it all wouldn't work. I ended up restoring the stock firmware (from here: http://www.amazon.com/gp/help/customer/display.html/ref=hp_left_v4_sib?ie=UTF8&nodeId=201830180, be sure its 5.1.1 so it doesn't brick device), re-rooting, and then using flashfire to put on slimlp, which worked with the gapps package recommended.
[Fire Original Android Development] nirogu325:
Kinda weird to see brightness and navigation soft-key buttons bug reports. I have two tablets with the latest SlimLP ROM version without any of those issues. Installed on both tablets ever since release day. Only thing I did was not upgrading to the latest Amazon firmware, then I used TWRP to clean flash everything. I don't even use Xposed Framework. Zero issues, not even random reboots. I don't know but something tells me FlashFire is not a safe route to have a bug-free custom ROM.
[Fire Original Android Development] csolanol:
I agree but there isn't any alternative way to flash custom ROMs for people with 5.1.1 firmware :(
[Fire Original Android Development] nirogu325:
Yeah, hopefully some progress is made soon for this group of people :fingers-crossed:. By progress I mean perhaps an unlocked bootloader or a means of making Fastboot work as before.
[Fire Original Android Development] sd_shadow:
I think it's an issue with 5.1.1 stock, not flashfire, i'm just using flashfire without issues with 5.0.1 stock
[Fire Original Android Development] t3chwizard:
I'm using the 2.3 build with the ART optimizations and I am not experiencing this issue.
[Fire Original Android Development] psychoTR2:
Same here. I'm using the same build, and have nothing but good to say about it!
[Fire Original Android Development] laofan:
I blocked OTA but somehow my fire was forced upgraded to 5.1.1.

That leaves me no choice but flashfire the SlimLP v2.3.

I have yet run into any issues. Brightness slider works right out of box. Soft keys are always there.

For records I did clean install.

So maybe issues are not from flahfire.
[Fire Original Android Development] blueberry.sky:
Which method did you use to block OTA?
[Fire Original Android Development] enigma27:
Can anyone help me out?

Rooted my Amazon fire 7 last night and then installed Flash fire and then flashed this rom + Mini Addons package + Mini Gapps package and once flashed the device is just looping the initial android set-up of optimizing apps.

cant seem to get it out of this look.
[Fire Original Android Development] KennBr:
I installed the 2.2b build from FlashFire on the 5.1.1 firmware. Only issue I have had is with the notifications. Sometimes when a download completes, and it notifies me it does so constantly, but then if I click it it says it's disabling heads up display for 5 minutes and it stops.

I love how fast it is. I tried installing Xposed today though and found out that doesn't work on this version...

Question though, if I disabled the lines in build.prop that enable the optimizations will xposed work, or do I need to install the new Roman entirely? Just asking because I don't actually need xposed at all.
[Fire Original Android Development] csolanol:
You can test it. Btw there is a build without art optimizations in 4th post.
[Fire Original Android Development] York_21:
Mirror? I can't download from androidfilehost from work.

Also, I can't wait to try Slim on Ford
[Fire Original Android Development] sd_shadow:
Over stock 5.1.1?

Can you get to stock recovery?
[Fire Original Android Development] York_21:
Can I flash open gapps?
[Fire Original Android Development] sd_shadow:
Yes just not full stock, try Mico or Pico
[Fire Original Android Development] York_21:
That worked a lot.

Thanks dude!
[Fire Original Android Development] laofan:
I use the rootjunkie tool box. There is a option to disable OTA in stock fire system.

Either I screwed up something, or my fire is screwed...

Make sure you select wipe system, data, cache and dalivk cache at the very first.

Then select install the rom and Gapps.

I don't know the add-on here so I didn't flash. And usually it is not a necessary procedure.

I personally like Pico gapps over mini gapps. But since you are new to this, you should use mini games like OP suggested.
[Fire Original Android Development] csolanol:
Don't flash multidpi add-on or you will get problems with play services.
[Fire Original Android Development] nirogu325:
By the way, I don't know if you've noticed but the RAM management is sometimes quite aggressive. Spotify sometimes can't survive in the background and I see redraws even in a light launcher as Nova Launcher. Not even my 512MB RAM Galaxy S1 does that...at least not as frequent. Any idea? I just have the build.prop lines you suggested for the ART optimization.
[Fire Original Android Development] laofan:
Little warning for those who like to play "clock and date" setting : please leave the "date position " alone.

If you change to "right of line". System UI would FC. And your only choice is factory reset (5.1firmeware) or reflash.

[MENTION=2511007]csolanol[/MENTION] this is minor issue. Won't bother others if they don't play with the settings . Just wanted to let you know as well.
[Fire Original Android Development] BurningKoala:
I'm on the 2.3 and I get some strange moving pattern on the display in some occasions....for example going on theverge, while the images are still loading there's something strange going on in the colored boxes, anyone else?
[Fire Original Android Development] laofan:
I use chrome to browse theverge, all seems OK. Have Not noticed the pattern you mentioned even on other websites.
[Fire Original Android Development] toadlife:
Bluetooth Wiimote fix?

Would it be possible to fix the bluetooth so that Wii Remotes can be paired? I didn't realize that Google added some security in their bluetooth stack around 4.3 that made pairing Wiimotes and other bluetooth devices impossible. I've read that some custom ROMs have this fixed.

Thanks.
[Fire Original Android Development] blueberry.sky:
Do you have a link to more information on this and/or a link to the fix that other roms have implemented. We are currently stuck with the amazon kernel so if the fix requires a modified kernel then it may not be possible until/unless we get kexec working (Fire kexec thread).
[Fire Original Android Development] lovejoy777:
hi, nice rom. if i want to build without ezios optimisations, which repos do i need?
[Fire Original Android Development] Vlasp:
Hey, nice to see you joined us from the original Kindle Fire! I think in the third post there are instructions on how to build the ROM, just remove the ezio lines.
[Fire Original Android Development] toadlife:
It does require kernel modification. Here is a link to the CM code review.

http://review.cyanogenmod.org/#/c/89843/
[Fire Original Android Development] lovejoy777:
ok i followed the instructions from post 3 and checked all commits added to all repos and cant find ezio mods anywhere, which repos have these mods added and where? cheers steve
[Fire Original Android Development] sd_shadow:
http://xdaforums.com/showthread.php?p=63986627
[Fire Original Android Development] lovejoy777:
thanks [MENTION=4267571]sd_shadow[/MENTION] , nice seeing you over here. im just getting things setup on my build enviro. im nearly done building this rom just to make sure everything is correct before i start something of my own.
[Fire Original Android Development] sd_shadow:
[MENTION=2511007]csolanol[/MENTION] & [MENTION=4375260]diegocr[/MENTION] may not be using ezio mods still, think they stopped because it had not been updated in sometime.
[Fire Original Android Development] lovejoy777:
thanks i have been intouch with ezio as i have him on hangouts, he has pointed me to all his optimisations and commits ill check if there added, ill be able to sort layers with full compat too as im one of the app devs for that project :)
[Fire Original Android Development] csolanol:
Hi [MENTION=4410674]lovejoy777[/MENTION], you only need to sync slim official lp5.1 sources and add ezio's local manifest from here https://github.com/ezio84/scripts/blob/lp5.1/My_mods-commits_and_tips/local_manifest_backup/local_manifest.xml.

You can get the device tree for this device from my github: https://github.com/csolanol/device_amazon_ford

Btw in 3th post we used official slim sources, forked some projects and added most of the features that ezio added to his github but the ones that doesn't take care of this device like telephony ones.

Tested layers 2.1 commits from ezio too but looks like this device and screen don't like it too much. I know you from bitsyko community and layers app development so would be awesome if you get layers engine fully working.

If I can help you in any way just hit me here or hangouts (csolano at gmail).
[Fire Original Android Development] lovejoy777:
will do ? and thanks for all your work. I'm new to this device. only just got it 2 days ago. i still develop for the kindle fire 1st gen (otterx) but i think that's coming to an end as the new versions of android just don't work right on a 512mb ram we have, marshmallow is working fine but so so laggy its not usable ? so here i am just starting with ford ? ill see what i can do and keep you posted. thanks again. steve.

ps. i tried your other build with out ezios stuff but after boot i had google issues with not being able to install aps. it was a clean install with slim mini gapps (same package i used on build 2.3) i tried several times but had the same issue, reinstalled 2.3 and all works good again.
[Fire Original Android Development] csolanol:
Yup, we are having problems with play store and app compatibility. We are on holidays now and will get back to work in the rom next week.
[Fire Original Android Development] lovejoy777:
nice, enjoy your holidays ?? new year will be here in 7.5 hours, so its party time here ???????
[Fire Original Android Development] Hedied4me:
Sorry if this is a bad question to ask but im just now realizing this. Since ezios is built into this rom does that mean xposed will not work in all future updates? Thanks

sent from my CDMA Virgin Mobile Motor G3
[Fire Original Android Development] sd_shadow:
as of the 21st of Dec, xposed should work

http://xdaforums.com/showthread.php?p=64417348
[Fire Original Android Development] Sblood86:
So I was attempting to follow the steps in [MENTION=4375260]diegocr[/MENTION]'s post to compile this and I'm getting an error, wondering if anyone has a solution (my device troubleshooting is terribad).

http://pastebin.com/feeVVYPz
[Fire Original Android Development] lovejoy777:
[MENTION=3973140]Sblood86[/MENTION] have you pulled the device files from device?

cd into device/amazon/ford and run. . /exract-files.sh
[Fire Original Android Development] lovejoy777:
maybe try syncing again, just repo sync again incase you have some..missing files
[Fire Original Android Development] toadlife:
The default DPI setting of 160 causes notifications to not show up correctly when you pull down the status bar. They show up perfectly at 180 DPI. In fact, everything seems better at 180.
[Fire Original Android Development] Sblood86:
yep, standard step in compiling iirc

I've done it a couple times to make sure I wasn't somehow losing my mind or something lol. Just for a laugh let's see how complicated I can make this though :p

I'm building on a server instead of my local box so what I had been doing was cding into the device directory on my local box, running extract-files.sh on the device, cding over to the new vendor directory, tar balling the ford directory and copying it to my server using scp then on the server untarring the ford dir in place in the repo.

Just now as another "sanity" check I went ahead and mounted my home directory on the server using sshfs on my local box, cd'ed(? or whatever the past tense of cd is :p) and ran the extract-files.sh script on the server so that the files were extracted directly into the vendor dir on the server instead of being moved after the fact in a tarball (incidentally don't do that, adb pulling files to a server over sshfs is slow lol).

Same issue in either case.

Yep, done that a bunch of times also at this point lol
[Fire Original Android Development] lovejoy777:
what java version?

edit: stupid question :) as the build would have pulled that up ? sorry im nearly p&#*ed ??
[Fire Original Android Development] Sblood86:
1.7, I've compiled for other devices on this machine it's an android build server that several of us use lol.

You know what's funny though, I'm running into a similar issue if I try to compile cm-12 (different file missing but similar none the less); the crazy part though is if I take the slim device tree, change a few things to make it build cm it will compile just fine in the cm-12.1 repo, it boots most of the way up and loops right after setting up all the apps (not insanely surprising I'm sure there's a few things in the slim device setup that would break cm). The point is I can build some form of rom for the device on this machine so I don't think it's the machine config itself lol.
[Fire Original Android Development] lovejoy777:
ok my build compiled fine. thanks, its running sweet i'll now look into the layers issue
[Fire Original Android Development] csolanol:
Uploaded some commits a few days ago and didn't test. Will look into it soon. Sorry.
[Fire Original Android Development] lovejoy777:
strange though, i only synced yesterday morning and it built fine
[Fire Original Android Development] diegocr:
Try mkdir dir before compile

mkdir out/target/product/ford/obj/KERNEL_OBJ/usr -p
[Fire Original Android Development] Sblood86:
Why didn't I think of that lol, I just used the same solution for a non-android C++ project not even 2 days ago....

Thanks!

[MENTION=2511007]csolanol[/MENTION] looks like [MENTION=4375260]diegocr[/MENTION] solved the issue I was having, I'll let y'all know if I have any other issues (build is running for now).

edit: built fine and works, thanks again
[Fire Original Android Development] lovejoy777:
just trying a build with some extra layers commits added i'll keep you posted
[Fire Original Android Development] t3chwizard:
[MENTION=4410674]lovejoy777[/MENTION] perhaps we have encountered each other once before here on XDA? Lol
[Fire Original Android Development] t3chwizard:
Good to see ya pal
[Fire Original Android Development] csolanol:
Are you building from my repos or ezio's ones?
[Fire Original Android Development] lovejoy777:
yours
[Fire Original Android Development] lovejoy777:
well i forked frameworks and settings to my github and am now using them
[Fire Original Android Development] lovejoy777:
internet is so slow im struggling to sync source ??
[Fire Original Android Development] BR3W CITY:
So somehow I didn't even make it past step 1. I literally did the vol+power thing to get into fastboot, and now its just stuck there. Has the =>Fastboot Mode.... then nothing. Any combo of buttons or inputs has no effect. Do I just need to let the battery run out or?
[Fire Original Android Development] lovejoy777:
long hold power for 30 seconds
[Fire Original Android Development] sd_shadow:
do not let battery run out

boot the recovery with fastboot.exe

or hold power button until it powers off

---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------

Steps are not numbered in op, so what are you calling step 1?
[Fire Original Android Development] BR3W CITY:
Sorry meant step 1 as actually getting into the recovery. I reopened the device with fastboot and it took the command. I was improperly using the fastboot commands I believe. Thanks.
[Fire Original Android Development] csolanol:
Long press power button until it power off.
[Fire Original Android Development] BR3W CITY:
csolanol, thats what freaked me out. I swear I sat there for 1:45 holding the button to no avail. I also realized that my USB drivers were causing an issue (was plugged in thru usb via my onboard slots on keyboard instead of direct to case). I plugged into the other slots, it recognized the device, and I was then able to get fastboot.exe to function.

However, even after going back and making sure I had all the adb/drivers/stuff installed from the all-in-one tool, I see that my : adb devices only returns a blank result (yet device mngr shows the fire).

I went from almost daily device flashing 5+ years ago, and have reverted into a complete n00b.
[Fire Original Android Development] BR3W CITY:
Got pretty much everything figured out in terms of the fastboot functions, mounting etc. I just want to make sure that since my device is still 5.0.1; if I try to restore to factory, will it go back to 5.0.1, or will it go to 5.1.1? The SlimFord files are labeled 5.1.1, hence my curiosity.
[Fire Original Android Development] lovejoy777:
[MENTION=2285339]BR3W CITY[/MENTION] just get a 5.0.1 factory image and boot into stock recovery (power and vol down) , choose (apply update from adb) , type (adb sideload </path to 5.0.1/firmware/here ) into terminal and press enter