yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] :
Can you also add "Audio fx" on the next build please.
[Miscellaneous Android Development] Gubbl:
After some time of testing I have some issues I wanna share with you.

The device is restarting or just going off some time, I was not able to reproduce this while using the tab. It only occured for me when the tab is in standby, but its somehow annoying.

An app that worked for me before the update doesnt with the new OS. Its called "Lister" (Link Playstore: https://play.google.com/store/apps/details?id=com.DramaProductions.Einkaufen5&hl=de)

The app is starting and I'am able to agree to the privacy policy, but after this the app got stock.

Since the app worked well on LOS12 I wanted to post this issue aswell.

It seems that the tab is sometimes really really slow and laggy without any app running.

I only tested it with one game, the lister app and my smarthome app since I only use the tablet for cooking and smart home.

Cooking is with the lister app and this is broken. ;-)
[Miscellaneous Android Development] DOCa Cola:
Had a random reboot while the device was unattended as well.

I have also had an issue where the GUI was completely freezing two times when i was actively using the device. The device was still reachable via SSH. Not sure if these issues are related. I am using the Kernel for the alternative screen.
[Miscellaneous Android Development] artgopi:
Hi.

I also don't have wifi.

I try the "Edit3" method, but it don't work for me.

Old recovery + LOS-12.1 also don't have wifi (it was working before upgrade)

Is it possible to install stock image from TWRP, keeping TWRP?

I wold like to check if wifi is still working with stock image.

Edit 2:

I install old recovery and stock 422. No wifi!!!

Regards
[Miscellaneous Android Development] superdragonpt:
Twrp can be picky to what regards to wiping...

1: Go to "wipe" and perform an factory reset

2: Now go to "mount" and mount "system" partition

3: Go to "wipe" > advance : and wipe " system"

4: Go to "mount" and unmount "system" partition

5: Flash your ROM

If its still not working :

Do the above

but instead, in the last step of flashing the ROM:

> just reboot to recovery again and repeat the wiping steps again,

Then flash the rom
[Miscellaneous Android Development] pennatom:
The screen is a bit buggy... like flashing... Maybe I messed up in the unlocking bootloader phase, because it is like this even in the TWRP screen. Anyone experienced the same?

------ edit: solved with the kernek package
[Miscellaneous Android Development] cubitci:
Still wi-fi and bluetooth not works on my tab (memo pad hd 7 me 173x) can you help me? İm usin twrp and los 13
[Miscellaneous Android Development] DarkJoker360:
@superdragonpt Hi, nice work. I would like to ask if it is possible to have full device sources of this tablet. I would like to take a look if I could contribute to development. Thanks.
[Miscellaneous Android Development] rainlight:
I can't seem to unlock bootloader so I can give this OS a try, can anyone help? Is there a video I can follow so I can do this?

There's some apps that I use regularly that I cannot instal because of how old 4.2.2 KitKat Android OS is.

Please help.
[Miscellaneous Android Development] artgopi:
I brick my device trying to reinstall TWRP.

But after I get a Windows laptop I recover it :)

Stock firmware still don't have wifi working.

Then I flash recovery and new TWRP.

Wipe everything and then install new Linage 13.0.

This time WiFi is working!!!

Install alternate kernel (my device need it) and WiFi still is working fine.

Thanks for your help and good work.

PS1: /data was only 1GB, I had to go to TWRP recovery and resize the filesystem
[Miscellaneous Android Development] artgopi:
Check the beginning of this thread. There is a link, the one I follow to unlock bootloader.
[Miscellaneous Android Development] rainlight:
Yes, I tried.

