yashsingh1/xdaforums huggingface dataset:
[MeMO Pad 7 Original Android Development] lambdadroid:
It could work, in general, if

and only if

it has received an update to Android 5.0 (Lollipop). Otherwise there is no way to unlock the bootloader.
[MeMO Pad 7 Original Android Development] jerbear294:
It never received 5.0.
[MeMO Pad 7 Original Android Development] kusama15:
Thx for the response the problem is there's no android 5 update the memopad 8 but memopad 7 does, i downloaded the Android 5 update of the memopad 7 i tried to install it on memoapd8 but it fails is there some way to edit the update to make it work on my tab? I'm using a fully working temporary twrp recovery on the memopad8
[MeMO Pad 7 Original Android Development] lambdadroid:
No, sorry. It depends on a device-specific firmware update that cannot be taken from another device.
[MeMO Pad 7 Original Android Development] TimmyP:
Do not default to trying this, on any device. Only work with what it says it works with or you eventually will break something.
[MeMO Pad 7 Original Android Development] angelor3d31:
Good ROM new life this tablet, bug sound crach turn off sound notification and works great. But Bluetooth sound works great :)
[MeMO Pad 7 Original Android Development] lambdadroid:
This just happened to me for the first time. I'm guessing I haven't "heard" this issue before because my tablet is in "Do not disturb"/muted the whole time. So when I test the first thing I do is to enable "Do not disturb" so I don't need to hear those annoying touch sounds.

Indeed, it happens when different kinds of sounds are mixed together. Long running sounds (e.g. Music/Videos) are played differently than short sounds like touch sounds or notifications. Switching between different playback modes causes this choppy playback.

So you might be able to avoid it most of the time by disabling those annoying touch sounds in settings. Then it will only happen if you receive a notification while playing music/videos.
[MeMO Pad 7 Original Android Development] lambdadroid:
I have just released a new version of the ChromeOS addons: https://github.com/me176c-dev/android_vendor_google_chromeos-x86/releases/tag/11895.118.0_nocturne

There is now a somewhat easier guide how to build them, including additional dependencies: https://github.com/me176c-dev/andro...eos-x86/blob/11895.118.0_nocturne/BUILDING.md

Would you like to try it? This time you should not need to download the ChromeOS recovery image manually. If you run the "sudo apt install ...." line first the script should do the download for you.
[MeMO Pad 7 Original Android Development] baran.kuzu:
This issue gone for me after i installed ViPER4Android FX
[MeMO Pad 7 Original Android Development] lambdadroid:
LineageOS 16.0 (2019-06-09)

Security Advisory

Android security patch level: June 5, 2019

Added mitigation and CPU microcode update for:

CVE-2018-12126, CVE-2018-12130, CVE-2018-12127, CVE-2019-11091

aka Zombieload, RIDL, Fallout, MDS, … so many names, sigh

Changelog

Enabled MPEG2 video codecs (including hardware acceleration)

Fixed warning: "There's an internal problem with your device. Contact your manufacturer for details."

Flashing "vfp-fix-lineage-16.0-me176c-signed.zip" is no longer necessary

Updates: Linux (4.19.42 -> 4.19.49), Mesa (19.0.4 -> 19.0.6)

Addons

CPU Microcode addon is now obsolete, since CPU microcode updates are included by default again.

Re-install me176c-boot if you have been using it.

Widevine/Houdini: Updated to 11895.118.0_nocturne

There are now simplified build instructions in BUILDING.md

Download

Installable ZIP: lineage-16.0-20190609-UNOFFICIAL-me176c-signed.zip
[MeMO Pad 7 Original Android Development] dirkp1:
Thanks you for the new update, works for me without any problems.

Here are the new one:

b39c5a4fe145ce917ffd681aea21dda7907f0ea3 houdini-x86-chromeos-11895.118.0_nocturne.zip

df27f11635ebefa19ddbb8c752b12fa909ce0ef2 widevine-x86-chromeos-11895.118.0_nocturne.zip

