yashsingh1/xdaforums huggingface dataset:
[Fire TV Android Development] TechVendetta:
There is a lot of confusion there. It has a lot to do with some developers using the wrong terminology. As far as I can tell from the sourcecode, we have an unlocked boot partition only. Things like fastboot require the oem to enable them in the uboot (or derivative bootloader system) on the device. U0 typically loads from chip and controls the very lowest level of hardware setup its essentially the bios. Then the boot image is like your mbr and has your kernel and ramdisk. If we did have fasboot and an unlocked bootloader (as in eng build with fastboot and direct flashing support on chip) then testing would be alot easier and near impossible to brick even when using the mmc device for the rom.

My A-A usb cable is currently in storage but when I find it I'll give it a try but I highly doubt, given the sourcecode of the supposed unlock that any otg flashing, fastboot or engineering flags beyond removing the boot image writelock are actually implemented in the bootloader. And before anyone asks, no I cant straight up write a uboot binary that won't brick on the first try.
[Fire TV Android Development] rbox:
As i've stated many times, including in the OP for the unlock, both fastboot boot and fastboot flash work.
[Fire TV Android Development] TechVendetta:
Thanks for the correction rbox, but isn't there still no hardware way to trigger the fastboot mode? Meaning that you can't effectively use it to test on the boot partition since you wouldnt be able to reboot to the bootloader? Thats one of the reasons I avoided even trying and have been using the recovery partition and usb for storage. If you screw up on partition mapping with the internal storage blocks you would have no way to boot into the bootloader for fastboot. Unless the bootloader has a failsafe fallback in these cases....
[Fire TV Android Development] rbox:
As I've also said many times, having a USB A to A cable plugged in to a computer while the Fire TV is turning on will cause it to stop in fastboot mode.
[Fire TV Android Development] TechVendetta:
Thank you again rbox, I think the issue with this is that myself and the others here just followed the AFTVnews guides to get started which didnt mention any of this. I'm still having issues with wifi and bluetooth bringup and co-exist too by the way. I can get the wifi to start and list AP's but then it resets. And if I instead load the wifi the way CM12 wants us to, it doesn't start at all. I probably need to revise wifi.c but I still only get a couple days a week to go over everything.
[Fire TV Android Development] rbox:
Yeah, I only briefly messed around with the bluetooth. But wifi was working perfectly for me.
[Fire TV Android Development] TechVendetta:
Think it could have to do with USB booting since the ath6kl is USB?
[Fire TV Android Development] rbox:
Doubtful. The bus can handle it, else you wouldn't be able to use wifi and a usb hdd on stock software.
[Fire TV Android Development] TechVendetta:
It's been driving me a bit mad since your original code didnt work for me without removing the Android TV stuff and changing the init files in the ramdisk. And now some builds it works others it doesn't.
[Fire TV Android Development] freezer2k:
When running Fedora on the FireTV, I have the rootFS on a USB stick.

WiFi is being detected, but I never used it, just wired connection.

Not sure if it would make any sense testing how well wifi works there?
[Fire TV Android Development] TechVendetta:
I was tempted to try Ubuntu touch or buildfs if you want to send me a ramdisk and rootfs it could be helpful to see how it handles it. Do you use rboxs kernel config or stock or something entirely different? It seems my issue is upstream lollipop is still changing how WiFi works considering 5.1's changelog. I'm going to strip everything down to core and start piece by piece stepping through things. Something keeps changing when i sync between builds and it needs to be frozen and reverted.
[Fire TV Android Development] freezer2k:
Mostly relying on the work done by Robclark almost a year ago.

kernel: https://github.com/freedreno/kernel-msm/commits/firetv-drm

Wiki: https://github.com/freedreno/freedreno/wiki/FireTV

Android kernel image: http://people.freedesktop.org/~robclark/f20/fire-boot-f20.img

This kernel also works for Fedora21.

You need to extract the image with something like 'abootimg' and edit bootimg.cfg to point to the rootFS on the usb-stick.

For rootFS, I took it from here: https://fedoraproject.org/wiki/Architectures/ARM/F21/Installation

I used Xfce, which was quite snappy: http://ftp-stud.hs-esslingen.de/pub...ges/armhfp/Fedora-Xfce-armhfp-21-5-sda.raw.xz

