yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] dlfuller:
Thanks for the quick responses.

It does not seem that "wait a bit after launching" makes a difference.

I'm attaching log files of two simple cases that repeat consistently.

1. Launching Amazon Underground Store app which stops right a launch: 2017-02-02-16-59.txt (verbose) and 2017-02-02-16-59-errors-only.txt (just the errors).

2. Feedly app which launches but stops at login: 2017-02-02-17-07.txt (verbose) and 2017-02-02-17-07-errors-only.txt (just the errors).

The txt files were created using CatLog. Evaluating their contents is way beyond my ability.
[Nexus 7 Android Development] Vladimir2k9:
This helps me, if I wait some time the app not crashes. Youtube crashes if make some actions after start.
[Nexus 7 Android Development] Dark Obsessions:
when i try to click in sounds in setting it's force close
[Nexus 7 Android Development] azcom:
Same here on latest build (only one I've tried so far). Also I don't seem to be getting sound output through the speakers or headphones when playing video, although if I connect my Bluetooth speaker that seems to work ok. I do get the 'beep' of pressing volume up when already at max volume through the tablet speaker so something's working but even that is buggy & only works if I adjust the volume through the on screen slider first or it doesn't respond to the physical buttons correctly. Something's definitely screwy on the audio side.

Additionally WiFi seems to be a little buggy for me too. If I'm close to my router so signal is as full as can be it seems to be better but anything less than completely full signal, say I walk into the next room the signal drops just a little and I start to get random complete signal dropouts where it suddenly shows no connection until I play around with it. If I turn WiFi off & on again it often pops back to being connected at what shows as a reasonable signal but will soon drop out again. Also sometimes the signal remains visible but it just sits there trying to obtain an IP address. When this happens I can only see my router listed & none of my neighbours get picked up at that time so it's almost like the radio just stops functioning correctly.

Other than these 2 bugs which are pretty much making it unusable right now the ROM seems great! It's way faster than the previous one I was using (PureNexus) that was based on Marshmallow and battery life seems to be about the same as I was used to before (possibly better). If these 2 bugs get ironed out I'll be a very happy bunny!
[Nexus 7 Android Development] Charles IV:
[MENTION=4798269]Dark Obsessions[/MENTION] and [MENTION=569229]azcom[/MENTION], I am building again now, and will see if i have the same issues. I recommend attaching logcats, and people on this forum know how to use those to find the bugs (and i will try to learn!) Did you have the wifi issue on other ROMs, because unless something is found, I would be inclined to point the finger at the wifi aerial, but I'm probably wrong.

I've also noticed that I'm pretty much building weekly!
[Nexus 7 Android Development] Dark Obsessions:
i dont have any problems in wifi or sound , just sound in settings refuse to open and force close every single time i press on it
[Nexus 7 Android Development] Charles IV:
that bit was directed at azcom.
[Nexus 7 Android Development] azcom:
I've moved from the 20170122 build to the build dated 20170129 after wiping dalvik/cache/system & retaining data & internal. The immediate crashing of the sound settings seems to be fixed for me now but I'm still having the other issues with audio playback & WiFi. Since these appear unique to myself I'm going to have a play around with the different builds & see what results I get across them before I waste anyone's time posting any logcats. I'll see what happens if I wipe data too & also with clean vs dirty flashing for upgrading to newer builds to try & rule everything out.

To answer the question no, WiFi has been fine with all other ROMs I've installed as is the audio so I know it's not a physical fault with my Nexus. Hopefully I can figure out whatever the unique conditions are that have manifested these couple of issues for just me & share my results in case anyone else comes across the same thing.
[Nexus 7 Android Development] Dark Obsessions:
would you please share the download link of the latest built 20170129 , i am on 20170122 built and cant find the download link in cthe OP.
[Nexus 7 Android Development] azcom:
If you click on that link then once you're on the android file host site click on aaopt's name near the top left you can find a list of all the different builds that have been uploaded. The download link on here hasn't been updated to that new build but it's there.
[Nexus 7 Android Development] aaopt:
If I am reading correctly, your logcats both show the same thing: a crash related to the webview component used by those apps. The odd thing is that I use Feedly every day -- I would not upload a build on which Feedly crashed for me. Not sure why it is behaving differently for you... maybe because I am already logged in. Edit: tried logout and login with no issues.

There were some WebView related changes recently-- lineageos switched to their own fork of the webview package so they could rebuild it based on a newer Chromium. I'm not sure but I think that version was already included in my 0122 build though. You could try the 0129 build just for fun to see if it helps. One more thing you could try, if you have Chrome installed -- under developer settings you can try the relatively new setting "WebView implementation" which lets you choose to have Chrome take the place of the separate web viewer for apps.
[Nexus 7 Android Development] Dark Obsessions:
the last built solved my problem , thanks a lot .
[Nexus 7 Android Development] dlfuller:
Thanks so much for checking my logcats and your suggestions.

I did try a wipe of the Dalvik/ART Cache partition and install of a fresh copy of Feedly from the Store. Again with the same result. The splash screens you see before a way for existing users to login do differ from an installed and working Feedly logout/login.

Next I downloaded your 0129 build, but didn't install it (yet) to minimize the changes in each step troubleshooting. Then your tip about changing Developer Options>WebView Implementation. Since I did have Chrome installed, I set it to Chrome Stable from AOSP WebView and re-booted.

Bingo! The first four in my list of consistent app stops were gone! The apps all worked as expected.

I will try your 0129 build shortly, but meanwhile am enjoying the new usefulness of the ancient Nexus 7.

BTW, is there any significance in this situation of the next item in Developer Options for running WebView renderers separately?
[Nexus 7 Android Development] movfan:
error settings sound

Hi, today i installed the latest rom from 22-1-17, almost everything works fine except the sound settings .

There i get the error, settings are stopped.

Any ideas? By the way , you doing a great job, many thanks.
[Nexus 7 Android Development] aaopt:
See 116 and 118 above.
[Nexus 7 Android Development] movfan:
The 29-1 build fixed the sound settings, thanks.
[Nexus 7 Android Development] alokjkashyap:
Every thing is fine and working good but apps crashes many times. Almost all apps crashes.
[Nexus 7 Android Development] Dark Obsessions:
i am not facing this problem here
[Nexus 7 Android Development] marty_bebop:
I too have the issue with sound settings - the settings app crashes. I'm downloading 29-1 now and will try it out.

I'm a newbie to much of this - can I restore apps & stuff from backup or do I need to reinstall everything again from fresh?

How do I know if there is an 'official' updated release which will fix this and maybe other gremlins?

Thanks to everyone for their work with all of this.
[Nexus 7 Android Development] aaopt:
Don't wipe data. Apps will be fine. Wipe system and cache, install ROM and Gapps, and reboot.
[Nexus 7 Android Development] marty_bebop:
Wow - that was fast, many thanks, learned a little something there.

I'll report back tomorrow sometime with my findings.

Again, many thanks.

---------- Post added at 01:03 AM ---------- Previous post was at 12:28 AM ----------

Well, with my new knowledge about not wiping data, in spite of it being bed time and I'm weary, I just cracked on and installed the 29-1 rom and gapps (pico).

Everything looks good - sound issue is fixed, which was the only actual gremlin I've come across in the few days I've been doing this.

Cheers, thanks for your help :)

