yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] Charles IV:
[MENTION=389117]min1968[/MENTION] I'm interested, have you tried flashing the ROM or not, and if so did it work?
[Nexus 7 Android Development] gordp:
F2FS works with this ROM

Yes; here are the results from 'sudo adb shell' which show that I am using F2FS with my /cache and /data partitions, with lineage-14.1-20170108-UNOFFICIAL-grouper.zip:

grouper:/ $ mount | grep f2fs
/dev/block/platform/sdhci-tegra.3/by-name/CAC on /cache type f2fs (rw,seclabel,nosuid,nodev,noatime,nodiratime,background_gc=on,discard,user_xattr,inline_xattr,acl,inline_data,inline_dentry,active_logs=6)
/dev/block/platform/sdhci-tegra.3/by-name/UDA on /data type f2fs (rw,seclabel,nosuid,nodev,noatime,nodiratime,background_gc=on,discard,user_xattr,inline_xattr,acl,inline_data,inline_dentry,active_logs=6)

I formatted my /data with F2FS from within TWRP, before even copying over the .zip file(s) for this ROM + GApps.

HTH! Have fun!
[Nexus 7 Android Development] 007.4:
I've just loaded this rom. All seemed to go well. I also loaded opengapps.pico.

However, after configuring the wifi I cannot get past the next the next screen regarding "On your other device....."

I do not have another device! If I try "Try this instead..." I just get stuck in a two screen loop. Pressing "skip" after the wifi configuration (for the short while it shows) does nothing. How can I bypass this configration screen an move on to the next one?

TIA

SOLVED

I installed opengapps again and all seems fine. Just going to finish configuration now.
[Nexus 7 Android Development] magnaflare:
kernel upgrade necessary?

Is upgrading the kernel necessary to use this rom? I have a grouper with stock kernel 3.1.10, Android Kitkat.

If yes, please point me towards a recommended kernel.
[Nexus 7 Android Development] aaopt:
The ROM includes AndDiSa's kernel. I have not tested it with any other.
[Nexus 7 Android Development] Dggrr:
Fantastic! A big thanks to all involved in this.

This ROM has really bought my Nexus7 back to a useful life.

I upgraded from the last CM ROM which was struggling to do anything.

This ROM really rocks in comparison.

I've also followed the build steps and updated to today's ROM with no problems.

Great to know there is life after CM.
[Nexus 7 Android Development] Charles IV:
Great, can i ask you something about the build, do you have su built in?
[Nexus 7 Android Development] hanschke:
can we expect a 15 merge?
[Nexus 7 Android Development] jackspeed:
It seems to be executed correctly w/ cron scheduler app from play store.

I have to watch the performance for a longer period...
[Nexus 7 Android Development] JT1510365:
no please stop asking for oreo i doubt our nexus 7 will get oreo
[Nexus 7 Android Development] hackintosh5:
I'll have a look at building it when I work out why I can't build for my athene.
[Nexus 7 Android Development] Charles IV:
[MENTION=4598799]hazzer[/MENTION] has an Oreo tree, but when I last tried there were errors due to building a vendor image. I guess everything is wip of we ever do get Oreo
[Nexus 7 Android Development] hackintosh5:
We probably don't have a big enough oem partition for a vendor image anyway, so this could probably do disabled.

Edit: and my build PC needs fixing; idle temp is 60°©, which is 3°© below designated max. Trying to update bios soon so as to enable vcore voltage settings, which is the root cause.
[Nexus 7 Android Development] harryyoud:
Yeah, so basically our /system is far too small for 15.1 even with pico gapps. So, I made /cache into a /vendor partition and we can use /data/cache instead, and some stuff can move from system to vendor. 15.1 is booting for me, but it's gonna be a while before everything is fixed (last on my list is DRM and sensors). I can post a build in a few days if people are interested
[Nexus 7 Android Development] aiamuzz:
interested in an oreo rom ? ... of course !!!

some time back stargo did confirm that he was finding it difficult to bring out an oreo for our grouper ... so i had pretty much given up on it ...
[Nexus 7 Android Development] hackintosh5:
Is there a way to download this? Does WiFi work in 15.1?
[Nexus 7 Android Development] AndDiSa:
[MENTION=8556932]hackintosh5[/MENTION] you could try to use Magisk with the Systemless Gapps Module to get Gapps installed when /system is too small ... (only as a hint) ;)
[Nexus 7 Android Development] hackintosh5:
Yeah I thought of that, but where do I download the system and vendor
[Nexus 7 Android Development] Pich018:
Hello,