Make sure to run 'yum update' since it fixes some stuff in recent packages.

Recently he requested a 23.976fps support patch from Qualcomm and I successfully applied and recompiled the kernel above with it. It seems to work (xrandr confirming 23.976hz). See attached pixelclock patch.

Rob also mentioned that the FireTV might use the same wifi part as the ifc6410 device. Maybe we can get working code from there?
[Fire TV Android Development] TechVendetta:
I actually got wifi fully working again last night, if I remember correctly it had to do with socket creation and permissions not sticking. I'm now working on bluetooth which requires a full conversion from bluez to bluedroid. Luckily this is almost fully working upstream so I just need to pull in the fragments and choose a coexist scheme and run some debugs.
[Fire TV Android Development] Jugstah:
Sounds good keep us posted. Do you plan to post testing builds soon?
[Fire TV Android Development] TechVendetta:
Yeah trying to get bluetooth up and pick the best gapps versions for the AndroidTV build. I'll release test builds in the same style as my previous ones while I work on an installer for those on the form list to do some testing of.
[Fire TV Android Development] nijhawank@yahoo.com:
[MENTION=3127756]TechVendetta[/MENTION] now that FireTV boot loader is fully unlocked, can't we load the cm12 boot image using "fastboot boot" command instead of flashing to recovery? That way I won't have to touch / overwrite the recovery and it'd be much safer?

I have the latest pre-rooted rbox rom with boot menu as well fully unlocked boot loader. Also I have data mounted over external usb. I want to play with cm12 but don't want to touch my working setup.

Thank.
[Fire TV Android Development] TechVendetta:
Flashing boot would destroy your working setup, thats where rboxs current loader is. As I've stated a couple times now, when the release candidate is ready there will be an overhauled and unified boot system to load all roms as well as recovery and update management. For now its ridiculously safer to just use recovery partition so you dont have to mess with fastboot and dont have to reflash boot every single time you want to switch between stock and usb.
[Fire TV Android Development] nijhawank@yahoo.com:
I had thought that "fastboot boot" loads and run the boot image completely off the ram and "fastboot flash" is the one that really flashes.
[Fire TV Android Development] TechVendetta:
Ah you meant a one time run! Yes that should work, it you like having to do that every single time. Personally I prefer to boot from my bed, bundled in blankets, because I live in michigan, and it's been as cold as -21F here lately (thats -29C for everyone outside the states).
[Fire TV Android Development] nijhawank@yahoo.com:
Sure I'd like the same way but for some play and testing I would prefer not to flash over my recovery even though I know with bootloader fully unlocked I should face less hurdles in recovering in case of a mess up.

So as per your steps in the opening page, instead of flashing the boot.img to the recovery partition, I just do "fastboot boot boot.img" from my computer.

The other thing I'll have to do is adjust my existing /data partition on usb drive and move it as the last partition. So that the first three partitions are for CM12 and 4th is for external /data when booting normal FireOS.
[Fire TV Android Development] TechVendetta:
If you plan to use the same drive for both yes, p1 is system, p2 is data, p3 is cache, I'll up a more recent build tonight with working wifi.
[Fire TV Android Development] TechVendetta:
Of course don't forget to change your stock boot config in your particular case or data will definitely be killed.
[Fire TV Android Development] nijhawank@yahoo.com:
I didn't understand this. What is this that I have to change?

My plan was this:

1. DD my existing /data partition (/dev/sda1) on the USB drive to /dev/sda4 (last primary partition)

2. Create ext4 filesystems in /dev/sda1, /dev/sda2 and /dev/sda3

3. DD the system.img from your .tar.gz file to /dev/sda1

4. Connect USB to FireTV

5. From the computer execute the command "fastboot boot boot.img" where boot.img is your provided CM12 boot img.

I assume that your boot.img is already fixed to mount /system, /data and /cache from /dev/sda1, /dev/sda2 and /dev/sda3 resp. So CM12 does not touch my /data in /dev/sda4 for FireOS.

And when I boot normally, it'll automatically pick /dev/sda4 because the partition selection is based on UUID and not fixed partition numbers. When I clone /dev/sda1 to /dev/sda4 in step 1 above, UUID is preserved.

Surely I'd have had to change /dev/sda1 to /dev/sda4 if I was not using UUID. Was this what you were referring?

