yashsingh1/xdaforums huggingface dataset:
[MeMO Pad 7 Original Android Development] Weegee1:
Hello. I flashed this rom clean install and i also flashed magisk. Everytime i try to install a module through magisk i get this and it doesn't install. Any tips to fix this

Edit: sorry for the low quality picture it says, Efilinux error [start_boot_logic:498] No valid target found. Fallback to MOS
[MeMO Pad 7 Original Android Development] Nexive:
Download the module and flash it with twrp recovery, then it will work. :)
[MeMO Pad 7 Original Android Development] Weegee1:
Didn't think about that. It works thanks :good:
[MeMO Pad 7 Original Android Development] lambdadroid:
Is it supposed to work directly through Magisk? In that case, logcat would be helpful. The error message in the bootloader doesn't mean anything, just that the device was rebooted with no explicit target (e.g. recovery).
[MeMO Pad 7 Original Android Development] Nexive:
It is supposed to work directly. It worked directly before. I will send you a logcat when I'm back home.
[MeMO Pad 7 Original Android Development] Weegee1:
I don't know which one you need so here's the logs I could find
[MeMO Pad 7 Original Android Development] lambdadroid:
The install log is only somewhat useful. Can you post the system log (using logcat) instead? See https://wiki.lineageos.org/logcat.html. Note that you need to capture the logs while you're installing the Magisk module.
[MeMO Pad 7 Original Android Development] Weegee1:
Is this what you want? (Had to put it in a zip file because it was a couple of bytes over the threads limit)
[MeMO Pad 7 Original Android Development] lambdadroid:
Not sure, but that might be a problem in Magisk. Could be related to:

avc: denied { write } for path="/data/adb/magisk_merge.img" dev="mmcblk2p16" ino=440655 scontext=u:r:kernel:s0 tcontext=u:object_r:adb_data_file:s0 tclass=file permissive=0

Since I haven't seen this without Magisk before, it may be missing some needed SELinux rules. Those are manually patched in by Magisk so I don't control them directly. Until a few versions back, SELinux was not in enforcing mode which might be why it was working on older builds.

It might also work if you temporarily run "setenforce 0" as root using a shell before installing a new Magisk module (it will be set back to default after a reboot).
[MeMO Pad 7 Original Android Development] n30wav3:
First of all. I would like to really commend on your efforts of bringing Lineage OS to this device. For some reason Asus really dropped the ball on this device. This atom processor, if optimized properly could have yield better results compared to ARM processors of its time. E.g. I still get better latency on this tablet while using it for Nvidia GameStream compared to Nvidia Shield tablets which were specifically made for that purpose.

Anyway, I think it's the effort of guys like you which is keeping Custom Android relevant in the marketplace so Kudos on your efforts here.

Now I flashed your latest build on the tablet couple of days ago. I am thinking of giving it to my daughter to run Leappad Academy for the most part but she also use it to watch videos in Youtube kids etc. YouTube kids is taking about 2 mins to start. The app freezes as soon as it tries to change orientation. I am thinking it could be related to that but it could also be related to video drivers as the screen flashes red and then green before the app gets to its menu.

I am seeing something similar on standard YouTube app. Sometimes the screen freezes when orientation changes or if you change the screen from full screen to normal mode. I haven't captured a CatLog yet but I can do this If you are willing to look at this. My current setup is your latest build + Magisk Root + Xposed (linked on OP)

Let me know
[MeMO Pad 7 Original Android Development] lambdadroid:
Yes, please post a copy of your logcat shortly after you run into these problems. I personally haven't seen any freezes with the standard YouTube app recently. Another suggestion would be to try without Xposed (and possibly, although much more unlikely also without Magisk). I don't test these very often.
[MeMO Pad 7 Original Android Development] lambdadroid:
LineageOS 14.1 (2018-04-21) now available

Note: 2018-04-21 has been released to fix issues with charger detection on 2018-04-20.

Announcements

me176c-boot, a custom bootloader I’ve been working on for a while is now available. Just like the old unlocked bootloader, it is able to boot custom ROMs. However, it is much simpler, fully open-source and designed specifically for this device.