I have install this ROM with Android gapps pico. It's very cool.

I have just a bug with android.process.acore. it's stopped all times.

Do you have the same bug ?
[Nexus 7 Android Development] hackintosh5:
Factory reset from twrp and try again
[Nexus 7 Android Development] Charles IV:
Thanks, I've just built and got this error, and it appears to be because of this commit.

I've made a pull request to [MENTION=2188693]AndDiSa[/MENTION]'s github, but because nothing has been done to fix the issue so far, I imagine AOSP builds don't have this, so I'm not sure if it will be merged, or if there's something we can do in out device tree to override it.
[Nexus 7 Android Development] Charles IV:
Hi, I've been trying to build lineage 15.1 from your tree, however I always get an error about

You cannot install files to /.../android/lineage-15.1/out/target/product/grouper/system/vendor while building a separate vendor.img!

You said it was booting for you, so how did you get round this?

(I imagine quite a few of us are interested in your build as well!)

pastebin of my build error
[Nexus 7 Android Development] hackintosh5:
Weird, that sounds like it is trying to build treble...
[Nexus 7 Android Development] AndDiSa:
[MENTION=7211583]Charles IV[/MENTION]

/.../android/lineage-15.1/...

you are building lineage 15.1 instead of 14.1 I doubt it will run out of the box as there are several kernel modifications needed
[Nexus 7 Android Development] Charles IV:
Perhaps, this is building lineage 15 though. I'm not really sure, because I don't think it has to build treble. I'll update my message to say I'm building Los 15.

No, I didn't expect it to, however [MENTION=4598799]hazzer[/MENTION] implied he'd got it building and booting using his sources, yet I keep getting stuck on this error, and all I can find on the internet is irrelevant (removing lines from configs in vendor/gapps, which we're not building).
[Nexus 7 Android Development] aiamuzz:
could somebody tell me the name of the boost app(to boost memory) that is present on the desktop of this ROM by default ?

Its very handy and seems very light weight and does its job well.

thanks.
[Nexus 7 Android Development] hackintosh5:
Could tell if the #Filesystem section of BoardConfig.mk contains any references to a vendor partition and, if there is, try building without it?
[Nexus 7 Android Development] Vladimir2k9:
In treble theme suggested to copy files from vendor partition to /system/vendor

https://xdaforums.com/project-trebl.../tool-capire-le-treble-terble-vendor-t3774629
[Nexus 7 Android Development] hackintosh5:
and also look in proprietary-files.txt and make sure nothing references /vendor, only /system/vendor. Alternatively you could actually try to build for treble and make sure of the opposite! That would be truly awesome
[Nexus 7 Android Development] Charles IV:
From what [MENTION=4598799]hazzer[/MENTION] said, he's using the vendor partition because there's not enough space on system for los 15. From what you guys are saying, it sounds like he's also building treble, so I'll look through propritetary-files.txt etc to ensure it's all looking right for that.

Thanks

edit: also i did previously try building without vendor, and I got an error saying there wasn't enough room in the system img!

update: nope, still getting

Non-symlink /media/charles/SSD/android/lineage-15.1/out/target/product/grouper/system/vendor detected!
You cannot install files to /media/charles/SSD/android/lineage-15.1/out/target/product/grouper/system/vendor while building a separate vendor.img!
[Nexus 7 Android Development] AndDiSa:
[MENTION=7211583]Charles IV[/MENTION] try to disable optimization in BoardConfig:

WITH_DEXPREOPT := false

then even LineageOS 15.1 should fit into the /system partition
[Nexus 7 Android Development] hackintosh5:
Try `grep -r`ing for `system/vendor` in the device tree
[Nexus 7 Android Development] Charles IV:
thanks, will try

It was only a few days ago someone on irc told me how to grep, and I've already forgotten to do it xd.

I checked and there were no references other than comments.

update: ok, so i just reverted the vendor commit, without AndDiSa's idea, and it built successfully! however I image it will fail when I try flashing. I may try flashing it, however for now im gonna mka clean (because I didn't do that for speed earlier) and try again, if it works, great, if it doesn't, it doesn't, and either way i'll try anddisas idea, so hopefully it works during flashing.

another update:

I've built again, and after updating twrp, I flashed successfully, without AndDiSa's patch - I think this is because 'WITH_DEXPREOPT_BOOT_IMG_ONLY := true' is already present in BoardConfig.

Unfortunately, I've got a soft brick, and it stays on the google logo. It's progress though, but now I've got to troubleshoot the possible causes.