Sorry for bothering you too much but that's the only media system I have and the whole family uses that for daily TV viewing and I can't take the chances to mess up the setup.

So want to get a feel of CM12 without touching the existing setup.

Thanks and appreciate all your work.
[Fire TV Android Development] TechVendetta:
If its uuid based int the boot img mount scripts it should be okay. But when formating the drive make sure the partition numbering matches up. I used direct blocks in my mounts so whatever is sda1 sda2 and sda3 is what will be used. Im compressing the image with working wifi now, still working on bluetooth. This particular image is android tv based which is less stable than the pure CM12 I was previously using but it has working playstore and generally feels better on a tv.
[Fire TV Android Development] nijhawank@yahoo.com:
[MENTION=3127756]TechVendetta[/MENTION], I thought to confirm this with you. It seems that the stock kernel in FireTV (I'm on the rbox latest pre-rooted rom) has swap support enabled. I did a mkswap on a regular file (not partition) and swapon successfully and "free" command showed the swap in it's output. This was kind of surprising that Amazon kept swap support enabled in the kernel. I'm kind of doubting it. Do you think all the right support is enabled in the kernel to actually be able to use swap?

Till now I have been using a microSD with a USB card reader to mount /data to an external drive but I have ordered a self-powered usb hub and I plan to attach a hard-drive. And if the swap is available, I plan to add a swap partition.

Thanks.
[Fire TV Android Development] TechVendetta:
If the memory is displayed under the free command then everything should work. However the FireTV isn't exactly low on memory, and android's built in memory killer will still manage memory. If I remember correctly the memory management will prefer builtin memory over swap memory when deciding how to manage memory since it is much faster than a swap file or swap partition. If making a fourth partition of type swap doesn't automatically get found you may need to make a userinit script to run swapon for the partition, and that should definitely work. Swap support is a standard part of any linux kernel so it really isn't surprising it was on in amazon's stock kernel. I'm not sure if you would really notice much of a speed increase even with multiple background apps however since androids memory management system is pretty fine tuned at this point to handle keeping the memory usage from getting out of control.
[Fire TV Android Development] ahoslc:
Is BT the only thing not working? I can help test more if you would like.
[Fire TV Android Development] TechVendetta:
Audio is probably not working correctly either I have some debugging to do and some code cleaning. If I cant get Bluetooth up reliably i might have to look into backporting bluez.
[Fire TV Android Development] will4958:
On the chance this hasn't already been asked, have you looked into or thought about addressing the screen mirror issue with compatible Android devices? I ask because I have both a Samsung Galaxy S4 and Tab 3 8.0, and both offer screen mirroring. I was able to have a little success using Mirror OP, but the free version is limited, and I wound up getting a black screen after a few minutes if that. My Tab has over 50 games on it, most of them don't offer game pad support, and I was hoping to stream those games from my Tab to the Fire TV. Just curious.
[Fire TV Android Development] E--Man:
TechVendetta,

Thanks for all your hard work on this. I was just wondering (not pressing) when you think think a beta user-friendly flash with basic functionality working (video/bluetooth/audio/etc) might be available for us all to try out?

I know you are hard at work, but I am eager so a ballpark ETA would really be nice.

Let me know, thanks.
[Fire TV Android Development] TechVendetta:
Well the current uploaded one has video and WiFi working AFAIK Bluetooth is driving me mad and cm12 isnt officially stable yet. My goals going forward is Bluetooth, installer app, audio, then bug fixes. Audio is probably relatively easy but Bluetooth is undergoing the most changes upstream so its hard to tell the official way to do it on our chipset. If my latest attempt doesn't work I'll move onto more dirtier ways to do it.
[Fire TV Android Development] kalinskym:
Video of Install on Fire TV

Guys, has anyone got a video they can share of how to install CM12 Android TV on the Fire TV for beginners. I would very much like to install this rom on my Fire TV but I am afraid incase I do something wrong. A brief install description would be very handy, just to get the grasp. :)
[Fire TV Android Development] TechVendetta:
Since you asked I'll start working on the installer tonight since I'm finally off tomorrow.
[Fire TV Android Development] gamer765:
I believe this is not yet meant to be used by everyone. If you do not know how to install this, then this is most certainly not for you. Wait for this to get stable and for easier install steps. You're not the target audience for this ROM yet, sorry.
[Fire TV Android Development] aHcVolle:
Sounds great ;)
[Fire TV Android Development] TechVendetta:
This is a good point, without Bluetooth working you need a USB hub to plug in a keyboard and mouse, and for now it overwrites the recovery partition. I have plans to restore recovery, but they are low priority right now.
[Fire TV Android Development] ahoslc:
Is audio working?
[Fire TV Android Development] kalinskym:
Thank you TechVendetta =) can't wait
[Fire TV Android Development] TechVendetta:
I've been up for entirely too long. But I'm almost done with a very basic installer application. After a bit of testing on my end, I'll send links out to the survey takers for testing. The initial version will be a giant apk with what ever the latest nightly is, fully included in the app. It will overwrite your recovery partition which you can always reflash until I get to the multiboot manager I'm also working on.