I'm trying to install the drivers, but since there's no pictures (it's a very old post) I can't seem to install it as I've got no clue what I'm doing since it's the first time I'm trying to do something like this.
[Miscellaneous Android Development] rainlight:
"Next, Click Write Memory, Open Raw and choose the "sro-default-lock-sign.img" file from the "signed_bin" Folder.

Memory Settings must be "EMMC" "

Hi. I'm trying to do this to mine, but I can't get through this part. It's so many things I must confess I'm super lost, been at this for hours lol.

Anyway, i'm new to all of this so i may not even have the required download files, but i think i do.

I got the flash tool, I'm in, i can do everything until this point, i cannot find the "sro-default-lock-sign.img" file, and i cant find a folder called "signed-bin".

I've been stuck here.
[Miscellaneous Android Development] Hotte37:
Hello, i have the same problem with /data. Its only 1 GB. I have the 16GB version of the MeMO Pad HD 7. Can you explain what to do to increase the size of the /data?

Is the whole flash unused or is it used for a different purpose?
[Miscellaneous Android Development] filus:
Hi, try flashing the stock rom first and then lineage os and you should restore the original partition table if you are referring to a total memory problem. A greeting
[Miscellaneous Android Development] rpcll:
any way to watch videos in landscape mode without autorotation?
[Miscellaneous Android Development] Hotte37:
Maybe it helps someone with the same Problem:

In TWPR i had to select Wipe -> Format Data. Now i have 12 GB instead of only 1 GB internal Memory.
[Miscellaneous Android Development] filus:
Screen Orientation Control - App su Google Play

Questo è uno strumento che controlla l'orientamento/rotazione dello schermo

play.google.com
[Miscellaneous Android Development] superdragonpt:
If you flash via SP FlashTools an stock rom, your internal storage should be fine.

But you should do the first boot of the stock ROM first so that nvram does it job.

If you flash for example an stock ROM, and immediately flash twrp and proceed to flash lineageOS that can lead to that problem of wrong storage detected.
[Miscellaneous Android Development] superdragonpt:
New build coming very soon, with some good progress done, more kernel drivers and functions reversed engineered from the stock (closed source) Asus kernel as well as porting those to work on lineageOS marshmallow :)

Just doing some final tests

Cheers
[Miscellaneous Android Development] superdragonpt:
Build 20210821

Kernel:

DCT / Power resolve more issues

LCM: nt35521_dsi_vdo: Add backlight enable ctrl function

Fix magnetometer sensor: akm8963

Battery: Corrections

Camera LENS AF (for the rear camera) fixed

Front Camera : mt9m114_mipi_raw ( ME173X 16GB Version) fixed

mmc: more handling fixs

msdc: more fixs

Touch Panel: GT927: Implement a proper suspend & resume

Some other small fixs.

LineageOS source and device:

LineageOS LiveWallpapers, Wallpapers are now included ( as per-user requests)

Gello browser removed, it's depricated and has security risks

Disable Live Display by default (not supported by this device)

Some device clean up

Fix some eGL crashs

Fix some core missing symbols

Added Front camera support ( Pictures )

Some other small fixs.

Build 20210821

https://www.androidfilehost.com/?fid=7161016148664790672

If you have the second hardware Screen revision by LG (check FAQ), flash this

kernel for the Build 20210821

https://www.androidfilehost.com/?fid=7161016148664790675

Cheers ;)
[Miscellaneous Android Development] tweakradje:
@superdragonpt thanks for your work. Amazing you manage to get new builds out!

Using LG kernel the camera is not working. Is this correct?

Battery charging is very slow. Option for compressed ramdisk/swap (zram) would be nice to have.

Cheers
[Miscellaneous Android Development] superdragonpt:
Kernel rev2 only haves LCM screen driver changed, so camera should work as well.

just couple notes:

- camera usually takes one reboot to be available, at first boot it will appear "can't connect to camera" 7/10 times

So, usually after the first reboot (after rom flashed) camera should be fine, if not, then go Settings > Apps > Camera app > And in Storage , Clear Data and Clear Cache of the Camera app

If after all this, there's still no camera:

- > there's also an second hardware revision on camera sensors.

Some devices came with the mt9m114_mipi_raw sensor, and some devices came with the gc0339_raw for the front Selfie Camera

i think the difference is between the 16GB and 8GB versions.

( on the 8GB version, camera had less MPX, cheaper camera sensors)

Im working at adding support for the gc0339_raw front sensor as well, but i can't fully tested it, as none of my tablets have it.

i currently use an 5v, 2AMPs charger and it can charge at ~1.08 AMP / 1.10 AMPs ( Max available on this kernel)

If the device is below an certain percentage ( i think 15% to 20 % ) it only charges at about ~0.50 AMPs, after it reachs 15% to 20%, it should go up to 1.10 AMP but sometimes it doesn't do it automatically ( little kernel bug, on my charger driver )

So just let it charge a bit, after it reaches 20% or so, just unplug the charger and then plug it back, and it'll charge at max current.

About ZRAM, that's something i've been around for some months now...