The old bootloader will likely stay working in the future, but from now on me176c-boot is recommended for use with this ROM.

me176c-boot is (optionally) able to dual-boot into a regular Linux distribution. More information coming soon!

Improvements

Android security patch level: April 5, 2018

Updated CPU microcode to 836 (2018-01-10) - includes Spectre-related fixes

Fixes

Fixed crash when playing webm videos (#50)

Other changes

Updates: LineageOS, Linux (4.14.29 -> 4.14.35), Mesa (17.3.7 -> 18.0.1)

Download

Installable ZIP: lineage-14.1-20180421-UNOFFICIAL-me176c-signed.zip
[MeMO Pad 7 Original Android Development] Nexive:
Flashed the new bootloader and after that succesfully flashed the new lineage build.

Thanks Lambda! :)
[MeMO Pad 7 Original Android Development] jerbear294:
Oh yeah, I noticed that popped up on GitHub a while back; glad to see it's out!
[MeMO Pad 7 Original Android Development] Nexive:
Yes Lamdbadroid is still developing this ROM.

If you follow his Github, you can see the things he is doing at the moment to make this ROM better. :)
[MeMO Pad 7 Original Android Development] lambdadroid:
Correct! I was on vacation the last 3 weeks but I'm back now and have continued development. I will probably release a new update in a few days after the new security patches (August 2017) have been published.

Current changes for next build:

Added headphone detection (experimental)

Added support for running ARM apps (Can be used to run Netflix. The latest version has issues but an older version is working fine.)

Added microphone support

Minor power management improvements (device should get less hot now, also you can switch between different power profiles in the settings (e.g. power save, balanced or high performance).
[MeMO Pad 7 Original Android Development] Ruben Craveiro:
Thats amazing, but unfortunatelly i wont be able to do try it once it gets released, since im in switzerland till september 4rt... I'm really thankful your going to add support for headphone detection and netflix support, its all i need
[MeMO Pad 7 Original Android Development] jerbear294:
Hello, new daily driver.
[MeMO Pad 7 Original Android Development] lambdadroid:
Unfortunately, I haven't managed to solve the hard part yet - make the tablet go into a low power state when suspending. It still expect it have more battery drain than the original ASUS system. :/
[MeMO Pad 7 Original Android Development] bryandroid98:
I'm waiting the update, thanks dude for you work.
[MeMO Pad 7 Original Android Development] NahuelMS:
I am waiting for bluetooth and the draining fix and then it will be my daily driver for sure. Thanks a lot!

Pd: It is stable? I mean it doesn't restart or get stuck like asus LP?
[MeMO Pad 7 Original Android Development] lambdadroid:
It freezed one or two times for me in the whole time I've been working with it. In my opinion it is stable enough for daily usage but you should not expect a rock-solid device (not yet anyway).
[MeMO Pad 7 Original Android Development] NahuelMS:
This device work like **** since i bougth it. 2 months after buying it updated to lp and become a paperweigth. 2 years after that someone managed to downgrade to kitkat but KK is obsolote and has a lot of bugs. So for me if this work is like getting a usable tablet like 2.5 years later hahahaha

Thanks a lot!
[MeMO Pad 7 Original Android Development] jerbear294:
I actually got the stock ROM in a decently usable state. I'm using a debloated ROM, and from there I removed Google Play services on top of it.
[MeMO Pad 7 Original Android Development] lambdadroid:
Agreed, LP was at least kind of usable if you removed all the bloat. Unfortunately I didn't find a way to have more free RAM available for apps without disabling/removing Google Play services (and unfortunately I needed it for some apps). The other thing I found really annoying was the crappy UI and the fact that we haven't got security updates since December 2015 (or something like that). Nougat is just much nicer. :)
[MeMO Pad 7 Original Android Development] lambdadroid:
LineageOS 14.1 (2017-08-10) now available

Upgrade notes

When coming from the ASUS system please make sure you do a full factory reset before installing LineageOS 14.1.

When coming from the preview version of LineageOS 14.1 (released in July) you must either flash lineage-lambdadroid-migration-signed.zip before flashing the update or do a factory reset.

New features

