yashsingh1/xdaforums huggingface dataset:
[MeMO Pad 7 Original Android Development] lambdadroid:
LineageOS 14.1 (2018-05-22) now available

Note: TWRP 3.2.1 (2018-05-22) is available with similar changes.

New features

Added USB OTG support: You can now connect USB devices (e.g. USB keyboards or USB flash drives) to the tablet using USB OTG adapters.

Security advisory

Android security patch level: May 5, 2018

Preliminary information regarding new speculative execution vulnerabilities published on 21 May 2018:

CVE-2018-3639 ("Spectre V4 - Speculative Store Bypass (SSB)"): Not affected.

CVE-2018-3640 ("Spectre V3a - Rogue System Register Read (RSRE)"): Requires CPU microcode updates for mitigation. Right now it’s not clear if/when these will be provided for the CPU in this tablet.

Improvements

Minor power management improvement: Put USB controller into suspend when not connected.

Other changes

Updates: LineageOS, Linux (4.14.35 -> 4.14.42), Mesa (18.0.1 -> 18.0.4)

Known issues

In some cases, the USB controller may enter suspend even though the tablet is connected to a PC, causing it not to show up on the PC. In that case, first try reconnecting it.

One way to trigger this situation is connecting the tablet to a PC while ADB is disabled, waiting several seconds and then enabling ADB. In this case, the device will not show up until it is reconnected.

Download

Installable ZIP: lineage-14.1-20180522-UNOFFICIAL-me176c-signed.zip
[MeMO Pad 7 Original Android Development] sazon goya:
I loaded this on to a MeMO Pad 7 today and ran into a few hiccups, mainly with the TWRP USB Storage mounting not showing up on my PC, it wasn't a big deal since I could ADB Sideload the build and gapps just fine.

Thank you for your efforts!
[MeMO Pad 7 Original Android Development] Agusti94:
is bluethoot working??
[MeMO Pad 7 Original Android Development] lambdadroid:
Yes.
[MeMO Pad 7 Original Android Development] :
Hi, I would like to know if someone has already installed the rom on a ME572C, it looks great and I would like to try it!
[MeMO Pad 7 Original Android Development] jerbear294:
From my (very limited) research, the ME572C never got a bootloader unlock. I'm also unsure if it uses a UEFI as a boot solution like this tablet does.

I remember that it doesn't have a custom recovery and it can't use the tethered recovery exploit due to having a Cherry Trail based processor and not a Bay Trail.

Due to the above reasons, you wouldn't be able to get *any* ROM that isn't a derivative of your stock ROM, let alone this one.
[MeMO Pad 7 Original Android Development] Skymaxx:
Hey all,

is there a fix for the massive battery drain in standby?

that's the only Problem what I see in this great Rom for the me176c.

thx for this great work ??
[MeMO Pad 7 Original Android Development] lambdadroid:
No. The tablet only turns off the screen, it doesn't actually suspend to save power. I was hoping to enable that with this months update, but at this point it is unlikely to make it.

For some reason I'm running into tons of problems when attempting to enable suspend, where it either doesn't even suspend properly or fails to wake up at some point (so the tablet seems to be turned off, but it is actually still on!). I've already fixed several problems but new ones just keep popping up. I'm unable to spend all my time trying to work around problems that only exist on this tablet; so unless I find a simple solution and/or the problems disappear with some future kernel update, I'm not sure if I'll ever be able to improve the standby power usage.
[MeMO Pad 7 Original Android Development] sixdown:
Any idea if this would function with the dual core Atom ME170C?
[MeMO Pad 7 Original Android Development] Ruben Craveiro:
No, different device, different Drivers and Hardware, and can you even unlock the bootloader?
[MeMO Pad 7 Original Android Development] lambdadroid:
Do not install the ROM as-is on your device. The kernel contains code that will only work on the ME176C. However, depending on how similar the ME170C is, it might be possible to port most parts of the ROM without much effort. The main requirement for this would be that it received the update to Android 5.0. If yes, and you are able to root it please post a copy of the kernel log (type "dmesg" in a root shell) here and I can check how similar the devices are.
[MeMO Pad 7 Original Android Development] Skymaxx:
Ok, thx for you answer.

I think i shut down the Memo pad if I dont need it..and restart when I want to use the Memo tab.

I hope you find a simple solution in future without Many time.

So you can use the time for yourself.
[MeMO Pad 7 Original Android Development] lambdadroid:
LineageOS 14.1 (2018-06-19)

New features

