I have had 2 AFTV1 devices since launch and they have been good devices. In my opinion, the hardware is still great. The most disappointing thing about these boxes is that they have never received a non-FireOS based ROM. We have TWRP recovery now and pre-rooted stock ROMS, but I'm starting to wonder if we will ever see a true custom ROM on this device will vanilla Android Marshmallow or Nougat. I use KODI to stream my Blu Rays from a local mediaserver/NAS and with KODI recently getting up to snuff on "Official" Android standards with the latest Krypton builds, DTS passthrough has been removed since the the FireOS API version only on version 22, based on Lollipop. API 23 is the minimum for DTS support now, Marshmallow. These boxes aren't much use to me know if I can't have surround for my movies.
I think you need to either update your AFTV1. (Not sure if possible, since even the AFTV2 is Lollipop), or downgrade your Kodi back to Jarvis 16.x. Which is still the 'Stable Current' Build.
Perhaps down the Road, SPMC, or other fork, might correct these oversights for these Boxes.
That is just the problem there. "Downgrade" my Kodi to Jarvis. I don't want to do that. Kryton stable is not far off now and I have been running the nightlies for a while now. I also have SPMC (jarvis-based) loaded so I can have DTS passthrough support. I don't see FireOS getting updated anytime soon if ever from Lollipop. Normally, a custom ROM will get you around this on a device. We just never got one for this box. I just don't get the KODI team removing the working DTS Passthrough (apparently they had a workaround in place to make it work), and now that they have decided to adhere to the Android API standards (which isn't a bad thing) they broke existing functionality. Their stance is "bug your vendor" for android update on your device which is not a good answer for these boxes. So although this hardware is more than capbable, if I want to use Krypton I will most likely have to buy new hardware.
Did you say AFTV, or AFTV2?
AFTV with its Snap 600? Might eventually someday perhaps get a custom ROM, as Qualcomm are pretty decent about releasing Code.
AFTV2 With its MediaTek SoC? Not a chance in Hell Amazon are in a fairly decent position to muscle MediaTek 'round a bit, but as is the case with these Chinese outfits. Once the Parts out the Door, its no longer their problem. And what's that? You wanted a new Android?! Well buy our new Box then.
But, back to the topic if you like what is a beta version of Krypton better then Jarvis. Then you'll have to live with the fact that somethings will break.
Related
Hi,
I have little knowledge of android and Roms development, but I understand it was very difficult to develop for aftv given amazon restrictions.
Now, given the accomplishments in unlocking the boot loader, what prevents from a bunch of new Roms to appear? I live outside the us, so amazon ROM is quite useless, very slow, prevents me from having a decent UI (I know I could use xposed modules, but I don't think they solve the issue of the system being quite overloaded by useless stuff).
I was wondering why don't we get at least some clean aosp images to play with. TechVendetta is making a very nice experiment with cm12 on lollipop, but he also runs in the issues of this system being quite new. Can't we get anything based on 4.4.4? That's mature and stable now I guess. Is the issue just in having a decent TV UI?
Sorry, I know I could start studying and do this myself, I am not blaming anybody, just trying to understand better
Thanks!
i agree with you. TV UI is nice, but also having a clean decent 4.4.4 rom or even 4.2.2 would be very helpfull.
Quite a lot launcher can be controlled (after setting up with mice) via remote. I'm also in the beginning of ripping useless Amazon Stuff off my aftv (do a backup of recent System Apk's via titanbackup and then afterwards uninstall them). If we might get a Clean 4.4.4 than even a cool launcher might be usefull
https://play.google.com/store/apps/details?id=com.theatreinabox.android.codered
So if there are any other dev's outside, or someone knew one he might ask them in jump on AFTV
Besides getting a new phone lol!
I'm currently running CM11 by ggow (who is a genuine Android god! Awesome work! You rock!) and to be honest it's the most stable experience I have EVER had with CM across tens of devices I've used it for.
However recently I've had to sell quite a few of my devices to help pay bills during a career transition. Now the Fire Phone has became my daily driver solely because of how cheap the hardware is (resell value isn't that high, it has fantastic hardware, plus I got mine for free when I used to work for at&t), and although CM11 is so damn stable with phenomenal battery life; I have began to notice how often I use apps that utilize the stock camera... Like Snapchat & depositing checks through my bank app.
I have a backup of my rooted 3.5.1 installation, but before I go back I just had a few questions that maybe someone else here has ran into or has had experience with.
What's the most optimal way of running snapchat to your experience?
Should I upgrade my Fire OS or keep it at 3.5.1? I want permanent root, and I plan on tweaking it w/ xposed to manipulate the interface to be as close to a stock Android/AOSP experience as possible. However it is quite outdated. Is battery life better on newer releases? Is permanent root possible on newer releases? Or is 3.5.1 the best version to stay on for tweaking/flashaholic purposes? Would restoring my 3.5.1 backup break my Safestrap recovery at all?
Do Google Play Services break all the time still for those of you using Fire OS?
I've read many threads and different boards/reddit trying to find answers and what other users are doing, but I wanted to get a little dialog going about this and maybe hear from users with experiences.
Sent from my Fire Phone using Tapatalk
Unfortunately, no custom ROM for the Fire Phone can use those apps (i.e. snapchat, some scanner apps). The problem is not the ROM itself, there is no source code available for the custom HAL(Heuristic ALgorithmic), so the cause for all those apps not working properly is located "deeper". You may have to go back to stock Fire OS. Sorry. You should have Fire OS 4.6.6 for best experience.
Hello guys, it is possible to run Atmosphère on a NVidia Shield ? The hardware (most of it) is the same, so, how difcult can be, to make a "nintendo switch" from a Nvidia Shield TV ?
The X1 in the Switch is locked to a specific clock, which likely creates issues right off the bat.
From my understanding, it is possible. However, it's highly unlikely you'll ever see more than an experimental test, which wouldn't be published.
You would have to have the source code of the Switch OS. And since that is 100% not happening, emulation would be the next step, but emulation requires substantially more power than running the OS natively.
So, no, this will likely never exist.
It's far more likely, and realistic, that you'll see a Switch running Android TV.
[Also, this should have been posted in Q&A]
smam1338 said:
The X1 in the Switch is locked to a specific clock, which likely creates issues right off the bat.
From my understanding, it is possible. However, it's highly unlikely you'll ever see more than an experimental test, which wouldn't be published.
You would have to have the source code of the Switch OS. And since that is 100% not happening, emulation would be the next step, but emulation requires substantially more power than running the OS natively.
So, no, this will likely never exist.
It's far more likely, and realistic, that you'll see a Switch running Android TV.
[Also, this should have been posted in Q&A]
Click to expand...
Click to collapse
There is this, though, if someone has the gusto: https://github.com/reswitched/switch-oss
Switch on shield, damn that would be heavenly
Bone stock 2013 nexus 7 flo. Last update was 6.0.1 in 2016.
Just repaired usb jack, and replaced battery. Tablet now works again. Replacement battery has about 85% cspacity of stock, but its very useable.
I have read all I could digest about ROMs, etc. Seems like lineage 14.1 is the best.
What i use this tablet for, is mostly just web browsing and Netflix. Maybe amazon and ebay purchases as well.
Ive read that Netflix won't work automatically if I install a new ROM, because they have blocked it . I've read there are two ways to get around that.... One is a script that made it work again, and the other is to use a very old version of netflix that's been modified to work.
1. Long-term, over a year or two or three does this Netflix issue pose any problems ? How much pita is it ongoing?
2. Does this Netflix issue go away if you revert back to stock?
3. for my uses, is it worth upgrading the ROM at all or just keep everything stock. Stock works, except it's a little slow sometimes. Does that get better or worse with lineage 14.1?
In spite of the security drawbacks, i lean towards just leaving it alone because it works. Thats more important than fancy additional features in Android. It's going to quit working soon then that would be a good reason to change the ROM. I have an old phone that the version of Chrome won't update in it and gives some problems.
My 2 cents, as a noob.
I would recommend the jump to 14.1 over stock. If nothing else you get streamlined right from the starting line with little bloat. I am still using 14.1, and very happy with it, but then I am doing nothing very demanding, just reading books, email, etc..
I used Wug's Nexus Root Kit when I initially rooted and installed 14.1. It worked like a dream for me (who was terrified of accidentally bricking my Nexus 7).
Here is the link to Lineage 14.1 that remains stock with continuing weekly security updates.:
Notice: LineageOS build repository discontinued. | disavowed.jp
Best of Luck, Tam
Installing old netflix version can't happen. Doesn't do downloads. I use this to watch while travelling.....that's a must.
Do the other workarounds work? What about 17.1? Any bugs like this in it? I didn't see any mentioned.
I'm currently on the summer 2021 release of the Verizon stock rom based on Android 11 and ONE UI 3.1, but have been hearing about newer versions based on Android 12. I'm fairly happy with the performance of the existing combination, (the speed and battery life are nothing short of epic) but have never found a solution for the longstanding bug where audio playback inside of Shazam is choppy.
My question to the community is if newer builds of the stock rom fix the choppy Shazam audio playback, and also, whether or not they break the Wichita version of the Google Camera app, which I rely on extensively (unless there's a less-broken distribution that I haven't heard about yet, in which case, lay it on me!).
Well, I finally bit the bullet and chomped down all the dirty/in-place updates for both the stock rom based on Android 11 and Android 12. After I inserted a T-Mobile-branded sim card, it set off a whirlwind of changes, including switching the stock rom from the Verizon rom to the T-Moible one all by itself somehow. Lots of nasty packages to disable, but it calms down well enough after doing so. Among other things, the T-Mobile stock rom is extremely aggressive about software updates. I let it push me around this time, but after getting through the batch, I did disable the obnoxious & pushy updater.
I can confirm that choppy Shazam audio was fixed by one of those (can't remember which one) and that the Google Camera app still works in the new rom, so that's a win. The sidecar widgets are degraded, and the little animation that appears when power is connected looks kind of weird, but everything else is alright, except for the horrible widget shaping on the newer stock Samsung launcher. Also, the friendlier band switching menu is stripped out, requiring use of the dialer code to prompt the more primitive one.
If anyone was on the fence about it, as long as you're okay with those minor caveats, I'd recommend going along for the upgrade.