yashsingh1/xdaforums huggingface dataset:
[MeMO Pad 7 General] social-design-concepts:
[MENTION=5479482]jerbear294[/MENTION] well finally got the UFO graphics to load but still not booting :( guess i'll take it to Florida with me to see if i can debug whats missing / wrong and get the baytrail_base device tree cleaned up so i can start a build when i get home Friday night, maybe i'll be able to shim some of the missing pieces to figure out whats causing it to crash.
[MeMO Pad 7 General] cheeze.keyk:
can this tablet handle high intensive games? like Vainglory?
[MeMO Pad 7 General] TalhaGirgen9:
Any Progress On 5.1 Rom?
[MeMO Pad 7 General] jerbear294:
Well, luckily for you, it's supposed to rain in Florida today and tomorrow! (well, at least where I am in Florida)

Yaaaaaaaay!
[MeMO Pad 7 General] vampirefo:
Can you adb? If so grab a logcat and check if any modules loaded.

adb shell lsmod
[MeMO Pad 7 General] sistah:
Quick question:

All my apps are on internal storage, my 16GB SD Card was for movies and random files other than apps.

I wanna change my SD Card so I backed up my personal files and I am left with the Android folder that it says it's 1GB but I can't see anything on it.

Is it safe to delete it or should I back it up also?

If I delete it will the tablet recreate it or I'm gonna loose something?
[MeMO Pad 7 General] Mis012:
As there are some ongoing projects, shouldn't be there Development Threads opened to track them?

---------- Post added at 08:55 PM ---------- Previous post was at 08:53 PM ----------

And I wanted to ask about that twrp, if it's only too big please try it with fastboot boot.
[MeMO Pad 7 General] Ruben Craveiro:
This tablet has 1gb of RAM, vainglory doesnt install on devices lower than 2gb of RAM...
[MeMO Pad 7 General] jerbear294:
The way I see it, once the projects are confirmed working (which none of the three projects (5.1 and CM12.1 and 6.0) are right now) then a development thread can be created.

At least, that's how I did it when I did development for the Sero 7 Pro.
[MeMO Pad 7 General] Ruben Craveiro:
I tried it didnt work when I do fastboot boot twrp3.img, it just stays in fastboot... But i could port cwm i copied the cwm files from vampirefo to stock ROM and flashes it was glitchy but it booted ;-; ill see if i can make it less glitchy i think it has something to do with partition.tbl
[MeMO Pad 7 General] vampirefo:
I thought you already had twrp, what's to big about it?
[MeMO Pad 7 General] Ruben Craveiro:
hes talling about twrp 3.0.0.0 (which i tried to port but didnt work, but i was able to make cwm boot with your files but its glitchy (lots of errors when it starts, most likelly because of partition.tbl)
[MeMO Pad 7 General] vampirefo:
I will release my twrp 3 for ares8 soon, perhaps you can use or port it to your device.
[MeMO Pad 7 General] Ruben Craveiro:
sure i could try shouldnt be hard at all just changing some files
[MeMO Pad 7 General] daspex:
would this be possible with the me176c? http://xilfy.com/v/NbVxnbG8Gu4

the guy said something of setting a password in the uefi menu to unlock the devices secure.cant take a look at it because i have still kk.

you have to watch the video until the end rather late he talks about the uefi thing.
[MeMO Pad 7 General] Ruben Craveiro:
our device is already unlocked
[MeMO Pad 7 General] jerbear294:
I didn't fully watch that video (I'm at school), but I did skim it and from what I can tell all this guy's doing is installing Android-x86 onto the tablet.

We already tried that and I think a bunch of drivers were missing, won't hurt to try again though. We could try taking Android-x86 and modifying the kernel (similar to how we're trying to port that i708Q ROM)
[MeMO Pad 7 General] daspex:
i know that it's already unlocked i can read and i'am not stupid but i thought the androidx86 he used could have drivers inside which could fit to our device what would be helpful....imho
[MeMO Pad 7 General] vampirefo:
You can try mine here.

