yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] TureX:
Ehm,i don't know how,but thanks , i Will try to update bootloader.
[Nexus 7 Android Development] Flounderist:
You can find a lot of useful guides in the forum.

I would recommend to use wugfresh nexus toolkit or fastboot commands using minimal adb & fastboot for PC.
[Nexus 7 Android Development] ThaiFighterGo:
Holy moly! The Rom is light and fast! I primary use N7 2012 as a Carplay display. It boots fast with almost no lag.
[Nexus 7 Android Development] :
Another great update from [MENTION=2188693]AndDiSa[/MENTION]! Many many thanks. I'm just so pleased my aging old grouper is still like new. :)
[Nexus 7 Android Development] Ahkah:
For whatever reason the search bar is back to non serif font with the January version. Strange. I installed opengapps pico from today.
[Nexus 7 Android Development] sc00ter98:
Hi I'm new to this build. It is very smooth and runs perfect for me.

But small issue.

My device connects to the car audio system via Bluetooth and then disconnects after 10 seconds. Ideas?
[Nexus 7 Android Development] AndDiSa:
Sorry, I've no clue what might be the issue ... to analyze the issue a log would be great.
[Nexus 7 Android Development] louwii_fr:
Just installed the rom, I'm super happy to see my N7 alive again, with no much issues. I keep it as clean as possible of course, not many apps installed, especially no social apps. And it seems to work very well. I'll see how f*cked my battery is, as I think I haven't charged it for a long time and that might have damaged the battery a bit.
[Nexus 7 Android Development] TNSMANI:
So long as you ensure that the battery is having 30 to 80% charge, I don't think that it would be damaged. If you allow it to run down completely and do not charge it for sometime then you may face issues.
[Nexus 7 Android Development] louwii_fr:
It's stayed turned off for months, not sure if I turned it off or if it shutdown because it ran out of juice. It seems to be holding a bit for now.
[Nexus 7 Android Development] loveandmarriage:
Question: Can the workaround for baseband_xmm_power wakelock be included into the rom?

Background: Some tilapia devices have a massive issue with the baseband_xmm_power wakelock. The battery drains very fast when the device is in standby. A guy named vorcers has developed a workaround for older android versions based on input of some other guys (see here: https://xdaforums.com/showthread.php?t=2107224). I used the workaround in the past and it helped quite nicely with the battery performance. Unfortunately, I cannot do something like this myself, but I would very much appreciate the inclusion of the workaround into this rom. I also think, that this may help other people as well ... :)

Thanks a lot and greetings to the world!
[Nexus 7 Android Development] AndDiSa:
This patch is included within the kernel almost since the beginning. As you might have seen this patch was already developed for Android 5.x ...
[Nexus 7 Android Development] SGH-i200:
So true!

I forgot to shut my N7 2012 down and never touched it for a year. Needless to say: The battery is done... Because of this ROM I'm thinking about replacing the battery! :cyclops:
[Nexus 7 Android Development] loveandmarriage:
This is cool and I did not know that ... So the obvious question ... How do I activate the patch? Cause I do not think that it works on my little Nexus ...

Thanks a million!
[Nexus 7 Android Development] AndDiSa:
There is nothing to activate. Do you see wakelocks? If yes, which ones? Do you have a log to provide? ...

... only the obvious questions ;)
[Nexus 7 Android Development] _tike_:
[MENTION=2188693]AndDiSa[/MENTION]

Thanks for your great work.

[MENTION=9350973]All[/MENTION]

is it necessary to update opengaps?

my nexus7 Grouper works great :)
[Nexus 7 Android Development] AndDiSa:
Normally Gapps shall update automatically, so no need to update manually. For initial install choose an actual package.

Edit: if you ask for re-installation after updating the ROM, then yes, you need to re-install.
[Nexus 7 Android Development] TureX:
Hi, Just a Little update, isn't necessary upgrade bootloader, was my magisk zip corrupted. Thanks anyway. Hope Will help anyone has same problem. Sorry for my bad English
[Nexus 7 Android Development] Ahkah:
Use the latest one from opengapps. Make sure to get ARM/7.1./pico as described in the first message of this thread.
[Nexus 7 Android Development] OlliWi:
Hi

can some of you please provide dmesg files after you connected your device to a charger?

And another dmesg file which is taken about 2 minutes later.

I´m currently trying to find out the cause of the slow charging issues that we are experiencing.

It seems that there is an issue with the configuration of the sm347 charger IC inside the Nexus.

