[ROM][UNOFFICIAL][11] LineageOS 18.1 for Fire TV Stick Lite/3rd gen (sheldon/p)

Search This thread

Sus_i

Senior Member
Apr 9, 2013
1,701
725
If the OTG adapter could still be the problem, can anybody recommend one for the FireStick Lite?
Usually even the cheapest one you can get from china will work fine...
 

ryanrudolf

Senior Member
Nov 12, 2012
273
149
Anyone else unable to get OTG to work on their FireStick Lite? I followed all the steps as described here, and in the unlock thread, except needing to disable the rpmb check during unlock as suggested here. LineageOS 18.1 [20220505] seems to run well, but no device connected to the OTG adapter (Link to product page) is recognized / working.

What I've tried so far:
  • Confirmed the OTG adapter's functionality on my 2nd gen FireStick => all devices work like a charm
  • Tried different cables and different 5V chargers with up to 2.4 A
  • Tried FAT32 flash drive, TV remote dongle, gamepad dongle
  • Changed default USB connection mode in developer options to MTP (which interestingly gets reset to "only charging" after each OS restart), also tried some of the other modes
  • USB debugging on/off
  • Enabled USB host API by populating XML files in /etc/permissions as described here. This will result in various "OTG checker" apps confirming OTG support, but it has no effect on functionality.
  • Inspection via ADB shell: didn't find any trace of the flash drive; lsusb is always showing the same 3 unnamed devices, no matter what's plugged in the adapter's USB-A slots

To be frank, OTG wasn't working on stock ROM either, I was secretly hoping that the custom ROM would fix that, but no luck. The stick was on Fire OS 7.2.4.2 when I unlocked it. I don't know if an update would have fixed it, but that's no option to me as I am unwilling to use Fire OS.

I'm running out of options due to my limited knowledge...any ideas?
If the OTG adapter could still be the problem, can anybody recommend one for the FireStick Lite?

OTG works fine for me for stock ROM and LineageOS ROM. could be your OTG adapter is at fault.
although with LineageOS i can see my USB stick but cant write files to it. it works fine with stock ROM so i reverted back to stock ROM for now.
 

jfmcbrayer

Senior Member
May 9, 2011
219
116
are well all using the stock launcher with this build? what's the preferred replacement? I get a black screen so far when I F with wolf launcher.
I'm using FLauncher. I like the channels and access to notifications on the stock launcher, but the prominent ads for streaming apps and no choice of background are too vexing. Flauncher is simple, and available in the Play Store. There's also an update to Leanback on Fire that is pretty good.
 

flaviokosta

Member
Apr 23, 2014
7
2
I found a solution myself. I still don't know why the volume was so low, but with the following adb command the volume can be changed to maximum:

Code:
adb shell service call audio 10 i32 3 i32 15

The 15 at the end is the volume and it looks like 15 is the maximum value.
How can i do it?
When?