https://www.androidfilehost.com/?fid=24421527759887180
[MeMO Pad 7 General] Ruben Craveiro:
android x86 works but only version 4.4 that i know of

---------- Post added at 07:20 PM ---------- Previous post was at 07:09 PM ----------

done, it booted, but touchscreen isnt working.. how to fix?
[MeMO Pad 7 General] vampirefo:
Your may need to unpack and repack with your kernel, my touch is built into my kernel.
[MeMO Pad 7 General] daspex:
tested on my samsung n145plus netbook with intel atom processor and 1gb ram

android x86 5.0,5.1,6.0

everything works fine even gapps without updating but wifi doesn't connect to my fritzbox only to the wifi hotspot of my cellphone unfortunately can't test on my tablet because i won't send it to asus before a custom rom is available.(i don't like white and the issues reported here.)

btw.the guy in the video i wrote about installed android 5.1 on a acer tablet.
[MeMO Pad 7 General] Ruben Craveiro:
i already changed kernel (recovery.img-zImage)
[MeMO Pad 7 General] Nexive:
How did you changed settings to black? I already set the quick settings toggles to black but i can't find a layer for settings.
[MeMO Pad 7 General] dog121:
Use the dark settings zip from here

https://my.pcloud.com/publink/show?code=sDUrtalK#folder=50292425

Use number156
[MeMO Pad 7 General] Nexive:
Thanks for the link and fast reply. I've made a backup of my original settings apk and moved it to another place, then i flashed the zip in recovery but now my settings icon is removed so i can't access settings now. And another worse thing: my backup file is corrupt. :p

Can someone give me the original AsusSettings.apk please? :)
[MeMO Pad 7 General] dog121:
Use this link

I found a lite & clean version of .36 FW without Asus bloatware at 4pda.ru, it does keep custom bootloader and recovery

https://cloud.mail.ru/public/EfuY/81Nk2HGTB

Credits goes to nfs911 from 4pda.ru
[MeMO Pad 7 General] vampirefo:
Try this one, looks like your touch screen drivers are external modules, not built in like ares 8.

This is sdc twrp, which looks like just stock recovery, that i replace sdc twrp and replace with twrp 3.

should boot as is, if not repack it.

https://www.androidfilehost.com/?fid=24421527759887554
[MeMO Pad 7 General] social-design-concepts:
It should look just like stock recovery, the original unreleased installer I wrote generates a twrp recovery image by patching the devices factory recovery and then injecting my twrp build assets, then appending selinux permissive to the command line when repacking the recovery.img.

Working on the same type of installer for :

