yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] phaleg:
You are right!

I did not, because I did read here that when you update with his build, it wipes /system automatically, that's why you need to flash gapps again also during a dirty flash :)

---------- Post added at 07:23 ---------- Previous post was at 07:20 ----------

yes, they are hosted there, but today website is down

http://builds.unlegacy-android.cf/
[Samsung Galaxy Nexus] miomaguro:
Actually I did the update without any wipe and I didn't get your error, but I was coming from the 26 July 2016 build. I don't know if it means anything.
[Samsung Galaxy Nexus] WoolTomb:
Are these 7.1 builds ziyan's builds??¿

Why aren't uploaded in this thred??¿
[Samsung Galaxy Nexus] phaleg:
They're Ziyan's and his team...

it is common to host them on the thread before they get something more dedicated online

I am using MM build and runs great
[Samsung Galaxy Nexus] Ziyan:
.org instead of .cf :) http://builds.unlegacy-android.org/
[Samsung Galaxy Nexus] musical_chairs:
I would venture the guess that /sysem was mounted when you flashed the first time. When you manually wiped /system, it unmounted it, then the flash succeeded.
[Samsung Galaxy Nexus] Netosan:
Hi, comunity!

I have similar problem but with aosp_7.1_tuna_2016-10-21.zip ..

My fault error says

e: unknown command [log]

e: unknown command [log]

And if I remember correctly error 7 as the photo...

I've installed aosp_mm_tuna_2016-07-25.zip and all very OK.

I performed this procedure:

1.- Install twrp-3.0.2-0-maguro.

2.- lanchon-repit-20170115-system=1G-cache=62M+wipe-data=same-maguro

3.- wipe (maybe not necesary).

4.-

a) With aosp_mm_tuna_2016-07-25.zip ALL OK :highfive: + open_gapps-arm-6.0-nano-20170214 ALL OK :p + wipe + :eek: very long REBOOT ALL OK.

