yashsingh1/xdaforums huggingface dataset:
[Fire TV Q&A, Help & Troubleshooting] davekaz:
Fantastic rbox. Can't wait for your genius to take over and make the fire a more pleasurable experience
[Fire TV Q&A, Help & Troubleshooting] KLit75:
I like the fact that he's sharing his progress. Bought another aftv last nite and rooted it. Maybe I'm just paranoid but I have a feeling once this becomes reality they maybe harder to find with rootable firmware. Rbox's work on cm was most of my motivation for purchasing the 2nd unit.
[Fire TV Q&A, Help & Troubleshooting] LittleBear1981:
Thanks rbox! We are patiently waiting. Greatly appreciate the updates on progress. :) I look forward to being able to run Lollipop on all my devices.

Edit:

I pledge 25$ USD to rbox for his hard work on cm12 for aftv!

Thank you so much..

I understand that you do this for fun.. And I would like to encourage you.. Lol. Willing to alpha test for the rest of us too.

Thanks Again. Happy holidays
[Fire TV Q&A, Help & Troubleshooting] jmerrilljr2:
I'm up to date with all the pre-rooted firmware, etc. but I'm not really an Android person. The Fire TV was my first such device. So I'm wondering how this rom will enhance the AFTV experience other than better compatibility with the Google store. Any downsides? I'm just curious, not critical. I will try this right away as I have a rooted backup available.
[Fire TV Q&A, Help & Troubleshooting] mcsephoenix:
This would be comparable to loading Linux vs Windows on a PC. You would be changing the whole base operating system to something that is open source...
[Fire TV Q&A, Help & Troubleshooting] mjbxx:
The only real downside to a possible [MENTION=3991724]rbox[/MENTION] ROM would be losing access to Amazon Prime content and not sure I am comfortable with that as it is quite popular with my family. It would be great to move forward with the ROM and still have access to Amazon Prime if and or when it becomes available. Perhaps Android TV will some day be able to support an official Amazon app.
[Fire TV Q&A, Help & Troubleshooting] 1el:
Great work RBox! You are a hero to many of us. You dedication to this lollipop port is really amazing. I appreciate and enjoy your frequent updates so thank you for keeping us posted. I think you haven't really advertise donations, but you really should put a donation "button" so we can show our appreciation and respect for your uncounted hours of labor. I myself set a recurring $5 donation for a the few months and I know many other have donated as well. You deserve all and more. Keep up the good work and thank you a million for your efforts.
[Fire TV Q&A, Help & Troubleshooting] rbox:
I managed to get the android system talking to the sound driver, after "fixing" Amazon's creative nature... Still getting some failures but I have a log from the stock software of what it's supposed to look like, so hopefully I can figure it out. As for donations, there is a donate button in the sidebar on my posts. I don't like to make a big deal out of donations. If people want to, great. If not, that's fine too. I do appreciate everyone who does though. It's a nice reminder people care.
[Fire TV Q&A, Help & Troubleshooting] KLit75:
I think the trade off would be well worth it. Aftv is a great piece of hardware, but I find fire os to be really buggy. For all my xbmc devices, my family still prefers watching Netflix on atv2. So I've got 4 out of 5 hdmi slots filled on the living room TV.

Not that I care what people purchase and choose what devices to use, but if I were you I'd consider a fire tv stick to run on the side of aftv running Android TV. You get the prime you want, which doesn't need root so the stick will suffice, and you get the fire interface your family is probably comfortable with. 39.99 I think and would be surprised if it doesn't go on sale again.
[Fire TV Q&A, Help & Troubleshooting] 1el:
Quick question(s). Is it possible to modified the Android TV launcher to work with FireOS? what are the main problems with this approach?

---------- Post added at 03:40 PM ---------- Previous post was at 03:37 PM ----------

Never mind. Someone pointed out that the luncher will only work on 4.4 based roms. Since FireOS is based on 4.2 is a no go. Bummer!!!!!!!!!!!!
[Fire TV Q&A, Help & Troubleshooting] Y314K:
Opened/Setup my first of two FireTV Sticks to lend to a friend last night. Got it setup for them with Netflix, ESPN, ShowTime, TVMC & a few other apps.. I was pleasantly surprise how well the FireTV Stick did... It is slower then the FireTV but still very responsive. I could even see my self using it in an UnRooted state not only as backup. Definitely better then the ChromeCast. Will let another friend borrow the other one. I am letting the FW update for now. Might as well.
[Fire TV Q&A, Help & Troubleshooting] LittleBear1981:
Hi.. A little off topic just wondering if anyone else saw this page. Prime on AFTV?