remixOS pending conformation (status : need to see if can be shimmed by building some android-x86 parts from source waiting for the next release before i start working on this again.

iview i708 (status : a few more features to fix close to complete)

cm-12.1 (status : boots to setup screen before crashing so close but can't recompile till I get home)
[MeMO Pad 7 General] Anfas1:
Win To Go 8.1 boot

Good day.

I'm trying to boot Win To Go 8.1 from USB via powered USB hub and that proсess hangs with Windows logo screen. I was waiting for about an hour and hadn't results. Any ideas or suggestions? Thanks.
[MeMO Pad 7 General] jerbear294:
I can't wait, I haven't had CyanogenMod on a personal device since... about two years ago at this point.

Thanks for all the work you're doing!

Also, my camera/bluetooth doesn't work, and it was suggested to me that it's because my UEFI is outdated (which it is as I used a Nandroid to upgrade to .33 and I'm on the .24 UEFI update). I downloaded ASUS's .36 package and modified it and the updater-script.

Should a script that just says this:

mount("ext4", "EMMC", "/dev/block/by-name/system", "/system", "max_batch_time=0,commit=1,data=ordered,barrier=1,errors=panic,nodelalloc");
package_extract_file("esp.zip", "/tmp/esp.zip");
flash_esp_update("/tmp/esp.zip");
unmount("/system");

be able to update it, or are there other things I need to change as well? I'm not sure if the system mounting is necessary.

Not sure about that one

[MENTION=2656128]Ruwin[/MENTION] messed with Windows for a bit, maybe he can help?
[MeMO Pad 7 General] groovychap:
I'm still on .17, so my UEFI is obviously outdated too.

If I don't update my device, will this affect my ability to install custom roms?
[MeMO Pad 7 General] jerbear294:
Nope. Not that I know of at least.

If my camera and bluetooth still doesn't work on CyanogenMod and it's not the ROM's fault then I'll worry about updating it.
[MeMO Pad 7 General] groovychap:
Hypothetically, if I wanted to upgrade from .17 to .36, what would be the best way of doing so, bearing in mind that I can't update OTA because I'm rooted?
[MeMO Pad 7 General] Ruben Craveiro:
why did you mount system partition if what you want to install is ESP partition and its not in system partition?
[MeMO Pad 7 General] Ruben Craveiro:
it did not boot (without repacking). (with repack) i made the necessary changes and repacked and tried to flash but it doesnt boot (and fastboot boot image.img doesnt even boot and when it does it just reboots to OS and not recovery) i need to repartition recovery because i added some files and now its bigger than the partition, how do i repartition ive looked up for it and cant find it
[MeMO Pad 7 General] vampirefo:
What is fastboot boot image.img no ideal what you are saying, what changes did you make?
[MeMO Pad 7 General] Ruben Craveiro:
I downloaded the TWRP img you gave me and tried to flash it, it flashed but didnt boot to recovery so i unpacked and changed some files and repacked and tried to flash it via fastboot with the command fastboot flash recovery image-new.img it returned cmd line error, or something. then i went to stock twrp and tried to flash from there to see if it worked it said the file was too big. so i went back to fastboot and tried to boot it by doing "fastboot boot image-new.img" but it didnt reboot or anything just stayed there. so i need to know how to repartition recovery size (size i need: 17094656 bytes) so i can flash it.
[MeMO Pad 7 General] vampirefo:
fastboot boot recovery.img does nothing never did never will, you are confusing regular fastboot with dnx fastboot.

Try and flash either the twrp I gave you or sdc twrp.
[MeMO Pad 7 General] Ruben Craveiro:
i already tried both, and im not confusing fastboot with dnx, i know the difference, if all hardware buttons pressed it goes to dnx mode that has the #1#2#3 startings with the name "fastboot"... and fastboot either reboot with adb or pressing v- and p-ower and choosing fastboot option.. and both needed a change in archives i tried yours first

it needed some files to be changed i changed and it booted but then the touchscreen wasnt working so u gave that other twrp with the modules file there but all ive been doing isn copying some of the files u gave me of both twrps and pasting them and changing some files on the stock twrp.. i just need to repartition the recovery size so i can test it....
[MeMO Pad 7 General] vampirefo:
The dnx fastboot allows fastboot boot recovery.img but regular fastboot doesn't, so in regular fastboot boot recovery.img it is normal for nothing to happen.

I said you were confusing them cause you expected fastboot boot recovery.img to do something. It wont ever do anything in regular fastboot.

On older devices that worked, but has been removed, anyway you would need to use fastboot to format recovery partition.
[MeMO Pad 7 General] Ruben Craveiro:
oh ok but when i use fastboot boot on dnx it boots to os
[MeMO Pad 7 General] vampirefo:
Yes, as it should.

In regular fastboot

fastboot erase recovery

fastboot flash recovery recovery.img
[MeMO Pad 7 General] Mis012:
Even if you use right twrp.img? Try it with the one we know to work and then with the one you wanna try out. I am suggesting boot without fpashing so you can see if it works before trying to repartition.
[MeMO Pad 7 General] Ruben Craveiro:
tried booting normal and then the other twrp on dnx they both booted into android and then i tried going to fastboot and make the erase recovery command and flash the changed twrp it gave flash_cmds error, and the working twrp didnt gave any error
[MeMO Pad 7 General] social-design-concepts:
So from dnx you did fastboot boot twrp.img and it booted into android?
[MeMO Pad 7 General] Ruben Craveiro:
yes
[MeMO Pad 7 General] :
Since the tablet kills ram for no reason, can we change some settings in kernel auditor - > low memory killer?
[MeMO Pad 7 General] jerbear294:
I think [MENTION=2685592]bravesoul[/MENTION] played with that a bit (granted, that was back in KitKat) and while it helped a bit it wasn't a huge difference.
[MeMO Pad 7 General] Opensystem:
I've no luck with any oom settings
[MeMO Pad 7 General] chrismash:
any progress on CM 12.1?
[MeMO Pad 7 General] social-design-concepts:
We'll find out in about 4 hours when I do a fresh build tonight.
[MeMO Pad 7 General] chrismash:
thanks you very much for answer!
[MeMO Pad 7 General] Ruben Craveiro:
Theres something really weird happening, each time i go to this website: http://www.pcadvisor.co.uk/test-centre/tablets/10-best-budget-tablets-2016-uk-3412038/ and start scrolling it reboots to intel logo with efilinux error, and goes to boot animation... it has happend a few times usually on youtube and chrome
[MeMO Pad 7 General] jerbear294:
I haven't gone to the page... Does it have a video?

If so I had the same bug a while ago, seems like some videos are straight up broken in ZenUI, resulting in a hard reboot. While this never happens in YouTube for me, it does happen when I try to play a video of a Web page.

The efilinux error only shows up if the bootloader doesn't know why the reboot has occurred. In this case, it detected a hard reboot but no hard reboot (power button for ~15 seconds) or normal reboot commands were issues.

Ugh... Things like this are the reasons I can't wait for CyanogenMod. In a few days we'll never have to worry about ZenUI's lag, freezes, instability, memory management, crashes, random softboots, hangs... hard reboots... Unstable CM11 crashed less than ZenUI on my old Sero 7 Pro, and that crashed a LOT, to the point that I gave up and flashed AOSP.

One of my friends loves ZenUI... All I told him is that there's a reason his Zenfone 2 has 4 gigs of RAM...
[MeMO Pad 7 General] Ruben Craveiro:
it doesnt have a video and i also cant wait for aosp or cm or maybe resurection remix i come here everyday in a hope that a rom is avaible for our device to get rid of the ugly white stuff and bugs crashes and all that stuff.... and also when we get aosp or cm12/13, the themes will be 100% functional and wont have any bootloops(the one we have now works, but if some toggles are made it may bootloop device because it isnt aosp)
[MeMO Pad 7 General] russy23:
can we expect anything within the next couple of weeks :)
[MeMO Pad 7 General] Ruben Craveiro:
hows the build going? i think its been way more than 4 hours
[MeMO Pad 7 General] :
When it's done he will upload, I know we're all impatient..
[MeMO Pad 7 General] Mis012:
I hope [MENTION=4821597]social-design-concepts[/MENTION] is alive - anything can happen :'(
[MeMO Pad 7 General] jerbear294:
Just be patient, he's a busy man...

Even if the build did succeed there's no guarantee it would've worked either, so either way you'd have to wait :P
[MeMO Pad 7 General] Ruben Craveiro:
well i think im coming back to normal zenui... sixaxis controller (stuck on getting bluetooth adress) doesnt work or camera, and im gonna see if i can change kernel to allow usb charge and otg at same time
[MeMO Pad 7 General] jerbear294:
Maybe the issue isn't the UEFI, then (I recall you suggesting it's a mismatch between UEFI update and ZenUI version, doesn't seem likely though). I'm having the same symptoms. I'm sticking with lightweight ZenUI, though - I am not going to give up performance and memory management for two functions I rarely use.

Is your UEFI up to date (.36)?
[MeMO Pad 7 General] russy23:
Dont worry about camera, does anyone use it on this tablet anyway
[MeMO Pad 7 General] jerbear294:
That's why I haven't bothered investigating- I bought this tablet because of its specs and its price, not for the cameras.

Bluetooth has yet to be a problem, but if I ever get a smartwatch...
[MeMO Pad 7 General] russy23:
Cant say ive ever used bluetooth in over one year of owning, i just dont know why they stick 2mp/0.3mp cameras on anthing nowadays, ok its a 2014 model, but still, even a 8mp/2mp combo i wouldnt personally use
[MeMO Pad 7 General] Opensystem:
Is lightweight really that good? I was gonna wait but then I read "memory management" :P
[MeMO Pad 7 General] jerbear294:
Well it doesn't change the memory management per se, but there's much less for the memory management to manage.

I haven't had Google Now Launcher crash on me at all, which is a huge accomplishment. On old ZenUI I switched to Hiyai Launcher just to stop the constant crashing of Google Now Launcher.
[MeMO Pad 7 General] Ruben Craveiro:
yes it is and theres another reason i need to use the camera, its so that i can make videocalls
[MeMO Pad 7 General] Opensystem:
Ah. I'm a nova guy so I used the keep in memory option. Man if my launcher crashed constantly...No wonder people are so anxious for roms lol
[MeMO Pad 7 General] jerbear294:
I would've switched to Nova or Apex by now but I'm too used to GNL's Google Now integration. Other launchers emulate it but you can't swipe back out of Google Now since it's launched as a separate activity.

GNL is quite nice with Xposed GEL Settings. Gotta have my icon packs, after all.
[MeMO Pad 7 General] :
How do you deal with memory? I had to insert an SD card in order to keep all my apps, the tablet reports total space as 8 GB but system reserved is 4.16GB/8GB, meaning we have only 4GB, right?
[MeMO Pad 7 General] Opensystem:
We mean ram. Yeah other than rooting and debloating...
[MeMO Pad 7 General] :
I know..
[MeMO Pad 7 General] jerbear294:
Easy- I have the 16GB model. :p
[MeMO Pad 7 General] Ruben Craveiro:
8gb is nothing compared to 16gb glad i got the 16gb version too :3
[MeMO Pad 7 General] jerbear294:
In case you guys haven't seen it [MENTION=4821597]social-design-concepts[/MENTION] posted his CyanogenMod progress in the bootloader unlock thread.

It boots, WiFi is a bit crashy, audio, camera, bluetooth and GPS doesn't work. He plans to release an alpha build this weekend.
[MeMO Pad 7 General] social-design-concepts:
[MENTION=5479482]jerbear294[/MENTION] I think hope to and really hoping to have something to test by the end of the weekend latest.

After tonights build I should have a better idea.
[MeMO Pad 7 General] MojUk:
Awesome work dude, this will give my daughters tablet a new lease of life I hope :) i'll defo chuck you some beer fund once i've had time to play with it :)
[MeMO Pad 7 General] Ruben Craveiro:
what files does asus systemui use? its hard to find the right one because theres so many folders of resolutions... (i need the statusbar folder that it uses.. and its very hard to find)
[MeMO Pad 7 General] Ruben Craveiro:
I think i found the reason why boot.img is not booting..

