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

Search This thread

npjohnson

Recognized Developer
Just installed on wade, heres whats bugging me:
- Casting does not work, it does not show in list of devices nor Google home through automatic or manual discovery
- No option to "stay awake" (stay connected to wifi when tv off to enable casting to turn on tv like chromecast)
- No option to map IR remote (need for IR power on using stock remote), are there any android tv compatible apps to map IR signals to button presses and would that even work for device power on. (again not an issue if device was staying awake and just sent out a CEC command to power on TV)

Besides that I love it, extremely snappy considering the hardware. Android 12 looks exactly the same as android 10, would love some tweaks to get rid of the spam ads on services I dont use, but I understand thats out of the scope of this project.
1. Was a typo, uploaded builds with it fixed :)
2. In developer settings - but you don't need it - chrome cast works from sleep
3. IR power works but isn't configurable at the moment - we're working on it. You can try disabling CEC and seeing if it fixes it.
 

xtremeed2705

Member
Jan 20, 2016
15
5
A few bugs I've noticed on latest ROM(Dopinder)

It appears in Google Home now but virtual remote won't work usually.

When using the Android volume control instead of CEC the screen will flash when turning the volume up or down, tried it on 2 different TVs.

Seems a bit laggy going through settings to fast with single presses of the down button(not holding)
 

npjohnson

Recognized Developer
A few bugs I've noticed on latest ROM(Dopinder)

It appears in Google Home now but virtual remote won't work usually.

When using the Android volume control instead of CEC the screen will flash when turning the volume up or down, tried it on 2 different TVs.

Seems a bit laggy going through settings to fast with single presses of the down button(not holding)
Had to disable virtual remote temp - that should work soon - we ran out of space and I had to cut things so I cut that app.
 

castone123

Member
Mar 2, 2019
18
3
What happens when you cannot boot into bootloader or recovery mode on your android tv device? i have dopinder, it is rooted with magisk. When i try to factory reset on the device it just restarts itself, along with system update which usually fails. i have tried to hold the button to get into recovery mode, no such luck, just start up android tv. I can use the device but i cannot update or get into recovery mode or factory reset.
 

reduxd

New member
Jun 2, 2017
1
0
Attempted to build my own image as well and also got the following error on sideload attempt:

Code:
assert failed: update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list"))

Fresh pull of Lineage sources, set up with vendors from TheMuppets. Was succesfully running the 20220620 build + recovery.
 

Spusuf

Member
Sep 3, 2018
11
2
OnePlus 8T
1. Was a typo, uploaded builds with it fixed :)
2. In developer settings - but you don't need it - chrome cast works from sleep
3. IR power works but isn't configurable at the moment - we're working on it. You can try disabling CEC and seeing if it fixes it.
Just updated to latest.
Chromecast/Google home still not working so can't confirm the other points
 

CrysisLTU

Senior Member
Feb 1, 2012
336
399
Fantastic work! But there are two things that lock me down to the stock ROM:
1. IR control using the remote (my TV does not have CEC)
2. Display scaling (to combat overscan)

I understand IR is in the works. But what about display scaling?

Edit: I also couldn't find a way to change resolution and refresh rate. Hopefully that's coming too
 
Last edited:

RoyaldArmer1331

New member
May 13, 2022
4
0
No. Different generation of chip.





I've crossed out the links in the OP - further investigation is needed.

but there is a full factory image with DTB linked in the FAQ.

Install this driver: https://drive.google.com/file/d/1q3Hwrmx-YCrw9U5JGtI2Ocn06zPkjrEG/view?usp=sharing

Download the amlogic `update` tool http://openlinux2.amlogic.com/download/A113/Tool/flash-tool-v4.7/flash-tool/tools/windows/ and run `update.exe bulkcmd fastboot` - then you can flash the factory image as usual.

Sorry about this, AML DTB's are... weird compared to other devices.
I managed to brick my Onn Tv box dopinder (it seems to be in burn mode) and tried following your instructions except I got the 4.9 amlogic flash tool from github since your link is down. When I tried to run the `update.exe bulkcmd fastboot` command, I got the error message:
[update]:No [WorldCup Device] device after scan
[update]ERR(L1094):can not find device