Added ramoops that makes it possible to retrieve logs from kernel crashes after a reboot. (Available at /sys/fs/pstore with ADB or a root explorer)

Fixes

Android security patch level: June 5, 2018

Fix issue that may have prevented the tablet from showing up properly when connected to a PC via USB while ADB was disabled (#53)

Other notable changes

Updates: LineageOS, Linux (4.14.42 -> 4.14.50), Mesa (18.0.4 -> 18.1.2)

Download

Installable ZIP: lineage-14.1-20180619-UNOFFICIAL-me176c-signed.zip
[MeMO Pad 7 Original Android Development] dirkp1:
Thank you works great
[MeMO Pad 7 Original Android Development] lambdadroid:
There was a change upstream recently to increase the maximum volume of the speakers. I was always reluctant of changing it because at the same time there were reports for other devices where setting a high maximum volume could result in damaging the speakers. I guess it works fine for most devices if they change it upstream, but I can't say if it will work for this tablet.

Since I use the speakers sometimes and only have one single device I don't want to risk it myself. But if anyone else wants to take the risk and try increasing it, here is how to do it.

WARNING: This may damage the speakers! I don't know what will happen, but please don't blame me if they're not properly working anymore after you try it...

You need root on your device. Use a root explorer or ADB to edit "/vendor/etc/mixer_paths.xml". You can either download the updated file, or search for the following lline:

<ctl name="Speaker Playback Volume" value="29" />

Change the 29 to 35. Do NOT set it to anything higher than 35. Reboot the device and test the maximum volume of the speakers.
[MeMO Pad 7 Original Android Development] Ruben Craveiro:
Has the throttle been fixed when loading videos? Also, is the mic quality gonna ever get decent (one of the only reasons i use the tablet, mic for pc, too lazy to go buy one)
[MeMO Pad 7 Original Android Development] Ruben Craveiro:
-- deleted
[MeMO Pad 7 Original Android Development] lambdadroid:
I haven't fixed anything regarding the thermal throttling, but I've never been able to hit it by watching videos (because most of them are covered by the hardware accelerated video decoder). There might be minor improvements for the microphone in one of the coming updates (there were some changes upstream I can try), but I doubt it will ever be good enough to be properly usable. But tbh, no matter which ROM, the inbuilt microphone within this tablet sucks and there are probably much better cheap alternatives.
[MeMO Pad 7 Original Android Development] dan_dv:
They are selling new MeMO Pad 7 cheap where I live. I have planned to buy one and install Lineage OS.

Does all versions of ME176C work with this version of Lineage?

How is the performance of MeMo Pad 7 with Lineage OS 14.1?

How long does it take for the device to boot Lineage OS?

Is it possible to install Linux on the ME176C?
[MeMO Pad 7 Original Android Development] Nαi:
You can check in terminal: systemd-analyze. In topic header:
[MeMO Pad 7 Original Android Development] lambdadroid:
Weird, I don't think it's produced anymore so I'm guessing this must be some kind of remaining stock they're selling. You need to be a bit careful, there were many different models available under the name "MeMO Pad 7", but if it's called "ME176C", chances are quite high that you will be able to install LineageOS on them, yes.

From what I've heard, the LineageOS ROM generally performs better than stock. The stock ROM is 100% bloat anyway, but was somewhat usable with some work to remove it. However, you should consider that this tablet is and has always been more a low-end device. Especially the 1 GB RAM gets annoying rather quickly, especially when browsing with many tabs etc etc.

I think it's fine for some browsing, music, videos and some simple games. It'll get hot rather quickly if you do CPU/GPU intensive stuff, though.

I guess this depends on the amount of apps you have installed. Without any additional apps, it usually boots in like 10-15 seconds (where at least 5 seconds are the BIOS of the device, not the LineageOS ROM). The first boot might be slightly longer, maybe ~30 seconds. The stock ROM from ASUS usually had ~30 seconds or ~5 minutes for the first boot.

I've been using a dual-boot Arch Linux installation for about 5 months now and it works quite well. However, performance is rather poor and you're even more likely to run into issues due to the low amount of RAM. For example, you cannot actually open a browser with more than 2 tabs :3 I'm still working on getting proper instructions for installation.
[MeMO Pad 7 Original Android Development] lambdadroid:
Edit: Nexive has tested this below, so there is no need for testing anymore! :)

I just realized my post above to raise the maximum volume of the speakers was incorrect.... For some reason I included the wrong line to change in the instructions: It's obviously "Speaker Playback Volume" and not "HP Playback Volume", so the post actually raised the headphones volume and not the speakers volume... I have now updated the post with the correct instructions (see below).

