[OFFICIAL/UNOFFICIAL] LineageOS 19.1 for Amlogic G12*/SM1 Family Devices

Search This thread

Kalentia

Senior Member
Nov 14, 2014
51
7
Is there any possibility that you could release new builds of the dtb/dtbo images for dopinder? I understand that DRM is broken at the moment, but I don't personally care about that since I use this device mostly for YouTube and streaming from my local media server. Without DRM this device is still fully functional for my use case, but I can't continue with the installation instructions since the files needed to get recovery working have apparently been MIA for a couple weeks. Thank you!
 

BTK19

Senior Member
Jan 25, 2021
85
23
EARTH
Amazon Fire TV
Nexus 6
Is there any possibility that you could release new builds of the dtb/dtbo images for dopinder? I understand that DRM is broken at the moment, but I don't personally care about that since I use this device mostly for YouTube and streaming from my local media server. Without DRM this device is still fully functional for my use case, but I can't continue with the installation instructions since the files needed to get recovery working have apparently been MIA for a couple weeks. Thank you!
If you look in the rom zip the dtb/dtbo images are in there
 

RDS5

Senior Member
The problem is not speed, but the fact that everything works on the original rom, but not on this rom.
does it see regular flash drives? the older version of android may have had a driver that this newer version of android simply dropped for your specific drive enclosure.
you may want to try putting the ssd in a different drive enclosure and see if anything changes (i will likely test on mine too and check if my external hard drives work on my android tv).
if flash drives work and other enclosures work too its likely that this enclosure's drivers are non-standard and for some reason were included with the older android version. if nothing works then its got to do with your adapter/device.
 

npjohnson

Recognized Developer

crazyjim_68

Member
May 13, 2009
17
1
Where do you report bugs? It looks like you can only report for official lines of lineageos.

The issue I am having is that wifi direct is not working. I can use wifi direct apps on the official firmware. Examples, securetether, pdanet do not work.
 

npjohnson

Recognized Developer
Where do you report bugs? It looks like you can only report for official lines of lineageos.

The issue I am having is that wifi direct is not working. I can use wifi direct apps on the official firmware. Examples, securetether, pdanet do not work.
Which device? Need to know if I'm looking in Broadcom chip land or Realtek land.
 

pepenador

Member
Dec 5, 2020
13
2
Just a thought for dopinder and the failure to currently play streaming media. A few experiments showed that it is not all streaming media apps that don't work, just some. For example, Disney+ and Netflix do not currently work on dopinder, however ABCiView (ABC Australia Catch-Up Service like BBC iPlayer) does work. So I wonder, instead of DRM being the root problem, is it possible that one of the codecs has been corrupted on dopinder? I am guessing that Netflix and Disney+ currently use the same streaming codec, but that the Australian ABC iView uses an older (and different) codec. I have not dug into the logs yet, but I was just wondering aboout codecs as I investigate this device. That said it's the cheapest 4K device I can find here in Houston. Walmart may suck eggs, but they do have cheap stuff!

Edit. The ABCiView app as it is geo-locked to Australia. VPNs are your friend.
 

npjohnson

Recognized Developer
Just a thought for dopinder and the failure to currently play streaming media. A few experiments showed that it is not all streaming media apps that don't work, just some. For example, Disney+ and Netflix do not currently work on dopinder, however ABCiView (ABC Australia Catch-Up Service like BBC iPlayer) does work. So I wonder, instead of DRM being the root problem, is it possible that one of the codecs has been corrupted on dopinder? I am guessing that Netflix and Disney+ currently use the same streaming codec, but that the Australian ABC iView uses an older (and different) codec. I have not dug into the logs yet, but I was just wondering aboout codecs as I investigate this device. That said it's the cheapest 4K device I can find here in Houston. Walmart may suck eggs, but they do have cheap stuff!

Edit. The ABCiView app as it is geo-locked to Australia. VPNs are your friend.
Nope, it's DRM that stuff isn't L1, Disney+ and Netflix are.

We know exactly the issue - L1 TEE applets won't connect to TEE - but we don't know why.
 

pepenador

Member
Dec 5, 2020
13
2
Nope, it's DRM that stuff isn't L1, Disney+ and Netflix are.

We know exactly the issue - L1 TEE applets won't connect to TEE - but we don't know why.
I'm really reaching, but is there any chance that the device name "dopinder-default" is causing issues with TEE? I have found some applications are not happy with the device identifying itself as "dopinder-default" but start working if I spoof another device e.g. "BRAVIA_ATV2_EU". However none of these apps are DRM video related...