Last night, my Nexus war charging as fast as never before, pushing about 1800 mA current to the battery, charging from 36% to FULL in about 1h30.

[ 5538.334397] bq27541_get_capacity = 36% ret= 40

[ 5538.335157] bq27541_get_psp voltage_now= 4014000 uV

[ 5538.337425] bq27541_get_psp current_now = 1714000 uA

[ 5538.339506] bq27541_get_psp current = 1714 mA

[ 5538.341229] bq27541_get_psp charge_full = 3359000 uAh

[ 5538.342305] bq27541_get_psp temperature= 230 (0.1¢XC)

[ 5538.343131] bq27541_get_psp status: Charging ret= 0x0100

[ 5538.343841] healthd: battery l=36 v=4014 t=23.0 h=2 st=2 c=1 fc=3359000 chg=a

[ 5538.345251] bq27541_get_psp current_now = 1714000 uA

[ 5538.346059] bq27541_get_psp current = 1714 mA

Some more information may be helpful to solve the issue.
[Nexus 7 Android Development] anonym6x6:
How to modify the Rom with colored status bar and many more settings?
[Nexus 7 Android Development] Ad4m5on:
Thank you

Having used the lineage rom which brought a new life out of the old nexus I changed to this one after Roblox wouldn't display a few of the main screens correctly. I was hoping it would solve the problem but I may need to do some more research as it hasn't. Even though I would like to thank you on this anyways on an even more slimmed down rom which has brought another life into the old gal (seems she has 9) but also for me having the security patch fairly up to date and updated is very welcome. So again thank you AndDiSa. :)
[Nexus 7 Android Development] loveandmarriage:
Ahoj AndDiSa

Thanks a lot for your very active responses! This really is great!

A couple of years ago I used another rom and discovered the wakelock patch I mentioned. The patch fixed my battery problems and I therefore assumed that this wakelock was the problem ... :)

Since I am using newer roms, I did not apply the patch anymore as I thought it was only working with the old roms. And of course my battery issues reappeared.

When I started to use your rom, I still had the battery issues and that is why I assumed that the patch is missing (or not active ;) ).

I will now try to analyze the issue more throughoutly using BBS.

Thanks again
[Nexus 7 Android Development] loveandmarriage:
ok, I just checked the BBS results and it shows, that the GPS kernel wakelock was 100 % active. The only app using GPS is Google-Play-Service ...

I switched off location services, but they only stopped running after restarting. Now, the wakelock seems to have disappeared. But I have no idea why GPS behaves like this. Any idea from your side?

I have only few apps installed on the nexus, and none of them should use GPS on an ongoing basis. I also went outside to make sure that the nexus has contact with satellites - which worked fine - but the wakelock stayed active also afterwards.

Switching off GPS is a good workaround for me, I just wonder what makes the GPS running all the time ...
[Nexus 7 Android Development] AndDiSa:
Well, without having log files to analyze the issue it's like gazing into a cristall ball ...
[Nexus 7 Android Development] JabaMS:
Bugs

Hello to all, I recently installed latest version of this rom, and at first everything looked stable. But, since I am using pogo pins to charge my tablet, I noticed that tablet is not detecting that is charging. If, for example, I turn it on while charging, there will be an icon that tablet is charging when it starts, but if I disconnect a charger, icon will remain same as its still charging until reboot, and in opposite same, while battery is being charged actually. There is problem with poweramp for example... it won't start, but on every other rom, works normally, so I am assuming that its something with rom actually. Also I wanna let you know that I had issues with setup wizard, so I had to install a recommended fix. Also rooted with recommended app, after all setup and couple of reboots. That's what I noticed so far and I didn't tried with older versions, this is first time installing this rom and wanna use it as car dashboard, so the thing with not detecting charger is big issue to me.
[Nexus 7 Android Development] Ler0y:
Hello friends !

Sory for stupid question, but tell me please - what resolution have wallpaper for standart aosp launcher ?