http://chromakode.com/post/amazon-...ead covering this. Kindly post a link. Thanks
[Fire TV Q&A, Help & Troubleshooting] LittleBear1981:
Yeah I saw that its for phones, and require you to install two more apps. Specifically the amazon shop app for Phones. Its hit or miss anyway from what I read. It must have at least 4.4.4 too.

I just thought that since I have access to prime.. I may as well try an use it once lollipop is out.

I am not a fan of the current firmware. Mine is rooted and that's it.. Lol. But it has not been online or in use since I got it. I do like my Netflix though and I am certain it will work on 5.0.x

I look forward to being able to install it someday! :)

Thanks Rbox
[Fire TV Q&A, Help & Troubleshooting] patt2k:
on kodi forums there are some work arounds for xbmc/kodi etc.. but it requires chrome and flash (we can side load flash and chrome) so if a dev for this plugin would do it for android there would be no reason to stay on fire os firmware.
[Fire TV Q&A, Help & Troubleshooting] ECEXCURSION:
Picture quality would be one...
[Fire TV Q&A, Help & Troubleshooting] ahoslc:
Anymore progress on this?
[Fire TV Q&A, Help & Troubleshooting] hearnia_2K:
Mods: Thread title change?

Should we have a mod change the title of this thread? While it started out as a thread asking if it was even possible to have an alternative ROM, it has clearly now moved towards the discussions and progress of rboxs excellent work on CM12 for the Fire TV.
[Fire TV Q&A, Help & Troubleshooting] rbox:
Not really. I've tried playing around some more with audio and bluetooth. Not working yet. I remember I had some errors that last time I tried youtube, I think I fixed though, I'll probably try that again.
[Fire TV Q&A, Help & Troubleshooting] hearnia_2K:
Thanks for the update anyway, much appreciated!.

Without trying to push you, would it perhaps make sense to do an early release, with some well highlighted issues, in order to get more testing and playing with it? Perhaps someone else might be lucky and find the right things to get things like the bluetooth and audio going?

At the same time I also understand that if a large audience get it then it's likely to flair up a lot of people having installation issues, or a lot of noise from known issues and things. Although if a few more people get it earlier then there would be more experienced people to help answer those questions and issues once there is a wider release.

Just thinking aloud.
[Fire TV Q&A, Help & Troubleshooting] rbox:
Releasing a build isn't gonna do anything, since everything is broken. If someone knows what they are doing with compiling CM... that's a little different.
[Fire TV Q&A, Help & Troubleshooting] hearnia_2K:
OK. That's makes sense, thanks for explaining why it would not be helpful too!
[Fire TV Q&A, Help & Troubleshooting] KLit75:
Sorry. This was posted to the wrong location.
[Fire TV Q&A, Help & Troubleshooting] mdpauley:
[MENTION=3991724]rbox[/MENTION], if you have a repo set up I can help take a crack at it also.
[Fire TV Q&A, Help & Troubleshooting] rbox:
Well it looks like I'm probably going to have a lot less time to work on this stuff in the coming weeks. Unfortunately what I have right now is a big giant mess. I'll try to get it cleaned up and uploaded to GitHub.
[Fire TV Q&A, Help & Troubleshooting] mdpauley:
[MENTION=3991724]rbox[/MENTION], I can set up a private bitbucket repo if you want to hide the mess. ;)
[Fire TV Q&A, Help & Troubleshooting] TechVendetta:
I hope your device and vender trees have more fixes than mine so far. I managed to get dualbooting over usb working when my friend let me play with his for an hour. I finally picked up my own so I can run my own build tests. Right now I'm in the process of porting CM12 over, there is a decent amount of goodies in their source so much of it is just annoying work of rebuilding the files they left out and wondering why they included the source for doom (definitely adding that back in). I haven't personally pulled the Android TV source myself yet, is it mainly a replacement launcher like carhome was or is it heavily modified from typical CM/AOSP?
[Fire TV Q&A, Help & Troubleshooting] rbox:
There is no separate Android TV source. It's part of AOSP 5.0. The only thing that isn't part is the gapps and the launcher. I've pulled them from the fugu system image and some stuff from the molly dump.
[Fire TV Q&A, Help & Troubleshooting] TechVendetta:
So are you just mostly doing kangs so far then? I've been doing a full port since there isn't much in the way of simillarly spec'd devices.
[Fire TV Q&A, Help & Troubleshooting] rbox:
Oh, I made my own device tree from scratch. The fugu/molly stuff is just for the gapps.
[Fire TV Q&A, Help & Troubleshooting] TechVendetta:
Yeah I already got a working batch of those. I usually port to Problematic devices. Like reverse engineering sylvania tablets with no sourcecode and keeping my now ancient LG Optimus running the latest version of CM (albeit from sdcard since flash is too small). Have you played with usb dual booting? I'm noticing some awful slowdowns on my tests so far I assume its kernel, either that or they really gimped the universal serial bus. But yeah I'm flashing my new Fire's bootloader now, then getting all my testing stuff moved over on to this one, so any source you got certainly would be helpful for once I have my dev stuff back up. This is probably going to be my main project today. :cool:
[Fire TV Q&A, Help & Troubleshooting] rbox:
I actually boot with NFS and loopback mounts. Much easier than screwing around with copying things all the time.
[Fire TV Q&A, Help & Troubleshooting] TechVendetta:
True, at my friends nfs wasn't viable since his network isn't the nicest layout wise. Nfs probably has a reasonably faster file access time too I would imagine.
[Fire TV Q&A, Help & Troubleshooting] rbox:
I have pushed everything to github. I've pushed everything I have as is, including my NFS hacks. So you'll have to tweak and enable fstab or tweak how it mounts NFS if you want to keep with that. The way the NFS works is after I do a brunch or make systemimage, I run:

simg2img out/target/product/bueller/system.{img,raw} && simg2img out/target/product/bueller/userdata.{img,raw}

That converts the sparse images into something that can be mounted. Obviously you only should do the userdata one if you want to basically do a factory reset. Otherwise the data is persistent. I have a fork of netd because it so helpfully flushes the route table on boot, thus killing the NFS. So my fork has a variable to prevent that. If you want Android TV launcher and whatnot, then include the google repo, if not you'll get stock CM12. In the end, I think there should just be 1 rom and then an optional Android TV gapps package to turn it in to Android TV. There is no need to make 2 builds. Bluetooth doesn't work, wifi does, audio doesn't work, video might, I haven't tested it. Obviously if you are going to use NFS, you need ethernet. You can see hardcoded IPs in the init.

https://github.com/androidrbox/android_system_netd

https://github.com/androidrbox/proprietary_vendor_google

https://github.com/androidrbox/proprietary_vendor_amazon

https://github.com/androidrbox/android_device_amazon_bueller

https://github.com/androidrbox/android_kernel_amazon_bueller

Aside from netd, all my repos are on a branch called lollipop. The google vendor stuff is deodexed from fugu with some .so files from molly and a regular cm12 gapps. The amazon vendor stuff is mostly from the amazon rom with some stuff from flo.
[Fire TV Q&A, Help & Troubleshooting] freezer2k:
Awesome,

sure we will get this working sooner or later!

I'll try to reproduce what you have on my unit once I find some time.
[Fire TV Q&A, Help & Troubleshooting] TechVendetta:
You're awesome, I'm going to head to a coffee shop and start comparing your source with what I have. The audio probably needs to be manually set for the hdmi channel once the driver for that is loaded since the standard driver only does non-accelerated video in android. Bluetooth doesn't work because the fire tv used a different bluetooth stack, CM12 changed which stack is included from the bluez one.
[Fire TV Q&A, Help & Troubleshooting] rbox:
Well google switched from bluez to bluedroid ages ago. Not quite sure why amazon is using bluez. Nothing to do with CM12 though, Google did that forever ago.