There's been several issues that i've been fixing over time (on stability, old kernel 3.4.x, mediatek device .. it's all hard to work with haha)

Lets see ...

cheers
[Miscellaneous Android Development] tweakradje:
More feedback on latest rom with Rev2 kernel:

Wifi won't reconnect after (LONG) sleep (clearing network settings solved this for a day)

I cannot get camera to work. Tried 10 times. Not very important for me

Audio also on speaker when headphone inserted

Screen rotation doesn't work (known)

RGB sliders color correction don't work

Very rare complete hang, hard to put finger on

I can give you dmesg or logcat if needed for debug

echo 1 > /sys/devices/system/cpu/cpufreq/hotplug/cpu_input_boost_enable

makes screen little more responsive

echo 10 > /proc/sys/vm/swappiness

echo 10 > /sys/fs/cgroup/memory/sw/memory.swappiness

echo 200 > /proc/sys/vm/vfs_cache_pressure

makes my apps load faster

Cheers
[Miscellaneous Android Development] superdragonpt:
Hi thanks for the feedback

Please if you can, and your rooted, take a full boot dmesg for me to check out.

- RGB sliders color correction,this is not supported by this device

- As to WiFi not reconnecting after very long deep sleep, that's due to this very old (legacy) WiFi conn-soc.

I get that as well, but I slide to Quick Settings WiFi, long press, and on the WiFi networks menu, press " reconnect " and that's it.

Or just toggle WiFi OFF, then ON again.

Cheers
[Miscellaneous Android Development] tweakradje:
I'm rooted from day one but cannot manage to get first 10 seconds with dmesg. Buffer too small?

Cheers
[Miscellaneous Android Development] 5licko:
Hi there. Thread still alive, wonderful!

Camera not working(reset permissions, clear cache strorage etc)

Rotation not working( device info Hw see accelerometer and magnetometer but accelerometer dont pass test)

Dont know if this is a way to take dmesg.log

Edit: Attachment wont upload?
[Miscellaneous Android Development] mdruv:
Hi. First, thanks for your work @superdragonpt.

I've been running build 20210821 for a few days and, in general, it's been working really good. I haven't experienced any problems with wifi or bluetooth, no crashes, and it feels smooth (considering how old the hardware is). I've only found two issues:

1. Offline charging is not working for me. When the tablet is turned off, the moment I connect the charger, it turns on automatically. And if I shut it down while it's charging, it will simply reboot.

2. The battery indicator never reaches 100%. It stays at 99% even if I unplug it and plug it again. Not a big deal, but I'm curious if that's to be expected or if it's a bug. Nevermind about this. For the last couple of days it wouldn't get past 99%, even after an hour, but that seems to be fixed. Maybe I had a calibration problem or something.
[Miscellaneous Android Development] Jmackley:
I started messing around with this tablet again because I was bored and followed the steps to install the CWM-based recovery. The CWM recovery refused to mount /sdcard and the tablet wouldn't boot (stuck on asus splash), however I was then able to install TWRP via sideload, which now refuses to mount system and refuses to use sideload. Anyone got any ideas?
[Miscellaneous Android Development] superdragonpt:
Unfortunately this dmesg doesn't help, I need dmesg via adb during boot process to check image sensors regestering and / or errors .

As for camera ( only front camera supported for now for one hardware revision that haves the MT9M114 sensor)

For people that don't have working camera ,either your revision haves the other sensor , or there's an nvram issue (probably related to WW / US/ RU / CN different firmwares ) not mutch I can do without having those units to test...
[Miscellaneous Android Development] superdragonpt:
The buffer is already at max for ARM (32) , you need to unpack boot, and in default.prop of ramdisk allow debugging, and set ro.secure to =0

Tell me what's the screen / LCM revision of your unit, I can quickly do that for you ;)
[Miscellaneous Android Development] superdragonpt:
About offline charging, this is all related to the stock MediaTek preloader.

If you recall, on stock ROM , if the battery was under 20% ( or was it 30% ?) You could not boot the tablet, you had to wait for the battery to reach 20% ( or 30%) until you could power up the tablet.

This is all related to that. If the tablet haves more then 20% ( or 30%),then offline charging works fine.

Nasty workaround of Asus on stock preloader due to this LI-PO battery ( not very common battery )

Since offline charging relies on preloader + healthd , and we are no longer using stock healthd binaries ( libraries ) since they are completely broken on lineage 12/ 13.

Now, that's the expected behavior.

A complete fix would be to build a new mediatek preloader and patch for this recent APIs, and that's just not possible
[Miscellaneous Android Development] superdragonpt:
If you have twrp installed, and you have made a backup of your stuff on internal sdcard ...

Then on twrp just format / data, and then reboot to twrp again, and do all wipes ( including /system)

In twrp you can then just connect via USB to PC ( mtp works fine on twrp, unlike the old CWM recovery)

And just flash your desire ROM
[Miscellaneous Android Development] Jmackley:
Trouble is that I can't mount system at all in twrp, this is my second attempt after fully going back to stock and trying again

Every time I try to do an action involving /system it just fails with invalid argument, also all the partition sizes seem wrong

I'm probably doing something dumb tbh, most of my custom rom experience has been on samsung devices lol

Never mind I was just being dumb lol
[Miscellaneous Android Development] Mr.T3ILLER:
Hello fellow platformer

I was surprised to see that someone else is picking at this old platform besides me

Is your accelerometer broken in the core or in the LOS firmware?

I can help if anything, I just recently raised a similar one, I have a platform 8389. I, like you, was able to build the kernel without the source code (only the camera does not work yet)

Sorry for my bad English, I'm from Russia
[Miscellaneous Android Development] superdragonpt:
Its an kernel issue

This tablet uses an uncommon power gpios, and also custom chips.

I.e. : cameras are connected to a custom External ISP chip the "iCatch" chip, this is the first MediaTek device that I know ...up to this date, that uses this chip, the chip is usually used on QCOMM devices...

( hence main camera still not working , and on the selfie camera I was abled to bypass this chip by using the slightly modified power-on sequence with gated IRQ )

Same thing for many drivers inside the device, they have been extremely modified and hard to reverse engineered

The magnetometer driver was also quite time consuming to reverse, it has also an uncommon way to be powered up.

same thing for the Goodix Touch.Panel

( took some years to figured it out)...

Asus really did an impressive job here ..

Cheers
[Miscellaneous Android Development] Mr.T3ILLER:
The sad thing is that asus did not provide the complete source code for your device.

I came across their sources a couple of times and thought that they were complete, but recently I needed one driver, and it turned out that they are fake☹️.

As far as I understand, Axel uses gpio for you?

I had a custom axel using gpio, but the reverse didn't help me.

Through trial and error, I picked up the driver and, having slightly edited it, started it.

It differs from the drain, but it works)