i adb log and it kept returning these 2 errors:

E/SchedPolicy( 235): add_tid_to_cgroup failed; policy=1
E/SchedPolicy( 192): add_tid_to_cgroup failed; policy=1

and i have also been looking for a fix for this and i found a website but i still gotta look at it better, here it is: http://www.slatedroid.com/topic/364...ate-rom-posted-now-with-moar-3d-acceleration/

i think the problem is smoewhere in init.aosp.rc and init.rc

//// edit ////

i think i fixed part of the problem but now it shows this:

E/EM FG ALGO Iface:( 279):
E/EM FG ALGO Iface:( 321):
E/EM FG ALGO Iface:( 321): Failed to get File Descriptor
E/SchedPolicy( 228): add_tid_to_cgroup failed; policy=1

It keeps showing that over and over again. How can i fix it? (im with the ares software)
[MeMO Pad 7 General] social-design-concepts:
you still working on the iview boot.img? you need to remove that service from init.$(TARGET_DEVICE).rc your kernel doesn't have that. i think i posted about this earlier in one of the threads.
[MeMO Pad 7 General] Ruben Craveiro:
all of the fg files?
[MeMO Pad 7 General] social-design-concepts:
Compare it to your devices stock the ones related to algo are the ones I removed.
[MeMO Pad 7 General] Ruben Craveiro:
im also still trying to make twrp 3.0.0 work.. it boots but i need to add modules folder but when i do that the size is too big (touchscreen isnt working because i cant add modules folder because of partition being too small)
[MeMO Pad 7 General] Mis012:
Feel free to post me the boot.img which should work but is too big, I can boot it with grub2 as long as it's smaller than RAM ;)