Thank you @npjohnson and all other dopinder-detectives for your ongoing investigations... 😃
 

npjohnson

Recognized Developer
I'm really reaching, but is there any chance that the device name "dopinder-default" is causing issues with TEE? I have found some applications are not happy with the device identifying itself as "dopinder-default" but start working if I spoof another device e.g. "BRAVIA_ATV2_EU". However none of these apps are DRM video related...

Thank you @npjohnson and all other dopinder-detectives for your ongoing investigations... 😃
What do you mean? The device identifies as dopinder – default?

That wouldn't cause this issue but would be an entirely separate issue, mine doesn't do that, are you guys doing anything special that could be causing it to do that?
 

pepenador

Member
Dec 5, 2020
13
2
What do you mean? The device identifies as dopinder – default?

That wouldn't cause this issue but would be an entirely separate issue, mine doesn't do that, are you guys doing anything special that could be causing it to do that?

I'm not changing anything in the base OS, but if you use an app such as Aurora Store (open source google playstore alternative) it reports the device as "dopinder-default". Using these settings, the playstore does not return any available apps as the playstore does not have a device profile for "dopinder-default". However Aurora Store allow you to spoof a device ID, so if you choose something else, such as the "BRAVIA_ATV2_EU" then the playstore "recognizes" the device and makes downloads available. In a similar way that WiFi WPA encryption uses the SSID as part of the decryption key, I was wondering if Widevine uses the device name as part of the decryption key for TEE. I must admit that I know very little about the inner workings of TEE and Widevine at a technical level.

Do you know which version of LineageOS was the last to allow successful Widevine decryption? If I can get my hands on that, I may be able to do a little digging.
 

npjohnson

Recognized Developer
I'm not changing anything in the base OS, but if you use an app such as Aurora Store (open source google playstore alternative) it reports the device as "dopinder-default". Using these settings, the playstore does not return any available apps as the playstore does not have a device profile for "dopinder-default". However Aurora Store allow you to spoof a device ID, so if you choose something else, such as the "BRAVIA_ATV2_EU" then the playstore "recognizes" the device and makes downloads available. In a similar way that WiFi WPA encryption uses the SSID as part of the decryption key, I was wondering if Widevine uses the device name as part of the decryption key for TEE. I must admit that I know very little about the inner workings of TEE and Widevine at a technical level.

Do you know which version of LineageOS was the last to allow successful Widevine decryption? If I can get my hands on that, I may be able to do a little digging.
There was no version.

It used software backed decoding which was in large part useless for anything DRM'd.

There is no base besides stock to compare to.
 

pepenador

Member
Dec 5, 2020
13
2
There was no version.

It used software backed decoding which was in large part useless for anything DRM'd.

There is no base besides stock to compare to.
Ahh, I see. But it is working for deadpool and wade? Are they also using software backed decoding?

Anyway, I'll poke around with stock and see if there are perhaps some missing binaries that we can import.
 

npjohnson

Recognized Developer
Ahh, I see. But it is working for deadpool and wade? Are they also using software backed decoding?

Anyway, I'll poke around with stock and see if there are perhaps some missing binaries that we can import.
Deadpool and wade us hardware backed, all of them do now.

Nothing missing from stock, Wade and dopinder are near to identical stock ROM wise.
 

goapy

Senior Member
Dec 30, 2021
195
45
Nothing missing from stock, Wade and dopinder are near to identical stock ROM wise.

Does the build for dopinder include (or support) the droidlogic videoplayer (Movie Player), com.droidlogic.videoplayer, like the original rom?

I haven't tested your builds since lineage-19.1-20220513, but I seem to remember having some trouble with the droidlogic videoplayer on dopinder. The apk for this app is build specific, or something like that (signatures or something).
 

pepenador

Member
Dec 5, 2020
13
2
Has anyone experienced the following and perhaps have a solution...

I flashed dopinder back to stock using "udpate bulkcmd fastboot" and running the stock flash batch file. The flash appeared to succeed and all the messages confirmed a successful flash. However now when I plug the Onn unit into power it does not power-up at all.

I've tried re-flashing it a few times. Each time I get reports that the flash has been successful, but I can't get the unit to boot again.

Do I need to do anything else before or after the full stock flash to get the unit to boot again?

I had completed the same process previously while exploring the device and had no problem reverting to stock from LineageOS.

I flashed back to stock to try and identify any minor discrepancies between LineageOS and stock to try and identify what may be causing the Widevine DRM issue. However I've hit a block as I now can't boot at all.