With the standard Ktj2-1009 driver, it doesn't work?

Usually, there are no problems with launching with these axels, you like the address 0x1E like my kxtik1004, it seems like some kind of ktjf2 uses such an address, does not work with them?
[Miscellaneous Android Development] superdragonpt:
The "regular" drivers just don't work

I've tried that years ago, on the first tests.

The board was assembled very differently, the gpio / power and the way the components where connected on the board is very uncommon.

Hence the i2c slave addresses of this drivers aren't the "standard ".

Another example :The magnetometer needs to be manually powered up by calling the right gpio number that it is connected to, with the specific mdelay while the driver is loading.

Sensors: magnetometer: akm8963: Add gpio power ctrl · dragonpt/android_kernel_asus_me173x_new@df72d31

based on stock kernel reverse engineering

github.com

This device has been an tremendous headache.

We can only thank Asus by making such an weird board design :p

And by not complying with GPL, the kernel source they released is " dummy " , just an generic one, not containing any drivers used by the device
[Miscellaneous Android Development] Mr.T3ILLER:
Yes, you have a more specific device that you almost made it work (not a working magnetometer is not critical).

I don’t have that much experience in reverse engineering, so I’m probably not your assistant here.

But there is someone to turn to for help)

But I hope that with my sources when I bring them to a working state.

Do you think a simple porting and building of the kernel from your sources is enough to run the firmware on the mt8389?

(p.s. I do not know how much it will be considered a flood in this topic, if we can go to private messages)
[Miscellaneous Android Development] gadom92:
Thanks for new update. Just curious can i have DRM 1 on this tablet?
[Miscellaneous Android Development] k.dinya:
Thanks for your work. Dropping works well. Cameras refused to work for me, WIFi started working.

I just ran into a problem. After installing Google apps, the tablet starts to work slowly (very slow).
[Miscellaneous Android Development] fcaronte:
I don't try without gaps, but is very slow for me too
[Miscellaneous Android Development] gadom92:
i'm using nandroid + aurora store and tablet runs pretty smooth. With gapps it was very laggy
[Miscellaneous Android Development] xog64:
Hello,