I'll upload my build if anyone wants it to test themselves.
[Nexus 7 Android Development] Charles IV:
how can we tell? I know it was trying to build a vendor image, is that what made you guess it was building treble?

If there is another way of telling, do you know how to make it build/not build treble?

just want to find out why this isn't booting.
[Nexus 7 Android Development] hackintosh5:
Could you send the contents of the kernel fstab from the build output? I suspect you have ended up building treble but the kernel doesn't support treble
[Nexus 7 Android Development] Charles IV:
err... i don't understand, sorry, could you elaborate on how to get that please?

I've just build again, so I've got a new pastebin of the whole terminal output if you want.
[Nexus 7 Android Development] hackintosh5:
Never mind, I thought you got it to build and the boot failed. Please send from devicetree the file proprietary-files.txt

---------- Post added at 03:04 PM ---------- Previous post was at 03:01 PM ----------

Also `ls android-build-env/out/product/target/grouper/system/vendor` run in terminal
[Nexus 7 Android Development] Charles IV:
attatched proprietary-blobs.txt (there was no such thing as proprietary-files.txt)

I have tried building when I've replaced the /system/vendor with /vendor, but I've just synced, so they're system/vendor again.

(edit: also the device tree is: https://github.com/harryyoud/device_grouper)

and the command:

charles@eddie:/media/charles/SSD/android/lineage-15.1$ ls android-build-env/out/product/target/grouper/system/vendor
ls: cannot access 'android-build-env/out/product/target/grouper/system/vendor': No such file or directory
charles@eddie:/media/charles/SSD/android/lineage-15.1$

then I realised I had to change it a bit:

charles@eddie:/media/charles/SSD/android/lineage-15.1$ ls out/target/product/grouper/system/vendor
bin build.prop default.prop etc firmware lib manifest.xml overlay
charles@eddie:/media/charles/SSD/android/lineage-15.1$
[Nexus 7 Android Development] AndDiSa:
[MENTION=7211583]Charles IV[/MENTION] you are trying to build lineage 15.1 and I suppose you are using the Grouper branches for lineageOS 15.1 from Harry Youd ... in that case the BoardConfig contains a property to build the vendor image:

TARGET_COPY_OUT_VENDOR := vendor

and the fstab is configured to mount the cache partition as vendor partition:

/dev/block/platform/sdhci-tegra.3/by-name/CAC /vendor ext4 ro wait

changing his modifications back to

BOARD_NEEDS_VENDORIMAGE_SYMLINK := true
#TARGET_COPY_OUT_VENDOR := vendor

and

#WITH_DEXPREOPT_BOOT_IMG_ONLY := true
WITH_DEXPREOPT := false

and

#/dev/block/platform/sdhci-tegra.3/by-name/CAC /vendor ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,check,formattable
[/CODE

should fix the build.
[Nexus 7 Android Development] AndDiSa:
[MENTION=7211583]Charles IV[/MENTION] there are kernel modifications, modifications regarding sepolicy and other modifications needed to get the Oreo build booting, at least when I was trying it last time. I do not know the current state of Harry's branches but I doubt they will boot out of the box ... it's probably not as easy as you are expecting.
[Nexus 7 Android Development] Charles IV:
will do

edit: how should I do this? I've extracted the boot image, and looked inside the ramdisk folder at stuff like the fstab, but I assume this is telling us nothing new?

can't find much online on decompressing the kernel

I think the kernel I'm currently using is ua's nvidia/tegra3, but I'll try harry's.

It's certainly not easy, but it's just so annoying I can flash it successfully but go no further.

Due to my limited developing knowledge, I'm just trying to try everything, seeing if I can get something working, which is why I want to try your kernel.

The other thing was, harry said he got it booting earlier in this thread, I just can't replicate it.

Thanks for all the help though guys
[Nexus 7 Android Development] nex86:
This works with F2FS yea?
[Nexus 7 Android Development] Charles IV:
I think it does, but I haven't tried it.
[Nexus 7 Android Development] Flounderist:
Mine is running on f2fs on /data partition.

It won't make the device lightning fast, it helps a very little.
[Nexus 7 Android Development] Charles IV:
[MENTION=2188693]AndDiSa[/MENTION] I know a while ago I asked you about changing the BoardConfig to make the system partition larger, well someone on irc re-partitioned their Nexus 10 (here's their log) to enlarge system, and then flash gapps etc.

I was just wondering, what changes would be necessary to make this persistent across updates, and what do the board config values actually do? Do they just say how big the system.img etc will be?

Thanks.
[Nexus 7 Android Development] AndDiSa:
[MENTION=7211583]Charles IV[/MENTION] there is no easy possibility to change the partition layout for the Nexus 7, you need to flash a new partition table which is not possible using fastboot but only with the nvflash tool. The problem here is that the nvflash needs special keys whch we can get only by using the Flatline - Unbrickable Nexus 7 (Wi-Fi + 3G) mechanism. But even then it's not easy to change the partition layout of the device ... To cut a long story short it's almost impossible.
[Nexus 7 Android Development] aaopt:
Board config is supposed to reflect the actual partitions that exist on a device. The commands you linked to show how one person changed the actual partitions on his device. However this approach is not without risk, especially if you are considering distributing a ROM with partition table modifications as a prerequisite. Even if it works, anyone who tried it would not be able to switch back to an older ROM without putting the partitions back first.
[Nexus 7 Android Development] Charles IV:
thanks guys!

I was just interested as to how the whole thing worked, and I'm not using gapps anymore on my n7, so it doesn't really matter for me.
[Nexus 7 Android Development] sjrmac:
You all could do GPT backups and flashes inside of TWRP if you make a table and modify it...
[Nexus 7 Android Development] Sam Nakamura:
It would be much easier to modify systemlessly, this way it doesn't matter how less space in system partition is left, in magisk download section is a module "magisk GApps" which flashes GApps independent from space avilable on /system, this principe can be applied almost unlimited...

Changing partition tables is a outdated solution to this specific problem which can be solved so elegantly in a systemless way...
[Nexus 7 Android Development] hackintosh5:
Just in case anyone doesn't understand this, AFAIK he/she is trying to say that you could use a magisk-like way to mount some part of /system from /cache for example. Like flash system1.img in system partition and put system2.img in a spare partition as a file. Then tell the kernel to mount both of them to /system using a unifiedfs. Only problem is now /system will be read-only even with root. A solution to this is to use the outdated-but-functional mhddfs with fuse.

Oops, I just realised my post is more technical than the one above LOL!
[Nexus 7 Android Development] Sam Nakamura:
You're right, my answer need's at least some background information to understand.... But we're a development forum after all :laugh:

Just an addition, you typically don't need to duplicate a whole partition, it's usually sufficient to just write needed applicatios / mods to another partition (like /data) where space isn't an issue (besides other positive effects) and mount it to /system in a modular fashion, hence the naming 'magisk module'...

Just meant as practical option or suggestion, not intended to go totally OT here by repeating well described technical data...
[Nexus 7 Android Development] mikem1074:
help needed

I'm trying to download an app that's android 4.0 or higher. Play store says its not compatible. any work around or fix?
[Nexus 7 Android Development] hackintosh5:
What app is it? Netflix, movie or banking you need to fix safetynet with magisk and magiskhide props config module
[Nexus 7 Android Development] terasgeorge:
If it is a game maybe our graphics card it is not compatible. I had the same problem with the game C.A.T.S.
[Nexus 7 Android Development] street_dog:
well, you could download it from apkmirror or apkpure...
[Nexus 7 Android Development] SGH-i200:
Yalp Store - download apps directly from Google Play Store as apk files

I would recommend to download the "Yalp Store" app from F-Droid, because it "lets you download apps directly from Google Play Store as apk files." I don't feel save loading APKs from such websites...

https://f-droid.org/en/packages/com.github.yeriomin.yalpstore/
[Nexus 7 Android Development] Danielmariuss:
Question? - Is this ROM only for WiFi? I put it on a tablet with 3G and I do not have the 3G card setting.

What ROM do you recommend for a Nexus 7 2012 3G 3G tablet?

Thank you
[Nexus 7 Android Development] hackintosh5:
Use search
[Nexus 7 Android Development] Danielmariuss:
Hello, after installing this ROM I can not install any ROM for Tilapia. She no longer recognizes my tablet as Tilapia recognizes her as GROUPER.

This is the error message:

This package is for "tilapia"device; this is a "grouper"

Updater process ended with Error: 7

Error installing zip file '....

What to do...
[Nexus 7 Android Development] Flounderist:
Reflash stock image using fastboot
[Nexus 7 Android Development] street_dog:
i'm on the road right now, but i would format system partition and have a go.
[Nexus 7 Android Development] Flounderist:
Did you made a backup?
[Nexus 7 Android Development] street_dog:
if the installed image is wrong, why backup? but it is a good habit to backup every time you upgrade or install anything.
[Nexus 7 Android Development] Danielmariuss:
I installed the stock image, I'm going to try something dedicated to Tilapia.

If you have suggestions, please.
[Nexus 7 Android Development] Flounderist:
An AOSP build should be available. Check another thread in the device forum.
[Nexus 7 Android Development] Flounderist:
I was meaning a backup of your previously installed OS. :cowboy:
[Nexus 7 Android Development] street_dog:
i've never had the problem you'r describing. but if i had, then i would have had a backup. i learned the hard way many years ago and have always stuck with that since. one thing with nexus phones, you can almost always start over with a new installation of stock rom.

but to the described problem. there are files on the system partition telling what system you have installed and if you format system partition those files are gone, so it should solve the problem. but if you have a backup, roll it back. it would solve the issue.
[Nexus 7 Android Development] nex86:
Any ideas how to fix the MTP host crashing issue?

I can't connect my tablet to my computer to transfer files because of this.
[Nexus 7 Android Development] Sam Nakamura:
Even if you boot to TWRP?
[Nexus 7 Android Development] Flounderist:
I sorted using Google Drive or any cloud service.
[Nexus 7 Android Development] Charles IV:
I haven't actually noticed the mtp crash since I've gone gapps-less. Of course, this isn't an option in all cases, but it's interesting.
[Nexus 7 Android Development] CriticalComposer:
Has anyone run into any issue with applications not being able to write to the internal storage despite having the Storage permission enabled? FolderSync won't even see the Internal Storage unless I assign it as an OTG drive and Jotterpad (a writing app) tells me that it's lacks write permission to it's own folder. It's almost like the userdata partition is borked somehow. This has happened to me twice on the latest Testing img (20180121). I'm going to try and older version but I don't want to be behind on the performance tweaks.
[Nexus 7 Android Development] pieceofphil:
Have you restarted or force closed the app after giving permission, that's normally doing the trick.
[Nexus 7 Android Development] Charles IV:
I haven't had this, have you tried a clean wipe?
[Nexus 7 Android Development] CriticalComposer:
This worked perfectly. I could have sworn that I already tried a reboot (it is troubleshooting 101 after all), but it worked this time at least. I wonder what causes the issue.
[Nexus 7 Android Development] Charles IV:
I tried building again today, and I'm getting an error.

The relevant bit is

frameworks/av/camera/cameraserver/Android.mk:18: Target has integrated cameraserver into mediaserver. This is weakening security measures introduced in 7.0
find: ‘/media/charles/SSD/android/lineage-14.1/out/target/common/obj/SHARED_LIBRARIES/libwifi-hal-mock_intermediates’: No such file or directory
Starting build with ninja
ninja: Entering directory `.'
ninja: error: '/media/charles/SSD/android/lineage-14.1/out/target/common/obj/JAVA_LIBRARIES/android-support-dynamic-animation_intermediates/classes.jack', needed by '/media/charles/SSD/android/lineage-14.1/out/target/common/obj/APPS/CMParts_intermediates/with-local/classes.dex', missing and no known rule to make it
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
make: Leaving directory '/media/charles/SSD/android/lineage-14.1'

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

I can't tell if it is something I did, because I was messing with cmparts, but I deleted that and resynced, so it shouldn't be that, any ideas?

full pastebin
[Nexus 7 Android Development] hackintosh5:
You need to clean/delete out directory. Or at least try thT
[Nexus 7 Android Development] Charles IV:
I already did that and got the same error.

mka bootimage and mka recoveryimage ago with fine, it's just mka systemimage that gets the same error

Edit: appears to be a problem with my environment/upstream - hammerhead gets the same error, is everyone else building fine?

Another edit: so glad someone told me what grep was. While I remembered to resync the cmparts vendor, I forgot to resync the cmparts app. Seems to be building fine now.
[Nexus 7 Android Development] sjrmac:
Hey Charles, I'm gonna get back to working on LOS for our tablet here shortly. I see you are trying to assign a OTA server in the lineage OTA PHP thread. PM me, I've got one setup at home that hosts my stuff and we can add n7 to it
[Nexus 7 Android Development] Subhassh:
thanks developer

no issues for mtp transfer, great use as a kindle for a tab that is so outdated to be put in use, nice battery backup , install more than 5 apps or any heavy apps slows down.
[Nexus 7 Android Development] X-Flies:
my nexus 7 is bootloping.

I can only use fastboot.

Tried to flahs twrp again but it stays doing the same.

Can we flash LineageOS using fastboot?
[Nexus 7 Android Development] Flounderist:
Which was your setup before having bootloop?