yashsingh1/xdaforums huggingface dataset:
[MeMO Pad 7 Original Android Development] lambdadroid:
All older versions are available on GitHub: https://github.com/me176c-dev/device_asus_me176c/releases

HOWEVER, there shouldn't be anything wrong with the latest build. I've been using it for a month now without any issues. Could you clarify what exactly isn't working? Note that even if you install root via the Lineage addon you still need to enable it in the developer options. Otherwise, you can also give Magisk a try. As far as I've heard, it's working fine with the ROM.
[MeMO Pad 7 Original Android Development] profee:
Lineage root didn't work for me, too.. I tried it twice, and failed both times. Magisk works like a charm, tho.

MTP also doesn't work for me, so i turn on the recovery when i need to access internal storage via PC.

Another strange thing, when watching videos in MX player, tablet becomes pretty hot (both HW, and HW+ decoding, h264 and h265). Stock player doesn't have that issue.

But it's still a great rom, and all these little quirks are negligible, because there is always a workaround. Now we just need to wait and see if doze mode becomes possible.

Great work, man!
[MeMO Pad 7 Original Android Development] lambdadroid:
Yeah, MTP is broken right now, but in my opinion MTP is a horrible protocol. You can use ADB to transfer files without entering the recovery.

To be honest, I'm not really sure how they can claim to have implemented custom HW decoding. This is usually very device/SoC-dependent. If they have a custom implementation then it might not be optimized for x86 devices, since there are not many of them.

I think the stock player is pretty good though, so it shouldn't be a big problem to use it. :)

Thanks for the report! I have to admit that I've never really tested if addonsu is actually working properly. I'm personally not using root on this tablet (at least since I have the LineageOS ROM), so I only checked that it installs properly but I never tested if it actually grants root access.

I will try to test it within the next days and provide a fix/solution with the next update.

Edit: It seems like something is weird with Lineage's x86 addonsu. I was able to reproduce the problem. However, the addonsu I just compiled using my Lineage tree is working fine. I will provide it with the next update.
[MeMO Pad 7 Original Android Development] lambdadroid:
LineageOS 14.1 (2017-12-22) now available

Improvements

Security patch level: December 5, 2017

Updates: LineageOS, Linux (4.9.63 -> 4.9.71), Mesa (17.2.5 -> 17.3.1)

New features

WireGuard support

TWRP recovery improvements

TWRP 3.2.1 (still built in Android 7.1.2 tree)

Download

Installable ZIP: lineage-14.1-20171222-UNOFFICIAL-me176c-signed.zip

TWRP recovery image (recommended): twrp-recovery-3.2.1-20171222-UNOFFICIAL-me176c.img

addonsu: addonsu-14.1-me176c-signed.zip
[MeMO Pad 7 Original Android Development] TimmyP:
Thank you for updating this. I can guarantee there are 1000x more people that are actually thanking you, that want this. Keep up the good work. If we can help let us know.
[MeMO Pad 7 Original Android Development] AdmiralDock:
Hi!

Firstly, thank you for making this ROM, I've been using it for a few months now and before that I was considering getting rid of the device (It was sooooo slow, practically useless). This rom made the device useful and speedy again :D

Now on to an issue. I don't know if it was touched on in these posts before but casting the devices screen (screen mirroring) to chromecast does not seem to work at all, it just gives me a generic disconnect message. Casting from within apps that support it (youtube, etc.) works fine though!

Now I'm no developer but I do know my way around the system and some command line stuff, is there any logs or such I can send you if you're willing to check this out and try to fix it?

If this is a feature you're not willing or able to support, that's fine too. Just wanted to put up some info about this.
[MeMO Pad 7 Original Android Development] lambdadroid:
I'm not entirely sure how Chromecast is working. If it works similar to Miracast then it is indeed currently not supported. HOWEVER, the fact that Chromecast does work within apps like YouTube suggests that it might work differently. You can try getting the log while attempting to connect to the Chromecast, it might give some helpful information.

https://wiki.lineageos.org/logcat.html explains how to get the log, then just post it here as attachment.
[MeMO Pad 7 Original Android Development] AdmiralDock:
Thanks for the quick response. I've pulled a log right after I got the disconnect toast message. From a quick skim through there seem to be video and audio encoder errors but I am not familiar with the inner workings of Android to figure anything substantial out of this.

Apparently I'm too new to XDA to be allowed to attach files OR post links.