[MENTION=6833678]lambdadroid[/MENTION]: Thanks now I took the correct source. Hash is correct now
[MeMO Pad 7 Original Android Development] lambdadroid:
Hmm, the checksum does not match. I believe this is because the order of files is different in your generated ZIP.

Can you try building latest version (download: https://github.com/me176c-dev/android_vendor_google_chromeos-x86/archive/pie-x86.tar.gz) and check if your checksums now match the following?:

b39c5a4fe145ce917ffd681aea21dda7907f0ea3 houdini-x86-chromeos-11895.118.0_nocturne.zip
df27f11635ebefa19ddbb8c752b12fa909ce0ef2 widevine-x86-chromeos-11895.118.0_nocturne.zip
[MeMO Pad 7 Original Android Development] cr_28:
I can't flash the file, it gives an error when installing, saying that the file is not for that device. Can anyone help?
[MeMO Pad 7 Original Android Development] lambdadroid:
Do you have a ME176C(X) (or K013)? If yes, do you have latest TWRP installed? If yes, please post the full error (as image or text).
[MeMO Pad 7 Original Android Development] cr_28:
Yes, i have a ME176C. TWRP version is 3.0.2-0
[MeMO Pad 7 Original Android Development] lambdadroid:
You need latest TWRP (version 3.3.1) from https://xdaforums.com/memo-pad-7/orig-development/recovery-unofficial-twrp-3-2-1-asus-t3745190 to install LineageOS 16.0.

Follow the installation instructions carefully: Newer versions of TWRP require me176c-boot 0.3.0+.
[MeMO Pad 7 Original Android Development] cr_28:
Ok, I'll try that. Maybe i have to update the bootloader in first place.
[MeMO Pad 7 Original Android Development] cr_28:
Thanks buddy, everything is already installed and working.
[MeMO Pad 7 Original Android Development] baran.kuzu:
i can't download the files, i'm pressing download this file and nothing happens.
[MeMO Pad 7 Original Android Development] dirkp1:
Download works without any problems. But here is an other URL, both in one archive: https://www110.zippyshare.com/v/tmDlJsSs/file.html
[MeMO Pad 7 Original Android Development] 100ajk:
Anyone else not able to get Netflix working? I've flashed the Widevine zip posted by [MENTION=5646769]dirkp1[/MENTION] but Netflix shows "This app is not compatible with your device" when I open it
[MeMO Pad 7 Original Android Development] lambdadroid:
Where does it show that? In the Play Store *before* you install it or when you have it installed and start it?

Please install DRM Info and check if Widevine shows up there.
[MeMO Pad 7 Original Android Development] 100ajk:
Widevine doesn't appear in DRM Info, I guess it's not installing properly, I've tried flashing it again a few times. I think I'll do a clean install of the ROM and see what happens.

EDIT: No luck, Widevine isn't showing in DRM Info. When I flash it in TWRP it says install was successful.
[MeMO Pad 7 Original Android Development] lambdadroid:
Please post the logcat from shortly after opening DRM Info. (See https://wiki.lineageos.org/logcat.html)
[MeMO Pad 7 Original Android Development] 100ajk:
I've PM'd you the logcat file, I'm not a very active poster so I can't post link in this thread yet.
[MeMO Pad 7 Original Android Development] lambdadroid:
Ah interesting. Looks like this one:

W android.hardwar: type=1400 audit(0.0:1845): avc: denied { read } for name="libwvhidl.so" dev="mmcblk2p15" ino=3119 scontext=u:r:hal_drm_widevine:s0 tcontext=u:object_r:unlabeled:s0 tclass=file permissive=0
F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/android.hardware.drm@1.1-service.widevine": library "libwvhidl.so" not found

Do you have latest TWRP installed from https://xdaforums.com/memo-pad-7/orig-development/recovery-unofficial-twrp-3-2-1-asus-t3745190?

Will need to try to reproduce this...

Possible workaround:

Boot into Recovery

Mount -> System

Use ADB shell or Advanced -> Terminal and type:

restorecon -RFv /system/vendor/lib/

(Check if it mentions something with "libwvhidl.so")

Reboot and try again.
[MeMO Pad 7 Original Android Development] 100ajk:
Wow thanks for getting back to me so fast. I had TWRP 3.2.1 installed, didn't realise you had released an update, all good and working now. Thanks a million mate :D
[MeMO Pad 7 Original Android Development] lambdadroid:
To check if it was caused by the TWRP version or something else, can you try the following?

Install latest TWRP

Boot into recovery

Wipe -> Advanced -> System

Re-install LineageOS

Re-install Widevine, and whatever else you need (Google Apps, ....)

Reboot and check if Widevine is working

There should be no need to do a factory reset (i.e. wipe data). So you can keep all your settings and apps.
[MeMO Pad 7 Original Android Development] lambdadroid:
LineageOS 16.0 (2019-07-07)

Android security patch level: July 5, 2019

Updates: Linux (4.19.49 -> 4.19.57), Mesa (19.0.6 -> 19.1.1)

Download: lineage-16.0-20190707-UNOFFICIAL-me176c-signed.zip
[MeMO Pad 7 Original Android Development] moranop:
Update 2019-07-07 works great! Thanks for your effort to keeping this device alive!
[MeMO Pad 7 Original Android Development] or1m:
this update: lineage-16.0-20190707-UNOFFICIAL-me176c-signed.zip

bricked my device... :/

it is stucked on intel logo - normal power on or

i can get only to vol+ and - with power button into fastboot 1,2,3 and wait forever,

any advice, please??
[MeMO Pad 7 Original Android Development] lambdadroid:
Read the upgrade notes/installation instructions ;)

The "Intel" bootloader is no longer supported. LineageOS 16.0 works only with me176c-boot.

FYI if you are upgrading from LineageOS 14.1 without a factory reset I cannot guarantee that there won't be any side effects. I haven't tested upgrading from 14.1 -> 16.0.
[MeMO Pad 7 Original Android Development] or1m:
i was upgrading from this lineage v16 from demcember 2018 (i guess) to newest one,

so when this change of supporting bootloader happened??

nevertheless, is there anything i can do with that?

orim
[MeMO Pad 7 Original Android Development] lambdadroid:
Uh, if you were using one of the LineageOS 16.0 test builds, you must do a factory reset. Those builds were intended for testing only and cannot be upgraded to the "stable" builds.

The new bootloader has been recommended for more than a year now (even on LineageOS 14.1), but has become required with one of the last LineageOS 16.0 test builds.

Quite a few things were changed for LineageOS 16.0, so make sure you read the new installation instructions or the initial changelog.

If you can still boot to fastboot/droidboot mode (the screen where you can scroll through Reboot/Recovery Mode/Power Off/... with the volume keys), you can just install me176c-boot normally.

It should still work from the Intel bootloader, by booting with Volume Up + Power, iirc.

Otherwise, if this isn't possible, follow the troubleshooting instructions of me176c-boot.
[MeMO Pad 7 Original Android Development] or1m:
i see only this fastboot 1,2,3

thats it.

see picture.

and platform-tools>fastboot.exe devices

gives me empty line

so is this EOL for my MemoTab?
[MeMO Pad 7 Original Android Development] lambdadroid:
That's the screen you'd use the me176c-boot troubleshooting instructions on.

You might need special Intel USB drivers or something, I don't know how it works on Windoofs.
[MeMO Pad 7 Original Android Development] or1m:
thaks man, you saved my tab7!

you pointed me to the right direction,

i found Intel_Android_Driver_1.10.0

and did the fastboot flash and now i am in twrp finally!

:good:

thanks again!

have a nice day!

orim
[MeMO Pad 7 Original Android Development] Frisk Dreemurr:
I got this error when I was trying to build the zip of Houdini and Widevine using WSL (Windows subsystem Linux)... Is there any way to solve it? :confused:

Checking ChromeOS image...

chromeos_11895.118.0_nocturne_recovery_stable-channel_mp.bin.zip: OK

-> Extracting recovery image

-> Mounting partitions

losetup: cannot find an unused loop device
[MeMO Pad 7 Original Android Development] lambdadroid:
I don't think it can be built with WSL 1, it may be possible with WSL 2. Otherwise, you will need a virtual machine or a live image of a Linux distribution. Or there may be a link earlier in this thread....
[MeMO Pad 7 Original Android Development] Frisk Dreemurr:
I had set up a virtual machine, and the original problem is solved. :) :good: Yet now I encounter a new problem... How can I solve it? :confused:

Building ZIP for Widevine from ChromeOS 11895.118.0_nocturne...

Successfully built: widevine-x86-chromeos-11895.118.0_nocturne.zip

zip/build.sh: line 13: zip/build.sh: Permission denied
[MeMO Pad 7 Original Android Development] lambdadroid:
That's weird, especially because it worked for Widevine :eek:

Which distribution did you use?
[MeMO Pad 7 Original Android Development] Frisk Dreemurr:
I use Ubuntu 16.04 LTS when I encounter this problem... I'm now updating to 18.04, maybe the problem may be solved? :confused: (By the way, I use VirtualBox to run Ubuntu on my computer.)
[MeMO Pad 7 Original Android Development] lambdadroid:
That should be fine... Pretty sure I tested that a while ago. How did you download https://github.com/me176c-dev/android_vendor_google_chromeos-x86?
[MeMO Pad 7 Original Android Development] Frisk Dreemurr:
Sorry that I reply the message so long after it was sent, mostly because that I ruined the Ubuntu two times yesterday (once because a sudden power off happened during my update, and another time because I accidentally shut down the virtual machine when it was running something). :silly: Anyways, I download the resources through Chrome on Windows, and I downloaded the .tar.gz file, unzip it until I saw a folder through 7-zip on Windows, and use the folder-sharing function provided by the virtual machine to run it in Ubuntu. By the way, the ChromeOS image was downloaded through WSL... I'll try downloading the image again through Ubuntu later and see if it solves the problem. :)
[MeMO Pad 7 Original Android Development] lambdadroid:
That sounds complicated :) Copying files like this can change the file permissions, so I'd suggest that you download + extract it directly on Ubuntu.
[MeMO Pad 7 Original Android Development] Frisk Dreemurr:
I guess that's the reason why I failed to build the zip, for it went out smooth after I downloaded and extracted it directly on Ubuntu! :victory: The reason that I reply so long after is that I didn't give the virtual machine enough space to run, and I had to re-setup the virtual machine (it takes about 13.6GB at last (including the whole Ubuntu) to build this zip on VirtualBox). I have verified the checksums, and both of them matches. :) Guess I'll upload it somewhere later and share the files here. ;) Thanks a lot again, [MENTION=6833678]lambdadroid[/MENTION] ! :highfive:
[MeMO Pad 7 Original Android Development] Frisk Dreemurr:
Check the checksums before flashing! ;)