The second version of the installer will include flavor selection (Pure CM12 or Android TV) and rom downloading, updating and installer auto update checking. Again everything is very unstable and very little is tested right now since my days off have been scarce lately.

Those links will probably go out in the next day and a half or so since I need to make certain everything functions in it before I send it out.
[Fire TV Android Development] 1el:
TechVendetta,

I am super exited. Thank you so much for your hard work and dedication. I know you go out of your to get a working port.

---------- Post added at 06:07 PM ---------- Previous post was at 06:05 PM ----------

I donated some monies enough for at least a six pack for when you start working on this project again.
[Fire TV Android Development] ahoslc:
Did you get audio going?
[Fire TV Android Development] TechVendetta:
I added the board code and drivers in the build that's compiling now but I think I left out the alsa configs for the socket so probably not just yet.
[Fire TV Android Development] schybiorz:
superb,

can't wait to test. Will it work for install on attached usb drive?
[Fire TV Android Development] TechVendetta:
I'm almost done coding it so here's how it's going to work.

1) Download the very large apk (when it's finished)

2) Plug in a flash drive to the Fire Tv (8gb+ recommended but 4gb should probably work)

3) Sideload the apk (This will probably take awhile)

4) Run apk, accept any root/superuser requests

5) The app will then unpack some stuff into the data partition (The rom files and binaries used for formating)

6) The app also symlinks proc mounts to a mtab file this is just for the ext formating to work

7) Press the Install button and wait as the app reinitializes the flash drives partition table and creates the partitions and write the system image to it.

8) When its all done it will offer to reboot into the flash drive for you.

Note this first version will still use the recovery partition for booting, and unless the last build fixed bluetooth (havent tested it yet) youll still need a usb hub to play with anything via usb keyboard/mouse. Also side note, some flashdrives might not work, this seems to be a known issue with some cheap Chinese drives in general.
[Fire TV Android Development] will4958:
Very cool. For those who have applied one of the many methods to extend the internal storage of their Fire TV, will we have to apply the revert file to go back to the original internal storage, or can we just sideload the apk and proceed as instructed, provided we make a current backup, that is?
[Fire TV Android Development] TechVendetta:
Probably since it flashes file from data to a fresh USB. If you flash a new USB then revert to the patch after you could use rboxs boot menu to boot recovery and swap drives.
[Fire TV Android Development] kalinskym:
Does the .apk when it comes out root the device for me in order to install the rom?
[Fire TV Android Development] aHcVolle:
I think you will have to have root before you can install it, so I think the answer is no.
[Fire TV Android Development] freezer2k:
Yes and it will also cook you dinner
[Fire TV Android Development] retroben:
Something I either forgot to ask or have already asked about...

Will this CM12 also include the latest Qualcomm V@66..0+ driver update so we can get even more of a performance boost?

FireTV is on the crappiest of old drivers known as V@15.0 according to the PPSSPP emulator.

It is the key reason why there is so many issues with the rebooting and other various frustrations like the notoriusly "bad processing levels" slowdown issue.
[Fire TV Android Development] TechVendetta:
No you'll need working root. I never played with stock unrooted and flashing recovery and USB require root.
[Fire TV Android Development] gamer765:
Can you link to said drivers? You got me interested in this.
[Fire TV Android Development] ahoslc:
They won't work unless you bake a rom with them in there.
[Fire TV Android Development] TechVendetta:
I assume you mean the latest drivers available in caf? I'm slowly switching over various hardware drivers to caf, typically when they don't work with the amazon stuff. Ideally I would like to move all of the kernel and drivers over to caf but for now I'm using rbox's modified kernel source since I don't think our board fully aligns with other boards of the same identifier. Once core functions are stable we can get into the nitty gritty.
[Fire TV Android Development] retroben:
It is a rumor that FireTV's hardware is based on Samsung GS4 which would speculate that you need the drivers that go to that specific device in order for it to not go dead.