---------- Post added at 01:18 AM ---------- Previous post was at 01:03 AM ----------

As a matter of interest (perhaps) I could control the volume from within an app, say BBC iPlayer Radio, but going to sound in settings triggered the crash. As I said, fixed now.
[Nexus 7 Android Development] latinmaxima:
wrong thread sorry
[Nexus 7 Android Development] Dggrr:
I've been updating builds with repo sync -c, but this doesn't seem to pull in the Android February security patches.

What do I need to do to get these?

Thx
[Nexus 7 Android Development] marty_bebop:
VLC Player Issue & crashes

OK, I've run into one or two issues with the 29-1 build.

I've installed VLC player and was playing some music I'd transferred (Deadmau5 if you must know), went to quit the player but the music just carried on. If I relaunched VLC I could pause the playing music, but could not exit. The only way to exit was in Settings/Apps and force stop. I uninstalled and reinstalled VLC. The issue is persistent for me.

Also, I have seen many random crashes "MTP host has stopped".

As I said earlier, I'm a newbie at this - is it helpful if I report stuff like this? I don't want to waste your time (or mine).

Cheers

Marty
[Nexus 7 Android Development] aaopt:
For now, just wait. It seems there are some conflicts between one of the patches in 7.1.1_r21 and some LineageOS apps which need to be sorted. Watch this space for updates. After that commit gets merged into LineageOS, "repo sync -c" should do the job.

