yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] pmitrik:
building ua

I am attempting to build the ua project according to instructions found at https://www.unlegacy-android.org/projects/unlegacy-android/wiki/Sync_ua/9. I started with a docker minimal image based off of ubuntu. I attempt to install the build tools. (One item was not located, zlib1g-dev:i386. I have not tried to find it yet, I wanted to see how far in the build this would go.) I pulled the repo and edited the bashrc file. I did source the envsetup script. And then I did the following:

~/android# lunch

You're building on Linux

Lunch menu... pick a combo:

1. aosp_arm-eng

2. aosp_arm64-eng

3. aosp_mips-eng

4. aosp_mips64-eng

5. aosp_x86-eng

6. aosp_x86_64-eng

Which would you like? [aosp_arm-eng] 1

============================================

PLATFORM_VERSION_CODENAME=REL

PLATFORM_VERSION=7.1.2

TARGET_PRODUCT=aosp_arm

TARGET_BUILD_VARIANT=eng

TARGET_BUILD_TYPE=release

TARGET_BUILD_APPS=

TARGET_ARCH=arm

TARGET_ARCH_VARIANT=armv7-a

TARGET_CPU_VARIANT=generic

TARGET_2ND_ARCH=

TARGET_2ND_ARCH_VARIANT=

TARGET_2ND_CPU_VARIANT=

HOST_ARCH=x86_64

HOST_2ND_ARCH=x86

HOST_OS=linux

HOST_OS_EXTRA=Linux-4.14.12-1-default-x86_64-with-Ubuntu-16.04-xenial

HOST_CROSS_OS=windows

HOST_CROSS_ARCH=x86

HOST_CROSS_2ND_ARCH=x86_64

HOST_BUILD_TYPE=release

BUILD_ID=N2G48H

OUT_DIR=/root/android/out

============================================

~/android# make otapackage

[too much to display]

including ./vendor/ti/omap4/proprietary/vendor/firmware/Android.mk ...

including ./vendor/widevine/arm-generic/proprietary/vendor/lib/Android.mk ...

vendor/unlegacy/build/tasks/kernel.mk:194: **********************************************************

vendor/unlegacy/build/tasks/kernel.mk:195: * Kernel source found, but no configuration was defined *

vendor/unlegacy/build/tasks/kernel.mk:196: * Please add the TARGET_KERNEL_CONFIG variable to your *

vendor/unlegacy/build/tasks/kernel.mk:197: * BoardConfig.mk file *

vendor/unlegacy/build/tasks/kernel.mk:198: **********************************************************

Starting build with ninja

