yashsingh1/xdaforums huggingface dataset:
[MeMO Pad 7 Original Android Development] maaub:
I honestly can't believe each version actually gets this tablet better and better every time.

A couple things I've detected:

The occasional screen rotation bug has returned (rebooting the tablet seems to fix it)

For some strange reason I can't grant apps Notification access (for example for Greenify or media controls in ASAP Launcher)

Ever since Nougat, if I'm connected to Wi-Fi and connect my BT keyboard (Logitech K420), the Wi-Fi starts acting slow or perhaps even disconnecting intermittently. This I've tried many times in different networks and it's more or less the same result.

I can't enable split screen for any app. I've enabled the "force all apps to be rezisable" option in Developer options, I have reduced the screen density but for every single app it says "this app is not compatible with Split screen". In Nougat it used to work with every app but now I can't seem to work it out

If you have any workaround for these problems or need additional help to track them down, please let me know how I can help you.
[MeMO Pad 7 Original Android Development] jerbear294:
This one is intentional. This ROM is using Android Go since this tablet is definitely considered low end at this point, and Android Go lacks split screen support. It likely wouldn't work well on Pie either way.
[MeMO Pad 7 Original Android Development] Nexive:
[MENTION=6833678]lambdadroid[/MENTION] I flashed to latest version a few weeks ago and the rom was working fine.

Last week, I let my tablet the whole night on so the battery was completely empty (I think)

So I took a charger and let the tablet charge the whole day but I noticed that there was no offline charge screen or backlight. (I was using the stock offline charging method and it was working fine till now)

Then I took another charger and cable but still te same. Computer also doesn't recognize the tablet when plugged in.

I cant turn on the tablet (hold the power button longer than 30 seconds but still nothing, not even backlight).

Going into fastboot doesn't work also.

Is there a way to charge the battery or to turn on the tablet?
[MeMO Pad 7 Original Android Development] Nαi:
1. It looks like the battery is in deep discharge. 2. You can charge up through the laboratory power supply. Also, I advise you to search in the search engine "deep discharge".
[MeMO Pad 7 Original Android Development] lambdadroid:
Was it ever not present?

Not sure. I don't think I have done anything to break this. It doesn't quite sound like a device-specific option I haven't enabled.

WiFi and BT use the same antenna and unfortunately the coordination between them ("WiFi/BT coexistence") isn't working great for some reason. I'm not sure if it's a driver problem or a problem in the (proprietary) firmware. It got even worse when I tried upgrading the WiFI firmware (WiFi stopped working entirely once BT is connected). I don't have any solution for this at the moment.

I believe re-enabling split screen support is as simple as removing the "ro.config.low_ram=true" system property (manually or with Magisk or ...), although this will likely also disable some low RAM optimizations. I have enabled these by default on purpose, but feel free to investigate how you can disable them.
[MeMO Pad 7 Original Android Development] lambdadroid:
That's not good. Something similar happened to me when I started working on this ROM. I didn't have any battery or charging driver yet so I wasn't aware the battery was empty. Eventually the tablet didn't turn on anymore. I'm not sure if the backlight turned on when I tried connecting the charger. Back then I read somewhere that it may help to unplug the battery connector, wait a bit, and try again after plugging it back in. That's my only suggestion, unfortunately this tablet is not very reliable when the battery is completely empty.

Anyway, back then my problem was that I wasn't as lucky to have the stock offline charging option. So I was stuck without q boot partition that can charge and the tablet died after a few seconds even with the charger connected :) I'm not very familiar with charging batteries with external chargers, so what I did back then was to write a custom UEFI application (like a bootloader) that flashes the stock boot image to the boot partition. I placed it on a USB flash drive and was lucky enough that it survived long enough to load it from my USB OTG hub with external power supply. After that I was able to boot into the stock charging screen ;)

But I think that part should work fine now with the stock offline-charging option of me176c-boot. But it's not helpful as long as the backlight does not even turn on.
[MeMO Pad 7 Original Android Development] homopetteri:
[MENTION=6833678]lambdadroid[/MENTION] is this rom compatible with ME572CL - if not, would you consider compiling unified rom for it?
[MeMO Pad 7 Original Android Development] Nαi:
[MENTION=9906361]homopetteri[/MENTION], ASUS MeMO Pad 7 ME572CL 16Gb use PowerVR G6430 GPU. Nothing not will be work. GPU driver - proprietary and not have source code.