Thank you :)
[Nexus 7 Android Development] TureX:
1280 x 720
[Nexus 7 Android Development] Ler0y:
Thanks, but i have another problem, when i apply a new image (1280 x 720, *.jpg) - i have a black wallpaper, no image, only black font :(
[Nexus 7 Android Development] TureX:
Yes, i think Is an original Launcher bug, use another Launcher (example nova). Sometimes on "stock" luncher appear a pink background(in my case ,i don't know if Is only for me). Sorry for my bad English
[Nexus 7 Android Development] Ler0y:
Thank you for help, i think it's better solution.

But one moment - AOSP launcher "eat" 3 megabytes ram, Nova launcher "eat" much bigger.

And your english is normal, my language level - russian school ;)
[Nexus 7 Android Development] DragonTome:
Firstly, this is a great ROM and massive effort to keep early Nexus 7 alive. Much appreciation and admiration for the efforts.

I use 'WiFi ADB' (requiring root, which I have) to connect to my Nexus from a PC, mainly for side loading and file moving. I believe that the app used to work flawlessly. I am not sure when this new behavior started. I can only use 'WiFi ADB' and remotely connect to it, if I launch it and then go into Developer Options and toggle USB Debugging. The command line adb fails connect to the app until that last step is done. I have used this app on other ROMS/devices without the need for toggling that option. Can anyone suggest why this might be? and/or how I might solve the issue? It's not a 'showstopper' by any means, but it is a bit annoying when I forget to do the toggle.
[Nexus 7 Android Development] happy-kat:
This is a super rom thank you very much. I have it on my Nexus 7 2012 now to replace the stock Jelly Bean I had last applied as a working rom. As my tablet was already rooted and running a custom recovery clockwork 6.0.4.3, rooted and super su I did not change any of that, I pushed the files over and following the rest of the install worked really well, needed the wizard fix but that was quick to sort.

Now adding the apps I like to use.

Images also display even better and the screen was very good anyway I have always found.
[Nexus 7 Android Development] Flounderist:
I can't believe someone is still using cw recovery and su :D
[Nexus 7 Android Development] Codster314:
Love the ROM! And all the updates. I been using Ziyan's Unlegacy Project ROM, but lately there has been a few issues with it. I like how up-to-date this rom is and still getting performance tweaks in the Kernel.

I notice both of these projects are pure AOSP. Ziyan's using a 3.4 kernel, while this one is using a 3.1 kernel. Has there been any thought in updating this rom with that 3.4 kernel? Since it's been tested for quite a while now?

The main reason I been using the UA was because of the SELinux set to Enforcing, and SafetyNet and everything passes right out of the box (no need for Magisk or Root or anything). Which allows me to play FireEmblemHeros, Netflix, and other "SafetyNet" apps without Magisk or Root... very clean.

I haven't tried this rom in a while. Is SELinux set to Enforcing? And does SafetyNet pass without Magisk or anything? If not, since both projects are Pure AOSP, would it be easy to port the SafetyNet/SELinux fixes over from UA to this? Or is the different 3.4 vs 3.1 kernels the big issue?
[Nexus 7 Android Development] mikefive:
netflix/prime video etc. works fine here for me -without using safetyNet or SU-like stuff (microG with disabled SafetyNet, installed SuperSU)

HWInfo reports me "SELinux = Enforcing"
[Nexus 7 Android Development] AndDiSa:
I thought on upgrading to 3.4 but unfortunately the 3.4 kernel currently has some graphical glitches which might lead to blocking the device and finally to a reboot. (btw. that's one of the reasons why UA 8.x for the Nexus 7 is still not yet available). In addition the 3.1 kernel I am using is enhanced by several backports from 3.4 and other kernels so that it's not a big issue to stay on the 3.1 branch.

Regarding SELinux: it's in enforcing mode since ages now and also SafetyNet should pass without having Magisk installed (I didn't check recently but a few month ago it worked for me). In the beginning there was an su binary included within the ROM which prevented SafetyNet passing but this was removed some time ago exactly to get it passing the SafetyNet checks.
[Nexus 7 Android Development] :
Does this ROM support for USB DVB-T2 devices? If not, could someone please assist with the process to get this running. I have the latest version of this ROM installed with the following DVB-T2 device:

Geniatech T230C2

It is listed as a supported device here: linuxtv.org/wiki/index.php/DVB-T2_USB_Devices and here linuxtv.org/wiki/index.php/Geniatech_T230C2.

I have been able to get this device running on Ubuntu 18.04 LTS, using the above instructions, with Kaffeine as a frontend. However, I do not know enough about kernel compilation to include the specific modules needed for this device/kernel combination.

Any help in getting this up and running would be appreciated.
[Nexus 7 Android Development] samsungtab3:
kernel

hi! Iflash this rom and it do the imposible! Bring my nexus 7 from the dead ahaha

I want to do a oc to the cpu, but i can't the kernel dont let me.. someone konw some kernel compatible with this rom and with the support for the oc ?
[Nexus 7 Android Development] AndDiSa:
[MENTION=7056085]Codster314[/MENTION] Thank you very much for your kind and fruitful report! Reports like this are the ones who are helping very much to identify and resolve potential issues.

I had a brief look at your crash reports and as you already expected it's quite difficult to find the reason for the crash / FEH not running. I found some binder issues in the log (a topic I was already working on in the last days), so I'll append my experimental boot image for Grouper(!) which might fix this issue. If you would like to test ... ;) Not sure if this is the reason for FEH crashing, but there is a chance.