I tried several USB cables, all functional, and plugging it in in different USB ports and it keeps getting this error message. Is there something I can do to make my PC recognize the device?
 

RoyaldArmer1331

New member
May 13, 2022
4
0
Actually, never mind. My Onn box (dopinder) doesn't want to turn on anymore for some reason. I tried everything and it keeps staying on a black screen with no signal. I guess it's gone. RIP
 

Meliorem

Member
Jun 19, 2022
5
0
I managed to brick my Onn Tv box dopinder (it seems to be in burn mode) and tried following your instructions except I got the 4.9 amlogic flash tool from github since your link is down. When I tried to run the `update.exe bulkcmd fastboot` command, I got the error message:
[update]:No [WorldCup Device] device after scan
[update]ERR(L1094):can not find device

I tried several USB cables, all functional, and plugging it in in different USB ports and it keeps getting this error message. Is there something I can do to make my PC recognize the device?
I mentioned that the same exact thing happened to me, both in this message and your next one. I'm in the same situation as you. 980
Haven't gotten any response yet.
 

npjohnson

Recognized Developer
Actually, never mind. My Onn box (dopinder) doesn't want to turn on anymore for some reason. I tried everything and it keeps staying on a black screen with no signal. I guess it's gone. RIP
For what it's worth, there are faulty IC's on this thing. 2 of our devs have had them die, one had it just poof and die on stock lol
 

goapy

Senior Member
Dec 30, 2021
146
38
My current state is stuck on the onn screen (trying to boot to burn mode just results in this same current state -- stuck on the onn screen).
How are you "trying to boot to burn mode"?

Are you holding the button for a sufficiently long period of time, starting from before (or shortly after) power is applied? And doing this while the usb port is connected to a host computer with the worldcup drivers installed?
 

Meliorem

Member
Jun 19, 2022
5
0
How are you "trying to boot to burn mode"?