If you interest: closed source code in userspace, not kernel...
[MeMO Pad 7 Original Android Development] jerbear294:
Does the ME572CL even have an unlocked bootloader?
[MeMO Pad 7 Original Android Development] lambdadroid:
FYI, I tried to reproduce this but so far I have been unable to. Not sure why... It detects it correctly without error:

[ 56.358651] phy phy-dwc3.1.auto.ulpi.0: Detected charger type: DCP
[ 56.360043] android_work: did not send uevent (0 0 (null))
[ 56.398473] bq24192 i2c-TIBQ2419:00: bq24192_set_inlmt:1246 1200
[ 56.399803] bq24192_cable_callback AC_IN
[ 59.916836] android_work: did not send uevent (0 0 (null))
[ 59.932324] phy phy-dwc3.1.auto.ulpi.0: Detected charger type: NONE
[ 59.933225] bq24192_ac_unlock
[ 59.933231] bq24192_cable_callback CABLE_OUT
[ 62.545428] phy phy-dwc3.1.auto.ulpi.0: Detected charger type: DCP
[ 62.546802] android_work: did not send uevent (0 0 (null))
[ 62.585328] bq24192 i2c-TIBQ2419:00: bq24192_set_inlmt:1246 1200
[ 62.586328] bq24192_cable_callback AC_IN
[ 62.713755] Input source: 32
[ 62.713770] bq24192 i2c-TIBQ2419:00: bq24192_set_inlmt:1246 1200
[ 65.076729] android_work: did not send uevent (0 0 (null))
[ 65.092534] phy phy-dwc3.1.auto.ulpi.0: Detected charger type: NONE
[ 65.096259] bq24192_ac_unlock
[ 65.096270] bq24192_cable_callback CABLE_OUT
[ 67.025791] phy phy-dwc3.1.auto.ulpi.0: Detected charger type: DCP
[ 67.026755] android_work: did not send uevent (0 0 (null))
[ 67.067383] bq24192 i2c-TIBQ2419:00: bq24192_set_inlmt:1246 1200
[ 67.068504] bq24192_cable_callback AC_IN
[ 67.126748] Input source: 32
[ 67.126770] bq24192 i2c-TIBQ2419:00: bq24192_set_inlmt:1246 1200
[ 68.525109] android_work: did not send uevent (0 0 (null))
[ 68.544094] phy phy-dwc3.1.auto.ulpi.0: Detected charger type: NONE
[ 68.545488] bq24192_ac_unlock
[ 68.545500] bq24192_cable_callback CABLE_OUT
[MeMO Pad 7 Original Android Development] lambdadroid:
LineageOS 16.0 (2019-09-22)

Android security patch level: September 5, 2019

Updates: Linux (4.19.68 -> 4.19.75), Mesa (19.1.4 -> 19.1.7)

Addons

Widevine/Houdini: Recommended version updated to 12239.92.0_nocturne

Download: lineage-16.0-20190922-UNOFFICIAL-me176c-signed.zip
[MeMO Pad 7 Original Android Development] Nαi:
In Android OC and TWRP device view:

lsusb
Bus 002 Device 024: ID 0b05:7773 ASUSTek Computer, Inc. Zenfone GO (ZB500KL) (Debug, MTP mode)

Can fix?
[MeMO Pad 7 Original Android Development] lambdadroid:
I think that display name is based on the USB ID (i.e. 0b05:7773). I suspect ASUS has re-used the IDs from a different device or the ID database is incorrect. Either way, as far as I know these are the USB IDs used by the stock ROM, so I wouldn't know what to change them to.
[MeMO Pad 7 Original Android Development] Nexive:
I unplugged the battery connector and left it for an hour and then plugged it back in. Suddenly the backlight was turning on and I took immediately a charger to charge it and turned it on. The tablet is working fine now! Thank you for the suggestion to unplug the battery!
[MeMO Pad 7 Original Android Development] Surikan:
works perfect!
[MeMO Pad 7 Original Android Development] Surikan:
[MENTION=6833678]lambdadroid[/MENTION], I found one issue, whereat I'm not sure if this is issue or supposed to work this way. If connecting to wireless network (WPA2), it#s not possible to connect to hidden SSID. Once I change configuration of my router to broadcast the SSID the is no problem to connect. Can you please let me know if its a bug or this supposed to work like this due to some limitation. As far I remember I didn't hat this issue with your build 14.1 for the MeMO Pad 7 on the same device.
[MeMO Pad 7 Original Android Development] lambdadroid:
I replaced the WiFi firmware with the one from the stock ROM at some point, but otherwise I didn't do anything to break it. Could be also some change in Android that is preventing it to work.