Added headphone detection (experimental, make sure no audio is playing when switching between speaker and headphones)

You can now use Netflix (the latest version is not working currently, but you can use an older version that is available on the Netflix website. The only limitation is that you cannot download videos.)

Added Microphone support (quality is pretty bad though, not sure why)

Added support for running ARM apps

Improvements

Security patch level August 5, 2017

Minor power management improvements (reduced heat; you can now switch between different performance profiles in the battery settings)

Reduced delay when enabling WiFi

Fixes

Fixed Internet connection after reconnecting WiFi

Fixed display of internal storage size: Shows the correct size now

Device should be no longer recognized as emulator by some apps

TWRP recovery improvements

Fixed splash screen

Fixed Permission denied when mounting /factory error

Serial number is now loaded correctly, if you've made backups with the old TWRP version (or the one from the unlocked bootloader thread) you may need to move the backup folder so TWRP can find your backups. To do that, connect your SD card to your PC, go to TWRP/BACKUPS and rename the folder there to the serial number you can find in About -> Status -> Serial number.

Download

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

TWRP recovery image (recommended): twrp-recovery-3.1.1-20170810-UNOFFICIAL-me176c.img

lineage-lambdadroid-migration-signed.zip (flash only if you don't want to make a factory reset and had the preview version installed before): lineage-lambdadroid-migration-signed.zip
[MeMO Pad 7 Original Android Development] NahuelMS:
I am in the same situation but K.K is so slow for me, don't like it and LP was unstable, after debloating and everything. I will just wait for this room, thanks!
[MeMO Pad 7 Original Android Development] Nexive:
I came from the preview build and did a clean flash.

Device booted up. I am installing the necessary apps now that I need.

Headphone detection works, a lot more apps are compatible in the Play Store.

I can change the performance profiles in settings and kernel manager let me choose between powersafe and performance as cpu governor.

Storage shows the size correctly now.

So far no WiFi issues and no reboots.

I was already happy with the state of the preview build so you can imagine how happy I'm right now with this build. :D

You are doing a great job by building this ROM for our device. So, many thanks to you!! :)
[MeMO Pad 7 Original Android Development] lambdadroid:
Thanks! I appreciate the feedback :) There is no need to use a kernel manager to switch between the CPU governors because that's one of the things the performance profiles do. :)
[MeMO Pad 7 Original Android Development] groovychap:
You're doing some amazing work.

Thank you!
[MeMO Pad 7 Original Android Development] Nexive:
I don't know if it's just me but MTP doesn't work on the preview build and on this build.

I pulled the notification bar down and chose Transfer files but Windows can't install the drivers.

I installed the Intel USB drivers but nothing changed.

I did this on 4 PC's and none of them installed the drivers correctly.

Fastboot and ADB connection works.

Am I doing something wrong?

Also, the backlight stays on when you put the tablet in standby.
[MeMO Pad 7 Original Android Development] jerbear294:
Just tested on my computer and I am having issues with MTP as well on Arch Linux.

My computer recognized the tablet immediately once I tapped "Transfer files", and I can view the files on the tablet via MTP just fine. What I can't seem to do is transfer files to the tablet. It'll just hang and never finish.
[MeMO Pad 7 Original Android Development] groovychap:
Is it possible to enable root access on the latest version?
[MeMO Pad 7 Original Android Development] jerbear294:
I flashed Magisk to achieve root access with no issues.
[MeMO Pad 7 Original Android Development] Ruben Craveiro:
can i install this bootloader and still use the stock version, seems nice to be able to dualboit
[MeMO Pad 7 Original Android Development] lambdadroid:
Yes, the bootloader should also be able to boot into the stock ROM. (I don't test that very often, but it has worked before..)

If you're interested in dualboot, it's technically already working but I'm still working on some details. Installation is somewhat tricky because the kernel needs to reside on the internal storage, while everything else can be on the external SD card (the tablet can't boot to the external SD card directly).
[MeMO Pad 7 Original Android Development] AdmiralDock:
Thanks, webm files play perfectly across apps now (except the ones that are encoded in too high a bitrate for the device to handle, but they still work to an extent) :)