Today I managed to install lineageos 13 on my me173x. These are the steps I followed:

1- When using windows 10 remember to enable third party drivers, otherwise it is not possible to install the mediatek drivers properly https://support.viewsonic.com/en/su...how-to-install-unsigned-drivers-in-windows-10

2- I used Windows 10 to unblock the bootloader following the guide in the first post https://xdaforums.com/showthread.php?t=2503668

3- I uploaded TWRP from linux as windows 10 didn't recognise the tablet on fast mode (some driver missing)

> fastboot flash recovery recovery.img

> fastboot reboot

4- I started the tablet in recovery mode (TWRP), connected the tablet to the PC (on linux again) and uploaded the lineageos zip file

5- TWRP install zip file

6- As the the screen was flickering I did the same as steps 4 and 5 but with kernel_rev2 build file, as my tablet has the lg screen
[Miscellaneous Android Development] amy_aimei:
Thanks, everything you stated working is working. I'm not so concern about the rotation. I want to get the camera to work to scan QR code. I would like to help. How can I find out which sensors my ME173X is using without dissembling it?
[Miscellaneous Android Development] rpcll:
More Troublesome x86 Android Tablets Being Fixed Up By New Linux Driver - Phoronix

www.phoronix.com

You think this could be relevant to this tablet?
[Miscellaneous Android Development] amy_aimei:
This is a x86 version of that tablet. I don't think it helps. But I think the camera hardware, i.e., the sensor chip must be used by another Android phones or tablets too. That's why I try to find similar code and adapt it.
[Miscellaneous Android Development] xiao_changchang:
may i ask you what version of aurora store do you use?

im using this version of los and cannot install aurora

i try to install 4.0.6 from its website

it always said parse error :(

----update----

it looks like microsoft edge's problem

i use bulit-in browser it can install
[Miscellaneous Android Development] gadom92:
good for you, for brower i recommend Bromite
[Miscellaneous Android Development] Jak08:
Hi, the rom for now works properly, i have the lg screen because i had black screen and an huge flickering issue , so i flashed the 2nd kernel but sometimes when i lock the screen and i wake up from standby i have these black lines, i have to lock and wake up again with power button, at least i don't have to reboot the device to solve it, i tried to clean reflash etc, but it didn't solve the issue, maybe there is another screen revision? i don't have this issue with the stock rom
[Miscellaneous Android Development] filus:
After having had several problems with the latest versions of magisk on this device, I have successfully tested the root by flashing via recovery of addonsu, the official root method of lineageos. By doing this in the developer menu you will be able to activate the root and manage permissions. Attached both the root and the unroot. I haven't tested the unroot but it should work too. If the rom developer wants, he can attach this alternative root method on the front page.
[Miscellaneous Android Development] filus:
I wanted to know if other users have had problems with crashing or closing after opening with the latest updates of some apps. If so, what could be the cause? Example: Voice Aloud Reader and Youtube Vanced... In the case of Voice Aloud Reader if I manually install the apk it doesn't crash after opening it, if I install it from the play store it crashes after opening. By chance you should change the device name to build.prop to avoid problems with updates?
[Miscellaneous Android Development] djvantri1:
Does anyone have an issue with the device rebooting itself after you have shut it down?

The tablet does this without plugging it in.

Thank you
[Miscellaneous Android Development] tonybot:
Hi, great job. On my version with the LG additional kernel everything works except BLUETOOTH. It is visible and recognizes the devices, it pairs only in appearance but does not communicate. With the version "ASUS_ME173X_AOSP_20160929.zip" everything works, but once you switch to 12 or 13 the bluetooth does not work. I have tried the different tips already posted above to fix wifi problems without solving the problem. How can I solve. Sorry for my immature English.
[Miscellaneous Android Development] juggled_balls:
Hi all,

I've just tried to download the "Unlock_Bootloader+install_Recovery.zip" through the download links but the link that opens up says no mirrors found. Does anybody have the file they can pass on? thanks
[Miscellaneous Android Development] tonybot:
Rectification: the tablet does not communicate with mouse-like input devices. I've tried with different devices and it doesn't work with mice. For example: with my smartphone it communicates and exchanges data, but with a Trust or other brand bluetooth optical mouse, even if it recognizes it, it does not paring.

How can I fix it please?