yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] daniel_hk:
Up to this moment, no one can tell what's really happen. It appears in most of the N ROMs among all the developers. My post was trying to discuss and figure out why. Hoping to avoid these kind of trouble for the others. If you can't see that most of us are trying to help, that's you problem. Any form of teasing and blaming won't achieve anything but hate. Please don't test anyone's limit. OK? :)

At this moment, it seems impossible but I can only guess that your vol- button doesn't work.

If that's your case, it's your tablet's problem. You need adb for sure.

There are many many info. and guides for adb. It doesn't bother anyone that much. You don't even have adb and fastboot. I'm quite curious how you installed your first TWRP.

Anyway, even if you can go to bootloader, you can't recover without fastboot on your PC.

In short, you don't need the whole Android SDK. All you need is the platform tools. Fastboot and adb are two of the utilities in platform tools. Here is not the right place for these kind of basics. Anyway, I would list what I think might help.

There are too many versions of Linux. I'm using Ubuntu 1510 and Ubuntu 1604.

For earlier versions of Linux, you need to add device rules in /etc/udev/rules.d to permit the r/w access of the devices connected. Otherwise, adb and fastboot won't work.

Here is one of the example:

/etc/udev/rules.d/51-android.rules

#Garmin-Asus
SUBSYSTEM=="usb", ATTR{idVendor}=="091E", MODE="0666"

#Google
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666"

#HTC
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666"

#Huawei
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"

#K-Touch
SUBSYSTEM=="usb", ATTR{idVendor}=="24e3", MODE="0666"

#KT Tech
SUBSYSTEM=="usb", ATTR{idVendor}=="2116", MODE="0666"

#Kyocera
SUBSYSTEM=="usb", ATTR{idVendor}=="0482", MODE="0666"

#Lenevo
SUBSYSTEM=="usb", ATTR{idVendor}=="17EF", MODE="0666"

#LG
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666"

#Motorola
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666"

#NEC
SUBSYSTEM=="usb", ATTR{idVendor}=="0409", MODE="0666"

#Nook
SUBSYSTEM=="usb", ATTR{idVendor}=="2080", MODE="0666"

#Nvidia
SUBSYSTEM=="usb", ATTR{idVendor}=="0955", MODE="0666"

#OTGV
SUBSYSTEM=="usb", ATTR{idVendor}=="2257", MODE="0666"

#Pantech
SUBSYSTEM=="usb", ATTR{idVendor}=="10A9", MODE="0666"

#Philips
SUBSYSTEM=="usb", ATTR{idVendor}=="0471", MODE="0666"

#PMC-Sierra
SUBSYSTEM=="usb", ATTR{idVendor}=="04da", MODE="0666"

#Qualcomm
SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", MODE="0666"

#SK Telesys
SUBSYSTEM=="usb", ATTR{idVendor}=="1f53", MODE="0666"

#Samsung
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666"

#Sharp
SUBSYSTEM=="usb", ATTR{idVendor}=="04dd", MODE="0666"

#Sony Ericsson
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0666"

#Toshiba
SUBSYSTEM=="usb", ATTR{idVendor}=="0930", MODE="0666"

#ZTE
SUBSYSTEM=="usb", ATTR{idVendor}=="19D2", MODE="0666"

In current versions of Linux, adb would work but fastboot also need the above rules.

Good luck!
[Nexus 7 Android Development] Hubird:
My tablet kept rebooting regardless of what I did, I could not seem to get it into ADB / Fastboot mode however out of nowhere it worked.

For those with ongoing problems don't give up

For those that have not flashed this yet consider giving [MENTION=4948627]daniel_hk[/MENTION] time to work out a solution
[Nexus 7 Android Development] Hubird:
I could not get Systemless Root to work, has anyone manged to gain root?

If so please link to which version of SuperSU you used
[Nexus 7 Android Development] abhifx:
This known issue in AOSP recovery issue which also emerged in kerbel 3.4.x thread. you need adb to boot the device into bootloader mode and flash twrp again which will fix everything once and for all.

interestingly there is no such problem in AOSP based ROMs (DU and Carbon).
[Nexus 7 Android Development] Hubird:
No matter how hard I tired I could not get to the boot loader screen either and I think this might be our problem, expecting it to behave normally when it's in such a bad state..

I tired following the instructions posted about charging it and using the volume down + power button but it never seemed to enter the standard bootloader screen and it wasn't detected as a fastboot device.