The warning still applies - I believe that it should work but I don't know for sure. Maybe someone who doesn't need their device anymore or someone with multiple devices can try it and post the results here. If it works, I can apply it for everyone in a coming update.
[MeMO Pad 7 Original Android Development] Nexive:
I increased the "Speaker Playback Volume" to 35 and played some music on maximum volume. It did not damage the speaker but the sound was distorted/crackled
[MeMO Pad 7 Original Android Development] lambdadroid:
Thanks for testing! That's good to know. Could you try it with "32" or "30" and see if that works without the crackling?
[MeMO Pad 7 Original Android Development] Nexive:
30 is all good for me. Got some little crackling on 31 and 32 on louder parts or bass of the songs but not on 30. :)
[MeMO Pad 7 Original Android Development] lambdadroid:
Thanks again for testing! :) I will try 30 on my device and if it works fine update it for the next release. I'm guessing that it will only provide minor improvements (given that we were on 29 before), but if this is the maximum that works reliably I think this should bring it on a par with the stock ROM.
[MeMO Pad 7 Original Android Development] lambdadroid:
LineageOS 14.1 (2018-08-17) now available

Improvements

Android security patch level: August 5, 2018

Increase maximum speaker volume: The new maximum seems to be the highest value that works reliably without causing distortion and/or crackling. Thanks to [MENTION=4491111]Nexive[/MENTION] for testing!

Minor improvements to (internal) microphone quality: It’s still really bad, but not sure how to improve it further.

Replaced a part of the hardware accelerated codecs with an open source version built from source. For some reason Intel decided to keep the interesting part - the OMX implementation for Android - closed-source so it is still proprietary. :(

Minor cleanup to reduce ROM size a little bit.

Other notable changes

Updates: LineageOS, Linux (4.14.50 -> 4.14.63), Mesa (18.1.2 -> 18.1.6)

Download

Installable ZIP: lineage-14.1-20180817-UNOFFICIAL-me176c-signed.zip
[MeMO Pad 7 Original Android Development] uknetfreak:
Is it possible to use a microSD card as "adoptable storage". I have tried various cards up to UHS-1 spec and keep getting SD corrupted after a process taking only a few seconds. When I was on stock marshmallow, it allowed me to move some apps using third party movers but this doesn't work now either.
[MeMO Pad 7 Original Android Development] AlekseyLP:
"Is it possible to use a microSD card as "adoptable storage""

Yes, it's would be a great option for this pad, I fully support.
[MeMO Pad 7 Original Android Development] simthadim:
EDIT: somehow it worked now. After re-flashing the custom bootloader, re-installing TWRP it somehow for it after a few tries. Weird.

Thank you very much for your work on this ROM, much appreciated!! Thinking about flashing the latest stockROM and than going back to your ROM in order to have the latest firmware.

Would love to contribute, but have absolutely no idea where to start. Especially your Arch Linux implementation on the memopad is interesting :)

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

[ the old problem]:

Unfortunately I get "Update process ended with signal: 7" when trying to flash this ROM with TWRP. Even the stock roms refuse the flash:

https://www.asus.com/Tablets/ASUS_MeMO_Pad_7_ME176C/HelpDesk_BIOS/

I have model K013, verified by using 'getprob' in the TWRP terminal. The zip seems fine. Already tried to remove the assert (device check) from the updater script, but to no avail.

Is a log file that may be of help that I can add?
[MeMO Pad 7 Original Android Development] noj777:
me172v

hi sir can i try this in my asus memo pad me172v?
[MeMO Pad 7 Original Android Development] jerbear294:
No, the ME172V has an entirely different CPU architecture (ARM, as opposed to x86-64 on this tablet), is significantly older, and doesn't have anything remotely similar to the UEFI bootloader used on this device.
[MeMO Pad 7 Original Android Development] lambdadroid:
I think it used to be working, but I'm going to test this myself before the next update and fix it eventually.
[MeMO Pad 7 Original Android Development] jerbear294:
Speaking of MicroSD cards, I just tried an SD formatted to ext4 and it didn't work- it looks like the system is running a fsck when plugging it in but the version of e2fsck shipped with Lineage is too old to properly do it.

09-18 16:07:00.106 I/e2fsck (157): /dev/block/vold/public:179_65 has unsupported feature(s): metadata_csum
09-18 16:07:00.107 I/e2fsck (157): e2fsck: Get a newer version of e2fsck!

