yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] fidoedidoe:
Hi [MENTION=2188693]AndDiSa[/MENTION]

I'm sorry to hear about your recent hardware failure and would just like to extend my gratitude for keeping our devices working so well for so long.

If you don't mind (and have time) I've a quick question regarding your github source. I'd like to build from your source, I've built a few roms in the past and still consider myself a noob. Following the readme.md in github 'repo sync' fails due to 404's relating to the 'unlegacy' repo. Below is the output from 'repo sync'

> repo sync
...
remote: Not Found
fatal: repository 'https://github.com/Unlegacy-Android/platform/system/bt/' not found
remote: Not Found
fatal: repository 'https://github.com/Unlegacy-Android/platform/hardware/broadcom/wlan/' not found
error: Cannot fetch platform/hardware/broadcom/wlan from https://github.com/Unlegacy-Android/platform/hardware/broadcom/wlan
error: Cannot fetch platform/system/bt from https://github.com/Unlegacy-Android/platform/system/bt
error: Exited sync due to fetch errors

To my untrained eye, the URL 'repo sync' errors on appear incorrect. For example: https://github.../platform/hardware/broadcom/wlan produces a 404, the correct URL (as far as i can tell), is: https://giyhub.../hardware/broadcom/wlan (note '/platform/' is not present in the working URL)

Am I doing something wrong here (likely) or perhaps I should be modifying default.xml to instruct repo sync to use a different URL to access requisite Unlegacy-Android repo?

Any advice, pointers on how to proceed would be very much appreciated. :)
[Nexus 7 Android Development] AndDiSa:
[MENTION=3865771]fidoedidoe[/MENTION] I've just updated the repo references. Not sure when those urls were changed, but if you re-sync now you should get the correct ones.
[Nexus 7 Android Development] fidoedidoe:
Perfect, I can confirm repo sync is now working as expected. Once again - many thanks! :)
[Nexus 7 Android Development] AndDiSa:
Most likely I'll push my other locally changed repos, too. In that way you don't need not to apply all those different patches from the repo directory. Initially I thought I could prevent to create my own repos for them, but there are now a whole bunch of changes which are easier to deal with in separate repos.
[Nexus 7 Android Development] frankusb:
The USB port is pretty easy to replace and amazon has them cheap. I’ve replaced several.
[Nexus 7 Android Development] AndDiSa:
[MENTION=3771488]frankusb[/MENTION] I had it already replaced two times and checked it with several different ones ... unfortunately it's not the USB port itself. I suppose it's either the cable which is connecting the usb port to the mainboard, or something else. I have the impression, in the beginning it was also temperature related: the longer the device was in use the more likely the connection got lost. Later I had only flickering connections until it never connected again. Even changing cables, usb port, etc. didn't help yet.
[Nexus 7 Android Development] TNSMANI:
[MENTION=2188693]AndDiSa[/MENTION]