I could not do it... :(
 

t3chg33k

Senior Member
Jan 6, 2011
347
176
I use Send Files to TV app to transfer files and APKs with the stick and for some reason, it only works for me the first time I open the application after a restart. Thereafter, keeps failing with a "no route found" error which I presume has something to do with the WiFi connectivity on the device.

This is a great initial effort but I suppose it is back to FireOS for me now as this thing matures, especially as I also use mirroring a lot.
 

t3chg33k

Senior Member
Jan 6, 2011
347
176
I use Send Files to TV app to transfer files and APKs with the stick and for some reason, it only works for me the first time I open the application after a restart. Thereafter, keeps failing with a "no route found" error which I presume has something to do with the WiFi connectivity on the device.

This is a great initial effort but I suppose it is back to FireOS for me now as this thing matures, especially as I also use mirroring a lot.
I went back to FireTV OS and now the remote is not pairing and I am stuck on the 'searching for remote' screen. The same remote paired fine with the stick when I first set it up and also with LOS.

Someone else had the same pairing issue with LOS instead earlier in this thread which was related to HDMI CEC but that is not the case here since I have been using the stick with a monitor.

So any suggestions as to how I can proceed? The stick hasn't connected to WiFi yet and thus I cannot use the app either to proceed further.

Edit: So for some reason, it only worked with the original remote that came with the stick. I was initially using an older remote that I had originally paired with the stick when I first set it up, before rooting. Not sure why it didn't work after the reset, may be because the firmware is different.
 
Last edited:

t3chg33k

Senior Member
Jan 6, 2011
347
176
Although I went back to stock OS, there was another issue with LOS when trying to log into an app that uses OTP. For some reason, the numeric only keypad required to enter the OTP never appeared in the app on iOS.

I use the same app now on FireOS and it does invoke a numeric keypad to enter the OTP. Not sure why it wasn't working on LOS.
 
Aug 9, 2022
6
1
Edit: So for some reason, it only worked with the original remote that came with the stick. I was initially using an older remote that I had originally paired with the stick when I first set it up, before rooting. Not sure why it didn't work after the reset, may be because the firmware is different.
I have a similar problem with the stick not pairing with the remote (the original that came with the stick). Tried everything, but in the end, I started from scratch again, re-flashed the LineageOS ROM, BUT WITHOUT GApps, and was finally able to pair the remote.

The possibility that Gapps causes problem with remote pairing was described here:
 
Last edited:
Aug 9, 2022
6
1
I spent quite a bit of time trying to get LineageOS working with my Fire TV Stick Lite Remote, so I want to describe my problems and how I solved them to help others with similar issues.

I followed the instructions, boot to TWRP (I had TWRP and magisk installed), wiped data, system, and cache, and flashed lineage-18.1-20220505-UNOFFICIAL-sheldon.zip and open_gapps-arm-11.0-tvmini-20220215.zip.

Everything went smoothly until it's time to pair the remote. The screen would show the image of the remote, and the animation indicates that I need to push the back and home buttons. As soon as I clicked on the home button the countdown was replaced by a spinning circle, but after a while the pairing will fail and the countdown timer start again. I tried holding the Home button for 10+ seconds, tapping it for 10+ seconds, holding Home + Back for 10+ seconds, etc. All sorts of combinations. All failed. I gave up and pressed ESC on the USB keyboard attached to the Y-splitter and continue to the rest of the setup. Once the setup is finished, I went into setting, Accessories and Remotes, and tried pairing again. LineageOS will find the "AR" device as soon as I click on the home button, but pairing always fails ("cannot pair") in the same fashion as during the initial setup. I did notice that if I hold Back+Home then the pairing failed quickly rather than a long timeout.

I though that maybe something was wrong with the remote (came with my brand new stick, with fresh Amazon batteries). Measured the battery voltages and they were fine. Also some people say that the LED light on the remote should flash if Home button is held for 10+ seconds but mine does not. So I tried pairing the remote with an Android phone. The pairing was very easy. I only needed to press Home once to let Android detect the remote, then hold Back+Home for the pairing to be done. I can even use the remote to navigate around on the Android phone.

So the hardware is fine, and I know the stick's Bluetooth is fine too because I can pair it with a generic Bluetooth keyboard with no problem whatsoever. So I started googling and found that the problem may be cause by GApps: https://forum.xda-developers.com/t/...11-for-raspberry-pi-4-b.4212945/post-86089723

So I started from scratch, re-installed LineageOS but this time WITHOUT GApps. During the initial setup, things are even worse than before because the remote cannot even be detected. So I pressed ESC on the keyboard and got into the Home Screen, and proceed to Settings, Accessories and Remote to try to pair again.

Same problem, no device detected. So I tried to pair the remote with my Android Phone again. This time Android phone cannot detected the remote either. I took out the battery of the remote, turned Bluetooth off and the on on the phone, and finally I was able to pair the remote to the phone again.

Now I went back to try to pair the remote with the Fire TV Stick. This time it finally worked. The remote was detected as "AR" and I held Back+Home and then clicked on "pair" and finally the pairing was successful.

I also rebooted the stick a few time and the pairing continued to work.

I decided that I actually like the system without GApps. I installed F-Droid and then installed VLC from it. For everything else I just use adb install. BTW, if you are on Windows and all you need is adb, you don't need to install the whole Android SDK, you can just install this: https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/
 
Last edited:
  • Like
Reactions: Merdeke
I found a solution myself. I still don't know why the volume was so low, but with the following adb command the volume can be changed to maximum:

Code:
adb shell service call audio 10 i32 3 i32 15

The 15 at the end is the volume and it looks like 15 is the maximum value.

Thank you kindly for this. To begin with I had no volume problems, then one day it became too low to hear.. tried fiddling with the Consumer electronics control (CEC) choices in Settings in case that was it - and it went back to normal volume - then it went low again and stayed that way no matter the CEC settings (so maybe the initial fix was just a coincidence).

Anyway this adb command seems to have fixed volume permanently.
 
Aug 9, 2022
6
1
I know that Fire TV Stick is supposed to boot into TWRP when it detects a USB keyboard, and indeed it boots into LineageOS directly if I power it up using a regular DC supply. But I noticed that if I have an OTG Y-splitter connected to it (so that I can plug in USB keyboard, hardrive, etc) then it boots into TWRP instead of LineageOS. Not a big deal, just that it takes an extra 5 seconds for the TWRP boot screen to time out. Is that how it is supposed to work? Is there a way to make the stick boot into TWRP only if there is a USB keyboard connected to it?

I know that this is a TWRP issue and not related to LineageOS, but I googled and did not find an answer so I though I'd ask it here.
 
Last edited:
Aug 9, 2022
6
1
One more beginner's observation. Even though the lineage-18.1-20220505-UNOFFICIAL-sheldon.zip is supposed to support both NTFS and exFAT in the kernel, only exFAT formatted USB keys are recognized. I guess that is because only exFAT is supported by vold (volume daemon)?
 

sergisx

New member
Aug 17, 2022
3
2
Thank you kindly for this. To begin with I had no volume problems, then one day it became too low to hear.. tried fiddling with the Consumer electronics control (CEC) choices in Settings in case that was it - and it went back to normal volume - then it went low again and stayed that way no matter the CEC settings (so maybe the initial fix was just a coincidence).

Anyway this adb command seems to have fixed volume permanently.
The voice assistant also helped me to increase the volume to the maximum
 
  • Like
Reactions: Merdeke

sergisx

New member
Aug 17, 2022
3
2
I see, I think there's an option somewhere in the Settings (I can't check right now, sorry), it was called OverScan if I'm not mistaken. If it's not there, I'll include it in the next build.
If it's possible, please add the option to change the screen resolution (in the next build):
Auto
1080p 60Hz
1080p 50Hz
720p 60Hz
720p 50Hz
for old monitors.
Because "adb shell wm size 1280x720"
enlarges the image, but does not change the resolution.
A volume control would also be a useful feature, as sometimes the volume drops to a minimum and the voice assistant helps to fix it.
 