[You could try to take that commit yourself, but then you will have issues as described in the Feb 9 11:31pm comment at that link.]
[Nexus 7 Android Development] Charles IV:
It's highly unlikely there will be an official release. Check the download page. download.lineageos.org if the link doesn't work
[Nexus 7 Android Development] SilentException:
Hi aaopt, thanks for this ROM and letting us have our old Nexus 7 devices alive.

I wanted to add a restricted profile for my kid and think there is a glitch in this process. Aftet switching to a newly created profile, 'Android is starting' message with endless progress bar is displayed constantly. Left it during the night but it never finished.
[Nexus 7 Android Development] Charles IV:
Strange, pastebin a logcat, although i haven't tried it myself, because having multiple user accounts REALLY slows the device down, especially our tablets. Unless you have used it before, restricted profile may not be what you want, as it doesn't allow basic functions, but it does allow things it shouldn't (as my dad found out). I recommend applock, great app, just lock the apps you dont want your child to access, if you want, create another profile (within applock) locking apps between certain times. It also has location lock!

I realise that this, however means that your data is shared, and you may not want this. Does creating a normal account work? If so, use applock on that account.

New problem: I am editing local manifests, to use my fork of the kernel etc., and using branches that i haven't changed. I got a ninja error 1 or something like that (can't remember), so i breakfasted and lunched and made and got the same error, i then only made the kernel ('bootimage' - i think thats the kernel) and got

DTBs not enabled
Kernel Modules not enabled
ninja: build stopped: subcommand failed.
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1

full paste bin for make bootimage and the brunch grouper and lunch, make.

All the code should be the same, and i just made your build successfully, any ideas?
[Nexus 7 Android Development] aaopt:
That's actually why I'm still here -- we have a few of these devices around and replacing all of them with something newer would be pricy. Some of them do use restricted profiles. But actually only one or two of those have moved to this ROM so far.

So I can say that restricted profiles which already existed before moving to Android 7 seem to work better (faster) than they did on Android 6. I haven't tried making a new one yet, but I actually have tentative plans to do that this weekend, after replacing a screen on a tablet from ebay. We'll see how it goes.
[Nexus 7 Android Development] Charles IV:
I'm just trying to create one now (if my tablet ever wakes up), and see if creating either of the accounts work for me

Edit:

Ok, so restricted users don't work, full users do. My next plan of action would be to test if it's a problem with lineage OS. Unfortunately my backup phone running an unofficial cm13 can create new users, but doesn't have an option for restricted users. Can anybody else test this?
[Nexus 7 Android Development] aaopt:
I am getting the same problem, and it seems like it might be related to gapps. Trying a newer opengapps build, but it doesn't seem to be helping.

Another alternative approach to diagnostics, rather than comparing to another device, would be to back up your data, wipe it, and try AndDiSa's AOSP ROM to see whether restricted profiles work there.

In any case, my pre-existing restricted profiles work, so there probably is a workaround of installing a CM13 ROM, creating whatever profiles you want, and then installing this ROM. That workaround won't be suitable if you don't want to wipe data though.

Strange: I created two restricted profiles, one works and the other doesn't. Only difference is which apps are avaiable.

Edit: The profile which worked had permission for Nova Launcher. I added it to the other profile and now that profile works too. Seems the restricted accounts don't have permission for the stock launcher-- and that launcher doesn't appear in the list of app permissions for user accounts-- so they get stuck in limbo waiting for some launcher to magically appear.
[Nexus 7 Android Development] dlfuller:
Simply outstanding! Thank you [MENTION=3729448]aaopt[/MENTION]. I was thinking of needing a new tablet, but now my old Nexus 7 2012 grouper has never run better.

I installed your 0129 build and again selected Chrome Stable in WebView Implementation. Only an occasional stumble happens when starting some apps, but that's usually solved by waiting a few seconds for things to settle down or by relaunching the app. Otherwise it runs great.

That 0129 build still uses Android System WebView (AOSP) #44.0.2403.119 and I experienced the same problems as before (posts #105, #109, #119). Changing to Chrome again solved those.

But to experiment a little further, I installed a newer AOSP #55.0.2883.91 extracted from my Moto G4 (Android 6.0.1). It added an additional WebView Implementation choice of Google WebView in addition to Chrome Stable. Either one works fine. Just not the AOSP WebView.