Thank you for keeping my (and others') Grouper running smoothly this long. Hope that you or someone else finds a way to maintain this ROM till our Groupers die, though this may sound selfish.

Once again thanks for your time and effort.
[Nexus 7 Android Development] GStar01:
Thanks for the rom, is there a way to deactiavte the automatic display on by motion?
[Nexus 7 Android Development] fidoedidoe:
I noticed a similar issue with my Tilapia (build 20181016) late last night, I'll admit I've not used much for a number of months. Annoyingly when I connected the tilapia to my laptop to see what logcat revealed it connected to my wifi network and stayed connected. I'll keep an eye on things to see if the issue manifests again and if so whether there's anything obvious reported via logcat output. In the interim I'll update to latest stable version of the rom as this may be producing false negatives.
[Nexus 7 Android Development] fidoedidoe:
I've installed latest stable on my Tilapia and can connect and maintain a connection to my WiFI network. On the device I keep wifi on even when sleeping (so it never disconnects) and I don't have a Sim card so mobile data is turned off (not sure if this makes any difference). I did see one time that my wifi status was "disabled", but clicking the connection and selecting "connect" corrected this (my understanding of this state is when multiple attempts to connect fail). I can't recall whether keep wifi on was enabled at that time, but I've not seen that state since. - ben running smoothly for more than 24 hours now.
[Nexus 7 Android Development] terranaut:
if there is some fundraiser started to get replacement parts needed let me/us know.

also, if this is the end of the nexus 7, though i have been tracking android tablets (or relative lack thereof) on the market, what would be the best tablet for the buck in later 2019 that will be as flexible as the n7 has been?
[Nexus 7 Android Development] Sam Nakamura:
It would be advisable if AndDiSa didn't start to do it himself but rather a willing member/friend (like gofundme, etc.) otherwise it might conflict with XDA rules from what I know, collecting donations must not be tied to the future of a project or to the release of the next update, which is to protect members from ruthless developers that are trying to milk the cash cow, sure this is not the case here at all but still it's a rule and generally reasonable!

But yeah I planned donating anyway, regardless of the future of this device, however I was unable to see a donation link yet, at least from within the app, not sure if checking on a browser may show different results...

Maybe AndDiSa is willing to point out his PayPal again, shouldn't take too long to get around 30 to 50 bucks and there are probably some more member who wanted to donate anyway and have now found a good motivation to actually do it!
[Nexus 7 Android Development] js-xda:
I got the feeling that many users would be happy to donate a few bucks (as it might require as little as 30 EUR with a bit of luck - see link in below quote) ...

... but, for now, it is for [MENTION=2188693]AndDiSa[/MENTION] to decide whether he wants to go for it (see below) and I haven't heard from him on this matter.
[Nexus 7 Android Development] AndDiSa:
Hi guys,

first of all I would like to thank all of you for your support you offered to me in the last days and I really feel honoured that so many of your would like to support / help me so that I am able to continue the development for the Nexus 7.

I've got many offers for a "new" Nexus device from all over the world which I really didn't expect. I was really torn between continuing and stepping out. I've thought very much about pros and cons and it wasn't an easy decision especially if you get so much positive feedback. Thank you again!

Finally I've decided to stop development for the Nexus 7 (at least for the moment). There are several other projects (not all of them related to Android) I've in mind and probably this now was a broad hint to start with something different. I've uploaded the sources of the ROMs latest version (inc. security patches for June 2019) to Github and tested together with [MENTION=3865771]fidoedidoe[/MENTION] whether all needed repos and changes are consistent and that one can build the ROM from those repos without the need of doing additional modifications or patches. The build should run smoothly after synchronizing everything. I will also support and help everybody who would like to step in and continue the builds.

I know there are several people interested in building the ROM from sources. Probably there is someone (or probably even a group) who would like to continue ...

Cheers,

AndDiSa
[Nexus 7 Android Development] JimXRS:
Thanks for everything!!!
[Nexus 7 Android Development] goran_s:
Thank You for all Your efforts. I wish You the best in Your future endeavors.
[Nexus 7 Android Development] Kctucka:
I just switched out the charging point to get one of these to work for the first time in many years. So I came to XDA to see what old development existed.

I was shocked to see there was still development for this device (it receives more frequent security updates than my current phone!!)

Anyways, I wasn't around for the whole ride, but I'm impressed with how well you've kept this device alive. I'm sure you'll succeed at your future projects. Thanks and good luck!
[Nexus 7 Android Development] Drumack:
Thank you!
[Nexus 7 Android Development] fidoedidoe:
Thanks for all your help [MENTION=2188693]AndDiSa[/MENTION], very much appreciated!!

Just testing the water .... Is there anyone else here that is interested in building from and contributing to the source? I can build from source and I'm hoping* I can security patch on a monthly basis (perhaps with assistance initially where needed or where questions/queries arise). What I'm not* is an android developer so for troubleshooting / fixes / improvements I'll not be much help (perhaps this is where others can step in?). I have tilapia (although don't use SIM card, just WiFi), so will be in the dark with regards to Grouper.
[Nexus 7 Android Development] AndDiSa:
Even better that you have a Tilapia device as ROMs build for Grouper will run on Tilapia, too, but not vice versa ... ;)
[Nexus 7 Android Development] :
Thank you so much [MENTION=2188693]AndDiSa[/MENTION] You have been an absolute star and a hero. I wish you well with your new projects.
[Nexus 7 Android Development] Nexus7_tilapia:
:crying:
[Nexus 7 Android Development] kozmo2k4:
Just want to join the group in saying THANK YOU, [MENTION=2188693]AndDiSa[/MENTION], for all your time and efforts, to keep this dinosaur of a tablet alive for this long.