ninja: Entering directory `.'

[100% 1/1] Package UA-OTA: /root/android/out/target/product/generic/aosp_arm-7.1.2-20180116.zip

FAILED: /bin/bash -c "(ln -f /root/android/out/target/product/generic/aosp_arm-7.1.2-20180116.zip ) && (md5sum /root/android/out/target/product/generic/aosp_arm-7.1.2-20180116.zip | cut -d ' ' -f1 > /root/android/out/target/product/generic/aosp_arm-7.1.2-20180116.zip.md5sum )"

ln: failed to access '/root/android/out/target/product/generic/aosp_arm-7.1.2-20180116.zip': No such file or directory

ninja: build stopped: subcommand failed.

build/core/ninja.mk:148: recipe for target 'ninja_wrapper' failed

make: *** [ninja_wrapper] Error 1

#### make failed to build some targets (47 seconds) ####

Does the kernel and possibly the android project need to be built first before running the otapackage? I'm assuming that the instructions found at the above url are not 100% complete and that I need to refer to the android documentation to build the kernel and android. Any advice or guidance is much appreciated.
[Nexus 7 Original Development] adstraylight:
[MENTION=2633638]Ziyan[/MENTION]

Is there any chance or hope that you could enable the ability to use Zram? I know it's not a pure aosp function, and I don't need it to be configured to a preset size, so the net effect for those that didn't want it would be 0. It would be great to have as an option though to be able to tease a bit more space and app reload speed out of the device.
[Nexus 7 Original Development] adstraylight:
[MENTION=2633638]Ziyan[/MENTION], I just saw your post in the N4 thread re: Android Go, would it make more sense to set up the grouper this way?

I'm testing out some Go apps on it already, and they run pretty well, especially the Google Go search app, about as fast as the chrome search widget, but with more content.
[Nexus 7 Original Development] DumF0rGaming:
Is Oreo development completely dead? [MENTION=2633638]Ziyan[/MENTION]
[Nexus 7 Original Development] abhifx:
Slow maybe. all tegra based devices seems to be struggling to get oreo.

Unlegacy seems more focus on qualcomm based devices which is understandable as they are easier to develope
[Nexus 7 Original Development] Ziyan:
It's not that they're easier to work on, but they're our daily drivers, so we have much more motivation to work on them (and we have much more users on them) :( for some reason, we never really had a lot of "supporters" of k3.4/UA on grouper; but don't worry, we're not giving up on it nonetheless. :)
[Nexus 7 Original Development] sheffzor:
And btw, the Oreo bring up is just paused, my tilapia just got an issue so I'd to pause the bringup to oreo, but as [MENTION=2633638]Ziyan[/MENTION] said, we did not give up on it, it will just take a little more time. ;)

Enviado do meu A0001 através do Tapatalk
[Nexus 7 Original Development] adstraylight:
Well I think you've done a brilliant job so far with this project, but do sometimes wonder at the lack of discussion in this thread. I don't know what your download figures show, but I hope it's a lot more than those that post here..
[Nexus 7 Original Development] gmikhail:
Many people are not registered here or simply do not take part in the discussion, but nevertheless use these ROMs.
[Nexus 7 Original Development] adstraylight:
Well it's a shame that they don't, as without a certain level of energy and enthusiasm, projects tend to fizzle out which is bad for everyone. I try to contribute in my small way, but without any one to respond it sometimes feels like I'm talking to myself ??
[Nexus 7 Original Development] X_TonyK_d:
I'm randomly getting freeze in 7.1 (not tried other versions yet) while using :(

(I'll try to get logcat asap, but it's hard to catch)

It seems like board type is not a matter anymore, but just in case ;)

~ # dmesg | grep pcbid
<6>[ 0.441548] [MISC]: pcbid=0x009e (projectid=0x00)
~ # dmesg | grep max77663
<6>[ 1.471586] print_constraints: max77663_sd0: 600 <--> 3387 mV at 1025 mV normal standby
<6>[ 1.472551] print_constraints: max77663_sd1: 800 <--> 1587 mV at 1200 mV normal standby
<6>[ 1.473585] print_constraints: max77663_sd2: 1800 mV normal standby
<6>[ 1.474648] print_constraints: max77663_sd3: 600 <--> 3387 mV at 1350 mV normal standby
<6>[ 1.475630] print_constraints: max77663_ldo0: 800 <--> 2350 mV at 1000 mV normal standby
<6>[ 1.475779] set_supply: max77663_ldo0: supplied by max77663_sd3
<6>[ 1.476841] print_constraints: max77663_ldo1: 800 <--> 2350 mV at 1200 mV normal standby
<6>[ 1.476930] set_supply: max77663_ldo1: supplied by max77663_sd3
<6>[ 1.477987] print_constraints: max77663_ldo2: 800 <--> 3950 mV at 2800 mV normal standby
<6>[ 1.479041] print_constraints: max77663_ldo3: 800 <--> 3950 mV at 3000 mV normal standby
<6>[ 1.480278] print_constraints: max77663_ldo4: 800 <--> 1587 mV at 1000 mV normal standby
<6>[ 1.481336] print_constraints: max77663_ldo5: 800 <--> 2800 mV at 2800 mV normal standby
<6>[ 1.482366] print_constraints: max77663_ldo6: 800 <--> 3950 mV at 3300 mV normal standby
<6>[ 1.483355] print_constraints: max77663_ldo7: 800 <--> 3950 mV at 1200 mV normal standby
<6>[ 1.483502] set_supply: max77663_ldo7: supplied by max77663_sd3
<6>[ 1.484548] print_constraints: max77663_ldo8: 800 <--> 3950 mV at 1200 mV normal standby
<6>[ 1.484637] set_supply: max77663_ldo8: supplied by max77663_sd3
<6>[ 1.485026] max77663 register misc device for I2C stress test rc=0
<6>[ 1.493208] set_supply: fixed_reg_en_1v8_cam: supplied by max77663_sd2
<6>[ 1.495181] set_supply: fixed_reg_cdc_en: supplied by max77663_sd2
<6>[ 4.455701] using rtc device, max77663-rtc, for alarms
<6>[ 4.455848] max77663-rtc max77663-rtc.0: rtc core: registered max77663-rtc as rtc0
<4>[ 5.456525] regulator_init_complete: max77663_ldo8: incomplete constraints, leaving on
<4>[ 5.456695] regulator_init_complete: max77663_ldo4: incomplete constraints, leaving on
<6>[ 6.133382] max77663-rtc max77663-rtc.0: setting system clock to 2018-01-26 14:25:21 UTC (1516976721)
[Nexus 7 Original Development] X_TonyK_d:
I'm still trying to get logcat, but tablet is not going to freeze when connected to usb...
[Nexus 7 Original Development] adstraylight:
I haven't posted one of these for a while, in the mean time I've switched to using the UA "stock" kernel, as sadly the more flexible custom one was discontinued and is no longer compatible. Attached is the text of my current startup script that I run in Kernel Auditor's init.d section.

The key change is the line setprop ro.hwui.texture_cache_flushrate 0.0 , I found that graphically complex apps eg. Reddit, or YouTube were not being completely purged from the dalvik heap untill the device was restarted, and as the visual content of these apps changes continually, the effect becomes a memory leak, untill the system starts to be impacted, and eventually locks up. With this tweak, all of the texture cache is available for the system to reclaim as required.

Other KA tweaks that help the overall UX:

CPU section

CPU Quiet governor - runnable

CPU minimum frequency - 340

CPU Governor Tuneables

Boost Factor - 0

go maxspeed load - 80

midrange go maxspeed load 85

min sample time - 40000

timer rate - 50000

Other non KA things:

SSD Boost app, helps with io speed of the internal storage

This Task Killer : https://play.google.com/store/apps/details?id=com.rhythm.hexise.task&hl=en_GB

The only one I've found to effectively kill unneeded apps when the screen goes off. This helps the smooth running by limiting the need for minfree ram reclaim in the background, so giving the maximum system resources to the UX.

I also use the Google Go Search app available via apk mirror, as it is much more lightweight than the standard Google app, and does everything I need.

Anyway, as always, these are just what work for me to prevent system slowdowns and freezes, YMMV, but I hope they make a difference to somebody?

Thanks to parrotgeek for most of the script that I've repurposed!

Thanks to UA for the great ROM to play with?!

PS, I'm using the 7.1 version of the UA ROM btw...
[Nexus 7 Original Development] abhifx:
interesting with ro.hwui.texture_cache_flushrate 0.0, my gripe is there seems to be some memory leak while using google related apps. ultimately resulting in lag and freeze. if this is can fix it then i can live with this ancient tablet
[Nexus 7 Original Development] adstraylight:
Most of my Google issues disappeared when I uninstalled the Google App, and started using the Go version. I do have to clear recents before/after running Maps or YouTube to maintain a smooth ui even so. The screen off task killer can help with this too.

It's my contention that a lot of the lag happens when the system is clearing ram space to load new content, so I'm trying to take some control of when it does this. I know the android cliché "free RAM is wasted RAM" but it fails to take into account of the severely limited system resources we're dealing with, so I feel a new approach is required.

This is also why ive been begging in vain for Zram, and miss the custom kernel so much.

The flushrate thing is interesting, I could be wrong, but I think this may have started with introduction the patched graphics drivers needed to get the device to play nice with N...
[Nexus 7 Original Development] AceDuff93:
Hi, I'm running into that same problem with my N7. From Twrp (3.2.1-0) I can install both the firmware and then the Open Gapps Pico, but during the initial setup I get the same error.

My problem is that after the installation inside Twrp, I lose the connection to the pc... I assume usb debugging gets toggled off when I go out of the recovery and start the first boot of the rom, so I am unable to run the command you suggested. I am kinda confused at this point, is there something I'm missing?

Thanks a lot for your courtesy!!!

P.S.: after flashing the Gapps I usually do a wipe dalvik/cache in twrp, might this be the problem?
[Nexus 7 Original Development] adstraylight:
There are a couple of other things you could try:

1. If you don't get the fc error immediately, try pressing the four corners of the screen several times in a clockwise direction starting at the top left. This can cause the setup wizard to close and allow acces to the launcher from where you can set up the device manually. This may depend on the version of the setup wizard included in your gapps pckage.

2. There is a brief window of opportunity, just before the wizard starts, to swipe down the notification panel, from where you can access the settings ,enable Wi-Fi, grant permissions to the system apps that are missing, incuding the setup wizard, and this should allow it to function correctly.

I recently did a completely clean flash, and found the second method worked for me, it took a few goes as the notification panel is only available for a split second.
[Nexus 7 Original Development] AceDuff93:
Thanks a lot for your help! Luckily, I stumbled upon an user mentioning Beans Gapps while I was reading the thread and flashing them instead of Open Gapps worked! No wizard setup error with that package and Play Services are now up and running!

Thanks again for taking the time to answer! ;)
[Nexus 7 Original Development] adstraylight:
No worries, glad you got it sorted out
[Nexus 7 Original Development] abhifx:
I am not going anywhere the way charging issue my nexus 7 is showing. even with 2 amp charger and pogo pins, the tablet barely charges. let alone charge in 2 hours as per youtube videos. anyone who has some thoughts in this? initially i suspected usb to be the culprit and pogo pins would be god send... but not anymore.
[Nexus 7 Original Development] adstraylight:
This os totally OT, but have you concidered that it might be just that the battery is worn out? I'm not sure if you can still get replacements on eBay etc, but I bet they'll be very cheap by now.

Also I find that cleaning the Pogo contacts occasionally can make all the difference, for this I use a can of specialist contact cleaner, available from lots of places. The battery/charging controller is very sensitive on the N7, so any variation in current can cause this problem, I gave up on the USB port years ago, and have been using a dock ever since.

Btw, a 2hr charge time is a bit optimistic, the best I've ever managed is about 3.
[Nexus 7 Original Development] dirtyreturn:
Hi XDA, on the latest 7.1.2 build of unlegacy I've tried to flash opengapps package and it says I've no more space in the system partition. Could you please help?
[Nexus 7 Original Development] abhifx:
you are lucky to get the dock, i cant even find / afford the dock. Contacts cleaning is a good idea as the contacts were unused for so many years.

I have no idea how / why people have used nexus 7 as car HU as i pissed at ASUS pathetic quality. usb fails, speaker fails, headphone socket fails... and my latest battery shake up.

end of off topic.

I am using this without gapps and its flying. i guess i should search for alternative market app to keep my softwares updated at least.

does this os support signature spoofing?
[Nexus 7 Original Development] sheffzor:
Signature proofing is still not supported but we are aware of that and we have some potential solution for it.

Enviado do meu A0001 através do Tapatalk
[Nexus 7 Original Development] adstraylight:
The only version that will fit is the Pico version, you then need to DL the individual apps you use from the Play Store, as these will install to the /data partition.
[Nexus 7 Original Development] AndDiSa:
Or install Magisk and the Magic Gapps Module which installs Gapps systemless :)

Btw.: I didn't use it yet, but some people reported already that it's working fine on my AOSP build
[Nexus 7 Original Development] :
Hello, flashing grouper 6.0 is successful, but I am stuck at Android logo (bootloop?)

order: TWRP 3.0.2-0 > wiped everything > flashed rom zip > wiped cache/dalvik > rebooted > stuck at Android logo

nexus 7 2012 wifi

Help me please
[Nexus 7 Original Development] adstraylight:
To follow from the above, I'm now using the default balanced setting for cpuquiet, and everything is much snappier, no lockups so far!?
[Nexus 7 Original Development] adstraylight:
And back to runnable, the other options just proved too unstable.
[Nexus 7 Original Development] DesertShadow:
3.1 Kernel Not Upgrading to 3.4

Hello everyone,

I've followed the steps for installation exactly as they are typed but I can't seem to get the 3.4 kernel to stick.

My device is a Nexus 7 (2012/3G) with Grouper TWRP & UA-Grouper ROM. I don't need the cellular network capabilities for it so I opted for the Grouper ROM. If that's my mistake then I can correct it easily.

My end goal is to have it up and running with the latest Nethunter.

EDIT: Not removing anything because I'm not afraid to look stupid. There was a discrepancy with a ROM I was flashing. Unlegacy is perfectly fine.
[Nexus 7 Original Development] dmierzej:
Report from 7.1 on Nexus 7 3G 2012 model (tilapia)

The installation was almost smooth. I managed to install the latest 7.1 build 20180208-1017 for tilapia and Magisk 15.3. I had to reformat the /data partition to F2FS, otherwise I'd get fsck errors on the next reboot. The tablet feels much more responsive than with the stock Android 5.1.1, however I'm experiencing occasional lock-ups of the GUI (for example, when browsing around in Play Store). Access via adb works even then so if you have any pointers on how to debug what's causing the lock-ups, I'd be happy to help. Thanks for keeping this nice piece of hardware alive!
[Nexus 7 Original Development] FitzCreativ:
Unable to try the test build for grouper android 8.0. Stuck in a boot loop then it goes to the recovery menu
[Nexus 7 Original Development] abhifx:
Its a known issue and development is presently on hiatus for oreo.

a bit sad of nexus device, but devs have promised to work on it some day.
[Nexus 7 Original Development] Codster314:
Amazing Amazing Amazing ROM! Very fast and clean. I'm very impressed. No problems with lockscreen swipe. Wifi seems stable. And this is the first time (in a long time) where I can use the latest OpenGapps and still have the setupwizard run perfectly without any hiccups. Also right out of the box, SafetyNet passes, SELinux is enabled and Play Store Device Certification is successful. So no problems installing Netflix or anything. Thanks a lot for all your hard work!

My steps to Install incase anyone wants to have OpenGapps (without any hiccups):

[MENTION=2633638]Ziyan[/MENTION], [MENTION=4619263]sheffzor[/MENTION] The only thing that this grouper ROM is missing is the AOSP Night Light feature! I see you included it in the unlegacy mako device back in April 2017. I understand getting this feature working in grouper would require: "HWC2 support for the tegra3 to enable Night Light but we only have hwcomposer.tegra.so as a binary that, for my knowledge, doesn't support setColorTransform". Which is needed for AOSP's Night Light.

If getting AOSP's Night Light to work for grouper is too difficult, maybe you could add Lineage's Live Display into this rom for grouper. The unofficial lineage grouper ROM includes Live Display, so that is working on the Nexus 7 (grouper) just fine (thus their implementation must not need the setColorTransform support). It does the same thing and does change the screen colour during nighttime reducing blue strain, but the options are a bit different than the AOSP Night Light. Just Lineages version of it I guess.

I know this ROM's ideas are to keep it as pure to AOSP as possible. But Night Light is part of AOSP. So supporting it should be part of the unlegacy project for grouper. Even if you have to add some other's (non-setColorTransform) implementation to get grouper to support it.

Love the ROM! Thanks a lot for your hard work!
[Nexus 7 Original Development] abhifx:
Implementing lineage's method of night light does not looks optimal as it sorts of overlays a colour layer to mimic night light and makes our laggy system even more lag. AOSP does the real correction but as you have already pointed out, does not seems to be possible with the existing binary. unless someone reverse engineer and writes a new code, night light will not see the day of light on grouper (pun intended) :P
[Nexus 7 Original Development] adstraylight:
This explains why the colour corection facility for colour blind users doesn't work well on grouper either, but I do use a night light app called eyefilter that uses an overlay without causing noticeable lag.
[Nexus 7 Original Development] Codster314:
I noticed a small bug on grouper. When on the AOSP launcher home screen, and if u are in landscape orientation, u can not swipe up to access the app list. U see the small arrow in the bottom left, but no matter where I swipe up u can't access the app list.

In portrait mode it works fine to swipe up though. Just landscape mode doesn't work. Please correct me if I'm wrong. I feel like it's the grouper's soft keys which are blocking the "swipe up area" in landscape mode.

This is on the default AOSP Launcher which comes with the ROM.
[Nexus 7 Original Development] Almere:
Finally got Gapps working properly

I've followed this tread for a while now and as I own a few old nexus 7 groupers that I picked up for a bargain trying out different roms became some sort of a hobby. But although these roms (Nougat and Marshmallow) installed fine without Gapps, I've always had problems after installing them with Gapps. In fact post two mentions that installing GApps is problematic. They varied from not even booting to hanging initial setup to crashing apps. But after trying BeanstalkGApps from androidfilehost I found them working perfectly. It seems to skip the first setup but gives full support for all Google apps.

Unfortunately after reset same problems. Then I wiped everything, including internal storage from twrp. Formatted data to f2fs, and installed the 6.0 version with OpenGApps nano. Tried it several times, including resets on different Groupers (8, 16 and 32GB) and works great!
[Nexus 7 Original Development] FitzCreativ:
7.1 ROM appears to be stable after install and after flashing gapps but freezes when installing apps in the background. Any suggestions?
[Nexus 7 Original Development] adstraylight:
[MENTION=2633638]Ziyan[/MENTION], I see a recently added open commit for 8.1 to fix system ui crashes, could that also be relevant for N?

The system ui does crash occasionally on this ROM, and afaict it's not due ro OOM, it doesn't happen very often hence the lack of logs, but the conditions seem to be when the system is interrupted by me when it is doing something intensive like loading a big app.
[Nexus 7 Original Development] Clamor:
Please enclose dmesg/last_kmesg logs while freeze occures. It may be reproduced by intense swyping in menu/home screen and opening many apps (intense work as you said). Thanks
[Nexus 7 Original Development] adstraylight:
Got system ui to crash by rapidly punching the navbar keys, it did restart, so managed to get both logs. Hope they help?
[Nexus 7 Original Development] adstraylight:
Just had an unintended complete system ui crash + lockup, causing the screen to flash on and off, requiring a forced restart. This also wiped my wallpaper setting as is usual in the worst crashes btw.

It happened when I tried to open a news article on the website of a national newspaper, my guess is that it had an ad or embedded video that chrome didn't like, or that overloaded a background process.

Edit: I'd better add some names so this is seen: [MENTION=2633638]Ziyan[/MENTION] [MENTION=5424240]Clamor[/MENTION]
[Nexus 7 Original Development] Clamor:
[MENTION=2583740]adstraylight[/MENTION] I have seen this issue on other Tegra 3 devices, it is on Nougat and maybe Oreo. It will be investigated and fixed in near future. Please DO NOT remove attached log from your post.
[Nexus 7 Original Development] adstraylight:
Hi, I've installed the new experimental version, and it runs well so far, I was just wondering what the experiment was/is? Is there any specific comparison or feature to monitor or test?