b) With aosp_7.1_tuna_2016-10-21.zip, I could not install :( , the error mentioned above exits.

Any idea or procedure to install 7.1 , 10xs & regards.
[Samsung Galaxy Nexus] _yen_:
This error doesn't affect in any way the flashing procedure, it's only a new command introduced with 7.x and still unsupported in TWRP 3.0.2.

Never mind it... flash should be ok.

bye

yen
[Samsung Galaxy Nexus] WoolTomb:
I want to update to 7.1.1. Are there many bugs in 11.02.2017 build?
[Samsung Galaxy Nexus] phaleg:
AFAIK MM offers the best ratio between stability and being up-to-date...
[Samsung Galaxy Nexus] _yen_:
Yes, it doesn't boot due to SELinux denials, as all other 7.1.1 automated builds from unlegacy site. All these builds needs a permissive kernel to properly boot.

bye

yen
[Samsung Galaxy Nexus] WoolTomb:
Thank you, i hope in a future working Nougat build :(

And a Ziyan's LinageOS build :)
[Samsung Galaxy Nexus] mk070:
Ziyan, could you comment on the question above concerning a 14.1-LineageOS build for maguro? :) Thanks!

Can I be of any help with the SELinux denials? I offer testing.
[Samsung Galaxy Nexus] mlsoftlaberge:
I Hope [MENTION=2633638]Ziyan[/MENTION] will tell us soon what he envision for the future of the maguro.
[Samsung Galaxy Nexus] morrademedo:
Network not available

Dear, I am using AOSP for two weeks. Everything is fine, but sometimes the message "Network not available" apears when I make a call and the 3G doesn't work at all. I can receive every call and Wifi is fine.

Do you have a hint how to turn on the 3G and treat this "Network not available".

But first of all, congratulations, great job.
[Samsung Galaxy Nexus] miomaguro:
Which version do you have installed? I'm with MarshMallow 6.0 and I've never experienced it. It only happened when I had the CM13.
[Samsung Galaxy Nexus] morrademedo:
AOSP 7.1 Nougat (2016-10-21) + Open Gapps Pico + SuperSu

How do you correct this problem?
[Samsung Galaxy Nexus] bamtan2:
There is nothing you can do about 7.1 except wait for a new release and donate to developers :(
[Samsung Galaxy Nexus] morrademedo:
cm12.1

Thanks, I'll wait using CM12.1, that works fine for me...
[Samsung Galaxy Nexus] miomaguro:
You cannot: it is commonly agreed that 7.1 is still buggy and not enough stable for daily use. Sorry.
[Samsung Galaxy Nexus] AgusL:
I have the same network issue, the only fix is to reboot the phone.
[Samsung Galaxy Nexus] yaghmaie.p:
I have same problem. I fix it by turning data off then rebooting the phone and keeping data off until I need it.
[Samsung Galaxy Nexus] gabrielex:
I've just updated today from the 10/21/2016 build to ua_tuna-7.1.1-20170211, hoping it would solve my problems with GPS but I haven't had any luck.

Opening GPS Status app doesn't show any satellite (0/0 satellites), even though it is detected as available sensor, while opening Stellarium freezes the app leaving you no choice but closing it.

Anyone else with the same issues? Google Maps apparently works, but guess it's with mobile and wifi location data.
[Samsung Galaxy Nexus] miomaguro:
Down in the thread there are many posts confirming this issue on the Nougat version, together with several others (like the network unavailable related to the SIM). In you really need it, you should install the latest MarshMallow version 6.0 that has almost no issues.
[Samsung Galaxy Nexus] gabrielex:
I was just hoping it was solved, what I've found in previous threads wasn't so clear. What could be the reason of the GPS not getting any satellite? Probably is just some misconfiguration.

Nobody found out why or has any idea yet?
[Samsung Galaxy Nexus] _yen_:
Sadly it isn't solved...

I have enabled debugging in sirfgps.conf but no way to obtain some logs that can be useful for devs, it simply doesn't work...

bye

yen
[Samsung Galaxy Nexus] Netosan:
Well, no success!

The GApps shows error.

I installed it MM, because my phone heats up in area of camera (maybe defect of factory).

The phone work, only problems with video 60fps.

However it great.
[Samsung Galaxy Nexus] Mimamau:
Well it's open source, dive into the source and correct it yourself...
[Samsung Galaxy Nexus] harry10101010:
Hello,

I tried ua_tuna-6.0.1-20170207.zip on my Galaxy Nexus.

Upon first boot there weren't issues.

Since the second boot, the home button and the recent apps button does not work.

I also can't expand notifications drawer and Settings/Users does not work.

The same problem is described here but with aosp_7.1_tuna_2016-10-21.zip https://xdaforums.com/galaxy-nexus/...sp-project-t3334574/post70126335#post70126335.

I tried

adb shell

settings --user 0 put secure user_setup_complete 1

This brought the home button back to life but the other issues still persist.
[Samsung Galaxy Nexus] miomaguro:
If I were you I would try first a check on the permissions and if I could not solve it a deep re-flash...
[Samsung Galaxy Nexus] lippy lipkowski:
Any chance we might be blessed with a revised release of this anytime soon Ziyan? I am holding out for one before I was going to decide to take the phone back to the Android 6. This one sure is on the cusp of fabulous. IT runs beautiful in all regards that work on it. Thanks.
[Samsung Galaxy Nexus] osm0sis:
*cough*/su/su.d/000tunasefix:

#!/system/bin/sh

supolicy --live \
"allow init block_device lnk_file relabelfrom" \
"allow recovery shell_exec file getattr" \
"allow { audioserver bootanim cameraserver dumpdcc fs_setup mediacodec mediadrmserver pvrsrvinit smc_pa_ctrl } rootfs lnk_file getattr" \
"allow rild system_file file execmod" \
"allow { audioserver bootanim cameraserver dex2oat surfaceflinger zygote } debugfs file { write open }" \
"allow system_server system_file file execmod" \
"allow init logd dir getattr" \
"allow rild toolbox_exec file { getattr execute read open execute_no_trans }" \
"allow vold logd dir { read open getattr }" \
"allow zygote debugfs file getattr" \
"allow bluetooth storage_stub_file dir getattr" \
"allow sysinit rootfs lnk_file getattr" \
"allow netd system_data_file file open" \
"allow shell debugfs file write" \
"allow shell dalvikcache_data_file dir write" \
"allow system_app radio_data_file dir getattr" \
"allow system_app netd_service service_manager find" \
"allow system_server unlabeled file unlink"

Tested on today's (0227) build: http://builds.unlegacy-android.org/aosp-7.1/tuna/ :cowboy:

Flash ROM, reboot recovery, then flash (optionally GApps, and) SuperSU stable, then immediately use my SUmount script zip to mount /su in recovery (ie. don't attempt boot first), and place the above 000tunasefix in /su/su.d with 755 (rwxr-xr-x) permissions.

This'll get it booting completely with no SELinux denials. There may be some features that will trigger more (I haven't found one yet), but at least everyone will have the system to a point that they should be able to fix them on their own with aLogcat and a file explorer app to edit the /su/su.d/000tunasefix script. :cool::good:

Obviously expect some possible ROM bugs, since it's not officially ready for public consumption yet. ;)
[Samsung Galaxy Nexus] bamtan2:
Someone send this gentleman a donation! :cowboy:
[Samsung Galaxy Nexus] harry10101010:
Thanks! It works now.

I did:

Wipe / format everything with twrp 2.8.7.0.

Installed stock images (takju-jwr66y).

Installed twrp 3.0.2.0.

Wipe / format everything with twrp.

Installed ua_tuna-6.0.1-20170207.zip.

Dunno what exactly did the trick.
[Samsung Galaxy Nexus] Teemoo:
md5 of the latest build, https://builds.unlegacy-android.org/aosp-7.1/tuna/ua_tuna-7.1.1-20170227.zip , doesnt match.

I get 361e71f0a89092bfbdcf1f8485817f9c

File says 09fed0dd1e94a2a7a36a7019f8b0e050

Why? which one is the correct one?

0211's md5 do match.
[Samsung Galaxy Nexus] _yen_:
Bad download, download again until your file match md5 published on UA site.

bye

yen
[Samsung Galaxy Nexus] Teemoo:
Have you tried downloading and checking? I've tried with multiple VPNs, multiple times, they always result with 361e71f0a89092bfbdcf1f8485817f9c
[Samsung Galaxy Nexus] _yen_:
Yes, look attached screenshot.

bye

yen
[Samsung Galaxy Nexus] kamwaikin:
Can't watch video and camera connection always fail

My Galaxy Nexus is using unlegacy 6.0.1. I feel satisfied about the performance of this ROM. Credits to the author. :good:

But camera always loss connection. A reboot can fix it and after a few times, it happen again. Also video can't play properly, just black window is shown with sound. Anyone facing the same problems? Thanks.
[Samsung Galaxy Nexus] winlinand:
Awwwwwww, look everybody, our little GNex is all grown up now :'-)
[Samsung Galaxy Nexus] morrademedo:
I'll be happy if I can help. Can you give me the directions to start in this project?

First: I can't find the code I need to compile and generate the ZIP in Source Code: https://github.com/Unlegacy-Android/;

Second: Do you know if there is a virtual machine prepared to compile this code?

Thnx
[Samsung Galaxy Nexus] _yen_:
before you start building rom, try the solution proposed by [MENTION=4544860]osm0sis[/MENTION] here:

https://xdaforums.com/showpost.php?p=71215509&postcount=1326

root with SuperSU and add his 000tunasefix script in /su/su.d/

hope it helps.

bye

yen
[Samsung Galaxy Nexus] vortex-5:
Did project unlegacy lose access to it's domain? Seems like you guy's don't have the build server public for several weeks now.

Nevermind you moved the url to: builds.unlegacy-android.org

So I noticed the main notes don't mention GPS flakeyness can we get some confirmation that the GPS issues are resolved in 7.1.1 now?

Edit: never mind looks like it's still an issue as of 3 pages back.
[Samsung Galaxy Nexus] fadiesis:
Yes, gps issue is still present as well as the one relating to in call volume (you can't adjust voice volume in calls).

bye

Edit FYI in call volume issue has been resolved but not yet implemented

https://xdaforums.com/showpost.php?p=69305058&postcount=860
[Samsung Galaxy Nexus] bitbidu:
I can confirm ua_tuna-6.0.1-20170227.zip is also broken. I get "CRC failed: system.new.dat" - tried downloading several times.

MD5 of the downloaded file is 652635cbc2d5bc786ac1f7dd1e013e3d every time instead of the expected 06b021b9458dfb1e6b2ace29bae59533.
[Samsung Galaxy Nexus] yossSP:
Donwloaded and dirty flashed (over precedent version) with no aparent issues (haven't tested everything ) the new MM 6.01 ua_tuna-6.0.1-20170227 from https://builds.unlegacy-android.org/aosp-6.0/tuna/

mmm, I downloaded two days ago with no issue (checked MD5 also) ... try to download from PC.
[Samsung Galaxy Nexus] miomaguro:
I've tried to download and check: I can confirm the md5 check failure. However, I would definitely say it's a problem of the ua_tuna-6.0.1-20170227.zip.md5sum file that reports the absolute pathname of the file,

06b021b9458dfb1e6b2ace29bae59533 /home/apinela/Android/source/out/target/product/tuna/ua_tuna-6.0.1-20170227.zip

Just my personal idea.
[Samsung Galaxy Nexus] rahimali:
I flashed ua_tuna-4.4.4-20170301.zip today and encountered bootloop after installing xposed so I did a bit of searching and found this fix, following which I created a flashable zip which I'm sharing here.

I've replaced libdvm.so from the ua_tuna-4.4.4-20170301.zip build with one from aosp_kk_tuna_2016-10-12.zip available here

While this works just fine for me, please do make a backup prior to flashing, either a full nandroid or at least a backup of the libdvm.so which will be replaced by this fix
[Samsung Galaxy Nexus] yossSP:
mmmm, checked with WinMD5(http://winmd5.com/) file and md5sum match here.
[Samsung Galaxy Nexus] miomaguro:
I tried with md5sum under linux and none of the md5sum files actually matched with the zipfiles... I've no idea now... More confused than before :confused:
[Samsung Galaxy Nexus] yossSP:
Ok, I found out why it is... you're right, the file is wrong because it contains not only the right MD5 code, but also some more text with a path...

With WinMD5 I have to copy/paste the code inside the file, so I take only the MD5 signature and it match the file :)
[Samsung Galaxy Nexus] miomaguro:
Ok: just to be sure, I did some tests and actually the filename is not affecting the final outcome of the MD5. Only the content of the file is used to evaluate the md5.

~/Downloads$ md5sum SD2.zip
b11507e7f1e86fb81c6de5b2869f6b09 SD2.zip
~/Downloads$ mv SD2.zip SD.zip
~/Downloads$ md5sum SD.zip
b11507e7f1e86fb81c6de5b2869f6b09 SD.zip

Then, there is definitely something wrong there (probably the md5sum is evaluated on a different file than the uploaded one).
[Samsung Galaxy Nexus] osm0sis:
Do in-call volume and GPS work on the latest 7.1.1 with my SELinux workaround?
[Samsung Galaxy Nexus] markitosd:
Is there any way to flash a kernel, or whatever is needed, on top of KitKat based MIUI rom in order to have the CMA?

Thanks
[Samsung Galaxy Nexus] davejimson:
i will install this rom for my galaxy nexus to see :)
[Samsung Galaxy Nexus] davejimson:
Im flashing the rom now. Why its look like stuck in "patching system unconditionally?"
[Samsung Galaxy Nexus] _yen_:
Usually I got this behaviour when I came across a bad download, please check md5 against that published on UA site.

bye

yen
[Samsung Galaxy Nexus] ASHURiCAN:
ua_tuna-7.1.1-20170227.zip is installing and booting fine for me but not 03/03. It blocks at flashing unconditionally...

Envoyé de mon Nexus 5 CAF en utilisant Tapatalk
[Samsung Galaxy Nexus] kerpert:
Hi guys, what's the most stable daily use with GPS working MM ROM ??

Thanks

Same
[Samsung Galaxy Nexus] _yen_:
Confirming some troubles with ROM downloaded from builds.unlegacy-android.org

ua_tuna-7.1.1-20170303.zip downloaded from build bot is OK and flash fine; same rom downloaded from builds server has bad checksum (and doesn't flash).

Please check MD5 each time before trying to flash, for now.

bye

yen
[Samsung Galaxy Nexus] kerpert:
ua_tuna-6.0.1-20170227.zip

give me ERROR: 7

system partition has unexpected contents after OTA update

MD5 of downloaded file is 7c7320e0acd728053413503bfe879a4d

EDIT: I installed another ROM 6.0.1 (not of this thread) and all go fine, let me know if you have idea why I got that error 7.
[Samsung Galaxy Nexus] _yen_:
Sorry for being so late in testing but it has been a busy week...

With your workaround UA 7.1.1 boots fine and radio works, I've just some remaining denials (a sample of which is attached here). volume keys doesn't seems to have any real effect on in-call volume (but i've the same behaviour when using a permissive kernel) and still no signs of life from GPS. No particular denial in log when playing with volume keys during phone call or when trying to use GPS.

Thanks for your work.

yen
[Samsung Galaxy Nexus] osm0sis:
Fairly random..

These should fix them!

allow sysinit rootfs lnk_file getattr
allow netd system_data_file file open
allow shell debugfs file write
allow shell dalvikcache_data_file dir write
allow system_app radio_data_file dir getattr
allow system_app netd_service service_manager find

There might be a few more related that pop up after you add these though, since getattr and open are usually followed by read or write.

The secret to changing the denial into an allow is to just take the last 3 things (before permissive) listed in the denial, in order, chop them down to just the names, then add the bracketed action from earlier in the denial. You can also bracket things that are otherwise exactly the same to allow multiple things in one line. :good:

Let me know what else is needed and I'll add it to the previous post with the full script. :)

As for GPS, it must be a driver issue, not SELinux, and I guess [MENTION=3390093]MWisBest[/MENTION]'s in-call volume commit isn't sufficient?
[Samsung Galaxy Nexus] kerpert:
Why I'm having that error with your rom?

What I'm missing?

Anyone has tried the ua_tuna-6.0.1-20170306.zip?
[Samsung Galaxy Nexus] bitbidu:
There's some problem with downloads from builds.unlegacy-android.org. Verify MD5 hash before flashing.

I downloaded ua_tuna-6.0.1-20170306.zip earlier today and MD5 check was fine.

Haven't yet flashed it though.

UPDATE: Flashed ua_tuna-6.0.1-20170306 over ua_tuna-6.0.1-20170207 without any issues.
[Samsung Galaxy Nexus] fadiesis:
anybody has tried ua_tuna-7.1.1-20170308? I downloaded it and md5 check failed as well as zip check (bad checksum in system.new.dat)
[Samsung Galaxy Nexus] _yen_:
yes, bad MD5 checksum too.

same as 0303 build, zip file is OK on build bot but corrupted on builds server, may be some problem transferring file to builds server (which is now behind a CDN)?

bye

yen
[Samsung Galaxy Nexus] fadiesis:
May be. However the ua_tuna-6.0.1-20170306.zip works (not installed but checked)
[Samsung Galaxy Nexus] ASHURiCAN:
It works for me. Checksum is ok, just try to extract the md5 from the file and test again.
[Samsung Galaxy Nexus] morfances:
Link please.

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Samsung Galaxy Nexus] fadiesis:
I flashed ua_tuna-7.1.1-20170309.zip (no gapps+su) following osmOsis workaround. GPS and in call volume issues still in place
[Samsung Galaxy Nexus] miomaguro:
I think they are talking about the latest tuna release on

https://builds.unlegacy-android.org/aosp-7.1/tuna/
[Samsung Galaxy Nexus] kerpert:
I was able to install the ua_tuna-6.0.1-20170306.zip, MD5 was fine and no errors appeared, I just assured to let mounted the system partition.

I had only to repeat the SuperSU installation after the first boot.

GPS works, photocamera works, 5GHz Wi-Fi works, video are fine even if there are audio rumbles on the first recording while already from the second video onwards the audio is perfect.

The hotspot works only in 2.4GHz (5GHz show a generic "error").

With only nano gapps installed the system is absolutely fast.

While after installed a lot of apps and service [gmail, G maps (cronology on), G photo (autoupload on), G Now (always active and "from all screen" works perfectly), Whatsapp, Telegram, Nova Launcher (N theme), Opera Beta, Chrome, ES File Explorer, StickMount, TB, Spotify, and others] the memory RAM usage increased constantly between 93% and 100%, in few occasion some apps got closed, but the system never had a reboot or crash.

Of course there is an heavy lag during startup of Maps and use of Google Now, and also while take a photo, but system incredibly never crashed.

I'll uninstall the superfluous apps.

The last day with navigator on, the screen become black and not responding for about some seconds, only after pressed more time the power button it reawakened.

If the developers will be find the way to reduce the "main system process" RAM usage this will become an absolutely stable daily use ROM.

Good job! :good:
[Samsung Galaxy Nexus] miomaguro:
IMHO: it IS an absolutely stable daily use ROM... 15 days without any trouble... 361 MB of available memory on average... This is a 6 years old phone, we cannot compare it with newer phone... I simply think this ROM is AMAZING and almost close to a miracle!
[Samsung Galaxy Nexus] tonyrojas2007:
Could someone post their own ua_tuna-6.0.1-20170306.zip for download here? The one on the unlegacy-android.org site keeps mismatching with the md5 and wont install. Much appreciate it.
[Samsung Galaxy Nexus] regnfo:
Nexus

I got same problem... bad zip file, it's broken!
[Samsung Galaxy Nexus] _yen_:
back to the tunasefix things... [MENTION=4544860]osm0sis[/MENTION], I do some test today on 0311 build to remove remaining denials. The attached file has all the supolicy fixes needed by my UA setup.

May be this should be tested also by others to be sure all denials are fixed.

Thanks again.

yen
[Samsung Galaxy Nexus] kerpert:
For who has error, this is the file I downloaded and installed on my Nexus some days ago:

ua_tuna-6.0.1-20170306.zip

MD5

Let me know if you still get the issue, be sure to set system partition as writable and mount it before flashing.

I used actual last version of TWRP downloaded from official site.
[Samsung Galaxy Nexus] Ziyan:
Guys, don't forget that we have a Gerrit when you can submit patches (including SELinux), which I can review and merge ;) https://gerrit.unlegacy-android.org/
[Samsung Galaxy Nexus] PGHammer:
I'll be checking latest build (currently 20170311) later today (Mom is currently using my phone - it used to be HER phone); right now, it has unofficial LineageOS 14.1 (direct equivalent) on it, and I'll be using same GApps and same SuperSU that I did with Lineage. So this will be a straight apples-to-apples comparison.
[Samsung Galaxy Nexus] phaleg:
We are running ua_tuna-6.0.1-20170306 on my wife's Nexus... I had to flash it twice, probabily because of the mount system thing... after that I updated TWRP to 3.1

I can see that latest security patch is Jan 2017, is it correct?
[Samsung Galaxy Nexus] vortex-5:
Yeah I just checked mine ua_tuna-6.0.1-20170313 looks like it still says the security patch is from Jan 2017.
[Samsung Galaxy Nexus] vegancorr:
Thanks, kerpert! This one is good, not corrupted. I've just installed it using the latest TWRP 3.1 after wiping out everything.

It works great and really fast although I have the encryption enabled! I find it amazing. Everything seems to work fine, except for the 5Ghz. I think it worked once, but I lost my patience since I don't care about this band.

I had nightly CM13 before - rebooting, camera issues and **slow**. I miss though some of the CM features, but they are peanuts compared to the performance and stability of this build.

Great job, guys!
[Samsung Galaxy Nexus] werty100:
Just install the rom on my GNEX , TWRP 3.1 flashed before , WIPIE all EXT4 , ROM + GAPPS 7.1 ARM NANO ,

ROM not boting just vibrates like allways but not getting to startup screen... Maguro 16GBs

Try with lastest 6.0.1 and working well
[Samsung Galaxy Nexus] kamwaikin:
Ask for help

No one is faceng the same problem as me? This really disturb me:(:(
[Samsung Galaxy Nexus] kerpert:
Yes 5 Jan

I don't have any camera issue.

I have also 5 GHz perfectly working without disconnection.
[Samsung Galaxy Nexus] entux:
I've tried to install the latest 7.1.1 build on my maguro but got a "No SIM found" error. Couldn't resolve it. 7.1 worked well but I wanted the latest security fixes and stay on 7.1 so i installed the unofficial Lineage 14.1 which so far works without problems. It uses a bit more memory than Unlegacy though.