However, in my opinion, using hidden SSIDs is really a bad idea anyway. It usually does exactly the opposite of what you expect it to do: if you connect to a network with hidden SSID, the device needs to actively scan for the network to see if it is available. This means when you are away from home, it might start scanning for your WiFi network and leak your hidden SSID to everyone around you.

See e.g. https://www.howtogeek.com/howto/286...hiding-your-wireless-ssid-really-more-secure/

So IMO the better fix here is to stop using a hidden SSID ;)
[MeMO Pad 7 Original Android Development] Surikan:
Thank you for the quick reply. I know that hiding SSIDs doesn't really contribute to the security of my WLAN. I'm just used to have it hidden. I think I will consider to deactivate hidden SSID and look for another way to secure my wifi.
[MeMO Pad 7 Original Android Development] ISmikeAir:
Can someone give me a google drive share with the widevine drm zip that is need to install with TWRP.
[MeMO Pad 7 Original Android Development] jerbear294:
The license forbids redistribution, so this would not be legal. There's a reason it's not available for download to begin with.
[MeMO Pad 7 Original Android Development] lambdadroid:
This is the reason why I don't want to redistribute it. But I cannot do much if someone voluntarily posts a link in this thread (I guess there are already some).

Clearly, almost all people involved in Android modding do not really care about this, since pretty much all ROMs etc include many proprietary blobs, including Widevine, without separating them like I did. And I guess they don't have much choice: if the ROM does not work at all without them it doesn't make sense to keep it separate.

But with this ROM I have the opportunity that most things work with only very few proprietary blobs. I don't have to redistribute files that were never intended to be used for this tablet. And everyone using the ROM has the choice to install it only if they really need it. It makes installing the ROM with full features a bit more difficult, but I still think this is the best solution.
[MeMO Pad 7 Original Android Development] kws5013:
RE: me572c

Hi mates,

would anybody know is it working for me572c?
[MeMO Pad 7 Original Android Development] jerbear294:
No, the ME572C is an entirely different device.
[MeMO Pad 7 Original Android Development] kws5013:
pretty sad that couldn't find any ME572's Custom ROM.... :crying:

it's a rubbish device to me now...........
[MeMO Pad 7 Original Android Development] Blassounaldo:
For real... I've just repair my little brother's one and want to change the stock os which has a lot of ****ty app from Asus but not finding a good ROM...
[MeMO Pad 7 Original Android Development] lambdadroid:
LineageOS 16.0 (2019-12-13)

Android security patch level: December 5, 2019

Updates: Linux (4.19.75 -> 4.19.89), Mesa (19.1.7 -> 19.3.0), MediaSDK (19.2.1 -> 19.3.1), …

Addons

Widevine/Houdini: Recommended version is now: 12499.66.0_atlas

Download: lineage-16.0-20191213-UNOFFICIAL-me176c-signed.zip
[MeMO Pad 7 Original Android Development] ISmokeAir:
I have just installed the rom and i have some problems. First , i accidentaly wiped the system and internal storage pratitions i think(in twrp). I dont know if this is the source of my problems. When i am using the device cpu z reports just 1333mhz on all cores and the gpu beeing at 0%. After 5 min almost everything crashes , even the system ui. I have a backup of all partitions and the asus rom , if that can help. I also instaled widevine and the other zips besides signiture spoofing.

h ttps://drive.google .com/open?id=1 S_eP1ZhIlJs5V4cAwIxR9UHimv2qSdQ4 (delete the spaces to acces the link)
[MeMO Pad 7 Original Android Development] lambdadroid:
Wiping the partitions directly available in TWRP (i.e. "System", "Cache", "Data", "Internal Storage", ...) should be safe, as these will be recreated when installing/running a ROM.

In general that just means that your system is busy doing something (potentially related to your crashes).

Please provide a proper log file when these crashes happen, see https://wiki.lineageos.org/logcat.html
[MeMO Pad 7 Original Android Development] ISmokeAir:
What about the gpu? And why isn't the cpu at max speed? I also remembered that the first time i installed lineageos it stayed at 667mhz.