My Nexus 7 is rooted. I use Greenify to hibernate most apps and with a Hibernate Now widget on my desktop. It is used on occasion after I've been using a wide variety of apps.

Thanks again [MENTION=3729448]aaopt[/MENTION] for your efforts with this ROM.
[Nexus 7 Android Development] Charles IV:
That probable explains it, when i created it, i disallowed all possible apps to try and speed it up, which means it wouldn't have a launcher, I'm just creating another now.

Update: I can't allow the stock launcher, so i allowed nova launcher ... and it brought me to the nova launcher setup screen! I think I'll keep it for now to test the speed, all seems fast so far!

so [MENTION=2994103]SilentException[/MENTION], if you don't already use Nova launcher, I highly recomend you do, for all it's features, but to solve the issue, add a launcher to the allowed apps of the restricted user.
[Nexus 7 Android Development] movfan:
restricted profile

I have seem to managed a restricted profile with the stock launcher and pico gapps.

First you have to setup the screen lock.

A new restricted user has no access whatsoever, so you have to give *HPROF access for the stock launcher to work.

I hope that this brief explanation helps.

Keep up the good work.
[Nexus 7 Android Development] raksan:
Thank you very much [MENTION=3729448]aaopt[/MENTION], I just can't believe my nexus 7 alive again with this ROM. I was using official ROM and it was so slow, can't open facebook. However, this rom is very stable for me and the battery life is good too. I hope it stays like this forever :)
[Nexus 7 Android Development] gagmani:
Thanks [MENTION=3729448]aaopt[/MENTION], I am tryig to build this from source. I get this error:

git clone git@github.com:aperomsik/lineageos_local_manifests.git .repo/local_manifests -b cm-14.1

Cloning into '.repo/local_manifests'...

Warning: Permanently added the RSA host key for IP address '192.30.253.113' to the list of known hosts.

Permission denied (publickey).

fatal: Could not read from remote repository.

Please make sure you have the correct access rights

and the repository exists.
[Nexus 7 Android Development] aaopt:
That can happen if you don't have a github account configured with a public key. However please check #3 again because the instructions were updated a while ago to avoid that issue.
[Nexus 7 Android Development] gagmani:
Thanks [MENTION=3729448]aaopt[/MENTION]. I made a github account and generated ssh keys. I had built lineage os for other devices previously. So had to do a force sync for removing fetch errors. The build has completed without any errors. Thank you for your work.
[Nexus 7 Android Development] sol1dsn4ke:
There is a possibility that the release will become Official?
[Nexus 7 Android Development] aaopt:
Doesn't seem likely.
[Nexus 7 Android Development] Charles IV:
On the topic of being an official device, the Nexus 4 is supported to lineage os 14.1, however (according to gsm arena) it is officially upgradable to android 5.1, the same as the nexus 7. So I don't see lineage os's logic to this. Also i was looking through a few of the github things, and i think one was making an official device, and our device was in there! I'm probably wrong, but it is annoying that the nexus 4 is supported and our tablet isn't
[Nexus 7 Android Development] AndDiSa:
[MENTION=7211583]Charles IV[/MENTION] I suppose they do not have a maintainer for the Nexus 7 and as long as they do not find someone who is willing to act as a maintainer there will be no official builds ... Some time ago at CyanogenMod there was a similar situation with the Samsung Galaxy S2 if I remember well.
[Nexus 7 Android Development] Charles IV:
I was looking through the guides on how to add a device, and I'm getting stuck when trying to install ruby to 'contribute to the wiki'.

Following the guide at http://wiki.lineageos.org/contributing_using_repo.html, I get an error when running

rvm install ruby

.

The output is:

charles@charles-ubuntu:/media/charles/HDD/android/my-lineageos-14.1/lineage_wiki$ rvm install ruby-2.4.0
Searching for binary rubies, this might take some time.
No binary rubies available for: ubuntu/16.10/x86_64/ruby-2.4.0.
Continuing with compilation. Please read 'rvm help mount' to get more information on binary rubies.
Checking requirements for ubuntu.
Installing requirements for ubuntu.
Updating system............
Error running 'requirements_debian_update_system ruby-2.4.0',
showing last 15 lines of /home/charles/.rvm/log/1487180629_ruby-2.4.0/update_system.log
++ case "${TERM:-dumb}" in
++ case "$1" in
++ [[ -t 2 ]]
++ return 1
++ printf %b 'There has been error while updating '\''apt-get'\'', please give it some time and try again later.
404 errors should be fixed for rvm to proceed. Check your sources configured in:
/etc/apt/sources.list
/etc/apt/sources.list.d/*.list
\n'
There has been error while updating 'apt-get', please give it some time and try again later.
404 errors should be fixed for rvm to proceed. Check your sources configured in:
/etc/apt/sources.list
/etc/apt/sources.list.d/*.list

++ return 100
Requirements installation failed with status: 100.

(also, how do i show code in the same line, do i use php or html tags or something to keep the 'rvm install ruby' in the same line)
[Nexus 7 Android Development] sol1dsn4ke:
It is widely used as an OS for our Grouper: https://stats.lineageos.org/model/grouper
[Nexus 7 Android Development] Charles IV:
Irrelevant and incorrect post.

Can't find out how to delete
[Nexus 7 Android Development] reynard80:
Is this test branch available? I would like to use simultaneous OTG and charging very much.

Thanks for the hard work!
[Nexus 7 Android Development] AndDiSa:
[MENTION=3102926]reynard80[/MENTION] it's already integrated into my last build and the sources are on my github repo. But there is a chance that I was missing one commit (including usbhost.o into the kernel). I've build a corrected version and as aaopt is using my kernel, you could also try the kernel I posted in my thread
[Nexus 7 Android Development] reynard80:
Thanks again! I tried the corrected version on this LineageOS ROM as well, as I need some LineageOS functionality. However, this did not werk (keeps showing boot logo).
[Nexus 7 Android Development] marty_bebop:
I had the same experience. Being a noob - I won't go on - how can I get back to the original kernel? A link to a kernel image would be tremendous, I'm fed up with starting over!

Thanks in advance,

Marty
[Nexus 7 Android Development] aaopt:
If by starting over you mean reinstalling apps, don't bother. Wipe system perhaps, but not data, and reinstall the lineageos ROM and gapps. Whatever else you had installed should survive this process just fine. Same can be done for moving from any of my lineageos builds to a newer lineageos build.
[Nexus 7 Android Development] marty_bebop:
Thanks aaopt. I must stop fiddling with my tablet - it's working 95% very well thanks to you and others with an up to date Android OS.
[Nexus 7 Android Development] gagmani:
Thanks [MENTION=2188693]AndDiSa[/MENTION]. It is because of developers like you and Aaopt, it is possible for a beginner like me to build a custom rom for my Nexus 7.
[Nexus 7 Android Development] reynard80:
[MENTION=3729448]aaopt[/MENTION], could you perhaps activate NavBar tuner in this ROM? Thanks!
[Nexus 7 Android Development] Charles IV:
I think you're refering to this, if so, google replaced system ui tuner with alternatives.

Open quick setting, and there is a pen to edit quick settings (you may need to enable it, if so i can't remember how). Also in settings, scroll down to the bottom, and click status bar, some settings in there.

Browse around settings, I've found quite a few settings i wasn't expecting. I think there are also settings in display (e.g. expanded desktop, live display) and buttons (e.g. buttons and layout)

Please correct me if I got it wrong, but google led me to NavBar Tuner, which seems like a replacement to system ui tuner.
[Nexus 7 Android Development] papa-nundo:
This is great! Remember: this tablet is 5 yrs. old and now we have a smooth Android 7.1 .... awesome.
[Nexus 7 Android Development] donjamal:
Hi,

Is it rooted?
[Nexus 7 Android Development] :
Yep,it is!
[Nexus 7 Android Development] reynard80:
[/COLOR]

I see, apparently the 'buttons' function of LineageOS (CM) is (almost) identical to the NavBar tuner. Thanks for looking into it.
[Nexus 7 Android Development] eNVy:
Is there any new builds ?
[Nexus 7 Android Development] Dark Obsessions:
https://www.androidfilehost.com/?fid=529152257862702728

the last one
[Nexus 7 Android Development] rclar:
new builds

I've got a daily build setup and running. I've requested upload access at androidfilehost, and if I get that, I will try to upload the build with some regularity if that would help anyone.
[Nexus 7 Android Development] Charles IV:
Just interested, how did you set it up, because I find myself building weekly, but that was just me doing it in my spare time.