yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] donjamal:
yeah, thanks. figured it out. was missing supersu apk :) i mean i could not find it but then i did my read up and figured how to enable root. actually the rom feels quick and all good! thanks for the work!
[Nexus 7 Android Development] camp0s:
Tablet's compass not working right

Regarding this ROM, just flashed and tested the compass.. not working :(

It points the north and it's stuck there, then as soon as I move the tablet it start to move around, sometimes moving too fast around, sometime being "glued" to some angles, how's your compass doing? Google maps' blue triangle too not working too.

(I searched "compass" in this thread but no results came up.. I'm the only one?)
[Nexus 7 Android Development] XDA7:
Why isn't this rom official? Only the Nexus 7 2013 is official. :(
[Nexus 7 Android Development] Buratei:
here are some quick impressions, please pardon my ignorance if some of these were already addressed (couldn't read all 20 pages of stuff :p)

I am using my nexus exclusively in my car, mounted on the dash

+ install went smoothly, no unexpected hiccups

+ root works fine without installing supersu

+ most importantly, OTG+simultaneous charging works well

+ charge rate is pretty decent, on par with other roms (autodroid, timur's, oxydo kernel+mm) even though it doesn't do fast charge

+ definitely snappier than mm

+ works with autosleeper to detect power outage to put tablet to turn the screen off

- occasional app crash messages here and there (mostly system setting components), doesn't hang the OS though

- crackle & pop when using an external USB dac; thankfully doesn't seem to scale with audio volume and mild enough to be ignored (kinda)

- unable to set background image (tried trebuchet, nova lanucher, quickpic, etc), only works when I choose "set as wallpaper AND lockscreen" when I don't even use lockscreens

- doing the above skews wallpaper size and fit (clips on the right side)

- doesn't seem to wake on charge, usb cable needs to be removed and replugged to get audio through DAC (vs through internal speaker)

- audio volume defaults to zero when audio device is changed to USB DAC

- still not as responsive as JB, but most definitely liveable

? yet to test battery drain when put to sleep

? not sure if powereventmanager works on it
[Nexus 7 Android Development] Dggrr:
Rebuilt today and it picked up the February security patches.

Interesting to see how much work is going on behind the scenes in Lineage.
[Nexus 7 Android Development] Charles IV:
There have been many similar posts to this on the thread.

I think we eventually decided it was because lineage didn't have a maintainer.

It's a bit annoying, especially as the Nexus 4 is still supported.
[Nexus 7 Android Development] cpt.macp:
Any good kernel? Tablet lags a lot :(
[Nexus 7 Android Development] aaopt:
Kernel is fine. Have you run Trimmer lately?
[Nexus 7 Android Development] 3dfxvoodoo:
Thanks aaopt, for now the last nightly works fine, no fc. Steel test it
[Nexus 7 Android Development] Dark Obsessions:
would you please tell us how to run Trimmer ? thanks in advance for keeping this tablet alive after all these years [emoji2] [emoji106]
[Nexus 7 Android Development] dark0shark:
See this app: https://play.google.com/store/apps/details?id=com.fifthelement.trimmer
[Nexus 7 Android Development] :
Trimmer (fstrim) app in Google PlayStore

Gesendet von meinem Nexus 10 mit Tapatalk
[Nexus 7 Android Development] Buratei:
looks like not waking up on power turn on is most probably just the (physically) mangled usb port on the tablet, will have to check and see how it fares with an old spare I happened to have. Just got off my lazy ass and installed powereventmanager, let's see if fast charge and/or firm sleep works on this rom. the single biggest problem so far is the audio noise; it is a lot more prevalent and noticeable than I first thought. could be a deal breaker for us carblet folks :(

trimmer works superbly! no more slugishness, at least on par with kit kat as far as I could tell.

For some reason battery stats has "cellular network signal" being on at all times. there are a few wakelocks I probably want to kill, but can't do that without xposed just yeat :(
[Nexus 7 Android Development] Buratei:
reporting back as a follow up:

= crackle & pop reportedly has something to do with audio stream is handled in lollipop and up, or how it differs from earlier versions. Read up on the subject and found out crossfade or EQ might be related to this; surely enough, when I ticked on "use external EQ' and disabled crossfade in gonemad player (my audio playback app of choice), **I think** the annoying noise has all vanished! yeay!!

= wake & external DAC detection on power up event / deep sleep is all fixed now by installing and setting up powereventmanager. PSA for carblet users: auto sleeper is a bit wonky, use powereventmanager for a better effect. Firm sleep option wouldn't stick and disable itself upon leaving the settings page; nevertheless, I lost about 2% of charge over a 23h span with the engine off, so that's pretty good in my book.

the only lingering major issue (if you call it that) is the wallpaper not stretching the the proper size. I still lose about 10-15% on the right hand side of the screen. Pretty sure I chose center fit and it looks good in the preview, only to become the same old chopped off mess when "set as wallpaper" is selected.
[Nexus 7 Android Development] gordp:
Nexus 7 used in car - some Q's

I tried this last summer, and had issues:

I connected power to my Nexus 7 (2012) the the USB connector, turned the screen on, and ran two apps: Waze and Torque. Waze uses GPS, Torque uses Bluetooth. WiFi was also on, as I tethered my Nexus 7 to my cell-phone. So in total, I had:

screen on full-time, quite bright

Constant charging

in the sunshine, on my car's dash

all radios working

I found that my Nexus 7 overheated and would shut itself off :-O :( At the time, I wondered if removing the back would help prevent overheating...

But even before shutting off, it would slowly lose battery - eventually, it would have run out of battery if it hadn't overheated first, despite a high-current charging source. Oh, and when using Waze, the GPS was kinda laggy - about 3 blocks behind my actual position :-O

What do you do, [MENTION=4842109]Buratei[/MENTION], to keep your Nexus 7 from overheating, and keep the power flowing? I appreciate ideas!
[Nexus 7 Android Development] 9Lukas5:
Has anyone here successfully encrypted his/her grouper?

I tried a clean flash, /data and /cache on f2fs. Then all on ext4.

But on both, after bit and initial setup finished at up an Pin Code and started encryption.

But it then stucks forever on the encryption screen, telling me how much time is left. ?

L
[Nexus 7 Android Development] Buratei:
I think the single biggest difference is tinted windows, or how strict they are on regulating it. Around where I live, everyone and everyone's mom has got 50% front / 35% rear and sides, or even 35% front and 15% to 5% sides and rear. To go by the book, the front should be at least 65% transparent, except they would have to prosecute like 99% of the drivers to enforce that, even the cops got their squad cars tinted pretty dark anyway. I am pretty sure this factors into the high traffic accident statistics, but hey what do I know? Sometimes you just go with the crowd I guess... :silly:

Our summers tend to be relatively mild, reaching up to 33-34C ish on the worst days, so the ambient temps aren't too bad either.

Last but not least, I didn't exactly mount it on top of the dash tbh; rather, I mounted in the double DIN slot. The air behind the dash will likely heat up too, though probably not as much as the area directly above the dash with all the radiant heat and all.

At one point I had a 12mm fan blowing on the back cover, then ditched it seeing how it wasn't really necessary.
[Nexus 7 Android Development] gordp:
I keep trying; encryption keeps failing :(

With the most-recent ROM (dated Feb 26, 2017) I not only wiped, but re-formatted each partition - it never seems to make any difference - the encryption starts with a lot of promise, but fails :( My partition-formats are different than yours - mine are F2FS; yours are ext4), but the result is the same. I feel a bit like Charlie Brown, when Lucy pulls the football away :-O

But in all other respects, I'm really liking LineageOS 14.1!!! Thank-you, [MENTION=3729448]aaopt[/MENTION]
[Nexus 7 Android Development] 9Lukas5:
I tried it with both, f2fs first then ext4. Both failed.

Even tried to flash a old cm13 aswell as the AOSP 7.1 with 3.4 kernel.

But with none of those roms I was able to encrypt it ?

L
[Nexus 7 Android Development] arnofor:
Hi,

I have tried many times to convert every partition to f2fs. I only succeed with the data one. Both system and cache stays in ext4 format.

I use TWRP 3.0.2.0...

Any ideas ?

Thanx in advance.
[Nexus 7 Android Development] Tashiv:
"Update Recovery" Developer Option Resulted in Bricking

Hi everyone,

I have been testing out the 20170212 build for about a week now and everything was going perfectly until I selected the "Update Recovery" option in the developer settings. After I restarted, my beautiful nexus got stuck in a boot loop where the Google logo with the unlocked symbol shows followed by a blank screen that alternates the backlight every few seconds.

I have tried getting into the bootloader menu using the power and volume down buttons but it does not come up. As a result I also cannot get into the recovery menu, so there is virtually nothing I can do on the device.

I have also tried using adb and fastboot but with no luck either. In adb, my device shows up with the unauthorised descriptor and because of that I am unable to do any adb commands because I am "unauthorised". In fastboot my device isn't detected and I believe this is because I am not in the bootloader menu.

I feel like the device can still be saved as I can see it in adb, meaning that it is more of a soft-brick. Can anyone help me with this, perhaps help me find a way to get the bootloader to show up, because once we get to that stage, I can use fastboot to make a full recovery. Any help would be greatly appreciated :)
[Nexus 7 Android Development] aaopt:
If adb shows the device, did you try "adb reboot bootloader" ?
[Nexus 7 Android Development] Tashiv:
Hi Aaopt,

All abd commands return the following:

error: device unauthorized.

This adb server's $ADB_VENDOR_KEYS is not set

Try 'adb kill-server' if that seems wrong.

Otherwise check for a confirmation dialog on your device.

Additionally, since I can't boot into the OS or push files to the device, I have no way of authorising the device.

After a lot of research, I believe the only option now is to replace my motherboard. I ended up looking into nvflash, but unfortunately I did not make the blob backups before hand.

I'm probably going to try this ROM again, after I make those very important backups.
[Nexus 7 Android Development] AndDiSa:
[MENTION=8114957]Tashiv[/MENTION] please don't mix up so many different things which are not related to each other. At most boot into bootloader and install a factory image from Google.

Nevertheless even if you cannot boot into the OS for enabling adb it should be sufficent to boot into TWRP / CWM and to acccess with adb to the device. At that moment a dialog should come up to accept the device key.

If you do not have installed TWRP/CWM on your device then probably you should start reading befor flashing custom ROMs.
[Nexus 7 Android Development] Tashiv:
Hi AndDiSa,

As I mentioned in my initial post, the Power + Volume Down key combination do not allow me to access my bootloader menu, hence I cannot access my recovery.

Since I cannot access the bootloader menu, I cannot use fastboot to flash a clean image and because I cannot access my recovery via the bootloader menu I cannot used adb which needs authentication.

As you may know, if those options aren't available then the APX mode and nvflash is the next up for consideration because you can put the N7 into APX mode via the Volume Up + Power key combination. After getting to that stage I found out that nvflash isn't useful if you don't have the flatline backups which is my case. Therefore, the only apparent solution now is to replace the motherboard which will restore the bootloader's functionality, thus allowing be to revive my N7 at the cost of complete data loss.

I am quite familiar with Custom Roms and flashing them, but I have never had the problem of not being able to access my bootloader menu (which is needed to access fastboot and the option to get to the recovery menu). I did have the latest TWRP recovery installed but I cannot access it, so I cannot simply flash a factory image.

I hope things are now more clear and less "mixed up". Also, next time please read a few posts back so you get the full picture...
[Nexus 7 Android Development] 9Lukas5:
I booted a lot into bootloader by monkey grasp lately, and I always used Power + VolUp + VolDown.

Try to hold Power until device reboots (~10sec)

After display got dark IMMEDIATELY release power and press all three buttons.

Hope you can recover from your situation that way.

Alternatively I have a second way:

The back of the N7 2012 is removable. It is hold in place by plastic clips which are fairly Strong. Best place to get in I think is the usb Port. After removing the back, you cab disconnect the battery for a minute, so the device can switch off completely before you try another Bootloader boot.

L
[Nexus 7 Android Development] Tashiv:
Hi 9Lukas5,

Thanks for the advice. I definitely agree that pressing the buttons can be a bit of a finicky process, I'll keep trying different orders and timings of pushing them until the new motherboard arrives.

I did try the battery trick already, but it didn't resolve the issue. All that happened was that after I reconnected it the Google screen popped up again followed by the repetitive screen flashing which continues until I pull the battery or hold the power button which causes a reset.

To anyone reading this, please be very careful with the "Update Recovery" option under the developer options. I believe that was the cause of this bricking.
[Nexus 7 Android Development] eNVy:
I'm just asking, can you include the gello browser in your build.
[Nexus 7 Android Development] abhifx:
you do realize grouper has this mini system partition?
[Nexus 7 Android Development] C--Mon:
I wonder if there is any way to repartition the device? Don't know if it is possible but I remember back to my old Galaxy S2 (i9100) where you can flash something like a .pit file to increase the system Partition. I realy wish that something like this would be possible for our Nexus 7.
[Nexus 7 Android Development] eagle06:
Hi Guys, does this rom use AndDiSa's kernel ? I am asking this because this rom is more upto date than AOSP rom and i want to use lineage os specific features

edit: got the answer in changelog .Thanks!
[Nexus 7 Android Development] Iryon:
Hi and thanks for this Rom, it gave new life to my Nexus 7 2012 16GB grouper. I flashed the 20170122 with gapps mini from Open Gapps but now it's a bit laggy. Which new version can I flash? The 20170129 or the 20170226 (it should be the latest?) from second post?

What can I do with this Rom to get Nexus 7 faster and smoother?

I installed Trimmer and it's less laggy but not so fast expecially in animations (transition of homescreen, drawer etc).
[Nexus 7 Android Development] googleygoggles:
Have you been using this with parrotmod?
[Nexus 7 Android Development] aaopt:
Should not be needed. Just run Trimmer now and then.
[Nexus 7 Android Development] abhifx:
actually no, blame nvidia for that
[Nexus 7 Android Development] AndDiSa:
[MENTION=3692487]abhifx[/MENTION] well, you could do something lilke SuperSU-systemless is doing: create a file on /data and loop-mount that file as an additional partition ... A bit of work to do, but principally doable.
[Nexus 7 Android Development] br3wski3:
File Manager missing in 20170226

I just tried updating/flashing to 20170226 only to find that it seems that the File Manager is not available (I ended up flashing back to 20170212 within which I do indeed have it).

Was this missed in the latest build or am I missing something? :eek:

Thanks!

-br3wski3
[Nexus 7 Android Development] aaopt:
CMFM was removed by the LineageOS team due to incompatibilities with 7.1.1r21 if I understand correctly. Supposed to be replaced by the AOSP file manager, which might appear as Documents or Files. (On my tablet it is showing as Files... but I am running 20170308, which I am not uploading for now because I have the impression that it's kind of crashy.)
[Nexus 7 Android Development] abhifx:
seems plausible, however this is technically not increasing the partition size.

---------- Post added at 11:17 AM ---------- Previous post was at 10:45 AM ----------

as explained by aaopt, file manager has been removed as it was buggy and unmaintained. this will be replaces by AOSP file manager with some additions by LOS team
[Nexus 7 Android Development] Iryon:
No parrotmod :)

Which is the latest stable version of this Rom?
[Nexus 7 Android Development] br3wski3:
abhifx, yes, that insight was in direct reply to my inquiry

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

Thank you aaopt, greatly appreciate the insight and feedback!

-br3wski3
[Nexus 7 Android Development] Sir Charles82:
I have finally changed both N7 2012 to this rom and they were flying again :)

My N7 shows some force closing bay booting, especially cLock is being closed and sometimes Trebuchet. Nevertheless the device keeps working, (also the clock) so this can be only a minor bug.
[Nexus 7 Android Development] cy8aer:
Unfortunately the 20170226 does not work for me with Wifi: When trying to connect to an eap tls network the connection stucks and when I try to connect to an (hidden) WPA2 the device goes into a boot loop. Back to 20170212 and everything works fine again.
[Nexus 7 Android Development] Aquarius_1977:
Thanks for your work. Often there is a spontaneous closing of applications, with what it can be connected.
[Nexus 7 Android Development] aaopt:
What version? What app? Next time it happens please pastebin a logcat.
[Nexus 7 Android Development] EternalSeekerX:
So I'm running 14.1-20161130-UNOFICIAL-grouper with guava 7 api level. Nov 5th security patch with kernal 3.1.10-nougat. Its the nov 30th build on my 2012 nexus. Idk if its just my device but the android screen blanks and goes to the lock screen time to time. I get force closes for nova, MTP, google. And not to mention it crashes running linux either with linux deploy or gnuroot debian (a non root app). Don't know if a re flash with new build will help or if its my device ?
[Nexus 7 Android Development] aaopt:
Definitely worth trying 20170226.
[Nexus 7 Android Development] Vladimir2k9:
I am on 20170226 build. Crashes - youtube, skype, some time desktop (after notifications) but I use Google Strat launcher.

I see you made new build 14.1-20170315-UNOFFICIAL-aaopt-grouper . Whats new? How it works?
[Nexus 7 Android Development] alancai:
not enough ram, dude.
[Nexus 7 Android Development] Aquarius_1977:
Gruper. 20170308. yutube,google press. Where to find logcat?
[Nexus 7 Android Development] aaopt:
0315 is definitely better than 0308 and maybe also better than 0226. It has [MENTION=2188693]AndDiSa[/MENTION]'s latest kernel and most of his device tree updates.

(Trying XDA upload because AndroidFileHost has extensive system maintenance today.)
[Nexus 7 Android Development] EternalSeekerX:
Does the nexus 7 slow down if lots of apps are installed with this rom ? I factory reset to prep for flashing the new image and its been pretty decent, but has some spiked slowdown.
[Nexus 7 Android Development] aaopt:
Doesn't matter what ROM -- if you have no apps installed, there is nothing to slow down the system. But a tablet isn't much fun without apps. I do not recommend factory reset when going from older to newer versions of the same ROM. But if you have apps you don't use, removing those apps can help. Also it has been observed that this tablet does slow down if you don't have much free space. Not sure what the sweet spot is but I usually have 1GB free or more. Beyond that, just be sure to run trimmer regularly... perhaps once a week.
[Nexus 7 Android Development] EternalSeekerX:
Okay I have the 32gb varient and I did have a ton of space left with all the apps (like 12+gb) so probably a trimmer was needed. So you don't recommend me to completly format internal, data and the cache before flashing new version ?
[Nexus 7 Android Development] aaopt:
No, way too much work. ;) I always format cache, dalvik, and system... almost never data or internal.
[Nexus 7 Android Development] EternalSeekerX:
Sweet makes things easier. I wiped most of the residual chroot files and app data anyway so to get rid of any errors with app data. All I need is to copy the rom to internal. I already have pico gapps and the gapp config file in storage ?.

Does the new kernal suffer wifi bug like AnDiSa rom or was that patched ??

Also in your opinion should I flash superSU systemless or use Liniage built in root manager ?

I'll try to flash tonight when I get home ?
[Nexus 7 Android Development] aaopt:
I didn't build until after the wifi issue was fixed in [MENTION=2188693]AndDiSa[/MENTION]'s github kernel source... so the fix is included in my build. (Who says procrastination doesn't pay?)

Personally I use LineageOS' built in root. It's included in my build.
[Nexus 7 Android Development] EternalSeekerX:
Flash was successful!. So far so good. Installing all my apps. Got titanium backup and XDA labs. So far I had one force close regarding MTP and it happened in the default file manager.

What's the most supported app for changing CPU govenor and kernal tweaking right now ? Also what's a good trimmer app?
[Nexus 7 Android Development] akillenb:
DRM issues

There's still an issue with Play Movies - every attempt to play a movie results in an error.

Partial logcat attached.
[Nexus 7 Android Development] cameraddict:
I don't believe that Play Movies are supported on rooted devices.
[Nexus 7 Android Development] akillenb:
Play movies works fine on my Honor 5X, and Moto G xt1045, both running los.
[Nexus 7 Android Development] cameraddict:
I haven't tried your rom yet, I probably will in the coming days.

Between my fiance and I, we have a 16gb and a 32gb device since about 12/12. After KK, I have tried many different Roms looking for a sweet spot in usability. Over the years I have noticed several things:

1) LMK needs very aggresive settings: 60mb, 150mb, 180mb, 210mb, 268mb, 340mb anything less and I always run into low mem issues

2) The BEST governor that I have ever used with these devices was Touchdemand (it needs several tweaks to get the best out of it.). I don't see it in many kernels, however. It made a HUGE difference. As a matter of fact, this is so important, that any other governor makes this device a pain to use, in my experience.

3) BFQ seems to be the best scheduler for the N7 (this also gets better with some tuning.. though I lost my last set of settings...ugh)

4) If you turn off wifi, there is a major lag as the device syncs when you re-enable it. So, battery be damned, I leave it on.

5) I run with Chainfire's Recently App and have it set to force kill anything that hasn't been active in 6 hours and to limit the recents list to 4-6 items.

There are many people that preach that the 2012 N7 is not up to snuff on ram or processor... Even though Android has been optimized for low end devices for 2+ years now. One of the major problems is the quality of the memory. But otherwise, when things are tuned correctly on this ancient beast, it is still a usable device.

I look forward to trying your Rom. I hope that the kernel you use has Touchdemand implemented.

Peace
[Nexus 7 Android Development] Seferi:
Hi mate, just installed your rom . It's charging really slow, other then that everything works great. Thanks for your work. Is there alternative governments for the kernel ? If yes, which app would you recommend to mess with the kernel setups?