(From the release page:

Expected ZIP checksums (SHA-1): 1be75d6a1ac30461d11b81c8d2d41c2068b44fd1 houdini-x86-chromeos-11895.118.0_nocturne.zip 393c381c8be04c0d015aba378c7c13974c11a7e4 widevine-x86-chromeos-11895.118.0_nocturne.zip)

Google drive link: https://drive.google.com/folderview?id=12sk0FaCOPVibXoa8kx6U_pB7PfV9Vwh0
[MeMO Pad 7 Original Android Development] Frisk Dreemurr:
Today when I'm trying out the July 7th ROM release, I found that the CPU clock speed seems still not able to exceed somewhere around 900 MHz, and I found this problem since I updated the tablet to Android 9... Is it meant to be restricted so, or is it a bug or something wrong in my installation or other stuff...? :confused: (I found this problem mostly because the tablet lags when scrolling through the homepage (Trebuchet), and the games that used to be playable on the tablet becomes pretty laggy. I didn't install any modules other than busybox and Viper4Android FX Legacy. I use the app "Task Manager" to get the clock speed and CPU usage info.)
[MeMO Pad 7 Original Android Development] lambdadroid:
On the contrary - I have never ported the "power profiles" that were used on LineageOS 14.1. This means that the CPU clock speed is entirely unlimited, including the turbo frequencies (~1.7 GHz).