Also i tried to restore the asus os and i got error 1. Here is the log for it.

https:// drive. google .com/drive/folders/1vVdFGqk0mh3lsSzxyhzttfGu3_0WKqzm?usp=sharing (delete the space to access the link)
[MeMO Pad 7 Original Android Development] lambdadroid:
I'm not convinced that the GPU speed is displayed correctly.

By default, the LineageOS ROM disables the turbo CPU states, i.e. 1.3 GHz - 1.7 GHz. You can enable them by setting the power profile at least to "Quick". This was done to reduce heat slightly.

That's a weird error. Have you tried again?
[MeMO Pad 7 Original Android Development] Frisk Dreemurr:
I recently want to reflash the tablet back to stock ROM (and start flashing over again), and want to make rooting easier by pre-flashing Magisk to the boot image with the help of Magisk manager. Yet in the stock ROM pack, there are "boot.img" and "droidboot.img"... Which one should I patch? :confused:
[MeMO Pad 7 Original Android Development] lambdadroid:
droidboot.img is the Fastboot interface.
[MeMO Pad 7 Original Android Development] Frisk Dreemurr:
I got these error messages when trying to flash this stock ROM, even after not modifying the zip package... :confused: Guess I'll use the TWRP backup instead, just reporting to let you know. :)
[MeMO Pad 7 Original Android Development] Frisk Dreemurr:
Hmm... I reflashed the latest ROM, yet the charging current is still low. Weird. :confused:
[MeMO Pad 7 Original Android Development] lambdadroid:
Pretty sure I tested it at some point. I have to do ugly hacks to make the ASUS ZIP package work, because it uses some really old features. Guess they might not be working for some reason.

I suspect this is some problem specific to your device. I'm not saying your device is broken, just that it behaves differently compared to my device for some reason. I don't really know how to investigate this further. The charger detection code is really wonky and to be honest I am glad that it works at least in some situations.

I suggest that you use the workaround you have found, or just use the stock offline charging option of me176c-boot. It's working quite well so I personally never really charge the device from LineageOS (except when it is connected to USB for debugging).
[MeMO Pad 7 Original Android Development] Frisk Dreemurr:
Actually, after a few tries, I found that restoring the stock system bricks my device... I've tried wiping the partition myself first, wiping the internal storage too, yet they lead to the same result... Is there any known reason of this happening? :confused:
[MeMO Pad 7 Original Android Development] lambdadroid:
What does "bricks my device" mean? That sounds like your device is permanently broken.
[MeMO Pad 7 Original Android Development] Frisk Dreemurr:
It's just soft bricked (not able to boot into system), not hard bricked (not able to even boot into recovery or fastboot mode), sorry for not making this clear... :silly: After re-flashing the latest LineageOS 16 ROM offered here it's working fine now, yet I still feel curious of what caused the TWRP restore to soft brick my device. :confused:
[MeMO Pad 7 Original Android Development] ruchri:
[MENTION=6833678]lambdadroid[/MENTION]: Thanks for all the work with this rom! I started with 16.0 shortly after the release in May 2019. Changed back for a while to 14.0 and than again to Lollipop .136 K013

Now I'm running 16.0 almost for a week again and, wow, what a progress has been made! It's running like a charm already!

Amazing: this old lad (device, not me, although 70) is running on Pie! I have never thought this would be possible. Looking forward to further releases.

Many thanks again!
[MeMO Pad 7 Original Android Development] Nikos3234:
Can I install this rom on Memo pad 7 ME173x K00B?
[MeMO Pad 7 Original Android Development] ruchri:
No, device specific as stated in several posts om page 3 of this thread.

And the ME176CX (K013) must have Lollipop as the bottom line (See OP).
[MeMO Pad 7 Original Android Development] T_I:
I just dusted off my MP7 to see if it still worked. The old Lineage 14.1 image was nice. I was amazed that someone took the effort to build a lineage 16 for this oldie.

This tablet got me working on CyanogenMod 13 for the Samsung Tab S2 which I got from my wife after *****ing about this tablet's limitations. :D

Great, thanks.
[MeMO Pad 7 Original Android Development] ponpoco:
Are there any problems at login to amazon.