I've sent you a PM with the log, hope that's okay.
[MeMO Pad 7 Original Android Development] lambdadroid:
Hmm, I'm not sure what's wrong exactly. It could be related to the video/audio encoder errors but not necessarily. Do you have another device where it's working correctly? It would be helpful to have a working log to compare with.
[MeMO Pad 7 Original Android Development] lambdadroid:
I have an idea for one problem that's preventing it from working, but I'll need a few days to work on a fix (Christmas time is rather busy). That doesn't mean that it'll be actually working but it might help...
[MeMO Pad 7 Original Android Development] AdmiralDock:
I'm glad you got an idea, I couldn't make heads or tails of my phones logcat.

Take your time. There's no rush to get this working right now. Happy holidays to you :)
[MeMO Pad 7 Original Android Development] DoubleM101:
I know it's mentioned on the first post camera will not work and it's not planned to... But theres any update since then?

I'm asking because my mom has this tablet and even for the light tasks she does (mainly Youtube and Facebook Lite) the device has a terrible performance and it's always with no free space available even with few app's installed. Every time i need to do any kind of maintenance to it i loose my patience. Hardware isn't bad, software is!

However she like to take some photos to share on Facebook so camera is really needed.
[MeMO Pad 7 Original Android Development] Ruben Craveiro:
the camera on this tablet is horrible, and hardware *is* bad, it only has 1gb of ram, even 2gb isnt enough anymore for good multitasking..
[MeMO Pad 7 Original Android Development] lambdadroid:
I don't think it will ever be supported. Sorry :(
[MeMO Pad 7 Original Android Development] DoubleM101:
Yeah i know hardware isn't very good neither for the current standards but the tablet could be a lot better if it wasn't the horrible software. I never saw anything so slow like that.

I have a Moto G (1st Gen) with CM i still use as a secondary mobile phone and that thing flies comparing with the MeMo Pad.

Maybe i will try to Root the tablet and disable as much services i can. Not the best solution but i guess better than nothing.
[MeMO Pad 7 Original Android Development] isdex1:
would this rom work for the ATT memo 7 LTE model ME375CL?
[MeMO Pad 7 Original Android Development] T_I:
Thanks for the update. The previous image sometimes shows a non-working screen rotate. (after a crash it worked again) This image has no screen rotate (except forced rotates from landscape to portrait and back by apps). Could be my tab, as I didn't see reports of crashes on the previous build, does anybody else have these issues?
[MeMO Pad 7 Original Android Development] lambdadroid:
Generally, no. The tablet seems to have similar hardware, so with a few minor modifications some features might be working, but the ROM will very likely not work as-is. Definitely not working will be LTE/any other mobile Internet connectivity. I don't know anything about this tablet, did it receive a Lollipop update? You need the Lollipop (UEFI) update to flash an unlocked bootloader.