Well done, mate. Godspeed.
[Nexus 7 Android Development] fidoedidoe:
[MENTION=5576914]MacLeod100[/MENTION] I've have just experienced a wifi connection issue on my tilapia that seems to mirror your experience. as described above. I'm no expert, but looking at the logcat output I could see the following repeating sporadically:

SupplicantWifiScannerImpl: Failed to start scan, freqs=null

Some searching around suggested that this may* be related to incorrect WiFi region being selected. The kicker being I cannot see anywhere to set the WiFi region within the Tilapia settings, so changing the region doesn't seem to be an option for now. In my use case I have a number of WiFi access points in my house each broadcasting the same WiFi SSID each on a different channel, giving me full coverage throughout the house. I did notice that during the connectivity issue my Tilapia was attempting to connect to WiFi Channel 13 (2467 Mhz) which isn't a WiFi channel available in all regions (such as North America). For now I've changed my WiFi access point that was on channel 13 to channel 12 and for now i have* WiFi connectivity. This could be a false positive (time will tell), but it would be interesting to see whether changing the channel your WiFi access point broadcasts on alters your experience with connectivity
[Nexus 7 Android Development] AndDiSa:
[MENTION=3865771]fidoedidoe[/MENTION] might be the reason as the ROM has channel 12 and 13 allowed so people living in Europe are able to use those channels on their WiFi routers.
[Nexus 7 Android Development] AndDiSa:
That's really a pity and I am very sorry about this :(
[Nexus 7 Android Development] fidoedidoe:
thanks, I should find something on ebay :confused:, hopefully be up an running by the weekend
[Nexus 7 Android Development] DragonTome:
I have been able to use [MENTION=2188693]AndDiSa[/MENTION] 's repo to build the ROM. I had a slight issue with main.mk not liking that I have OpenJDK not Sun Java. I edited the file and set requires_openjdk to true. Once I did that the build (though lengthy) was successful. I do not know much about the AOSP process but it was pretty straightforward. I do no know how to apply the security patches, however. Any guidance would be appreciated.

*edit*: I forgot that I also ended up needing and environment variable LC_ALL=C.
[Nexus 7 Android Development] AndDiSa:
I can post some scripts easing the builds as you need also to adjust e.g. the max. memory settings for jack
[Nexus 7 Android Development] fidoedidoe:
This is great news. I'm also building from source, maybe we can collaborate going forward as AndDiSa suggested? I have the scripts that AndDiSa mentioned earlier, so from next month will be the acid test for pulling in the monthly security updates with a view to publishing the builds for the community (I have setup an account on android file host). FYI You can significantly increase subsequent compile time using compiler cache (ccache). I'll post the necessary environment variables / config to set this up when I'm next on my laptop. I also have a script on GitHub that fully automates the repo sync (on my laptop) and build, take a look if you're interested.

BTW,What device do you have (I have tilapia)?

EDIT

* Links to my build script(s) can be found here: https://github.com/fidoedidoe/build_scripts. The build script for Nexus 7 (grouper/tilapia) is named: build_aosp_7-1-0_nexus7.sh

* A generic overview detailing how to use the script(s), including setting up ccache / jacks server env vars can also be found in build_scripts repo

* My builds for the nexus 7 can be found here: https://www.androidfilehost.com/?w=files&flid=295925
[Nexus 7 Android Development] DragonTome:
I have a grouper. I am not advanced by any means, in the Android world, but I do download and build various other types of projects from the net so I am not exactly a novice. I gave your script a look. Mostly an expansion on AndDaSi's instructions? I am not sure I understand the option to apply patches though. Are they not already applied and committed in the repos? It's a nice wrapper for consolidating and directing the 'user' through the flow.
[Nexus 7 Android Development] AndDiSa:
since a few days all of them are now reflected in the repos so there is no need to apply the patches on to, before I didn't want to clone so many repos for relatively minor changes.
[Nexus 7 Android Development] fidoedidoe:
Yes my script is just a protracted version of AndDiSa's. The subtle difference is that for building it ensures the repo's a refreshed from source on each build (overwrites local changes). The patch implementation within the script is conditional based on an environment variable APPLY_PATCHES and if the 'repo init' selected is AndDiSa's or a fork form that then they are not needed (i kept in in situ, just in case the script every pointed back to android source respo's). If nothing else, the script/overview could help someone new to the building process (even if the script isn't' used directly).