Than we can look at re-partitionig if ecerything works ;)
[MeMO Pad 7 General] Mis012:
Sorry I meant recovery.img
[MeMO Pad 7 General] ardicli2000:
Can't you make it work with volume control and power keys? We don't need touchscreen then. Maybe you should change the ui to old cwm style.. Functionality is more important.
[MeMO Pad 7 General] Mis012:
I don't think there is an advantage of 3.0.0 text version over current touch.
[MeMO Pad 7 General] social-design-concepts:
being i modified the stock recovery via scripting and didn't have to copy any modules and there was no issues with the touch or no issues with touch in the tethered i suspect your issues with twrp 3 are else where. i still haven't built twrp 3 yet but i could probably package the assets and make the recovery.img with the same method.
[MeMO Pad 7 General] Ruben Craveiro:
it wont work it will either get everything messed up specially on text for example the top bar says header("team win recovery"), or it gives a black screen, or gets stuck on intel logo, or it boots to a black screen
[MeMO Pad 7 General] Mis012:
So can I test the so big recovery.img?
[MeMO Pad 7 General] social-design-concepts:
I didn't think I sent you my recovery generation tool and I know I didn't send any one my script for properly packing the assets to use with it. But OK.
[MeMO Pad 7 General] Ruben Craveiro:
i fixed recovery, kinda now i have 1 more error but i think its the last problably something i forgot to add... the recovery now boots but its really buggy at displaying all the names it says their function before it says the name do u know how to fix that?