I also forgot there is one more repo you need for wifi: CyanogenMod/android_hardware_atheros_wlan
[Fire TV Q&A, Help & Troubleshooting] TechVendetta:
So I get to the nexus remote pairing screen then it sleeps....booting over usb so I'm guessing I need to plug in a hub since apparently wifi doesn't start the service until after initial setup. By the way rbox, did you realize the system image we have so far is already bigger than the internal partition? I'm thinking usb dual booting will probably be the best way to boot going forward since we already have your bootloader and people can keep their prime and stock stuff and switch between the two.
[Fire TV Q&A, Help & Troubleshooting] rbox:
The pair screen is looking for bluetooth. If you press a keyboard key it'll continue.
[Fire TV Q&A, Help & Troubleshooting] TechVendetta:
As I expected. Which is why I'm tearing my desk up to find where all my usb hubs from my raspberry pi projects went. -.-
[Fire TV Q&A, Help & Troubleshooting] rbox:
You can also delete the pairing apk.
[Fire TV Q&A, Help & Troubleshooting] TechVendetta:
Got a 3.0 hub, things are moving along, much of the TV stuff isn't loading right for me, not sure if its a bad build or if I'm missing something you had. The permissions were an awful mess, I've been cleaning that up and working out the bluetooth and wifi issues since it uses a similar setup to the LG optimus I already develop for. Currently once I get to the select language screen it hard resets with no critical errors to logcat. If my current lib pull ins and boot patches I'm trying now don't help stabilize things I'll probably try rebuilding it based on a more CM12 focused build then port the TV stuff later when core functions are behaving. Also, what purpose does the modem partition serve? If it's not needed I'd prefer to not touch anything on sdcc.1 and just keep my little usb walled garden for everything.
[Fire TV Q&A, Help & Troubleshooting] rbox:
That seems odd. I was able to get completely through wifi and registration all the way to the launcher. What permission and wifi issues are you having? Also, I have last_kmsg enabled, so you could check there. If you just don't have the vendor/google directory it'll do a regular cm12 build. Some of the blobs need the files in /firmware. It never writes to it though. You could copy the files to your own /firmware directory i suppose. Or loopback mount the NON_HLOS.bin from the firmware there too.
[Fire TV Q&A, Help & Troubleshooting] TechVendetta:
That's what i thought the only thing I can think is that something tries to reset USB even though i disabled most if not all things that should. Permission errors were mostly in data so I'm using a more completed qcom init now also some files end up in nonstandard locations. The log says Bluetooth and WiFi are up but then the mysterious reboot hits before i can select anything. Ill look more into it tonight.
[Fire TV Q&A, Help & Troubleshooting] TechVendetta:
So I rebuilt with the TV stuff removed. Made it to the CM12 launcher and started interacting normally then got the reset again, I'm going to add my debug code back in and see if maybe now I can at least see the error. The only thing thats different is im using usb and didnt use your netd was there anything else weird patched in it other than fixes for nfs? Might also be helpful to get one of your img's to see if there really is anything different.

Does "undefined instruction: pc=402c1b88" mean anything to you? The kernel is complaining about it everywhere near the reset. The only other thing thats possible is wifi reseting the wrong usb bus maybe. It seems the wifi is on an internal usb bus after all.
[Fire TV Q&A, Help & Troubleshooting] rbox:
I'll do a build tonight and throw it up somewhere. You can ignore the undefined instruction "warnings". You'll get them constantly and they are mostly harmless. I'm pretty sure I even got them when I was attempting my original CAF JB rom. I tried everything I could think of to tweak the compile flags to prevent it. At one point I tried decoding the instruction it was complaining about and it seemed like a relatively standard and harmless instruction.
[Fire TV Q&A, Help & Troubleshooting] TechVendetta:
Upon further testing, it seems much of CM12 is still highly volatile, there isn't a stable branch yet and things keep changing, breaking, then getting patched only to repeat again. Got a new ATV based test build to try out today, got wifi working again which of course meant bluetooth stopped working, which means its probably something to do with the coexist setup or just general wifi hackery. Also, selinux was the primary source of my full crash, turns out auditd didn't like something and killed everything. Disabling every selinux flag stabilized that partially and last crashes were related to bad storage configs (on usb booting I'm in the process of implementing the emulated storage system) As for audio I remember seeing something screwy I wanted to look into but I want to get bluetooth stable first so I don't require a usb hub on every boot. Latest system image required another bumb up in partition size as well, somewhere around 825mb I'm now using a 900mb partition. I think languages account for much of the bloat in the builds most likely.
[Fire TV Q&A, Help & Troubleshooting] AFTVnews.com:
Thanks for the update. I'm sure many people, like myself, are eager for an Android TV ROM, so it's great to hear you're still working on it. I hope the dentist appointment wasn't too bad ;)
[Fire TV Q&A, Help & Troubleshooting] TechVendetta:
Update, my upper lip and half my nose is non responsive. O_O In about an hour I'm going to start testing and bug hunting again.
[Fire TV Q&A, Help & Troubleshooting] bastXda:
Hello. Any news on this very interesting work you made?
[Fire TV Q&A, Help & Troubleshooting] krasny2k5:
You can follow TechVendetta updates at:

http://xdaforums.com/fire-tv/development/cm12-android-tv-rom-development-t3016587
[Fire TV Q&A, Help & Troubleshooting] Unjustified Dev:
If you need anything from latest adt-1 build let me know as I have one. I have been porting it to two of my devices and so far it's been great. Adt-1 builds are deodexed by default the issue I had is with signing but it looks you've have gotten past that.
[Fire TV Q&A, Help & Troubleshooting] TechVendetta:
That would be interesting to look at going forward. Can you link me a build and any relevant source code?
[Fire TV Q&A, Help & Troubleshooting] sacwoo:
Just curious if this project is still being worked on. I'm excited about the possibilities.
[Fire TV Q&A, Help & Troubleshooting] jpeg42:
http://xdaforums.com/fire-tv/development/cm12-android-tv-rom-development-t3016587
[Android Apps and Games] tomasslavicek:
Hello, I would like to introduce you our new app: Koala Phone (koalaphone.com)

Download on Google Play: https://play.google.com/store/apps/details?id=com.koalaphone.silver

Help us translate Koala Phone to your language: https://crowdin.com/project/koala-phone-senior-launcher

It is a simple Android launcher, designed for seniors and people with vision problems. The interface looks like a classic feature phone with hardware buttons. If your parents still use these old Nokia phones, maybe it’s time for them to try something new :)

Main features:

large QWERTY keyboard for SMS messages, or classic phone keypad

touch-optimized apps: simplified camera, photo viewer, alarm clock and a flashlight

text can be enlarged, buttons have a vibration feedback

speech recognition for SMS messages, and text-to-speech support

Koala Phone is great for all the people who want to browse photos, use camera and other smart features, but do not want to fight with their phone.

An article about our research (Designing a mobile interface for older people): http://bit.ly/koala-medium

We are looking forward to all your feedback!

Koala Phone is available for free (you can unlock some paid features after 7-day trial, but you can still make calls or send messages, even with the free version).

I hope this post does not violate any community guidelines; similar Necta or Apex launcher has also a free and paid version. If this is a problem, I apologize...

[YOUTUBE]5BuxamysP1g[/YOUTUBE]
[Android Apps and Games] kamilhilal:
Not good enough need more enchantment
[Android Apps and Games] tomasslavicek:
Hello, what do you mean by more enchantment?

We are preparing a new update with possibility to change the color theme, or set the background image.
[Android Apps and Games] pcwalker:
Hello. Im using this launcher now. Is this diaplay normal? Please see attached image pls.
[Android Apps and Games] tomasslavicek:
The image should not be definitely that blurry. I have just checked our code and everything seems to be OK...

Is your display resolution really 960x540 px? Did you changed your DPI or other params in your phone?
[Android Apps and Games] burakerenn:
Dear Tomas,

I was changing a smartphone to a senior phone and realized that there is a new launcher called Koala. I would say that the market absolutely needs a proper senior launcher app, and I am talking with an experience as a grandson who change 4-5 smartphones into a senior phone, sadly by paying huge amount of money for BigLauncher.

I would be happy to provide you a feedback also in more detail if you are interested in, but at the first stage, I would like to comment and if you wouldn't mind, point out certain issues for me. But before that I should say that I am very impressed with the launcher. It absolutely has a good touch and one of the best among others (consider that I probably tried 15-20 different launchers :) ):

1- Language! Sadly the current version supports only English and Czech. Yet we would like to have it in every possible languages. Sadly my grandparents cannot understand English very well.

2- Call directly through phonebook or favorites: For eyes that have been worked for many years, it may be hard to write an SMS. So I would definitely like for my grandparent, a phone book which calls directly the contact that is selected without pushing more buttons.

3- A home screen, with phonebook icon, dialer icon, and favorite contacts.

I believe at least first two is necessary for me and felt obliged to write, despite the fact that I am mostly a lurker on xda.

I wish you a pleasant day!
[Android Apps and Games] tomasslavicek:
Hello, thank you for your kind words!

1 - Which language do they talk? We plan to add new languages soon, but we wanted to finish the app first.

2 - This is a great idea! I can add a new item into the settings, so you will be able to choose it.

3 - We will think about it... But currently the home screen is the dialer (so the launcher looks like a classic phone). Favorite contacts and other contacts are combined on one screen; this combination was more understandable for users, than two different screens.