---------- Post added at 10:31 AM ---------- Previous post was at 09:37 AM ----------

Hi [MENTION=5576914]MacLeod100[/MENTION], I've uploaded a test build for the Tilapia (June patches), based on [MENTION=2188693]AndDiSa[/MENTION]'s repo's that I hope addresses the Tilapia WiFi disconnect issue (manifests only under certain conditions / not all routers). The build is exactly the same as AndDiSa's latest June Patch build with a small change to wpa_suplicant.conf (changing pmf=1, to pmf=0). Can you dirty flash and give feedback (wipe art/cache/system and flash rom along with gapps and optionally magisk). I would test but I broken my Tilapia after dropping my laptop on it :(. The download can be found on AndroidFileHost, named: aosp_tilapia-7.1.2-ota-eng-20190625-TEST-WIFI-CONNECTION-ISSUE-FIX.fidoe.zip

Alternatively if you have root permissions you can edit the file directly and reboot and test (perhaps easier for you?)
[Nexus 7 Android Development] ayunatsume:
Would just like to give my observations on the WiFi issue. I always use my phone's hotspot for WiFi except when I'm in the office. One time, I connected my grouper to our office WiFi and notticed none of the 3 APs work (ch1, 6, 11). I connect, I see connected, then it disconnects. Thinking it might be hardware, I bent the pins inside to make better connection to the WiFi antenna. Still no dice. Then I found out my router was giving my nexus 7 a gateway that had no Internet connection at the time (I configure our network to give gateways to specific Mac addresses). So I tried giving my n7 a static IP and my WiFi finally worked. Then I switched back to dynamic and changed my router to give a tested and functional gateway and... It worked!

Tldr Android might be detecting no Internet thru WiFi and disconnecting it because it thinks its useless. Try with static IP/gateway that you know works to verify. I think its a battery saving feature trying to save battery by disconnecting unusable WiFi.

If it really is checking for an Internet connection, it might be a DHCP issue as I've read its picky with some routers. In my experience, some routers are pretty slow at issuing DHCP addresses or responding to DHCP requests, sonetimes even timing out requiring a reconnect or at least issuing a command to request for a new IP. Maybe our builds have a too-short timeout when it comes to waiting for DHCP responses or is sending a somewhat non-standard DHCP request causing some routers to not respond properly.
[Nexus 7 Android Development] fidoedidoe:
This is interesting...quick question: Would you (or anyone else with WiFi Issues?) be open to testing my Grouper/Tilapia builds and give feedback? For you you'd have to temporarily revert your static IP change (is that much effort?). The test Grouper/Tilapia builds with the proposed change (/system/etc/wifi/wpa_supplicant.conf, changing pmf=1, to pmf=0) applied is identical to [MENTION=2188693]AndDiSa[/MENTION]'s, June '19 security patched version (except for this change). If successful, I'll propose a pull request for AndDiSa to review. The builds can be found here: https://androidfilehost.com/?w=files&flid=295925, each file is device specific and has the file name suffix: 'TEST-WIFI-CONNECTION-ISSUE-FIX'

FYI: Interestingly today I found this xda article which suggests the same change to wpa_supplicant.conf as I'm proposing.
[Nexus 7 Android Development] :
I've just looked on my device and pmf is set to 0 already...

grouper:/system/etc/wifi $ cat wpa_supplicant.conf
update_config=1
eapol_version=1
ap_scan=1
fast_reauth=1
pmf=0

I'm running the May 2019 patch level ROM. I don't have connections issues as such (aside what I'll call WiFi hunting). Sometimes it doesn't connect first time and has to be forced but as a rule it's fine. I use a static IP address and my own DNS server, both assigned through the Nexus' WiFi config options.
[Nexus 7 Android Development] fidoedidoe:
Interesting. When I build for grouper/tilapia this setting is pmf=1. I'll try to understand this further (why yours is already set to zero), but if you aren't' having connection issue then perhaps with pmf set to zero this is a benign point. I think going forward it will be safer to say: "if anyone is having connection issues (connect attempt / fail, cycling until connection is disabled after ~5 attempts) for either grouper / tilapia then perhaps the first thing to check is what value they have set for "pmf" in the file: /system/etc/wifi/wpa_supplicant.conf". Once a few people have replied maybe we can move the issue forward.

FYI In my home i have a number of different makes of wifi access point - my connection issue *only* manifested against one make of access point, all others there were no connection issues at all. My pmf value (tilapia) was set to 1 (but i broke it before i could test the resolve).
[Nexus 7 Android Development] OlliWi:
Same here.
[Nexus 7 Android Development] AndDiSa:
If I remember correctly there is an overlay on the WiFi settings stored in /data/... somewhere, i.e. the values in system/etc/ are used as a default only if no other values are set.
[Nexus 7 Android Development] OlliWi:
The path is /data/misc/wifi/wpa_supplicant.conf
[Nexus 7 Android Development] MacLeod100:
Sorry for my late replay i was working alot and sailing around Sweden

I just download it and i will give it a try to see how it behave

I will be back in a few days whit a small update on hov rom is behaving

Hard days at work whit delays becouse of the windy wehater :(
[Nexus 7 Android Development] fidoedidoe:
Thanks, that's good to know. Am i correct in assuming: The above file can't be changed by flashing a new rom build once it already exists? If so, then to test whether this is / isn't the cause of wifi connect/disconnect until disabled issue would be to *manually* edit it (using root file manager / root terminal / or similar) and change pmf=0 (if it's set to pmf=1)?
[Nexus 7 Android Development] AndDiSa:
Repositories updated to reflect 2019-07-05 patch level

I would like to inform those of you who are doing a build by their own that I've just updated the repositories to include the security patches for level 2019-07-05 ... :)
[Nexus 7 Android Development] Sam Nakamura:
As I just had a look at your Github repos and I wanted to say thank you for getting your documentation updated, build-ready and very well structured, this basically looks like a copy & paste job through the efforts you just have put in and especially for those readmes you made! At this point it looks just great, hopefully someone is able to maintain those repos on this standard!

I'll try to make Grouper soon, my laptop is however only meeting the minimum requirements therfore not sure if I really get through with it - I happily share it if I ever get a OTA package to finish successfully, but don't get up your hopes to much everyone, if even it's going to be a one hit wonder, I guess!

-----

Edit: I found a new OEM screen for just 10 bucks on eBay (including shipping) and now my N7 is alive and well again, I accidentally smashed it the day after you reported about your's failing

Edit2: unfortunately my dedicated GNU/Linux drive has just to little space left to even finish repo sync, stopped near the end, means I have to re-partition my home & root partition with gparted to create more space but even then building for Grouper would probably eat all storage, so bye bye steam, downloads, music, etc. - therfore it's only feasible to build for grouper after buying a bigger SSD than the 120GB I have at the moment, these issues not even include my limited 8gigs of 1333Mhz ddr3 RAM or the i7 2630QM Sandy-Bridge mobile CPU... lol

Dang, I'm motivated nonetheless and may find solutions eventually but hey, I'm sure there are users in here willing to build form Andi's sources!

In any case a willing tester to provide feedback and logs if needed, just like almost anybody else here :angel:
[Nexus 7 Android Development] OlliWi:
That´s right. Flashing a new ROM never changes the /data partition.

Just give it a try.
[Nexus 7 Android Development] :
Howdy folks. Is anyone having a go at recompiling a new build?

I'd have a go myself (as I'm a bit techie) but lack the disk space.
[Nexus 7 Android Development] MacLeod100:
Hi the build works fine No more wifi problems and is a little more faster then previous one

Thank you guys for all your work and help ! ❤️❤️❤️
[Nexus 7 Android Development] fidoedidoe:
you may already know this, but you can significantly reduce the size of the repo download by requesting a "shallow clone" using the [depth] directive, ie:

repo init --depth=1 --no-clone-bundle -u https://github.com/AndDiSa/platform_manifest-Grouper-AOSP.git -b ads-7.1.0