I had turbo frequencies disabled on LineageOS 14.1 by default (unless you selected high performance mode), because I had the feeling that they were causing the tablet to heat up too quickly.

If your tablet gets too warm, the thermal daemon will try to throttle the CPU speed, including, but not limited to, reducing the CPU clock speed. Unfortunately, it tends to be not successful at all, so it limits CPU performance up to a point where it's not really usable at all. This might be one of the reasons why it does that for you. Have you checked shortly after boot after your tablet was powered off for a while?
[MeMO Pad 7 Original Android Development] Frisk Dreemurr:
I tested this after I turned the tablet off for an hour, and here's what I got...
[MeMO Pad 7 Original Android Development] lambdadroid:
I don't quite understand these screenshots, but note that is perfectly normal that it reduces the CPU clock speed while idle. Otherwise you would have significant battery drain.

It should, however, increase the CPU clock speed when needed. With these monitoring applications you can usually see that if you swipe down the quick settings a few times. The CPU clock speed should go up and eventually settle again after a while.
[MeMO Pad 7 Original Android Development] Frisk Dreemurr:
I recorded the screen while the monitoring application was running, and tried swiping down the quick settings for a few times during the recording, guess this should be able to force the clock speed to go up. Yet I found it not going up quite much, so I tested it on different apps to double check. Then I got different data on different apps I tried... I wonder if these results help? :confused: (I've tested these apps on a different phone, and the data should be the same.) https://drive.google.com/folderview?id=14cvVnN2SKjWOKJnAfXtaqs0dIrnsF0oP
[MeMO Pad 7 Original Android Development] lambdadroid:
I usually use AIDA64 to check the CPU frequency and found it to be quite accurate.

However, I'm afraid I cannot do anything here. I do not artificially limit the CPU frequency in the last release. When using intel_pstate as in this ROM, the CPU frequency is ultimately chosen by the CPU hardware itself based on previous load, and there is little control about that process except for parameters like the maximum CPU frequency that is allowed.

(There are ways to change that behavior and control the CPU frequency manually but I am not sure if this is worth it...)

The next release will re-introduce the LineageOS power profiles feature, which will allow you to select high-performance mode to switch the CPU governor to "performance" instead of "powersave". The "performance" governor raises the CPU frequency more quickly than the default "powersave" one, at the cost of increased power consumption and heat. (Alternatively, there are probably root apps that allow changing the CPUFreq governor...)
[MeMO Pad 7 Original Android Development] Frisk Dreemurr:
Got it, thanks for the reply. :) Actually, I have tried changing the CPU governor through Kernel Adiutor days before, and it do worked smoother with a higher energy consumption and temperature. Just wanted to know if there are other ways to solve it. :o Guess I'll go with the performance mode now and look forward to the new release.
[MeMO Pad 7 Original Android Development] lambdadroid:
Curious, does that really make the system significantly faster? e.g. does it fix your launcher/homescreen lag?
[MeMO Pad 7 Original Android Development] lambdadroid:
LineageOS 16.0 (2019-08-19)

Android security patch level: August 5, 2019

Use WiFi firmware from stock ROM

Add LineageOS power profiles

The default setting disables the turbo frequencies of the CPU to reduce heat (like on LineageOS 14.1).

The old behavior of LineageOS 16.0 (turbo on) can be restored by setting the power profile to "Quick".

