yashsingh1/xdaforums huggingface dataset:
[MeMO Pad 7 Original Android Development] lambdadroid:
With suaddon, did you actually enable root access in the developer options? It's not enabled by default.

For magisk: First remove suaddon using https://mirrorbits.lineageos.org/su/addonsu-remove-14.1-x86-signed.zip Then just flash the ZIP from https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445. You can find all info in that thread.

Yeah, I think the "cast" option uses Miracast and WiFi Direct, which is why it's not working.
[MeMO Pad 7 Original Android Development] jerbear294:
I'd like to add that Magisk has systemless hosts file support, specifically so applications like AdAway function without tripping SafetyNet. This can be enabled in the Magisk Manager settings.
[MeMO Pad 7 Original Android Development] jerbear294:
I've had an issue with this ROM for a while, which I hadn't bothered reporting until now.

Sometimes, music (and rarely video) won't play or will freeze after one or two seconds with headphones plugged in, but other times the audio will show as playing but nothing will be output through the headphones or the speakers. Music takes a lot of fiddling to get working, I'd say it only works about 10% of the time.

I do have Viper4Android installed but looking through a logcat I don't believe that's related.

https://ptpb.pw/9mk8.txt is the aforementioned logcat, which is a fresh reboot up until I managed to get working music through headphones. This logcat has both the freezing and the "ghost playback" issue.
[MeMO Pad 7 Original Android Development] lambdadroid:
The main problem is:

02-09 17:40:55.025 E/AudioIntelHal(324): getFramesAvailable: Unable to get available frames

I personally don't use headphones very often, but I have seen it sometimes when testing. I'm not sure why it happens. However, eventually it didn't happen as often if you 1) stop playing all audio for like ~10 seconds, 2) plug it the headphones and 3) wait another ~10 seconds. Usually, I've seen it happening when plugging in headphones while sound was playing (or shortly after), or when not waiting for a few seconds after plugging in headphones. I guess there might be some kind of race condition in the audio HAL where it doesn't switch the audio output properly.