Any ideas would be helpful.
 

Top Liked Posts

  • 1
    HDR_POLICY = "0" || #0 = SINK (connected TV or AVR determines HDR mode)
    HDR_POLICY = "1" || #1 = SOURCE (media file determines HDR mode)
    Agree. And, apparently "2" is debug mode, which I have not yet tested.

    hdr_mode changes do not appear to have an effect, as when set "0" (off) with or without sdr2hdr, HDR sources still output a HDR stream, but I have not tested this exhaustively.

    hdr_policy = 1 is probably what we want for most use cases. CoreElec (media player distro) also chose it as their amlogic default.

    Are there actually two distinct settings
    Yes

    If the former, should the HDR_POLICY setting not have any user control?
    It seems to have the most control over output selection, so it should be user controlable.
  • 6
    wade and deadpool are official now!
    3
    Hi all,
    quick question regarding the "Walmart Dynalink 4K Box". Can I use the same procedure/ image for the non Walmart Dynalink 4k box --> https://dynalink.life/products/dynalink-android-tv?

    i would like to install LOS on the dynlink 4k from Amazon (walmart does not exist here), same question at #1231.

    you write in #1233 that it is not possible - where are the differences there? from phones I know no problems in different regions and that only in the mobile area!
    Interesting.

    Yes. You totally can.

    Sorry, I thought this was asking about the dynalink stick - that box is the same.
    3
    Also, I solved the signing issue with Luca's help.

    Builds should hopefully roll for wade/Deadpool with no GMS tomorrow.

    I'll then look into tablet builds feasibility.
    2
    However I run into a boot loop. I see the LinageOS Logo and sometimes the remote control but after that the box restarts. I installed several times with the same result.
    Do you have an idea what I could do?
    You could list, with precision, the steps that you repeatedly did and maybe someone will notice where you went wrong. Most problems lately seem to involve failure to flash the appropriate dtb/dtbo at the appropriate time(s).

    With the v18 builds, it was fortunate that dtb/dtbo were also compatible with stock and vice versa. For whatever reason (I don't know) there is not this same sort of dtb/dtbo compatibility between stock and v19 builds.
    2
    For this you need to join the number of those people here who are waiting for the tablet builds arrival on the official release day. Take your ticket and have a seat beside me.
    Or just don't use google apps, you can build without them easily.

    ATV works fine enough without gapps.

    Tablet builds will follow.

    The official builds are queued but they fail to sign for some reason - working that out rn.
  • 26
    lineage-os-logo.png

    Amlogic G12*/SM1 Family Devices
    Code:
    - Your warranty is now void.
    - You have been warned.
    - Use at your own risk.

    Introduction:
    This is the Official Lineage OS 19.1 thread for the Amlogic G12*/SM1 SoC family of devices.

    Downloads:
    Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed:

    Official Builds:
    Disclaimer: My unofficial builds have full Android TV Google Apps and some other goodies included. OTA's roll roughly once a month. Support not guaranteed or implied.

    Unofficial Builds:
    We also support a few development boards, but at least (for now, until we have time to write up instructions), you're on your own to figure out the install process and set things up:
    EDIT: The development boards don't boot on LineageOS 19.1 at the moment for some reason, we're looking into it.

    If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

    Known Bugs:
    • Recent apps/Multitasking menu doesn't launch.
    • (sabrina only) The remote firmware sometimes gets hung up, you can reboot to solve this issue.
    • (dopinder/sabrina) L1 is currently broken, this is what is holding up official builds for these devices.
    Notes:
    • GApps are baked in - No, I will not be building without GApps included for this device. These builds are built, packaged, and signed by me, and not affiliated with LineageOS whatsoever.
    • Firmware is shipped in the ROM package for this device, so you'll end up on the newest version of compatible firmware after install. Please don't touch firmware partitions after install.
    • On the unofficial OTA is provided the same way officials would have them.
    • Find any more on an official build? Report them according to this guide.
    FAQ:
    • Does L1 Widevine DRM break when I unlock my bootloader?

      Nope, it works fine. L1 certificates, and the mechanism that reports is all still exist and work as expected.

    • Can I haz Netflix?

      Yup! Play Store has it for you.

    • Is this Android TV or Google TV?

      Android TV, with some of the better components of Google TV.

    • Can I go back to stock and relock the bootloader?

      Yeah, grab the factory image for your device and flash it just like you would for a Pixel device, you can find the factory images here. Don't know it I'd relock though, consider that process largely untested on these device. Especially on sabrina, where you can't necessarily re-unlock should you ever want to.

    • Are these the stock codenames for these devices?

      Astute observation, no, they are not. The ADT-3 is actaully `adt3`, but earlier in production is was `deadpool`, which is much cooler. The Dynalink box internally is extremely similar to the ADT-3, so we coined it `wade` after Wade Wilson, AKA deadpool. The Onn box is in the same family, but different enough to coin it `dopinder`, after, well, go watch Deadpool the movie I guess. sabrina is actually the codename given by Google - no clue as to the reason.

    • Does it pass SafetyNet?

      Maybe - the only sure fire way it Magisk, as our boot loader is unlocked and can't be relocked safely.

    • Does the stock remote work?

      Yup, just like it would on stock, in-remote-microphone and all! If it's an IR remote like wade's, it will even work in recovery!

    • Can we we support higher resolution than 4K, higher FPS, or HDR on non-certified screens?

      Nope.

    • I have a very similar device! Can I install these builds and use them?

      No. Please don't do that. You will brick your device, as we include firmware and bootloader images.

      If you're a developer looking to help port to a new device, contact me.

    Kernel Source: https://github.com/LineageOS/android_kernel_amlogic_linux-4.9

    Contributors:
    • npjohnson
    • bgcngm
    • stricted
    • webgeek1234
    • deadman96385
    • trautamaki
    • luca020400
    • aleasto
    14
    Yeah, you used the stock recovery. You need to fastboot flash, then fastboot boot recovery, I'll update the docs.

    For dopinder, it's needed right now.

    Found a procedure for dopinder without the need for keyboard/OTG.

    The docs under "Installing a custom recovery using fastboot" state to use "adb reboot fastboot" which doesn't work for booting recovery, needed to do "adb reboot bootloader" instead.

    Full command log (after unlocking bootloader and re-enabling USB debugging) of the install process with just a regular Micro USB to USB A cable:
    Code:
    adb reboot bootloader
    fastboot flash recovery lineage-18.1-20210805-recovery-dopinder.img
    fastboot boot lineage-18.1-20210805-recovery-dopinder.img
    adb reboot sideload
    adb sideload lineage-18.1-20210805-UNOFFICIAL-dopinder.zip
    # if successful then load bootloader and factory reset
    adb reboot bootloader
    fastboot -w
    fastboot reboot

    Successfully booted to LineageOS after this!
    6
    wade and deadpool are official now!
    6
    Note:

    Since the Lineage Android TV Builds for this little box (aka Boxes), are stable for the most part, but seems
    people are bouncing back in forth from Stock to Lineage and back to stock.

    I created a batch file that will auto flash the stock images and wipe data and so on.. pretty much it will
    make your box as it was when you first booted it after taking it home to try it.

    2nd, I also created a batch file that will backup current images.. No need for a fancy recovery or anything like the
    such. it will use the worldcup or what I like to say, USB Burn mode, and backup each and every partition.
    as well as some not so much needed ones like, misc and metadata. (Just for giggles)..

    backups will be copied to backup dir, I also created a separate batch file to restore your backup.


    I am one that hates doing things the long way over and over, so I always create ways to make things simple
    in the future for people.

    This way, you all can test your hearts out all the new lineages and still have your full Stock backup (including data).
    and restore back in forth as you wish.

    I will upload the backup_restore zip package as soon as I can and with @npjohnson permission I will link
    in thread. Otherwise you will have to just DM/PM me and ill link you the location.

    I am just trying to help the many that I seen complain and dont understand how to go back in forth.
    so with this script, it should take care of most on that. No Fancy Recovery needed...

    you will need worldcup driver for Amlogic........ you can find that on your own.

    Also, to get into USB Burn mode, press side button while plugging in USB cable.
    Keep pressing till you see the LOGO or hear the sound from your computer.

    then just run the batch file and wait..

    if its easier for you:

    Run the batch file, it will keep saying waiting for device..
    Just press the side button while plugging in USB, when you see it start, then release button...........
    and wait till finished..

    Only TESTED On Dopinder Boxes, but im sure they are all the same as for the partition layouts.
    5
    I ultimately settled on 1126400000, gives ~1.1GB to the system and accommodates the app adjustments I've been making for my builds without tripping OpenGApps' space check for TV stock
    this ended up being _wayyyyy_ to much, as this is the full value of the partition vs just the space to reserve, both will work, but we want to split it amongst partitions. One of our guys recalculated it and got it working.

    Should be good to build now from breakfast/extract-files (or syncing the muppets).

    Only thing left is hardware OMX. Hopefully we can figure it out!