There is a known issue with the accelerometer (which is used for screen rotation): https://github.com/me176c-dev/device_asus_me176c/issues/7. It doesn't work properly if you reboot your tablet. It should be working if you power off the tablet, wait a few seconds and then turn it back on normally.
[MeMO Pad 7 Original Android Development] jackalonez:
Hi guys, my compliments to the developer : I tried Xposed lineageos version with the last release (LineageOS 14.1 (2017-12-22) but it keeps bootllooping ....anyone had luck with this or a different old release ?

Thank you very much
[MeMO Pad 7 Original Android Development] lambdadroid:
It seems like Xposed is missing an upstream patch I backported which is required to make ART work on newer kernel versions. There is not much I can do about this, I might suggest adding it to Xposed but I'm not sure if it will break older kernels. For now, Xposed isn't working properly on this ROM, sorry about that.
[MeMO Pad 7 Original Android Development] jerbear294:
In light of the Meltdown and Spectre vulnerabilities, has an off-schedule security patch been considered similar to what happened with KRACK?
[MeMO Pad 7 Original Android Development] profee:
I honestly doubt it. They are probably too busy 'handling' server and business market to do anything for Atoms, because this is much bigger than KRACK. But i guess there is a chance if a lot of chromebooks/ulp notebooks are based on them. So, basically, i have no idea.
[MeMO Pad 7 Original Android Development] lambdadroid:
Yep, I hope to be able to provide an update soon(TM)! I've been monitoring progress on the patches, but the patch for Linux 4.9 is still being worked on. However, considering the Android security bulletin for January 2018 is out already, I'd prefer to combine both for the next update. I'm not sure when LineageOS will integrate the security patches, it also seems like Google has yet to push the remaining source code. We'll see!

The issue is pretty much the same for all Intel processors and to some extend, for other CPU architectures as well. The same "fix" (or better said: workaround) is used for all of them. At the end, the CPUs only differ by the overhead this workaround causes. Considering the tablet has a rather cheap Atom CPU, we'll have to see how much impact it has on performance.
[MeMO Pad 7 Original Android Development] joo young:
Hi, I want to buy a tablet in Korea.

Be in use

I read your explanation and repeat

Blocked at boot loader

Rooting

You can't copy cmd.

I need a full explanation and a photograph.

Thank you for your efforts.
[MeMO Pad 7 Original Android Development] lambdadroid:
I think the instructions are pretty clear. Of course, if you want to make modifications to the tablet you need to get a basic understanding of what you're doing, otherwise you will easily run into problems if something isn't working as expected. We might be able to help you if you are more specific about what you have already done, or which step exactly is causing problems.
[MeMO Pad 7 Original Android Development] lambdadroid:
Meltdown and Spectre update

I've been rather busy during the last few weeks, as I've been working on another project for this tablet (more info soon) and I'm also working on getting things running again with an upgraded Linux 4.14 kernel. This might finally bring some improvements with battery drain during suspend and/or USB OTG support, but it's still too early to tell.

Now, I promised a update for the recent Meltdown and Spectre vulnerabilities that have been found in Intel processors. Patches for these vulnerabilities are still very much WIP, which is the primary reason why I've been delaying this update. Also, if you've been following the news carefully, you also might have seen that fixes for these vulnerabilities come with a price: Depending on the use case, they have a more or less significant impact on performance. Especially for Meltdown, this affects older processors more than newer ones, but this tablet is using a rather cheap Atom CPU which does not appear to have the extra CPU features (e.g. "PCID") that reduce the performance impact of the Meltdown fix.

We'll have to see how much it affects our tablet and if this is a price worth paying. I'm not really comfortable with releasing this as a regular update for everyone just yet, not until we have tested this more and/or have a more or less simple way to disable it manually.

Updated boot image with Meltdown fix

I intend to keep my promise, though, so I have compiled a new boot image with an updated kernel. It fixes the Meltdown vulnerability, but not Spectre. First patches/workarounds have been proposed for Spectre, but not merged upstream yet. It requires changes in the kernel and the compiler toolchain, so it remains to be seen how much effort is required to integrate it into the Android build system.

You can easily flash it using Fastboot and ADB or a root file explorer. Note that if you have Magisk or something else installed that modifies the boot partition, you will need to install it again after flashing the new boot image.

First download the ZIP in the attachment, extract boot.img from the ZIP, boot your tablet into Fastboot and run:

fastboot flash boot boot.img

You also need to update the kernel modules on the system partition. Either use a root explorer to copy the "modules" folder in the ZIP to /vendor/lib/modules/ or copy it with ADB:

adb root
adb remount
adb push modules /vendor/lib/

Let me know how it works and if you notice any differences!
[MeMO Pad 7 Original Android Development] Nexive:
Thanks for the patch. :)

Booted succesfully but wifi isn't working, it stays off.
[MeMO Pad 7 Original Android Development] lambdadroid:
Yep, noticed this yesterday night... Totally forgot to upload the new kernel modules. I've edited my post above; WiFi+Sound should be working again after you copy the updated kernel modules :)
[MeMO Pad 7 Original Android Development] Nexive:
Yes, wifi and sound is working again after I moved the modules to my device. :)

Thanks for the fast update. :)
[MeMO Pad 7 Original Android Development] joo young yoon:
Help me.

Hi.

I'm doing it your way.

We did routing.

It's blocked at the unlock-boot loader.

I'm copying.

If you type a command,

They can't find the files and directories.

I don’t know what I should do.

Help me.
[MeMO Pad 7 Original Android Development] lambdadroid:
Can someone with a ME176CX (I have the ME176C) send me the output of (on a root shell):