Updates: Linux (4.19.57 -> 4.19.68), Mesa (19.1.1 -> 19.1.4), MediaSDK (2019 Q1 -> 19.2.1)

Download: lineage-16.0-20190819-UNOFFICIAL-me176c-signed.zip
[MeMO Pad 7 Original Android Development] Frisk Dreemurr:
Actually, yes. :laugh: I wouldn't say "as smooth as a baby's butt", yet it do go much smoother. By the way, just notice the new release! Guess I'll try it later. :D
[MeMO Pad 7 Original Android Development] Frisk Dreemurr:
By the way, I found that the slow-charging problem still exists in the latest build... I noticed it since the July build, and this problem exists sometimes when charging with the system booted, and sometimes it gets so slow that the percentage of the battery would even decrease. Yet sometimes it charges as fast as before. What may be the problem? :confused:

(Add: Just found a way to make it charge in a normal speed. By starting charging before booting, the charging current could rise up to 700~1000mA, and the battery percentage do increase faster. And if unplug and replug the charging wire after that, it would become slow again.)
[MeMO Pad 7 Original Android Development] lambdadroid:
That's weird. If you have root you can check "dmesg" for a message like "Detected charger type: SDP/DCP". If it says "DCP" then it has detected that it can draw more than 500mA. If it says SDP, then it believes that it is just connected to normal USB and won't draw more than 500mA (and the tablet requires about ~500mA...). Alternatively, Android should say "Charging via AC" if it is detected properly.

Unfortunately, the charging setup is quite a mess. Unlike everything else, the kernel code that is used for it comes from the stock kernel. It's about 30k of lines, with many of them absolutely useless. I tried to make it work mostly, but it is not very reliable...

That's why I still recommend offline charging with the stock ROM (an option of me176c-boot). It tends to charge more efficiently compared to this ROM.
[MeMO Pad 7 Original Android Development] Frisk Dreemurr:
I used Terminal Emulator to run the commands, yet I got no message matching what you said... :confused: Here's the message I got, not sure if the word-finding system have missed something...
[MeMO Pad 7 Original Android Development] lambdadroid:
It's there:

[ 2273.302807] binder: send failed reply for transaction 941522 to 926:1233
[ 2274.428919] phy phy-dwc3.1.auto.ulpi.0: Detected charger type: NONE
[ 2274.432510] bq24192_ac_unlock
--
[ 2277.379968] phy phy-dwc3.1.auto.ulpi.0: Failed to read POWER_CONTROL register for charger detection: -110
[ 2277.379996] phy phy-dwc3.1.auto.ulpi.0: Detected charger type: SDP
[ 2277.381628] android_work: did not send uevent (0 0 (null))
--
[ 2594.718588] android_work: did not send uevent (0 0 (null))
[ 2594.745266] phy phy-dwc3.1.auto.ulpi.0: Detected charger type: NONE
[ 2594.745815] bq24192_ac_unlock
--
[ 3044.990893] phy phy-dwc3.1.auto.ulpi.0: Failed to enable charger detection: -110
[ 3044.990913] phy phy-dwc3.1.auto.ulpi.0: Detected charger type: SDP
[ 3044.993309] android_work: did not send uevent (0 0 (null))
--
[ 3063.360946] android_work: did not send uevent (0 0 (null))
[ 3063.388551] phy phy-dwc3.1.auto.ulpi.0: Detected charger type: NONE
[ 3063.390055] bq24192_cable_callback CABLE_OUT
--
[ 3066.980110] phy phy-dwc3.1.auto.ulpi.0: Failed to read POWER_CONTROL register for charger detection: -110
[ 3066.980138] phy phy-dwc3.1.auto.ulpi.0: Detected charger type: SDP
[ 3066.981739] android_work: did not send uevent (0 0 (null))

Note the error it runs into every time. This will be why it's not detecting the charger properly, and keeps charging limited to 500mA.

Now the question is why it runs into this error. I have seen it before, but it happened only occasionally, not every time. I'm not sure right now.