The system assumes it failed because the filesystem is corrupt, preventing use of the SD card until the system reformats it. I assume it's just going to reformat to FAT32, so I haven't tried it.
[MeMO Pad 7 Original Android Development] lambdadroid:
It seems like this was a regression when I upgraded to Linux 4.14. I've now fixed this for the next release.

I can reproduce this problem when attempting to read an USB flash drive formatted as ext4 on my desktop. Indeed, the fsck version in Android 7.1 Nougat is rather old. However, you should be able to avoid this issue by formatting the SD card as ext4 in TWRP instead of your desktop. It should then be usable on both systems.

I've also tried updating e2fsck: While it is pretty easy to build a new version from upstream, it seems like LineageOS has made a couple of modifications to the old version. Restoring these changes would take quite a bit of time. This is going to be fixed automatically when upgrading to a newer Android version.
[MeMO Pad 7 Original Android Development] lambdadroid:
LineageOS 14.1 (2018-09-26)

Android security patch level: September 5, 2018

Fixed adoptable storage corrupting SD cards instead of re-formatting them.

Other notable changes

Updates: LineageOS, Linux (4.14.63 -> 4.14.72), Mesa (18.1.6 -> 18.2.1)

Download

Installable ZIP: lineage-14.1-20180926-UNOFFICIAL-me176c-signed.zip
[MeMO Pad 7 Original Android Development] seamo123:
Great to see a working ROM for this device. Is the deep sleep function working yet, btw?
[MeMO Pad 7 Original Android Development] AlekseyLP:
[*]Fixed adoptable storage corrupting SD cards instead of re-formatting them.

Very good working, TY
[MeMO Pad 7 Original Android Development] lambdadroid:
No. It doesn't go into suspend at all; something is causing errors while suspending which means it always wakes up again immediately. Sometimes the tablet is unusable until the next reboot after suspend. This is why it's still disabled in the builds released here. The problems are really weird and somewhat random, which is why I haven't been able to fix them. I feel like I have wasted too much time already with the suspend stuff... Contributions welcome!
[MeMO Pad 7 Original Android Development] simthadim:
Do you have the same problem with your Arch Linux builds on the memopad? I have 0 knowledge of linuxkernels&android development (yet), but it sounds like an interesting project.
[MeMO Pad 7 Original Android Development] lambdadroid:
I haven't tested it much, but in initial tests I had less problems when enabling it on Arch Linux and TWRP. That doesn't mean that it actually reached the deep sleep states, but at least it entered suspend successfully. Not sure what Android is doing differently.
[MeMO Pad 7 Original Android Development] youling257:
the problem is Android alarm，https://github.com/jwrdegoede/linux-sunxi/commit/883517fee139ca18ee5eb53f1719c960c91018be

---------- Post added at 08:48 PM ---------- Previous post was at 08:40 PM ----------

4.18 rc8 kernel make atom can reach s0i3，https://bugzilla.kernel.org/show_bug.cgi?id=198631#c14

more fix s0i3 problem at here，https://github.com/jwrdegoede/linux-sunxi/commits/master https://github.com/jwrdegoede/linux-sunxi/commits/v4.18-footrail

why you still use lts android-4.14 branch，do you know android-mainline-tracking branch ?

https://android.googlesource.com/kernel/common/+/experimental-android-4.15

https://android.googlesource.com/kernel/common/+/experimental-android-4.16

https://android.googlesource.com/kernel/common/+/experimental-android-4.17

https://android.googlesource.com/kernel/common/+/experimental-android-4.18

https://android.googlesource.com/kernel/common/+/android-mainline-tracking

Androidx86 lineage 14.1 with my https://github.com/youling257/android-4.9/commits/experimental/android-mainline-4.19-tracking branch，can suspend reach s0i3.

but s0i3 for my device，every hour use 200mah，discharge 200ma per second，it should be < 50ma when reach s0i3.
[MeMO Pad 7 Original Android Development] lambdadroid:
iirc I had wake alarms working on my tablet, so not sure if that commit is really the problem.

I'm aware of the android-mainline-tracking branch, but I don't really have the time to do frequent upgrading. Unfortunately, at least on this tablet, there are always some regressions when upgrading. Partially this is because of changes I've made, but there are also some regressions made upstream, when they don't consider certain use cases. Regressions are quickly fixed upstream, but they do cause a lot of work for me to bisect them to the related change.