However, if you just use the speakers (and don't plug in any headphones after a reboot), do you still run into these problems? I personally haven't seen any issues with the speakers so if it also happens with them there might be also another problem.
[MeMO Pad 7 Original Android Development] jerbear294:
This fix is the case for video, but not music, in my experience. Actually, video will usually fix itself if I pause the video, unplug the headphones, play and quickly pause the video again, and plug the headphones in.

MX Player is able to work when Shuttle+ doesn't by switching the audio backend from OpenSL to Java, but that bypasses Viper4Android.

Speakers have always worked, no matter what.
[MeMO Pad 7 Original Android Development] lambdadroid:
And have you tried without Viper4Android? Just trying to rule out possible reasons. Also, can you provide the log from shortly after you have this problem when listening to music (not video)? Otherwise, it's hard to be sure which part of the log actually refers to the problem and not the point where it starts working.
[MeMO Pad 7 Original Android Development] jerbear294:
Same results without V4A.

I am currently away from home with (very) spotty Internet access, so I will provide a new logcat tomorrow.
[MeMO Pad 7 Original Android Development] jerbear294:
https://ptpb.pw/3u1L.txt - New logcat, from boot to an immediate freeze.

EDIT: Poking around a little bit more with MX Player. It only successfully works with the Java AudioTrack audio backend and the HW+ or SW decoders. With the normal HW decoder, or on OpenSL as I mentioned yesterday, the same problem can be observed.

EDIT 2: Actually, V4A does appear to be part of the issue. If I disable headphone processing and start a track, it works successfully, and V4A even processes fine if I re-enable it. That being said, I had this issue with the stock Lineage equalizer too, with V4A still installed but not processing, similarly to this successful run.

It appears that V4A introduces a near-100% reproducible iteration of this issue, although it's also present at random otherwise.
[MeMO Pad 7 Original Android Development] lambdadroid:
Not sure right now, but let's wait a few more days until I release the next update. It changes quite a few things (although nothing related to this as far as I know) so it's not worth investigating this further on the old version.
[MeMO Pad 7 Original Android Development] VasilisGR:
I just booted up my Memo Pad to see if it still works. The last time I remember using it was before 2017. Then i found this rom... I'm surprised that people still care about that device. Flashing it ASAP. PLEASE continue working on it. Do not abandon the project. Thank you :)
[MeMO Pad 7 Original Android Development] lambdadroid:
LineageOS 14.1 (2018-02-16) now available

Announcements

TWRP is now available in a separate thread on XDA.

Optional: Custom build of Xposed that doesn’t cause boot loops: xposed-v89-sdk25-x86-me176c-signed.zip (flash it in recovery)

Major changes

Kernel upgrade to Linux 4.14: Experimental, might break things. More improvements and optimizations coming soon.

Security advisory

Added kernel mitigation for:

CVE-2017-5754 ("Meltdown") using KPTI (Kernel Page Table Isolation)

CVE-2017-5753 ("Spectre V1 - Bounds Check Bypass"): WIP, partial mitigation

CVE-2017-5715 ("Spectre V2 - Branch Target Injection") using Retpoline

Android security patch level: February 5, 2018

Improvements

SELinux Enforcing: Basic testing has been done but this might break some apps. Please report if something is not working correctly. (#39)

Note: You can temporarily switch back to permissive mode by running setenforce 0 in a root shell. (Not recommended - this will undermine parts of Android’s security system!)

SafetyNet passes on standard installation. Note that it will break with Lineage’s su-addon. Use Magisk if you want root without breaking SafetyNet.

Backlight:

Enable all 255 brightness levels. (instead of just 100)

Screen backlight now turns off correctly when shutting down the device. Pressing the power button after shutdown no longer causes the screen to flash. (#4)

Improved brightness handling when turning the screen back on: Previously, brightness was sometimes shortly set to maximum, and then reduced with some delay.

New features

Full disk encryption (optional) is now supported and can be enabled in settings. (#45)

Note: You need to wipe your data partition entirely once using the updated TWRP build to use full disk encryption:

Update to the latest version of TWRP, available in the separate thread on XDA.

Make a backup of all your data, including internal storage. (TWRP does NOT backup files in internal storage, you need to copy them manually!)

Use "Format Data" in TWRP.

Enable full disk encryption in the Android settings.

Fixes

Fixed Chromecast screen mirroring

Other notable changes

Added README on GitHub that explains how to build the ROM.

Moved /oemcfg to /vnddat ("vendor data") to better reflect its purpose.

Updates: LineageOS, Linux (4.9.71 -> 4.14.19), Mesa (17.3.1 -> 17.3.4)

Many other minor optimizations (check commit logs for details)

Known problems

Bootloader displays an error when doing a regular restart. However, it will still restart correctly.

MTP/PTP is now completely broken, the device doesn’t even show up anymore. However, given that file transfers were already broken before I don’t consider this as a regression. You can use ADB to transfer files.

Download

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

TWRP recovery image (recommended): Available in dedicated thread.
[MeMO Pad 7 Original Android Development] profee:
That's a really nice changelog. Thanks for all the hard work. Man.
[MeMO Pad 7 Original Android Development] Nexive:
[MENTION=6833678]lambdadroid[/MENTION] Thanks for the update! It's a big one. :)

I don't have any issues with apps with selinux set on enforcing.

Screenmirroring is working fine . I tested it on Android tv, great job!

Flashed magisk an it's passing safetynet this time. :)

But I don't know if it's just me but the touch sensitivity is weird, especially when scrolling. I don't know how to explain this well but when I'm scrolling/swiping through webpages, youtube or something else, it opens the URL or opens the youtube video instead of scrolling. Its like it does not detect the swipe movement very well.
[MeMO Pad 7 Original Android Development] lambdadroid:
Urgh, I was hoping that was just me. It's something I noticed as well, but it wasn't bad enough to investigate further. For me, links would get clicked randomly when scrolling or I had to try several times to drag an app icon to the "remove" icon at the top of screen... I couldn't say for sure that this hasn't happened before, though. Is this something that clearly started happening after this update?

Issues like these are annoying because it's not easy to track them down. I could try to revert some changes from the touchscreen driver introduced with the kernel upgrade, but we couldn't be sure that's it because it doesn't always happen... On the other hand it could be anything, even minor delays in the touch reporting could probably cause Android to assume swiping has stopped and interpret it as a regular "click".

Edit: As an example, long pressing app icons in the home screen to move them around barely works for me, had to try 3 or 4 times until I was able to drag it around instead of opening the app. Can you try to reproduce this?

Edit 2: Fun. Now it's working again :|

Just out of curiosity, did you use the screen mirroring feature available in the settings, or something like Chromecast? I was assuming the screen mirroring in settings requires WiFi Direct, but seems like this is not required if it's working for you.
[MeMO Pad 7 Original Android Development] Nexive:
Yes, this issue started after the update. Before that I didn't had such issues.

And I did what you said and sometimes I can drag it around but most of the time the app opens.

EDIT: Okay weird, the issue is gone now and it's working again. ?

And about screenmirroring, I'm using the cast option in quick settings to cast my screen to my android tv
[MeMO Pad 7 Original Android Development] lambdadroid:
It's weird, yeah. I can reproduce it sometimes but it doesn't always happen. Given that it doesn't cause any major issues right now, I'm going to leave everything as-is until the next update in a month or so. There is one change that looks potentially related, but obviously it will be hard to fix since there isn't a reliable way to reproduce it.

OK, cool I thought this requires WiFi Direct. In that case I can reduce the priority for that one...
[MeMO Pad 7 Original Android Development] lambdadroid:
[MENTION=5479482]jerbear294[/MENTION] Have you checked if your audio issues are still present on the latest update?
[MeMO Pad 7 Original Android Development] jerbear294:
I haven't, because I haven't installed the latest update yet. I'll do that tonight.
[MeMO Pad 7 Original Android Development] ninjeratu:
Yeah. The touch screen is really over sensitive.

Driver issue like with the old Pixels perhaps?

It's really annoying.

Other than that it's smooth as butter compared to the stock mess.
[MeMO Pad 7 Original Android Development] jerbear294:
Lineage 15.1 has arrived. https://lineageos.org/Changelog-16/

On that note, I just tested for that audio bug and results are identical to the previous build- audio refuses to play until V4A processing is disabled, at which point it plays properly and V4A works again after re-enabling it.
[MeMO Pad 7 Original Android Development] lambdadroid:
Yep, I've seen it. I will probably try to apply my changes I made for Oreo last August again when I have time, but the main reason I've been delaying Oreo is the hardware video decoding implementation: It was broken back then and nothing has changed, so it's likely still broken. I was (and still am) hoping that Android-IA will finally open-source it as planned, or at least provide an update for Oreo, but there were no public updates for about an half year now.

Falling back to software decoding all the time would make the Oreo release rather annoying, given how quickly the tablet heats up with high CPU usage.

It's really annoying, because this is the only (important) closed source component in the ROM, and I'd really like to get rid of it. Even worse, most parts of the implementations are already open-source (e.g. for Linux systems), it's only the Android implementation that's missing. Unfortunately, this is also one of the most important parts and neither trivial to implement nor well documented...

Since 14.1 is working well right now, I'll probably stay on it until this is figured out. Originally, I planned to upgrade to Linux 4.14 together with Oreo, but since I have it working on Nougat now, there are still a number of improvements I can work on: primarily USB OTG and getting suspend working. This is probably worth more than the Oreo upgrade, and I don't feel like wasting any more time on those stupid closed source blobs...

Thanks for testing, when I have time I will try to replicate the problem and see what I can do.
[MeMO Pad 7 Original Android Development] lambdadroid:
So I've just tested this a bit and this is what I was able to reproduce:

No matter if V4A is installed or not, there is no sound on speaker/headphones if you don't wait for ~5 seconds without any sound playing after plugging headphones in or out.

With V4A enabled I need to press play/pause for about 3 or 4 times when playing music until there is sound on the headphones and it plays properly. It doesn't seem to happen as often when playing video.

Is this what happens to you too?
[MeMO Pad 7 Original Android Development] jerbear294:
This happens on my end as well.

This adequately describes my issue. However, for whatever reason the likelihood of music working properly has gone down over time, going from three or four to countless attempts.

Video is still very rarely broken for me, breaking maybe once every two dozen videos or so. I can force that to work by doing the disable/enable trick or usually by just unplugging the headphones and plugging them back in.
[MeMO Pad 7 Original Android Development] lambdadroid:
GPS support

So, I took a few hours to check if there is any way to get GPS working. However, at the end my conclusion was that it is indeed almost impossible without the source code.

The situation on our tablet appears to be the following: the tablet has a combined Bluetooth/GPS chip, which communicate over the same interface. Considering this, it's already surprising that I managed to get Bluetooth working properly. What they did on the stock ROM is hack Android's Bluetooth implementation (bluetooth.default.so) to additionally provide a communication channel for the GPS implementation (located at /data/gps/brcm_gps_unix_socket). Without this change, there is no way the (also proprietary) GPS implementation can communicate with the chip.

Normally changes like these should be made in the device specific hardware implementation (HAL), but for some reason they decided to hack it into Android's Bluetooth implementation directly. Because of that, it is pretty much impossible to port this to newer Android versions - with each major update the Bluetooth implementation is also updated with new features and other changes - the old version wouldn't work at all on newer Android versions. Bluetooth (and GPS) is entirely broken when trying to use it on Nougat.

This does not only affect our tablet, but also some other smartphones from ASUS. For example, if you take a look at one of the ROMs available for the Zenfone 5, and search for GPS in that thread, they describe a very similar setup. They haven't been able to find any solution either.

With that said, it's unlikely that GPS will ever be working on this ROM, at least not unless ASUS releases the necessary source code for this setup. And this is likely never going to happen.
[MeMO Pad 7 Original Android Development] lambdadroid:
Interesting, I never tested it. Good to know that it works out of the box.

However, please note that it will likely stop working with LineageOS 15.1. They recently removed the FUSE implementation of exFAT that doesn't require special kernel support, and changed the rules for official builds regarding exFAT support. If I remember correctly, the stock ROM had exFAT support, so it would be fine to include it, but I'd need to port one of the kernel drivers to the much newer kernel version.

Given exFAT's horrible licensing, this isn't worth the effort. I've personally never needed nor used it and I don't think it's necessary. Unless you need files bigger than 4 GB, FAT32 will probably do the job. Otherwise, LineageOS additionally supports using ext4 or f2fs as filesystem on external SD cards, which will perform much better than exFAT. The only disadvantage is that you cannot read/write the SD card directly from Windows anymore, but there is always ADB (and in the future hopefully MTP too) to transfer files.

I won't change it for the 14.1 builds, but it's unlikely exFAT will be supported once I move on to LineageOS 15.1.
[MeMO Pad 7 Original Android Development] erazordj:
Hello! I installed this rom a few days ago but I have noticed that the touch response of the screen is very bad, when you slide your finger across the screen you run things alone, do you have this same problem? Thank you
[MeMO Pad 7 Original Android Development] Dutch Burdock:
I like the facr GPS and camera are not working, dont feel the need for the tinfoil hat as much. Makes a perfect tablet for the kids now. However, I use mine for my home automation system. Sits out in the hallways providing a HUD of smart appliances etc. For that, it is perfect!

Not an issue for me, I've been playing several games requiring smooth swiping as well as need it for gestures.
[MeMO Pad 7 Original Android Development] jerbear294:
This is a known issue with the latest build.
[MeMO Pad 7 Original Android Development] Dutch Burdock:
ahh, I'm still using 20171222 ?
[MeMO Pad 7 Original Android Development] lambdadroid:
It took a few days of work, but I've now replaced the old (rather complex) Audio HAL with a new, dead simple one and it seems to fix most of these issues. Plugging in headphones should also work while playing audio now, and Viper4Android didn't seem to make any problems with headphones plugged in. One problem remains but it only happens if you plug out your headphones while audio is currently playing. Then audio output will freeze for 10 seconds but should continue playing automatically.

I've built a test build with the audio changes (and a potential fix for touch screen sensitivity), would be nice if you could give it a try. It's not signed so you need to do a backup & factory reset before you flash it.

Download: https://www.androidfilehost.com/?fid=890129502657590294
[MeMO Pad 7 Original Android Development] jerbear294:
I will flash this ROM tonight.
[MeMO Pad 7 Original Android Development] Nexive:
I've flashed this build and I can confirm that the touch screen sensitivy issue is gone. :)

I will test the audio issue later tonight. :)
[MeMO Pad 7 Original Android Development] Ruben Craveiro:
Still going to wait for it to be more usable to play videos on HW and not heating up and stutter like hell
[MeMO Pad 7 Original Android Development] lambdadroid:
Did you have the chance to test it? I'd like to release a new build this weekend but it would be nice if one of you could confirm that switching to headphones works better now.

Basically just play some music or a video on the speakers, plug in your headphones (while it's playing). It should now switch successfully to the headphones without pausing. While playing, try to unplug the headphones again. This is where I ran into problems. Android pauses automatically (this is normal), but if you press play it will stay frozen for another 10 seconds or so. After that, it should automatically continue playing normally.
[MeMO Pad 7 Original Android Development] Nexive:
It does exactly what you said. The audio keeps playing when I plug in the headphones and when I unplug it the audio pauses and the audio plays again after +-10 seconds after pressing the play button.
[MeMO Pad 7 Original Android Development] phagenauw:
Just curious, will there be a new version this weekend (march 17/18) or will it take longer and is it best to use the not signed build (from march 13) which needs a wipe before flashing (and reinstall everything)?

Thanx!
[MeMO Pad 7 Original Android Development] erazordj:
151/5000

I tried this rom today, there is an error on the screen, sometimes a red frame appears that flashes across the screen and is a bit annoying
[MeMO Pad 7 Original Android Development] lambdadroid:
There will be a new version soon™, but I cannot provide ETAs. I have it planned for sometime within the next 7 days.

The unsigned test build is strictly for testing only and you should not use it for anything else. It's insecure, and has various additional debug features enabled by default (for example these red borders as you noticed). You won't be able to upgrade from it to the next release without wiping again.

You should use the last release (from February) until the next version is released. This is also the version that will support upgrading without having to wipe.

Nevertheless, the test build shouldn't have any errors. Could you clarify what "there is an error on the screen" means exactly?
[MeMO Pad 7 Original Android Development] erazordj:
Thank you! I will be waiting..

The error is the red frame, I did not know how to describe it :D
[MeMO Pad 7 Original Android Development] lambdadroid:
LineageOS 14.1 (2018-03-22) now available

Improvements

Android security patch level: March 5, 2018

Improved touch screen sensitivity

Improved audio routing:

Headphones should be more reliable now.

Switching to headphones should now work even while audio is playing.

Other changes

Updates: LineageOS, Linux (4.14.19 -> 4.14.29), Mesa (17.3.4 -> 17.3.7), Houdini (7.1.0a_y.49344 -> 7.1.1a_y.49564)

Known problems

After switching from headphones to speakers while audio is playing, playback will freeze for ~10 seconds. However, it should continue playing automatically.

Download

Installable ZIP: lineage-14.1-20180322-UNOFFICIAL-me176c-signed.zip
[MeMO Pad 7 Original Android Development] AdmiralDock:
Just a quick observation, it seems the last 2 (maybe 3?) rom versions do not seem to have .webm support baked in (I don't really know how android video codec handling works), webm content plays on browsers like chrome or firefox fine, but webm files don't play from the gallery (I know they used to) they do work from a video player such as mpv though. The problem is apps that don't supply their own codec fail to play webm (specifically booru browsing apps and the built in gallery video player). Not really a big issue, just wondering if this was an intentional removal or just something you're not yet aware of.
[MeMO Pad 7 Original Android Development] lambdadroid:
Thanks for the report. I've now fixed this for the next release.
[MeMO Pad 7 Original Android Development] julien_michaud:
HI,

Can I install this ROM on a K01E Asus tablet ?

Thank you.
[MeMO Pad 7 Original Android Development] Ruben Craveiro:
no. different device, different drivers.
[MeMO Pad 7 Original Android Development] Nαi:
Hey. Thanks for working on the firmware. There are some problems with displaying video files. The files are not broken.
[MeMO Pad 7 Original Android Development] lambdadroid:
Does this only affect the video thumbnails, or also when playing the video? I've seen this for video thumbnails before, just never bothered to fix it. I think it's related to the hardware accelerated video codec, but not entirely sure. Might take a closer look at some point...
[MeMO Pad 7 Original Android Development] Nαi:
Yes, this only affects the display of thumbnails. There are no problems with playing the video.