I'm trying to login to amzon, but I can't and the device say 'Amazon keeps stopping'.
[MeMO Pad 7 Original Android Development] lambdadroid:
Please post the log, from shortly after it happens. See https://wiki.lineageos.org/logcat.html (I probably won't be able to help you, might be a problem in the Amazon app...)
[MeMO Pad 7 Original Android Development] ponpoco:
Thank you for you reply.

I can login to amazon by chrome browser, but I can'n by default browser and prime video app.

default browser log

https://pastebin.com/sPShrKbc
[MeMO Pad 7 Original Android Development] bmw318is-black:
Thank you for your work!

B.
[MeMO Pad 7 Original Android Development] moranop:
I have one problem. The Rom works great, but I have this problem. If i turn off the Tablet, I have to force turn it off 2 o 3 times for make the WIFI working. The 1st time I power on the tablet, it starts with wifi off, I cannot accest to config. It is solved the second o third time that I forced restart the tablet. Anyone had this problem?
[MeMO Pad 7 Original Android Development] Frisk Dreemurr:
Actually I do. :laugh: And that's one of the reasons that push me back to use the LineageOS 14.1 version. I thought it was device-specific...
[MeMO Pad 7 Original Android Development] lanzador:
Same issue here with Wifi, just restarting and restarting come back to works.

Hoping lambdadroid will release new version fixing the issue :)
[MeMO Pad 7 Original Android Development] nico_7t:
toolchain

i wanna compile the kernel what toolchain i can use? any help
[MeMO Pad 7 Original Android Development] groovychap:
I'm looking to downgrade from Lineage 14.1 to Lollipop, so that I can flash this ROM.

When I attempt to do so, I get this error message:

Can anyone advise on how I can resolve this?
[MeMO Pad 7 Original Android Development] ISmokeAir:
Why do you need to downgrade? Can't you flash the new Rom?
[MeMO Pad 7 Original Android Development] groovychap:
In the instructions it says:
[MeMO Pad 7 Original Android Development] ISmokeAir:
Hmm, I didn't know that. Anyway, error 7 means that the phone doesn't meet the rom's compatibility. Before installing the Rom checks if it works on your phone number. You might have an incorect Rom or it is just a bug. If you are sure u got the correct Rom you need to remove the check. You can do that by unzipping the Rom on a computer, Delete the lines that check you model number using notepad++ and zipping the Rom back. Here is a link with instructions. https://xdaforums.com/showthread.php?t=2522762

You can skip step 3 and just right click and then click "edit with notepad++"
[MeMO Pad 7 Original Android Development] neodrake:
Same here, any idea to solve this?

Enviado do meu MI 9 através do Tapatalk
[MeMO Pad 7 Original Android Development] KRoman47:
I'm generally impressed by LOS 16 on ME176CX but I have question. How do games run? It's not primary not even secondary for me but I find strange I can't even play Cut the Rope since it stutters like hell. But maybe I've done something wrong and it's just me who struggles. I remember playing even 3D games on it quite nicely back in the days.
[MeMO Pad 7 Original Android Development] lambdadroid:
I would say that depends on the game. Some simple ones are probably fine. You can try changing the power profile to high performance in the settings to see if that helps a bit. But in general the stock ROM was probably a bit more optimized in terms of graphics performance.
[MeMO Pad 7 Original Android Development] 0LDST4R:
I've got the ME180A, development is dead for my device, could someone post the gps.conf from this rom please?

Thanks in advance,

Greetz,

0LDST4R

_-_-_-_-_
[MeMO Pad 7 Original Android Development] Xnehaxixh:
Can you tell, where that file is located?

---------- Post added at 11:47 PM ---------- Previous post was at 11:32 PM ----------

I just installed LOS 16 today. Going through all the resources available and the instructions. Honestly im impressed with how much work the dev has done on this device, considering x86 to be uncommon and everything well documented. Kudos to the dev!

But my experience with this ROM was not pleasant.

- No variants of GApps work. The Google Play Services crash. So basically you can't add any google account. I've even tried microG, same problem, the gms service crash.

- The ROM is very laggy / not smooth. Don't know what's the reason behind it, maybe it's the graphics driver.

Finally had to resort to use FDroid and Aurora Store.

I mainly wanted to use this tablet as a secondary display using Duet Display. But due, what I assume is caused by the graphics driver, I get green screen on that app and the whole ROM serverly lags, which had made it unusable.

I'm thinking to try LOS 14...