Additionally, newer kernel versions sometimes also require changes in the Android framework. When I started this I decided not to build on top of Android-x86. Many components (e.g. Mesa) are the same or very similar, but I wanted to make a ROM specifically tailored for this tablet; have it use the standard Android partition layout; and follow the monthly security updates. Especially SELinux enforcing usually causes additional work when upgrading kernels.

At least with my limited time, using these experimental kernel branches is not really an option, considering I'm trying to provide a ROM here that is as stable as possible. It's simple to do this if you compile your own kernels because you can switch back and forth as you wish, but most users here just use the provided builds as-is and don't compile their own kernels.
[MeMO Pad 7 Original Android Development] Simon555:
Hey, a few days ago I was trying to build Resurrection Remix Nougat using your sources (sorry if this is stupid, this was my first time building a ROM, so I'm not really sure how it's done), and after copying your platform manifest I couldn't sync because it couldn't find the LineageOS projects (I've noticed that they were in a separate file "rr-n.xml" which was added to the manifest using include).

So I then edited the platform manifest - deleted the patched projects it couldn't find (everything under the "Patched AOSP/LineageOS projects" except bootable_recovery and system_netd), synced the repo and tried building, it was going for a while but eventually an error occurred (I think it had something to do with the sepolicy).

So i guess the question is: Are these patched projects LineageOS specific? If not, is there a way to make it find the RR specific projects? Or do I have to somehow patch the RR projects to make sure it builds properly, or should I just try building it without any of your patched projects to see if it works? Again, sorry if this doesn't make sense, and thanks in advance.

Also i'm pretty sure I found a typo in the vendor setup.sh, at line 21 "$MEDIASDK_OMX_DOWNLOAD" should be "$MEDIASDK_DOWNLOAD", otherwise the download 404s :)
[MeMO Pad 7 Original Android Development] lambdadroid:
If this is your first time building a ROM then I'd suggest you compile the ROM as-is as a first step to see if it is working at all :)

Although the device tree relies on some LineageOS features, most of my patches are not specific to LineageOS. They are mostly backported commits from newer Android versions that are needed to make it run on newer kernel versions. You can probably apply most of my changes easily on top of the RR repos.

To do this, it's probably easiest if you remove https://github.com/me176c-dev/andro...b8c1720422f90f96de/lineage_me176c.xml#L44-L63 from the manifest, and then manually apply my changes to the RR repos. Then you need to go through all repositories you just removed from the manifest, check my fork on GitHub, and re-apply all changes made by me.

E.g. for "android_system_core", you'd:

Go to system/core in your RR workspace

Add my fork as Git remote:

git remote add me176c https://github.com/me176c-dev/android_system_core.git

Fetch my changes:

git fetch me176c cm-14.1

Go to https://github.com/me176c-dev/android_system_core/commits/cm-14.1, take the first commit not made by me and copy its commit ID/reference. E.g. in this case this is https://github.com/me176c-dev/android_system_core/commit/e025b0c94fb1609cf54865e4ccaf57821a0aef60 and the commit is e025b0c94fb1609cf54865e4ccaf57821a0aef60.

Apply all my changes to the RR repo:

git cherry-pick e025b0c94fb1609cf54865e4ccaf57821a0aef60..me176c/cm-14.1

And this for each repository I've made changes for as listed in the manifest. This is probably quite a bit of work; let me know if you need further help.

Alternatively, depending on the state of RR for Android 9 (Pie) you could try my experimental lineage-16.0 branch. It's not documented well yet, but it works mostly and requires much less patches (basically just 2 simple ones, although it should even boot without them).

That seems to be correct; thanks for letting me know :)
[MeMO Pad 7 Original Android Development] Ruben Craveiro:
Is it possible to get the app drivedroid to work on this device? I've used this app on multiple devices and in this device it doesnt work, it isnt able to find any type of usb.. (basically changes the usb mode so it thinks its a pen drive that loads from a specific image file - thats what the app does)
[MeMO Pad 7 Original Android Development] lambdadroid:
It doesn't appear to be open-source so I cannot check in detail, but I'd guess that it is not compatible with the new USB "configfs" configuration that is used in Linux 4.9+ (so only very recent models). The old method is no longer supported, so I don't think there is anything I can do on my side. You will need to ask the developers of the app for support.
[MeMO Pad 7 Original Android Development] andrococo:
hi guys,

I keep losing Wi-Fi. Everything else seems good.

any help?
[MeMO Pad 7 Original Android Development] mike0800:
Agreed. It goes on and off, but sometimes hold it longer.