grep . /sys/class/dmi/id/*

Thanks :)

[MENTION=4491111]Nexive[/MENTION] [MENTION=5479482]jerbear294[/MENTION]
[MeMO Pad 7 Original Android Development] jerbear294:
me176c:/data/data/com.termux/files/home # grep . /sys/class/dmi/id/*
/sys/class/dmi/id/bios_date:03/18/2015
/sys/class/dmi/id/bios_vendor:American Megatrends Inc.
/sys/class/dmi/id/bios_version:5.6.5
/sys/class/dmi/id/board_asset_tag:ATN12345678901234567
/sys/class/dmi/id/board_name:ME176C
/sys/class/dmi/id/board_serial:BSN12345678901234567
/sys/class/dmi/id/board_vendor:ASUSTeK COMPUTER INC.
/sys/class/dmi/id/board_version:1.0
/sys/class/dmi/id/chassis_asset_tag:To Be Filled By O.E.M.
/sys/class/dmi/id/chassis_serial:To Be Filled By O.E.M.
/sys/class/dmi/id/chassis_type:8
/sys/class/dmi/id/chassis_vendor:To Be Filled By O.E.M.
/sys/class/dmi/id/chassis_version:To Be Filled By O.E.M.
/sys/class/dmi/id/modalias:dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd03/18/2015:svnASUSTeKCOMPUTERINC.:pnME176C:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnME176C:rvr1.0:cvnToBeFilledByO.E.M.:ct8:cvrToBeFilledByO.E.M.:
/sys/class/dmi/id/product_name:ME176C
/sys/class/dmi/id/product_serial:SSN12345678901234567
/sys/class/dmi/id/product_uuid:03000200-0400-0500-0006-000700080009
/sys/class/dmi/id/product_version:1.0
/sys/class/dmi/id/sys_vendor:ASUSTeK COMPUTER INC.
/sys/class/dmi/id/uevent:MODALIAS=dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd03/18/2015:svnASUSTeKCOMPUTERINC.:pnME176C:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnME176C:rvr1.0:cvnToBeFilledByO.E.M.:ct8:cvrToBeFilledByO.E.M.:
[MeMO Pad 7 Original Android Development] Nexive:
me176c:/ # grep . /sys/class/dmi/id/*
/sys/class/dmi/id/bios_date:09/16/2015
/sys/class/dmi/id/bios_vendor:American Megatrends Inc.
/sys/class/dmi/id/bios_version:5.6.5
/sys/class/dmi/id/board_asset_tag:ATN12345678901234567
/sys/class/dmi/id/board_name:ME176C
/sys/class/dmi/id/board_serial:BSN12345678901234567
/sys/class/dmi/id/board_vendor:ASUSTeK COMPUTER INC.
/sys/class/dmi/id/board_version:1.0
/sys/class/dmi/id/chassis_asset_tag:To Be Filled By O.E.M.
/sys/class/dmi/id/chassis_serial:To Be Filled By O.E.M.
/sys/class/dmi/id/chassis_type:8
/sys/class/dmi/id/chassis_vendor:To Be Filled By O.E.M.
/sys/class/dmi/id/chassis_version:To Be Filled By O.E.M.
/sys/class/dmi/id/modalias:dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd09/16/2015:svnASUSTeKCOMPUTERINC.:pnME176C:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnME176C:rvr1.0:cvnToBeFilledByO.E.M.:ct8:cvrToBeFilledByO.E.M.:
/sys/class/dmi/id/product_name:ME176C
/sys/class/dmi/id/product_serial:SSN12345678901234567
/sys/class/dmi/id/product_uuid:03000200-0400-0500-0006-000700080009
/sys/class/dmi/id/product_version:1.0
/sys/class/dmi/id/sys_vendor:ASUSTeK COMPUTER INC.
/sys/class/dmi/id/uevent:MODALIAS=dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd09/16/2015:svnASUSTeKCOMPUTERINC.:pnME176C:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnME176C:rvr1.0:cvnToBeFilledByO.E.M.:ct8:cvrToBeFilledByO.E.M.:
[MeMO Pad 7 Original Android Development] tb79:
Is this Rom still Alpha?

Is oreo near?
[MeMO Pad 7 Original Android Development] lambdadroid:
It's quite reliable and stable but I still consider it experimental until the remaining issues have been fixed (see TODO in description). However, I believe it works fine for most use cases this tablet still has.

It's as far away as it is near. I had it running in August with only hardware accelerated video decoding broken. Haven't touched it since then and unfortunately I'm not optimistic it will be easy to fix. In any case, I'm not going to switch to Oreo until work on Nougat is completed, and I don't urged to do so either considering LineageOS 15.1 isn't released yet either.
[MeMO Pad 7 Original Android Development] seamo123:
Has anyone managed to get Xposed running on this? After endless bootloops I have to admit defeat and revert back to the stock (crappy) operating system.. boo-hoo.
[MeMO Pad 7 Original Android Development] lambdadroid:
See: https://xdaforums.com/showpost.php?p=75027929&postcount=296

I might be able to compile a custom Xposed build with the needed fix. Might try that later...
[MeMO Pad 7 Original Android Development] lambdadroid:
I've applied the needed patch to Xposed and built a new version of it. The boot loop is fixed but I haven't tested it further.

If you still need it, give it a try and let me know. I've attached the ZIP you can flash in recovery. Note that the first start is quite slow because it needs to recompile all apps. (Maybe 5 minutes, not much more)

Tagging everyone who has mentioned Xposed before in this thread: [MENTION=4680702]seamo123[/MENTION], [MENTION=8826114]jackalonez[/MENTION], [MENTION=4557146]T_I[/MENTION], [MENTION=7377386]bryandroid98[/MENTION]
[MeMO Pad 7 Original Android Development] jackalone:
Wow ty very much testing it really soon, I will let you how it goes :)...

TESTED AND WORKING PERFECTLY :))))) YOU'RE THE MAN !!!!
[MeMO Pad 7 Original Android Development] seamo123:
When you say quite slow, how long roughly are we talking? It's been stuck in the opening animation for 15 mins or so.. on the face of it it's the same result as last time, unfortunately.
[MeMO Pad 7 Original Android Development] lambdadroid:
Usual boot time for me is ~20 seconds, so I'm talking about 2 or 3 minutes here D: It depends on how many apps you have installed.

I don't have time right now, but I can send you a special debug boot image tomorrow that will allow you to get the log and see what it is doing all the time.
[MeMO Pad 7 Original Android Development] seamo123:
Cancel red alert, it's working fine! Many thanks. ?
[MeMO Pad 7 Original Android Development] T_I:
Thanks a lot for this xposed build, was missing it a lot. (have it on all other devices, minminguard was missed a lot here) Been out of commission for a while, concussion, but slowly getting back in behind the computer.
[MeMO Pad 7 Original Android Development] lambdadroid:
Update: Looking at Intel's Microcode Update Schedule it seems like Microcode updates for Atom/Baytrail/Valleyview CPUs are already available (we have "Valleyview, Baytrail M/D/T C0", CPUID 30678 as far as I know). This is funny because even most newer processors don't have a stable update yet. However, I haven't been able to find these Microcode updates anywhere, they're not included with the regular Linux Microcode download. I guess they expect the BIOS vendors to ship the update, but obviously ASUS isn't going to do that. I could apply it at boot time (temporarily) if I find a copy of them somewhere...

In any case, they're not too important. Linux has rather effective mitigations that work completely without Microcode updates. They're usually even more efficient than the mitigation provided with the Microcode updates.
[MeMO Pad 7 Original Android Development] seamo123:
Been playing around with this ROM for a couple of days and noticed that screencast doesn't work. Is this a bug or a problem at my end?

I noticed too that the removable memory card is given what looks like a randomly assigned name of numbers and letters - in my case it's called '6C02-919E'. Certain apps aren't detecting the removable card and I've had to change the path manually, which is kind of boring. Is this normal for Android 7? Or do I need to reformat the SD Card?

Also, the root seems a bit strange.. everything root-wise seems normal except with the 'Adaway' app. It keeps telling me that my device isn't rooted when root permissions have already been granted, for some odd reason.

It seems a bit skittish and crashy as well.. I replaced the Gmail app with a blacked-out version and the device went into a bootloop after restarting. This really shouldn't happen, even if the Gmail app is incompatible (which it isn't). So I gave up on it booting and went back to stock lollipop for the time being. ?

Anyway, I've attached a few screenshots to illustrate what I've been saying - I hope it's helpful!

P.S. Aside from that, I love the ROM - just being able to replace that GODAWFUL white ui with a dark theme is almost enough in itself. ?
[MeMO Pad 7 Original Android Development] lambdadroid:
What is "screencast"? There are many different ways/apps that mirror the screen and not all of them are working. They should work if they don't require the use of WiFi Direct which is broken (e.g. Miracast). As an example, Chromcast screen mirroring should work*, although quite slow due to a missing hardware accelerated video encoder.

* with the next update that will be released soon(TM)

That's how it's supposed to work. You should not rename the path manually, and it shouldn't be necessary either. The actual path should be hidden from most apps; maybe those apps need an update. However also note that with newer Android versions apps don't get write permission to the external SD card by default - except for their own data folder in the "Android" directory.

What does "replacing" mean? De-installing the original version and then installing the modified version? Android has rather strict signature checking, so crashes after modifying an app are not unexpected. In general, you should just use Substratum for all theming needs anyway.

In any case, there is not much I can do without a log, so set up ADB, capture the log when the problem happens and post it here.

What are you using for root? The suaddon or Magisk? You can try both and see if one of them works better.
[MeMO Pad 7 Original Android Development] seamo123:
I'm using the suaddon. How do I go about using Magisk? Never heard of it tbh.

I mean the in-built "cast" option on the ROM (it's in the 'Display' section of the 'Settings' menu I think?) doesn't work. It starts to activate and then switches itself off. Aside from that, any apps that cast to a TV Screen work just fine.