All I can suggest is unplug the tablet from your PC, hold down the power button for an extended period of time and the screen on the tablet should go black, from memory it does not stay black (off?) but if it does turn it on again, reconnect to the PC and see if it is detected as a fastboot device (don't worry if it is not on the normal bootloader screen).

Mine seemed to be detected even though it was stuck in the loop, once it was detected I used the Nexus root toolkit to flash the latest recovery again... Sorry I can't be of more help.
[Nexus 7 Android Development] abhifx:
yes

just connect your tab to pc with drivers installed ans issue adb reboot bootloader

once in bootloader mode flash recovery vide fastboot command. i was in your situation but quickly got out with this
[Nexus 7 Android Development] abhifx:
havent faced any issue with carbon or DU. AOSP however boot loops in first reboot. [MENTION=4948627]daniel_hk[/MENTION] has done a great job by providing nice nougat ROMs for our aging tablet.
[Nexus 7 Android Development] daniel_hk:
All tools required adb. Your problem was that you don't have a working adb. If you have a working adb environment (Linux or windows) in the first place, you won't have any frustrations and heat up the atmosphere here.

For SuperSU, it has its own forum. Start from 2.6, I think, all SuperSU from chainfire are systemless. Someone has make system ROOTs from it for those devices like MTK which need special headers for repack. You better check the official SuperSU forum for detail.

I just remembered something. I want to know what version of bootloaders you guys have. In early 2015, Google had put some faulty bootloaders in their factory images for Nexus7. Both LP & KK were affected. The factory images were replaced months later. There was a thread discussing this issue. Anyone interested might search and read it. It might also responsible for buttons not working too.

I have a ver. 4.23 bootloader in my Tilapia. I never have any of the problem you guys have. I intentionally tried many ways but I never got that message.... I really don't know if its the cause of all these.

My friends always teasing me as the trouble magnet. It's a kind of stupidity that I fail to quit.... I always pick up the problem that nobody want to respond. That's why I prepared post#2. I just wanted to share and discuss. Only hope it might help. Suddenly I became the target to be blamed... Am I deserve that? :(

This thread was not for releasing ROMs for daily use. That's not my intention in the first place. I clearly stated "ROM & discussion" in the title and there is the bold red line "Here is for sharing of experiences and discussions". Sadly, no one really read or care about.

I just tested build this as a start for my other custom ROMs. These test builds were in my kernel thread some times ago. I answered to the requests and started this thread earlier. It's mainly for discussion, hopefully other developers and users can share their experiences in further development. It not a place for crying and blaming.

There are other AOSP out there. Those from [MENTION=2188693]AndDiSa[/MENTION] and [MENTION=6754437]millosr[/MENTION] are good alternatives.
[Nexus 7 Android Development] CZ Eddie:
I get "Process system isn't responding" when doing a full wipe (everything but internal storage) and flashing just the ROM or also when flashing ROM + banks gapps.

Also getting "Music has stopped".

Flashed twice with two full wipes. Same issue both times.

I'm coming from Marshmallow Broken OS.

Any ideas?
[Nexus 7 Android Development] abhifx:
music is supposed to stop responding, disable it and get a new music player. (i suggest open source vanilla music player)

---------- Post added at 08:54 AM ---------- Previous post was at 08:52 AM ----------

Dear [MENTION=4336485]alezardstar[/MENTION]

OT

sincere request that you not go this route, at least the guy is responding. If you reread your last post its kind of bit on negative side. we as a grouper community would like to retain the small amount of devs we have left here.

cheers!

OT ends. Back to ROM discussion

---------- Post added at 09:01 AM ---------- Previous post was at 08:54 AM ----------

@daniel_hk my grouper version is 4.23 and i have not faced any issue as of yet, except for the stupid charging port issue.
[Nexus 7 Android Development] AndDiSa:
[MENTION=4336485]alezardstar[/MENTION] installing SuperSU in systemless mode is a bit tricky. In the beginning I ran into similar problems, especially as Chainfire stated that SuperSU will install systemless on unmodified AOSP 6.x / 7.x builds.

Nevertheless nobody is able to preview all the things that can go wrong. It's always a kind of trial and error. In first place everybody needs to try to fix his problems by himself. If you are stuck, ask for help, but there is no guarantee for it.

Everybody is working in his spare time on this stuff. If you are unhappy with the 'product' / help you are getting, look for an alternative. I do not want to offend you, only my 2 cents.
[Nexus 7 Android Development] AndDiSa:
Yes, I have Adaway installed and it works, you only need to define a different hosts path ...

Btw. If you would like to integrate pph's superuser, try to do it, all sources of all the ROMs we are discussing here are on Github but why are you trying to force other people to go your way?
[Nexus 7 Android Development] AndDiSa:
Yes, I used the official apk and I am using /data/hosts as path
[Nexus 7 Android Development] mooncow:
Hey, I wanted to say thanks to the developers for this ROM which brougt to life again my Nexus wifi.
[Nexus 7 Android Development] daniel_hk:
This latest AOSP Android-7.1.0_r4 builds are out.

I have triple checked. Every recovery related resources are removed.

If there is still reboot issue, it can not be from this. ;)
[Nexus 7 Android Development] myxomop25:
Hi there, brothers!