Another possibility for the different behaviour between UA and this ROM: UA is providing user-builds while this ROM is userdebug. Probably FEH is also checking the build variant ... but this is only a guess.
[Nexus 7 Android Development] happy-kat:
Sorry for this not being a technical contribution, but I wanted to share this rom is super fast and smooth on my Nexus 7 2012 but if you are a fan of swipe don't be tempted to install the Goggle GBoard as it will crush your fast tablet into a slow slug which is instantly remedied by uninstalling GBoard..

Also don't add a wallpaper, leave it empty (black) this also boosts performance.
[Nexus 7 Android Development] Codster314:
Hello, thanks for your help! I did try your new boot.img on a clean flash (clean flash, then "fastboot flash boot boot.img"). Upon booting up, the kernel was a newer version: 3.1.10-nougat-01711-g200f1c41973e-dirty ds@yoda #19 Fri Feb 1 19:10:18 CET 2019. However with nothing but FEH, it crashes at the same place (about 4 seconds during the loading of the app).

But your buildvariant=userdebug, is a really good guess! Since all the "Security" tests do pass, the app has to be doing something stupid'ish for its internal check. It looking at the buildvariant variable is very probable I think.

EDIT: I checked my "Xiaomi Redmi Note 3" which is running a custom Unofficial LineageOS ROM. Which was one of the few roms for Kenzo which also could run FEH/google pay/PokemonGo out of the box without crashing. It has a BuildID: "lineage_kezno-userdebug 8.1.0 ..." However, under AIDA64 it shows that the buildvariant=user.

I do not know if he generated a userdebug build, then manually set the buildvariant=user (so that certain secure apps could run, like google pay, and FEH, and banking apps). Or if the BuildID was just typed as userdebug, when it's not.

Either or, that ROM can also run FEH (and google pay, and such) fine (without magisk). And it's buildvariant=user... even though it may or may not actually be a userdebug build.

If that's possible, you could generate a userdebug build (if you really want that), and then just manually set procs so that it looks like a user build, ie the "ro.build.type=user". Which would maybe be enough to fool the FEH, pokemon go, and other apps which require a user build. Assuming this is the case. :) But yea another example of a custom rom with a buildvariant=user that runs FEH fine.