Are you holding the button for a sufficiently long period of time, starting from before (or shortly after) power is applied? And doing this while the usb port is connected to a host computer with the worldcup drivers installed?
Yes, from before. I figured 30 or 40 seconds was long enough to hold it.
Sorry for any possible confusion but I thought the worldcup "drivers" were a part of the update script. Where can I get these drivers for Linux? A quick search only resulted in finding Windows drivers. (I don't have a Windows machine.)
 

goapy

Senior Member
Dec 30, 2021
146
38
If the update utility worked before, then it is not the problem.

I figured 30 or 40 seconds was long enough to hold it.
That's plenty enough, as long as you didn't start too late and the physical momentary switch itself isn't somehow flaky.

Some reboot mode setting that boots to recovery can sometimes bypass the test for the burn mode button. A uart log would reveal what is going on for sure.
 
Last edited:

Meliorem

Member
Jun 19, 2022
5
0
If the update utility worked before, then it is not the problem.


That's plenty enough, as long as you didn't start too late and the physical momentary switch itself isn't somehow flaky.

Some reboot mode setting that boots to recovery can sometimes bypass the test for the burn mode button. A uart log would reveal what is going on for sure.
The update script never worked. Here is a link to my post:

980
 

sebas4200

Member
Jan 23, 2019
39
4
How do we turn it back on without pulling plug , remote gives red light after shutdown on Dopinder? I don't have cec, what about external storage with otg? You guys working on that full android yet ?
 
Last edited:

LeeX2

Member
Apr 16, 2017
20
14
my dopinder went kinda bricked
it isn't rly "bricked" cuz everythin is working except hdmi output
since I flashed dtb,dtbo for lineageos, theres no singal

but I was able to revert back to stock, sideloading stock ota update, boot it up, pairing remote
( by assuming what shxxts happening on the imaginary screen rn lol :/ )

I was trying to enable adb and bypass rsa auth so I could get logs for op
( weirdly I couldnt get any console-ramoops log )

but I couldnt mount system partition on the lineageos recovery so Im stuck here
( no fstab entry for /system )
Code:
[   87.442020] W:DM_DEV_STATUS failed for system: No such device or address

Im definitly missing smh... any idea would be appreciated


recovery.log https://pastebin.com/iXsa3nRA


p.s
Code:
[    0.162620] Failed to find/open a drm device: No such file or director
mb flashing lineage dtb dtbo recovery imgs tripped a safty switch and nuked itself?
or just a meaningless mummble log?


-------------

nvm, just realized that this is an eng build and adb is enabled by default X^(
logcat attached

but I still cant sideload magisk(for dmesg) its stuck at 0%
is there smh like addonsu for lineage 19.1?
 

Attachments

  • logcat.txt
    5.9 MB · Views: 3
Last edited:

npjohnson

Recognized Developer
How do we turn it back on without pulling plug , remote gives red light after shutdown on Dopinder? I don't have cec, what about external storage with otg? You guys working on that full android yet ?
Just unplug and replug - they're designed for this.

OTG storage works fine.

Full Android works fine but I'm not maintaining builds for it until we go official.
my dopinder went kinda bricked
it isn't rly "bricked" cuz everythin is working except hdmi output
since I flashed dtb,dtbo for lineageos, theres no singal

but I was able to revert back to stock, sideloading stock ota update, boot it up, pairing remote
( by assuming what shxxts happening on the imaginary screen rn lol :/ )

I was trying to enable adb and bypass rsa auth so I could get logs for op
( weirdly I couldnt get any console-ramoops log )

but I couldnt mount system partition on the lineageos recovery so Im stuck here
( no fstab entry for /system )
Code:
[   87.442020] W:DM_DEV_STATUS failed for system: No such device or address

Im definitly missing smh... any idea would be appreciated






recovery.log https://pastebin.com/iXsa3nRA

p.s
Code:
[    0.162620] Failed to find/open a drm device: No such file or director
mb flashing lineage dtb dtbo recovery imgs tripped a safty switch and nuked itself?
or just a meaningless mummble log?
If you flashed stock and nothing happened HDMI wise you have a hardware issue.

Flash the full factory image DTB and all - if you still don't get HDMI you have a hardware issue.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    Today is a somewhat special date: the first anniversary of this thread! 🥳🎂

    Looks like it unexpectedly turned out to be a real development marathon, so certain persons here should be recognized for their perseverance, I think. But since the journey to the official release isn't over, it would be nice to get some kind of progress state report. Is the project still has some roadmap with particular milestones, or to date it's all about catching occasional bugs?
    Without dopinder, we intend to ship wade and Deadpool officially very soon.

    Need to fix DRM on dopinder, then it can follow.

    devkits and Sabrina will lag behind.
    3
    On an upside, Sabrina now boots
    3
    lineage-19.1-20220720-UNOFFICIAL-dopinder.zip

    lasteat build still doesn't work streaming apps.

    also what is 'lineage-19.1-20220720-boot-dopinder.img' for?
    i can not find about boot.img on install guide
    It's not going to be fixed until we figure it out.

    We're actively trying to figure it out.

    I will loudly announce on this thread when it is fixed.
    2
    (dopinder) can't get Netflix to work. For me it's been that way for the past 6-7 builds. I was never able to get it to work. It says we're having trouble playing this title right now for all movies I select. I checked the guide and didn't see further pre requisites. Am I missing something?
    2
    That zip cannot be sideloaded. You have to extract its contents and flash using fastboot or update.
    @p0werpl Thanks, I was able to restore my dopinder.
  • 23
    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 Unofficial 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:
    • deadpool - Google ADT-3
    • dopinder - Walmart Onn UHD Box
    • sabrina - Chromecast with Google TV - Broken at the moment - working on fixing it.
    • wade - Walmart Dynalink 4K Box
    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:
    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 doesn't work
    • (sabrina only) The remote firmware sometimes gets hung up, you can reboot to solve this issue.
    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.
    • OTA is provided the same way officials would have them.
    • 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.
    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
    • bgcngm
    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
    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!
    4
    It's been a month and a half since we discussed the possibility of the tablet-flavored (non-TV) release. It seems that the number of complaints has decreased and the basic quality of builds has improved enough to bother you again in this regard: are there any positive changes in this direction, or it is not worth expecting to get a full-featured Android on dopinder? (I'm still following this thread carefully to make a buying decision.)
    Eh, soon, sure.

    I'll look into making a buildable target