Attachments

  • 081822015833.png
    081822015833.png
    561.9 KB · Views: 36
Sorry, this isn't strictly a posting about the ROM. but I am wondering: now that this is working nicely playing files copied across using a flash drive, does anyone have experience with a simple solution for using this LineageOS+FireTVStick combo to play video from an externally located collection of miscellaneous video files?

Just looking for any tips before I start fiddling about with an approach that's more trouble than it's worth!

I could host them on windows or raspberry pi , or a drive connected to an asus router. Given EAC3 codec apparently won't play, do I need a server that transcodes and provides a stream? Or is it simpler to convert any such videos to use a different audio codec, then just connect to a shared folder?
 

n4m3less

Member
Feb 26, 2010
38
14
I found a solution myself. I still don't know why the volume was so low, but with the following adb command the volume can be changed to maximum:

Code:
adb shell service call audio 10 i32 3 i32 15

The 15 at the end is the volume and it looks like 15 is the maximum value.
Thanks for sharing! it seems to have solved the low volume issue on my device.
 

darkside40

New member
Aug 6, 2015
3
0
Are there any serious downsides if i dont install Gapps? Is only the playstore missing or any relevant features?
 

Top Liked Posts

  • 1
    What is the advatage of micro g? I used it for vanced, but never really understand beyond that. Thank you for the new ROM, checking it out now. Sorry if this is a stupid question about micro g, i am curious.
    MicroG lets you run apps that require Google Services (like for location, or for push notifications) without having GApps or Google Services installed. Google Services is pretty big for older devices, and it's also pretty invasive in terms of privacy. MicroG isn't a privacy panacea, but it does let you do a number of things without sending data to Google where you otherwise would have to.
  • 13
    New build is up: 2022-09-25
    • Fixed the low-volume issue.
    • Switched to SMLK (Simple Low Memory Killer).
    • Added support for UKSM (Ultra Kernel Samepage Merging)
    • Fixed support for NTFS external devices.
    • Fixed (minor) YouTube video flickering(s).
    • Fixed crashes when trying to use (some) streaming TV apps.
    • Disabled some non-ATV features (leftovers).
    8
    I think some folk are forgetting that the hardware on these amazon devices is pretty limited to begin with.

    That coupled with the fact that certain code is locked down by amazon so the guys engaged in development on xda (and off) have done well to get this far and work around it.

    When recommending other devices in a dedicated thread we are drifting off-topic. There are always better devices but we should remember that a £25-30 device is never going to blow your boots off no matter what.

    Sometimes developers have busy lives outside of the forums. Let's just appreciate what they do when they do it and everyone... ...

    Keep up the good work

    Regards
    6
    Have you thought about updating to 19 or 19.1?
    Yes, I'm going to (soon). But I need someone to test the low volume fix for the upcoming 18.1 build.
    4
    Right now, my biggest problem is that certain apps don't work.....(peacock, pluto tv, etc....) comes up with error that it's an amazon device and use the amazon version. I haven't tried a build prop change but that is next.... I am going to change to a google chromecast w/ google tv in the build prop to see if that fixes it???
    The build.prop change should fix the problem. Anyway don't worry, I will include this fix in the next release.​
    3
    Just saw this from May, would be wonderful. Is there any update if this will be included soon?
    I'm currently working on fixing the low volume issue. I'll check that next.
  • 38
    1607247455067-png.5435845

    LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
    Instructions:
    • Reboot to TWRP
    • Wipe data, system (/system_root) and cache
    • Flash the ROM and the GApps
    • Reboot and enjoy!
    Downloads:
    Reporting Bugs:
    • DO NOT Report bugs if you're running a custom kernel, you installed Xposed or you installed Magisk
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    Known issues:
    • Dolby Digital Plus™ E-AC-3
    • Netflix
    Notes:
    • SELinux is in Permissive mode
    • The ROM supports both sheldon (Fire TV Stick Lite) and sheldonp (Fire TV Stick 3rd gen)
    • Do not ask for ETAs
    How do i...
    • Unlock and install TWRP?
    • Go back to the original/stock ROM?
      • Download the stock update.bin (sheldon | sheldonp) and flash it using TWRP
    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

    Code:
    What is your--
    LineageOS version:
    LineageOS Download url:
    Gapps version:
    
    Did you--
    wipe:
    restore with titanium backup:
    reboot after having the issue:
    
    Are you using--
    a task killer:
    a non-stock kernel:
    other modifications:
    
    Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

    Contributors
    R0rt1z2, k4y0z, t0x1cSH, diegocr
    Source Code: https://github.com/mt8695
    Kernel source: https://github.com/mt8695/android_kernel_amazon_mt8695
    16
    🕑 New build is up: 2022-05-05
    • Fixed the advanced audio distribution profile (A2DP)​
    • Fixed the remote disconnecting after rebooting​
    • Fixed the 3rd gen remote app-button(s)​
    • Fixed the microphone (assistant works now)​
    • Fixed Netflix not showing up in the Play Store​
    • Added support for newer remote revisions​
    • Enabled memory optimizations for low-RAM devices​
    • Enabled the XPAD kernel driver (xbox gamepads)​
    • Enabled exFAT/NTFS support in the kernel​
    • Switched to sheldonp blobs​
    NOTE: Netflix still has memory management issues (video playback), I'm still trying to figure out a way to fix this.

    NOTE: As for the assistant button, it works but in a bit weird way; do not release the button when you stop talking, keep it pressed even if you have finished (the assistant will notice once you stop talking).
    13
    New build is up: 2022-09-25
    • Fixed the low-volume issue.
    • Switched to SMLK (Simple Low Memory Killer).
    • Added support for UKSM (Ultra Kernel Samepage Merging)
    • Fixed support for NTFS external devices.
    • Fixed (minor) YouTube video flickering(s).
    • Fixed crashes when trying to use (some) streaming TV apps.
    • Disabled some non-ATV features (leftovers).
    12
    Just a reminder to make clear that development for this device is not dead. As soon as I can, I will resume development.​
    12
    when will the next compilation be ready approximately?

    Thanks for the work you do!
    I don't know. I'm currently on vacation so I'm away from the PC for some days, but I guess it'll be released during the next week.