I hope there is a good newer driver version for that device so it could maybe work on FireTV.

The best hope would be fixes for wrongful lag and a lot of compatibility bugfixes plus full OpenGL ES3 access via Kitkat or newer Android version update.

Edit: I found this topic...

http://xdaforums.com/showpost.php?p=54713752&postcount=164

I hope this can be used in some way. (Please let it actually be usable.)
[Fire TV Android Development] rbox:
The FireTV has nothing to do with Samsung anything... it's based on a reference design for the processor from Qualcomm.
[Fire TV Android Development] retroben:
Then what device's version of the Qualcomm drivers would you recommend?
[Fire TV Android Development] rbox:
flo, which is the Nexus 7 2013, has the same processor.
[Fire TV Android Development] retroben:
*derp*

Could that mean the primary download on the Qualcomm site for Nexus devices might work straight away on FireTV?

Just a guess,be extra safe about it though.

Here is the qualcomm site's page with a download link...

https://developer.qualcomm.com/mobi...le-gaming-graphics-adreno/tools-and-resources

And here is the xda page link I should have posted,I guess...

http://xdaforums.com/showpost.php?p=49878122&postcount=1

The August download is at the bottom of the exact post.

Hope this actually helps instead of being frustrating.
[Fire TV Android Development] rbox:
No clue
[Fire TV Android Development] retroben:
I found a Developers DOT Google page listing various Nexus devices and the "flo" one is marked as

Wi-Fi which makes it more likely to match up with FireTV's case.

The other Nexus 7 is named "deb" and marked as mobile,which I would assume doesn't support wifi.
[Fire TV Android Development] TechVendetta:
wifi has nothing to do with it since thats a different module on the board. As for the installer app debugging is holding me up, I can run the install process from shell fine but running it in app is failing. It's probably something stupid with the way system commands access the shell.
[Fire TV Android Development] retroben:
I wonder if the two were named after finding Nemo's Deb and her imaginary reflection Flo?

It is funny regardless.

As long as we can get a later Qualcomm driver version that is better than the crappily obsolete 15.0 one on FireTV.

I wish you good luck on getting past that buggy installer issue. :)
[Fire TV Android Development] fabi280:
Just take a look at the Codenames of the Nexus devices since Galaxy Nexus

GNex: Maguro (tuna)

N4: Mako (a shark)

N5: Hammerhead (also a shark)

N6: Shamu (the first orca to survive more than 13 months in captivity)

N7 (2012, Wifi): grouper (A fish family that includes sea basses)

N10: mantaray
[Fire TV Android Development] Jugstah:
Any news on this?
[Fire TV Android Development] ldeveraux:
Was anything posted? Then there's no news, prodding the devs just make them angry!
[Fire TV Android Development] retroben:
*prod prod* Oh shiddt!

Only joking,though everything I am interested in has been going REALLY slow lately.

1. Mupen64Plus AE including the GlideN64 plugin.

(not until the damn PC release before any work starts on the Android port.)

2. Various apps that should have updated by now,such as Goat Simulator with some fixes.

3. Cool projects like Tubby Super Cat by Nimso Ny.

I could be forgetting something else I was frustrated about.

I am fine on waiting for this,though I really want it plus the latest Qualcomm driver so Dolphin and Reicast can finally work on FireTV.
[Fire TV Android Development] TechVendetta:
Someone got fired at my job so I've been picking up their hours on top of my freelance work which is why things have been slow lately.
[Fire TV Android Development] danielcbit:
Hi TechVendetta, do you have a git repo where you are pushing you patchs? I'd like to help.
[Fire TV Android Development] citrusfizz:
Really got burned on donating to you and not receiving updates for a month or asking for help. I understand if you don't have the time, but this is a community. Please let people help.
[Fire TV Android Development] ahoslc:
Nobody made you donate the fact is he has a real life as well and has already explained he has picked up extra shifts at work due to somebody getting fired.