EDITEDITEDIT: KK, I did a clean install, and edited the build.proc so that ro.build.type=user (from userdebug) in TWRP (using adb pull / push). This indeed changed the value to "Build Type=User" in HWInfo. However FEH still crashed. So either it has to be a real user build maybe. Or something other needs to be done. :( Sorry I'm not much help.
[Nexus 7 Android Development] OlliWi:
To check if that can be reproduced I installed this app on my tilapia and it´s working without any issues. I played the tutorial and the first two prologue sessions.

I have attached two screenshots in a .zip file.
[Nexus 7 Android Development] spark001uk:
Thanks for your time and effort again [MENTION=2188693]AndDiSa[/MENTION] , it's much appreciated. The higher current charging is working now in this release.

In fact, I thought it would be a good time to share a bit of experimenting I have done with various chargers and cables, now we have this latest firmware.

First of all, it's important that everyone should know that, as you said before, a GOOD quality setup must be used in order to benefit from higher charging currents. The cable used must be of a decent size, with conductors in it which are adequate enough for the current, and ideally it needs to be screened as well. None of these flimsy pound-shop/dollar-store cables, they likely won't be up to the job !

One way that many charging systems regulate themselves is by performing a test of voltage drop. This is the voltage which gets lost in the cable, due to its resistance.

When plugging in to charge, the charging circuit begins (over the first few seconds) by increasing the charge current in several steps, and when it detects an excessive voltage drop - indicating the power supply/cable is starting to struggle - it backs off a bit and leaves it there. So, a better cable with thicker conductors and good grounding is likely to suffer less of a voltage drop, and therefore provide for faster charging.

Also it's equally important to say that the power supply should be at least 2A capable, although those of you that still have the original charger will have that already.

With my good quality 2.4A supply and a thick screened cable, I have now measured currents in excess of 1.4A (variable, depending on state of charge, battery health etc).

Hope this helps.
[Nexus 7 Android Development] OlliWi:
Thanks for your contribution.

But the charger issue is not mainly caused by the cables and/or charger you use.

It´s either a driver issue (and both drivers - the battery and the charger circuit driver - are a complete mess) or it may also be a hardware issue with the wiring of the charger IC.

There could be one pin (charge enable/disable) laying on an undefinded electrical potential as i´ve seen it on the grouper circuit diagrams.

It also may be related to both - driver and hardware issue.

I´m trying with [MENTION=2188693]AndDiSa[/MENTION] to figure out what´s going wrong there, but the biggest problem is, that you can´t find any data sheet of the charger IC (smb347) on the internet.

In a first step , we´re currently adding some debug output messages to the driver to understand, which program path is taken under which conditions.
[Nexus 7 Android Development] Codster314:
Heyas! Just wanted to make sure. Are you running Magisk? Or some kinda Root? I know the App will run with Magisk/Root, what I'm trying to figure out is if the app can run from just the Vanilla Rom (No Root, No Magisk).

And if you are NOT using Magisk/Root (just vanilla rom), what tilapia version are you on? (TWRP 3.2.3-0 / Build 20190110 / data formatted as ext4 or f2fs / installing google play or microg)?
[Nexus 7 Android Development] OlliWi:
Yes, i´m running Magisk 18.0. Pico gapps are installed. Data ist formatted as ext4 and TWRP is 3.2.1-0.

The device passes the basic SafetyNet check but not the fingerprint validation. Playstore says it´s not a certified device.

Upon first start, FEH asks to connect to a nintendo account but as i don´t have one, i skipped that. Maybe connecting to such an account will trigger additional safety checks, i dont´know.
[Nexus 7 Android Development] robgriff:
I've had 4 different nougat roms on my grouper and the swipe problem is consistent across them all, I've found that swiping fast, right to the top was the most likely to work but I just tried slow and short and it worked so maybe it's not about a swipe anymore, it's now a slide?
[Nexus 7 Android Development] k ahangar:
no run sim card on tilapia

please right sim card Operation on tilapia in next edit
[Nexus 7 Android Development] robgriff:
Just done a little more playing and it seems to me that I have to use some pressure ie not the lightest of touches, and have to swipe more than half of the screen (bit of a guess), and keep my finger on the screen until I know it's unlocked ie not flying away like spinning something.....
[Nexus 7 Android Development] AndDiSa:
[MENTION=7894717]robgriff[/MENTION] Thank yu for the hint, I had also some problems, but when I swipe slowly it's directly unlocking
[Nexus 7 Android Development] jolinnard:
Ok! Full logcat attached ;)
[Nexus 7 Android Development] cliffgamerz:
Can someone please guide me step by step on installing this rom as i am currently in stock nexus 7 2012 (wifi) 16 gb lollipop 5.1.1 rom. What are the steps to update as i am a noob to this scene. Thank you in advance.
[Nexus 7 Android Development] abhifx:
there are tons of guide online where they teach how to flash a custom rom.

as a brief intro

unlock bootloader (this will wipe everything)

flash custom recovery

copy rom and gapps files to tablet

go to recovery

wipe system-data-cache,

flash rom boot

go to recovery again and flash gapps

boot again and complete your setup
[Nexus 7 Android Development] cliffgamerz:
can you link me to the specific guide if you dont mind, do i need to backup my current rom or can i flash back the stock rom found online if i need to downgrade in future.
[Nexus 7 Android Development] abhifx:
this thread is not for discussing installation of ROM. google your answer and yes, unlocking bootloader will wipe everything so backup everything. including your apps. also you can flash stock rom whenever you want, the firmware is available with google.
[Nexus 7 Android Development] cliffgamerz:
K thanks for the help. but if i somehow mess up during the update process i will be back.
[Nexus 7 Android Development] AndDiSa:
[MENTION=2002216]jolinnard[/MENTION] thank you for the log, I think I've found the origin of the problem. For me it starts here:

---> CarrierConfigLoader: Failed to get package version for: com.android.carrierconfig

and then the carrier config is not beeing initialized. I've not really an idea why this happens, but probably [MENTION=6754437]millosr[/MENTION] will get it running.

Btw.: SuperSU is not installed correctly on your device, there are some permissions missing ... ;)