example: on title of twrp instead of showing Team win Recovery Project it shows stuff like [MENTION=7247453]twrp[/MENTION]_header=Team Win Recovery Project

and i have no idea how to fix that and also touchscreen is working

//////

edit

/////

i give up... just doesn want to work.. ill keep debugging boot.img..
[MeMO Pad 7 General] Mis012:
I think it's some change in xml between 2.7 and 3.0?
[MeMO Pad 7 General] vampirefo:
Sounds like it, but why mix 3.0 and 2.7 XML files? I don't even understand how it's too big, it's almost the exact size of sdc TWRP.

I simply replaced sdc TWRP 2.7 and XML files with those of TWRP 3. So no way should any 2.7 XML files be in the version I uploaded, nor is it too big.

Here is another version, you don't need to add anything to these recoveries they already include all the files they need. This one is even smaller than sdc 2.7 twrp.

https://www.androidfilehost.com/?fid=24438995911972278
[MeMO Pad 7 General] Mis012:
Thanks will try it.

P.S you have wrong device name (Venue 8) is it for reason?
[MeMO Pad 7 General] jerbear294:
Probably because his main development is for the Venue and he forgot to change device to "generic" when uploading (there's no dedicated section for our tablet on AndroidFileHost)
[MeMO Pad 7 General] Ruben Craveiro:
stuck on intel logo.. i think i know whats wrong

---------- Post added at 05:38 PM ---------- Previous post was at 05:30 PM ----------

theres something wrong in sbin i added the stock sbin files to your recovery and it booted to a black screen but at least it didnt get stuck on intel logo

link: https://www.dropbox.com/s/eb5t4lfzt39youu/TWRP-ME176CX.img?dl=0
[MeMO Pad 7 General] Mis012:
I connected a flash disk with OTG and it flashed so it is just display problem. I am sure you could write anything to framebuffer with adb, but I haven't tried.

I would recommend to use sbin from your twrp 3 which had the text bug. You haven't shared so I can't try.
[MeMO Pad 7 General] Ruben Craveiro:
is the partition.tbl needed? and how can the root be different? the root packages are the same..