EDIT: Also looking forward to trying out some dualbooting in the future! Thanks for your hard work on this aging device :D
[MeMO Pad 7 Original Android Development] AdmiralDock:
Haha I hate to be the bearer of bad news, but the latest ROM seems to not be able to charge my device anymore, while booted it does not detect a charger at all, and while off it just goes into a bootloop with the intel logo, showing the charging battery icon and then rebooting.

I'll try a complete wipe and see if that fixes things.
[MeMO Pad 7 Original Android Development] lambdadroid:
*****. I had some uncommitted changes in the device configuration (or more specifically the kernel configuration), which disabled the old charger detection driver in favor of a newer one. It was still WIP so I dropped the kernel changes for the new driver but apparently forgot to reset the kernel configuration. Which means the charger detection driver is now missing in the latest update...

Obviously this is also the one thing I didn't test before releasing the update... Guess I will need to build again later and upload a new build. Thanks for reporting!
[MeMO Pad 7 Original Android Development] lambdadroid:
LineageOS 14.1 (2018-04-21) now available

I've uploaded a new build that fixes charger detection as reported by [MENTION=8658809]AdmiralDock[/MENTION]. 2018-04-20 has been removed and is no longer available for download.

The original update post is updated with the new download link: https://xdaforums.com/showpost.php?p=76292667&postcount=378
[MeMO Pad 7 Original Android Development] n30wav3:
Alright so I have clean flashed your latest rom + pico gapps+ OP root and it seems slightly better when using YouTube kids. It's not getting stuck per say but it's still stuttering for like a min when executing the app. Logcat attached
[MeMO Pad 7 Original Android Development] MKKLR21:
Since 20180322 the accelerometer in my device isn't working any more. How can I test if it's hardware failure?
[MeMO Pad 7 Original Android Development] lambdadroid:
First try to power off the tablet, wait a few seconds, then turn it back on. The accelerometer isn't working after reboots (see https://github.com/me176c-dev/android_device_asus_me176c/issues/7)
[MeMO Pad 7 Original Android Development] MKKLR21:
Due to the missing deep sleep state, I always power off my device. I'm only using it frequently.
[MeMO Pad 7 Original Android Development] lambdadroid:
I've checked this myself and was able to reproduce freezes when starting the app. I think a relevant line from the log is:

E/Fence (180): HWComposer::fbPost: fence 32 didn't signal in 3000 ms

However, that isn't really helpful. The actual cause is funny: There seems to be some bug in the hardware accelerated video decoder that is causing the screen to freeze. This bug is triggered by the splash screen video. If I disable the hardware accelerated video decoder, the app displays the splash screen video and starts fine (although the tablet is much slower playing videos). If I extract the splash screen video from the APK and play it in the gallery, it freezes in a similar way.

Unfortunately, the hardware video decoder is also one of the very few "black boxes" in this ROM. It is proprietary, and as such I do not have access to the source code or any ways to debug it further. I'm not sure I can fix the bug directly.

Right now, I'm not sure what's the best way to avoid this problem. Going into /data/data/com.google.android.apps.youtube.kids/files/android/default/all/intro_videos/v1 with a root file explorer and deleting the files there seems to avoid the splash screen for a short while, but I'm not sure how quickly it will re-download these.
[MeMO Pad 7 Original Android Development] lambdadroid:
Other options:

Check on stock ROM (could be an issue in this ROM)

Disable auto rotation, then open a root shell and run "cat /sys/bus/iio/devices/iio:device0/in_accel_*_raw" several times. If the displayed values don't change something's probably broken.
[MeMO Pad 7 Original Android Development] n30wav3:
That my friend works for me fine. My daughter was actually able to spent the whole day yesterday without complaining about the tablet being stuck as well so I think your latest rom without magisk and xposed works better already

Although TBH having an unlocked efi bootloader is almost enticing me to use this tablet for myself now. To think about ubuntu, windows 10 etc just for fun... and the prospect looks delicious
[MeMO Pad 7 Original Android Development] lambdadroid:
Don't overestimate this tablet :) The CPU isn't comparable to a desktop system, although the real showstopper is RAM (only 1 GB) and I/O speed of the external SD card. You should expect things to be rather slow, although it works well as a portable Linux shell for me.

