I'm still very interested in this too. IMO AFTV got a lot better with the recent updates but this would still be really cool. There's no urgency or anything. I'm not even fishing for updates on progress. I think people would just like to know if this is still being worked on or if work will continue? Thanks
CM12 / Android TV ROM Development
- Thread starter TechVendetta
- Start date
I'm still very interested in this too. IMO AFTV got a lot better with the recent updates but this would still be really cool. There's no urgency or anything. I'm not even fishing for updates on progress. I think people would just like to know if this is still being worked on or if work will continue? Thanks
To everyone still working on aftv. Thank you. I have made a 25$ donation, I have NO expectations when I donate..
I bought the device because of the specs and the manufacturer.. and the fact that it would be popular.. And so hopefully hacked and developed by independents.
I bought one early (have not even set it up, just rooted it.. Hoping for lollipop.
May end up getting another aftv cause slingtv is offering a fifty dollar off coupon.
Thank you to all developers, hackers... Keep up the good work. I appreciate it.. And I find it to be a good read. [emoji1]
I bought the device because of the specs and the manufacturer.. and the fact that it would be popular.. And so hopefully hacked and developed by independents.
I bought one early (have not even set it up, just rooted it.. Hoping for lollipop.
May end up getting another aftv cause slingtv is offering a fifty dollar off coupon.
Thank you to all developers, hackers... Keep up the good work. I appreciate it.. And I find it to be a good read. [emoji1]
Last edited:
Thanks to someone testing GLideN64 on a device using adreno320,I now know there's hope for fully functional graphics for GLideN64 on FireTV if it gets at least the [email protected] development drivers baked into the MOD. 
Is there no way to collect money/people with a crowdfunding (Kickstarter or IndieGoGo) project?
Writing some famous aftv blogs and make a sticky thread to bring this CM to full power!
The hardware is good for the price but the software sucks a bit.
THX for your work.
Greetings by I_did_it_just_tmrrow
Hi. I registered myself in the Google Docs form TechVendetta put in the first post about two weeks ago. No word from him since.
Only after his permission we can download the images for trying his build?
Anyway. I'll try to build myself the CM12.1 image from his git repo and see what happens.
Hope to have news soon.
Only after his permission we can download the images for trying his build?
Anyway. I'll try to build myself the CM12.1 image from his git repo and see what happens.
Hope to have news soon.
Well at least there's some sign of progress,good luck with building and testing it.
The GLideN64 plugin is coming along nicely.
On GLES2,the texture size quirk is fixed yet some buffer effects are still missing,but it runs really well when the rendering resolution is set to 800x600 compared to Native resolution which slows to a crawl for some odd bottleneck reason.
Even 960x720 resolution runs really great.
The GLideN64 plugin is coming along nicely.
On GLES2,the texture size quirk is fixed yet some buffer effects are still missing,but it runs really well when the rendering resolution is set to 800x600 compared to Native resolution which slows to a crawl for some odd bottleneck reason.
Even 960x720 resolution runs really great.
Yeah so I'm now just about settled in across the country. Still in the process of getting my servers back up. I hear there is a developer testing lollipop image from amazon for me to try to collect the config and new libraries from. Can someone give me a tl;dr on what I missed during my move? Am I still the only one who made any progress on CM based roms? I'll try to find more time to keep track of this too now that I'm mostly settled in.
Ya I think you are still the only one, not much been happening.
Everyone was eagerly waiting for you
Welcome back!
Welcome back! You could check a couple posts above this one. @danielcbit said he'd try to continue your work but that was very recent. Otherwise its been a dead thread.
Hi Everybody. Sorry for the delay in news.
Well, I managed to get CM12.1 compiled for FireTV. I'm attaching my local manifest in case anyone else wants to try building it out. Just place inside .repo/local_manifests/ in you cm12.1 source and remove the ending ".txt".
@TechVendetta I was wondering if you can release the modified Rbox's bootloader? Its the last thing missing so I can try this image I built.
Thanks!
Well, I managed to get CM12.1 compiled for FireTV. I'm attaching my local manifest in case anyone else wants to try building it out. Just place inside .repo/local_manifests/ in you cm12.1 source and remove the ending ".txt".
@TechVendetta I was wondering if you can release the modified Rbox's bootloader? Its the last thing missing so I can try this image I built.
Thanks!
Hi guys, I am wondering if having access to another box would help you. I still have a first run aftv that I would be willing to set up remote access to. No it is not updated, and I am on a broadband connection in central WI. In case you happen to be nearby. Lol
Also I am almost caught up with bills. Donations coming soon, the 17th.
Thank you, i am glad you guys enjoy doing this kind of 'hacking' as do I.
Sent from my A0001 using Tapatalk
Also I am almost caught up with bills. Donations coming soon, the 17th.
Thank you, i am glad you guys enjoy doing this kind of 'hacking' as do I.
Sent from my A0001 using Tapatalk
A modified Rbox "bootloader" is not necessary. What you are referring to is actually his modified boot image. In the main page I discuss how to boot test builds, there was also some lengthy discussion regarding the FULL bootloader unlock. If you have your bootloader unlocked you can use fastboot just like with any other unlocked device. It would be beneficial for you to read over all the information I posted if you plan on getting into the actual porting process since you may have assumptions that would exceed the limitations of the Fire TV. For instance the internal storage is not a viable option for CM12 installation due to size constraints, also removing Fire OS would remove prime support for those who use it. Various things like that effected why I chose this particular dualboot method. If you're still interested in helping tackle some bugs (assuming they were'nt fixed by CM upstream) we can discuss this soon.
As for everyone else, my freetime looks like its going to finally start opening up a bit here soon. I should have the build server back online this weekend. From there I'll be syncing the couple months that I'm out of sync on and merging in CM's M fixes. I might start going back to my attempts to port bluetooth cleanly with no preconfigs to properly solve the abtfilter related issues. Life will be alot easier when we can have wifi and bluetooth working stably.
if you need a build server let me know .. i can give you access to my machine (used for pac-rom nightly builds but this shouldnt matter)...
clean builds run in ~20mins but the upload is 2mbit .. which is a bit slow ...
in case your build server is way slower (> 1h) this might be an option for you
I have a mini data center in my house and pretty decent connection speeds here (90 down and about 5-10 up). Right now its more about getting everything put back together since I just moved cross country. But thanks for the offer. I still need to finish my website overhaul too on top of all the things I'm doing at my new job. At least I keep myself busy!
Hey just bumping this thread, checking to see if anything is still happening? I like my Fire TV but I love the interface of Android TV. Is that what this project intends to bring over? Is there anything anyone can do to boost development and get it working? Would be a great device if that was possible.
I'm still working on it a bit but I'm fairly busy with projects for work right now. I suppose I could find a bit more time to dedicate to it.
Sent from my SM-G900P using XDA Free mobile app
Sent from my SM-G900P using XDA Free mobile app
Understood, thanks for the response. Am I right in assuming this would effectively let us run Android TV on the Fire TV?
I am curious as seeing this post has got me in a tinkering mood, have you played with trying to just run the launcher on the Fire TV? I have downloaded the file and transferred it to the Fire TV but can't launch it natively (I assume because of how it handles intents as a home app and the Fire TV ignores them) so I'm playing with adb next. Just wondering if you have experience with that or not.
edit: was able to get it to launch via an activity launcher. it runs and looks nice but doesn't work really since none of the other apps it works with are installed. oh well, I love the interface.
I am curious as seeing this post has got me in a tinkering mood, have you played with trying to just run the launcher on the Fire TV? I have downloaded the file and transferred it to the Fire TV but can't launch it natively (I assume because of how it handles intents as a home app and the Fire TV ignores them) so I'm playing with adb next. Just wondering if you have experience with that or not.
edit: was able to get it to launch via an activity launcher. it runs and looks nice but doesn't work really since none of the other apps it works with are installed. oh well, I love the interface.
Last edited:
Not sure if you saw there is a 5.0 Dev preview for Fire OS, not sure if that might help with getting CM 12 going?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
27This thread is for development updates, and an eventual release of testing candidates for the future of dual booting CM12 android roms on the Amazon Fire TV. At this time I am not planing on supporting the Fire TV stick since my development platform is based off USB3 booting.
There currently isn't even a stable branch in CM12 upstream so things are quite tricky right now.
I may eventually setup public nightlies once the core is stable.
IN PROGRESS FORM HERE: https://t.co/TXp9z7htDx
The goals for development are in this order:
- Wifi [working]
- Bluetooth [crashing]
- Stable core [random resets possibly storage related]
- Audio [possibly needs hacking to default to hdmi]
- Recovery system [rom boots using the recovery partition currently]
- Hardware Acceleration [untested]
- Android TV addons [require stable core]
- USB Formating and install app [apparently not everyone knows what gparted is]
- Modified version of Rbox's bootloader [I'd like to add recovery to the loader then have stock and custom boot options]
Also, if you want to be ready for possible nightly testing, I highly recommend going to walmart and buying one of the playstation USB3 hubs. It's about $20 but allows you to plug in a USB3 drive and keyboard and mouse until bluetooth is working.
SETTING UP USB BOOTING:
Code:#include <std_disclaimer.h> /* * Your warranty is now void. * * I am not responsible for bricked devices, dead USB drives, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in these files * before flashing them! YOU are choosing to make these modifications, and if * you point the finger at me for messing up your device, I will laugh at you. */
PART ONE [Preparing the drive]:
This process will eventually be streamlined but for now I'll explain the process and how it relates to testing builds during development. Since the Fire TV only has an 8gb flash chip and has no hardware recovery trigger, it is quite the unforgiving device to develop on. The current boot method for my CM12 builds involves flashing over the recovery partition and using it as a sort of dualboot partition. The modified recovery partition then searches for ext4 partitions on and external (USB3 preferred) flash drive. Currently each build generates its own boot image to be flashed over recovery, but I'm currently in the process of exploring the possibility of following Rbox's method of loading a boot image from a system folder instead making only one flash to the actual device necessary going forward.
For USB3 booting during the development process I highly recommend using a USB3 hub for a keyboard and mouse while bluetooth pairing and control mapping is being worked on. I also recommend a USB3 drive.
1) Turn on a Linux machine or boot a Live CD
2) Open Gparted
3) Delete any partitions on the usb drive
4) Create three ext4 partitions, the first partion is system and should be about 1GB, the THIRD partition is cache, and should be about 768mb with 0mb following, you should then have the middle portion empty in the display, in this SECOND partition make your data partition fill the rest of the space.
PART TWO [Preparing the bootloader]:
WARNING this process currently involves replacing your recovery partition, remember kids dd and root is like holding a grenade, make sure you don't throw it at something you care about.
Also, if you are testing a build and it does not load using the previous bootloader, try flashing the latest one from the nightlies (and vise versa) as I am still in the process of stream lining the boot process as far as what should take place before system bring up on our device. If a different boot image loads the system with noticeably more stability let me know asap so I can track the causes of my current issues.
Code:adb connect <STOCK FIRE TV IP> adb push boot-<DATE>.img /sdcard adb shell cd /sdcard su dd if=boot-<DATE>.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Next I recommend side loading this apk to make rebooting into USB boot easier.
The three most recent "boot" images have been added to the downloads section, remember these should be flashed to recovery. Although they would work in boot, that would disable Rbox's loader and prevent you from loading stock OS.
PART THREE [Playing with instability]:
Great so now you have a USB3 booting image flashed to your recovery partition and you have an empty flash drive. This is where the tinkering begins. In the download section you will find a .tar.gz archive with a somewhat booting system with the aforementioned issues. Inside this archive is a system.img file which you will use dd to flash to the first partition of the flash drive you formated. After the system image is flashed you can plug your flash drive into your hub and reboot into recovery. Things will be great, wifi will show up and if you're quick enough you can complete setup and make it to the launcher. (the issue I'm currently working on is an odd timed reset that may be kernel or storage related oddly if you make it to the launcher and don't touch anything, it takes longer to reset)
If you made it this far, welcome to development. You can help by "kanging" (replacing system apk's and files with other versions to find more stable matches, or remove apks until things don't die then report back to me) Also if you make it to this point go ahead and fill out the form I mentioned earlier. Eventually any hotfix builds I do between nightly builds will be accessible to those users to play with.
Overhauling the boot system next and working on the reset debugging.
XDA:DevDB Information
TechVendetta ROM Development, ROM for the Amazon Fire TV
Contributors
TechVendetta, rbox
Source Code: https://github.com/TechV/android_device_amazon_bueller
ROM OS Version: 5.0.x Lollipop
Based On: CyanogenMod
Version Information
Status: Testing
Created 2015-01-29
Last Updated 2015-01-299Hey,
i've got one question for the installation:
you use the recovery as boot partition (because you dont want to mess with the actual boot partition where the bootmenu is).
is there a reason we cant use rbox's bootmenu, add another entry "usb boot" which will boot from /system/boot/usbboot.img ?
Or is the only reason that this just hasnt been added by rbox so we have to use another way?
I think this would be the most brick safe version and shouldnt be a big problem for rbox to implement....
Chris
[edit]
i'm really looking forward to this
Thats one of the goals I put up there, just unlike rboxs current loader I know a way to make it remote controlled. ;D I started a bit on it. The "friendly user release" will have a root installer app that will handle multiboot, formating flash drives, recovery options, updates etc.7Someone 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.
Sent from my LG-VM670 using XDA Free mobile app7
Still working on setting up my build servers. Need to reinstall a CPU tonight to get it back up. Tldr, I moved and started a new job and have been a bit busy but am still pursuing CM on the original fire TV and hopefully it will support the second gen as well.
Sent from my SM-G900P using XDA Free mobile app6
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.