I know that my question may be stupid and someone might laugh at it. But I really don't know how to make camera work. I've tried a plenty of camera apps from Play Store. But all they don't work with force close. I positively don't know hot to manage camera work. Has anybody faced that problem? Maybe, there are some workarounds. I am very grateful to anyone who can show me the right way of eliminating the issue.

Sincerely yours,

Ilya.
[Nexus 7 Android Development] daniel_hk:
I don't think its your problem. I'll take a look this weekend. Cheers! ;)

Edit: I just checked. In 7.1.0, the CameraService fail to register old HAL1 camera blob. With no hope for an updated blob, see if there is a work around.

In the mean time, back to CR-5.1 (7.0.0_r14) if you really need the Camera.
[Nexus 7 Android Development] melkozerov:
Hi, Daniel/ I can't install this firmware. The process ends with error 7/ What not to do so?
[Nexus 7 Android Development] shibadoo:
[MENTION=4948627]daniel_hk[/MENTION]: Would you mind sharing your knowledge of building Android N for our beloved device (in my case tilapia)? I was able to build Android M for tilapia thanks to Dmitry Grinbergs excellent tutorial, but when trying to build Android N, I am getting errors (this one occurs while building grouper which - according to dmitry - is necessary for building tilapia):

Starting build with ninja
ninja: Entering directory `.'
[ 0% 4/24956] build out/target/product/grouper/obj/ETC/sepolicy_intermediates/sepolicy
FAILED: /bin/bash -c "(out/host/linux-x86/bin/checkpolicy -M -c 30 -o out/target/product/grouper/obj/ETC/sepolicy_intermediates/sepolicy.tmp out/target/product/grouper/obj/ETC/sepolicy_intermediates/policy.conf ) && (out/host/linux-x86/bin/checkpolicy -M -c 30 -o out/target/product/grouper/obj/ETC/sepolicy_intermediates//sepolicy.dontaudit out/target/product/grouper/obj/ETC/sepolicy_intermediates/policy.conf.dontaudit ) && (out/host/linux-x86/bin/sepolicy-analyze out/target/product/grouper/obj/ETC/sepolicy_intermediates/sepolicy.tmp permissive > out/target/product/grouper/obj/ETC/sepolicy_intermediates/sepolicy.permissivedomains ) && (if [ \"userdebug\" = \"user\" -a -s out/target/product/grouper/obj/ETC/sepolicy_intermediates/sepolicy.permissivedomains ]; then echo \"==========\" 1>&2; echo \"ERROR: permissive domains not allowed in user builds\" 1>&2; echo \"List of invalid domains:\" 1>&2; cat out/target/product/grouper/obj/ETC/sepolicy_intermediates/sepolicy.permissivedomains 1>&2; exit 1; fi ) && (mv out/target/product/grouper/obj/ETC/sepolicy_intermediates/sepolicy.tmp out/target/product/grouper/obj/ETC/sepolicy_intermediates/sepolicy )"
device/asus/grouper/sepolicy/sensors_config.te:16:ERROR 'unknown type sdcard_external' at token ';' on line 20915:
allow sensors_config sdcard_external:filesystem { mount unmount };
allow sensors_config sensors_data_file:dir mounton;
checkpolicy: error(s) encountered while parsing configuration
out/host/linux-x86/bin/checkpolicy: loading policy configuration from out/target/product/grouper/obj/ETC/sepolicy_intermediates/policy.conf
[ 0% 4/24956] target thumb C++: init <= system/core/init/init.cpp
ninja: build stopped: subcommand failed.
build/core/ninja.mk:148: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1

What do I have to change in addition to Dmitry's changes?

Thanks for helping!
[Nexus 7 Android Development] daniel_hk:
I had already uploaded and shared everything. The device tree is ready for N. I don't know why you still use the patch for M. Dmitry didn't upload the device tree so we need to start from LP.

If you can build M out. There is no need for further patch.

Don't just follow the steps. You need to study what they are really doing first. ;)

Good luck.
[Nexus 7 Android Development] shibadoo:
My guess was that the changes that were made from L to M where still valid for N. At least this is what I understood when reading Dmitrys explanations ("Cool hacks...").

I can build M only with the patch of course. Obviously there is some other problem that prevents me from building N. You are saying that not using Dmitrys patches would allow me to build N?

You are absolutey right, and that's exactly why I do not want to use something that you did upload somethere but understand what I have to change within the source files from android.googlesource.com and the blobs.
[Nexus 7 Android Development] daniel_hk:
I didn't refuse to help you. I have already provided and shared everything. Other developers would know what to do. I think you are new to github so you have these questions. This is not the right place but I would make it short here for the last time.

If you want to build LP, you clone the LP source from googlesource, right?

But, there is no source for M so you need to start with the LP source and apply the patch. If Dmitry had uploaded the source for M, you don't need to apply the patch. Just clone the source for M, right?

I don't know why you think download the LP source and apply patches is the right way. In that case, we should start from Android 1 and work our way up. It is obvious not necessary.

The sources in github have already provided a better alternative. There are commits that you can follow and its much better than just a patch. That's what I told you to study.

I didn't mean we don't need Dmitry's patch. If you ever study my source on github, they are already included. And all the changes on top are already listed in the commits. Would you think it's better than one large patch which I doubt you would read? You can always generate the patch with the "git diff" command. That's what Dmitry did.

This is not the right place to teach you how to port or how to use github and git. AOSP has a very good tutorial. Github also have decent helps. If you want to learn deeper, GIT have very detail manuals and tutorials. This is the usual path that every developer here would follow.

For further questions, you may PM me or start a thread in the Q&A forum.
[Nexus 7 Android Development] jacky03:
What a great rom:fingers-crossed: I didn't had N7:good:

Where is the screenshots,good Mr Dannil:o
[Nexus 7 Android Development] shibadoo:
Not my words, I never said that you refuse to help.

Wrong.

Correct, so let's stop this discussion here.
[Nexus 7 Android Development] rtiangha:
Flash performance aside, does anyone know how this ROM performs with encryption enabled? Does it even work?
[Nexus 7 Android Development] daniel_hk:
The new Android-7.1.0_r7 (NDE63X) is out.
[Nexus 7 Android Development] sasawatc:
Insufficient storage space available in System partition when installing OpenGAPP

I'm sorry, I know this might not really related to the rom... I have successfully installed the ROM (7.1_r7) but I can't install the OpenGAPPs due to insufficient storage. Does anyone know what should I do or how can I repartition the system partition? I'm using Nexus 7 (2012) Wi-Fi Only.

Thank you!
[Nexus 7 Android Development] AndDiSa:
You need to use the pico apps, other versions are too big to fit into the /system partition
[Nexus 7 Android Development] rauhut:
Encryption broken?

Switched tilapia to latest version coming from different ROM (clean install with F2FS in cache and data) and installed without problems. When turning encryption on in the settings the device rebooted and got stuck in bootloop (Google logo - reset - Google logo). Both bootloader and recovery can be accessed via key pressing but even after factory reset it doesn't boot. Will do reinstall tomorrow but would like to know if it is just here or does ROM have a general issue with encryption? :confused:
[Nexus 7 Android Development] suryatej77:
unable to install

keep getting the "updater process ended with error: 7" error

---------- Post added at 10:50 AM ---------- Previous post was at 10:42 AM ----------

fixed by rebooting to recovery :silly:
[Nexus 7 Android Development] 239:
You could try ext4 next time (I didn't notice any slowdowns after using ext4 on cache/data again):
[Nexus 7 Android Development] rauhut:
Changing cache and data back to ext4 unfortunately did not help, device ends also in boot loop but was worth a try. In case it can help to narrow down the issue: I have the impression that something is messing up the partition as soon as encryption is started and device reboots to execute the encryption (no messages appear, just black screen). After powered down / rebooted into recovery with key combination and wiped all partions to restart from scratch I was able to reinstall both ROM and GAPPS but ended in the same boot loop at first start again. Changing file system back and forth in TWRP solved the issue and reinstall worked. Will leave it unencrypted for now although would feel better if it were so hopefully reason can be found and fixed.

I'm still impressed about the overall performance this ROM gives to my old device. :good:
[Nexus 7 Android Development] 2x4:
i know this is still in beta, but how does it compare in terms of stability to an Android M rom like the unofficial PureNexus + parrotmod + DC kernel?
[Nexus 7 Android Development] ol@fson:
Would parrotmod work with this 7.1 release, or is it maybe already integrated?
[Nexus 7 Android Development] myxomop25:
Hey people!

I wonder if camera works in the new release of November, 11-th? As I noticed, no-one had mentioned that camera doesn't work in nAOSP ROM in the respective thread. So, maybe the problem had been solved all over in each ROM and camera started working?
[Nexus 7 Android Development] Psycho_Squid:
Thank you for this ROM. Is it possible to sideload or in other way update my Nexus 7 from previous builds of this ROM without overwriting the current installation, apps etc.?

Keep up the good work.
[Nexus 7 Android Development] daniel_hk:
Camera doesn't work in 7.1 yet.

You better make a backup in TWRP first. In case it doesn't work, you can easily restore your current state.

After that you may try dirty flash without factory reset/wipe data. Just wipe cache and dalvik-cache after flashing.

Good luck.
[Nexus 7 Android Development] daniel_hk:
Latest Android 7.1.1_r4 (NMF26O) is out. :D

Thanks for AndDiSa's heads up for the camera fix.

I'm busy at work and another device lately. Don't have enough time. Carbon followed the latest Android as usual and DU has upgraded to 7.1.0 now. If nothing "special" coming up, I'll release them one by one shortly.

Cheers!
[Nexus 7 Android Development] Troublicious:
Thank you daniel_hk ! Can you tell me if the horrible stuff called WideVine is integrated in one of these roms ?
[Nexus 7 Android Development] daniel_hk:
No. The outdated blob would crash in Nougat... It happen in my other devices too. Sadly, I can't access this service locally (blocked). Noway to study why further... :(
[Nexus 7 Android Development] 239:
Great to see the Nexus 7 still getting so much love, thanks for your support!

I guess you could update the known issues now that the camera is fixed :cool:
[Nexus 7 Android Development] tpuserhp:
I have the following problems with the updated ROM:

- WAZE app cannot get to my current location. I see many of the following logcat entries:

12-07 21:12:47.642 W/gps_daemon.sh(5864): type=1400 audit(0.0:478): avc: denied { getattr } for path="/vendor" dev=rootfs ino=2257 scontext=u:r:glgps:s0 tcontext=u:object_r:rootfs:s0 tclass=lnk_file permissive=0

12-07 21:12:47.662 W/glgps (5865): type=1400 audit(0.0:479): avc: denied { getattr } for path="/vendor" dev=rootfs ino=2257 scontext=u:r:glgps:s0 tcontext=u:object_r:rootfs:s0 tclass=lnk_file permissive=0

12-07 21:12:47.700 E/linker (5865): /system/bin/glgps: has text relocations

12-07 21:12:47.702 F/libc (5865): CANNOT LINK EXECUTABLE "/system/bin/glgps": /system/bin/glgps: has text relocations

12-07 21:12:47.702 F/libc (5865): Fatal signal 6 (SIGABRT), code -6 in tid 5865 (glgps)

Location is on. It could be the app's problem.

- I cannot edit the quick tiles for the settings. I cannot move any tiles around.

Thanks for your efforts on updating the ROM.
[Nexus 7 Android Development] daniel_hk:
We do tonight. I'll try to test build the Next Carbon tonight too. Cheers!

That would be a new SEPolicy. I'll include it in my subsequent releases. (probably Carbon first).

Can to send me the full log? I'll take a look tonight. ;)
[Nexus 7 Android Development] tpuserhp:
My logcat is attached. Thanks.
[Nexus 7 Android Development] daniel_hk:
The latest Android-7.1.1_r6 test builds are out. ;)
[Nexus 7 Android Development] Flowah123:
[MENTION=4948627]daniel_hk[/MENTION] do I need to flash ParrotMod?

Or did you add the same settings into the ROM?

Thank you <3
[Nexus 7 Android Development] daniel_hk:
I had only studied briefly and I never use it.

I'm not the right person to ask. These kind of questions should be asked in it's own thread, not here.

Good luck! ;)
[Nexus 7 Android Development] robgriff:
In the 7.1.1 AOSP ROM by Millosr he says that in the core he uses which I think comes from andisa most of the parrot mod settings are already included but I'm not sure if it really matters because in my experience for some reason every 7.1.1 ROM works well and all the ones before that seemed more sluggish so in my opinion something happened in 7.1.1 that may negate the need for parrot mod
[Nexus 7 Android Development] Flowah123:
Oh, I'm sorry D:

I thought you were the right person because other devs made what I asked you D:

Hope my sentence didn't offend you D:

---------- Post added at 02:20 PM ---------- Previous post was at 02:19 PM ----------

Wow, that's nice!

Thank you!