Windows 10 is probably not going to run at all from the external SD card. You could destroy your internal storage and install it there using the installer, but you'd be missing all sorts of drivers etc making this even worse. ;)
[MeMO Pad 7 Original Android Development] n30wav3:
Hmmm.......

https://docs.microsoft.com/en-us/wi...-hardware-requirements-summary-for-windows-10

I know Asus really crapped us out with 1GB on a chipset which supported 4GB..BUT...

it's a quad core proc which should be allowed to go to 1.8GHz

It easily satisfies the minimum requirement for 32 but version of windows 10 for desktops OR windows 10 IoT core with display in terms of proc and ram

As far as storage goes, can we not in theory partition the internal storage if possible now that we have access to bootloader and kernel? What about utilizing multirom?

Does your dualboot implementation works with two separate storage devices at this time?
[MeMO Pad 7 Original Android Development] lambdadroid:
OK, dunno. You're welcome to try it, but as I said, this won't work well due to missing drivers etc.

Yes/no. The bootloader can only directly boot from the internal storage (or USB if you have a powered OTG hub). However, for Linux, only the kernel and initial ramdisk need to reside on the internal storage. The actual root file system can then be located on the external SD card.

We could re-partition the internal storage, but considering it's only 16 GB I don't think this is worth it. It's not enough space for two separate systems.
[MeMO Pad 7 Original Android Development] Ruben Craveiro:
how would you manage to make multirom work tho?ive tried building it for my phone but its quite complicated so i gave up... And by the way, with this bootloader, we could simply theoretically, download the remixos iso and boot it from uefi and install it on external sd allowing dualboot with android stock/custom rom + remix os? What i see wrong about this maybe the drivers wont work properly?
[MeMO Pad 7 Original Android Development] jerbear294:
Keep in mind that this tablet is very atypical, has a full UEFI built-in, and that the open source bootloader is derived from PC UEFI booting solutions (like gummiboot/systemd-boot). Dual booting on a setup like that is much easier than a typical MultiROM.
[MeMO Pad 7 Original Android Development] Ruben Craveiro:
I updated the post, has a few more questions than the post u awnsered, sorry about that.
[MeMO Pad 7 Original Android Development] lambdadroid:
I don't know much about multirom but as far as I know it works on a higher level: When you start your device it boots a regular kernel which has all the needed drivers built-in. When you select a boot option, it loads the kernel and initial ramdisk to the RAM and reboots the device. It depends on having the contents of RAM persist after reboot so it can then boot into the loaded kernel cleanly.

There are some more details I'm not sure about, specifically the needed "kexec hardboot" patch set. It applies only to ARM64 code though, so it wouldn't work as-is on this tablet.

In any case, me176c-boot is a low-level UEFI application and does not require booting into a (Linux) kernel. It can boot into the selected boot option directly, without having to reboot the device. It is therefore also much faster, especially considering the tablet sometimes takes several seconds to start the booting process.

You could probably do this with some modifications to the Remix OS boot process. (Specifically making sure the kernel and initial ramdisk are on the internal storage...)

However, without a custom kernel some of the components won't be working correctly. Also, considering the display is rather small, there is no (inbuilt) mouse and keyboard, I'm not sure if using RemixOS would provide any advantages. And it would definitely run worse than the LineageOS ROM because I've spent quite some time optimizing it for this device (especially the low amount of RAM).
[MeMO Pad 7 Original Android Development] Nαi:
Hi, I have a problem with turning the screen. He does not work. The settings are correct. If you need a log, I'll add it.
[MeMO Pad 7 Original Android Development] lambdadroid:
Are you referring to screen rotation? If so, please try powering off the tablet, then wait a few seconds and power it back on. Screen rotation isn't working properly after restarts.
[MeMO Pad 7 Original Android Development] Nαi:
Yep, this. Has helped turn off, and then turn on the tablet. Thanks.
[MeMO Pad 7 Original Android Development] lelecureuil:
didn't think i'd find someone still making ROM for this tablet, but XDA never disappoints. thank you for your work!