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

[Kalentia]

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]

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

 

[npjohnson]

If you look in the rom zip the dtb/dtbo images are in there

correct.

 

[RDS5]

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.

 

[ls4860]

I can't find dtb and dtbo files on this website anymore, do I still have to flash dtb and dtboI files to my Onn. UHD streaming device or I can skip this step?
I also found those two files on OTA file (lineage-19.1-20220810-UNOFFICIAL-dopinder.zip), should I unzip the two files to flash to complete this step?

 

[npjohnson]

I can't find dtb and dtbo files on this website anymore, do I still have to flash dtb and dtboI files to my Onn. UHD streaming device or I can skip this step?
I also found those two files on OTA file (lineage-19.1-20220810-UNOFFICIAL-dopinder.zip), should I unzip the two files to flash to complete this step?

Yes, unzip.

 

[crazyjim_68]

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]

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.

 

[crazyjim_68]

Which device? Need to know if I'm looking in Broadcom chip land or Realtek lan

 

[crazyjim_68]

Walmart Onn Device--dopinder

 

[pepenador]

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]

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]

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]

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]

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]

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]

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]

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.

 

[Deleted member 11959327]

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]

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.