yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Android Development] scala_:
[MENTION=5061138]androcraze[/MENTION], I flashed the latest version, and it still appears to say February 1, 2017 security patch level in the settings.

Are you sure this is using the latest patch from Google?
[Nexus 5 Android Development] androcraze:
Don't know. All I can say is that it's the latest 6.0.1 release from Google.

Under "Build number" I get MOB31T which corresponds to 6.0.1_r79, released earlier this week for the N6.
[Nexus 5 Android Development] scala_:
Same here. Hmm weird. Does it also say February 1 2017 for you as well? or is it just me? (I dirty flashed)
[Nexus 5 Android Development] androcraze:
Yep. Same date.
[Nexus 5 Android Development] razzor1984:
Hello, how well performs your rom with xposed? Did anybody test it with xprivacy? - Is any google stuff pre build in (apps) - i dont use gaps.

best ragars razzor
[Nexus 5 Android Development] androcraze:
It should work with XPosed; it's a simple AOSP ROM, and users have reported success with XPosed.

No Google GApps are built-in, only those AOSP Apps that are part of the AOSP build. Please note that I've removed some apps that no longer function under Marshmallow.

You can easily remove all of the AOSP Apps with the debloating scripts that I've linked to in post #1.
[Nexus 5 Android Development] scala_:
works great with xposed and supersu here
[Nexus 5 Android Development] androcraze:
Thank you for the feedback, and I'm glad all is working well.
[Nexus 5 Android Development] alessio89g:
I flashed this ROM and I have installed Chronus App, but when I try to add a weather widget, I get a message that says that Location through Network is disabled (I don't know if translation is accurate, my message is in Italian) and directs me to Location Settings, but switching through the three available modes doesn't change anything.

I don't know if can helps, but I noticed that in this Settings page there isn't the three dot menu to enable location through Bluetooth and Wi-Fi even if they are disabled (present in Stock instead).

I have also flashed OpenGApps pico and I have enabled their permissions.
[Nexus 5 Android Development] androcraze:
Thanks for the feedback. If you do a search in this thread for "Google Fit", you'll see a similar issue.

None of the tweaks I've made to this ROM should affect location. I'm suspecting that there's an API change that Google is implementing in their stock ROM that isn't happening on the AOSP side.

Google Maps works fine with Location, as does Forecastie. I'm at a loss as to why some other apps are failing to work.

I'll do some looking using the information you provided.
[Nexus 5 Android Development] androcraze:
I was able to set the location manually with the app, and have the widget displaying the weather correctly.

With Google Maps, the "Use my location" fails the first time, then works fine with subsequent searches. Perhaps Location didn't initiate yet.
[Nexus 5 Android Development] alessio89g:
Yes, this is my current band-aid, but this way if you move, the location would remain the one you have manually set, it doesn't automatically update by the current location.
[Nexus 5 Android Development] androcraze:
As an alternative, Forecastie and Calendar Widget work fine and are open source.

If you see any possible solutions, including code, please let me know. I'd like to fix this. I was hoping it was simply a proprietary library that needed to be added, but it looks like an API issue.
[Nexus 5 Android Development] alessio89g:
Thanks for your support, I hope that sooner or later you find a fix.

I wish could help, but I have no idea what might be the cause, and (unfortunately) I'm not a dev.
[Nexus 5 Android Development] androcraze:
Interesting read:

https://github.com/microg/android_packages_apps_UnifiedNlp/issues/36
[Nexus 5 Android Development] alessio89g:
Reading I've a general idea, and I think to understand that, as you said earlier, it's an APIs problem.

Do you think you can fix the problem?
[Nexus 5 Android Development] androcraze:
The general idea in the response is that:

1. Google changed APIs

2. Recommends that developers not use the older, open one

3. Refuses to include the API in their AOSP

BE AWARE! A number of people reference this old link as a solution:

https://xdaforums.com/google-nexus-5/help/aosp-build-source-network-positioning-t2743517

The above patch may have worked early in the days after Google made the API split, but it certainly doesn't work now. I tried compiling it into VanillaAOSP, and once I installed GApps, my N5 was subject to continual, seconds-apart crashes that wouldn't go away despite setting every GMS and GPS service available. That patch alone will not work. If there's another ROM that has another sucessful implementation, I'm not aware of it.

I can add a patch and fix it if I have the patch. Until that time, I'm guessing that we have three options:

1. Only use apps that support the open location API

2. Ask developers if they're willing to fall-back to the open API if the Google one isn't available

3. Use the Nexus 5 factory ROM from December

I'll keep on the lookout.
[Nexus 5 Android Development] androcraze:
Something for you to play with:

https://github.com/microg/android_packages_apps_UnifiedNlp
[Nexus 5 Android Development] alessio89g:
Okay, now all working properly!

I have installed UnifiedNlp.apk that can be find in this page:

https://github.com/microg/android_packages_apps_UnifiedNlp/releases

Then I've also installed XposedUnifiedNlp (Experimental version), to force Android to use microG (only for Location services) instead Google Play Services:

http://repo.xposed.info/module/de.r3w6.xposedunifiednlp

Tested with Chronus, f.lux and Google Fit.

I don't know if it's possible, but both apps are open source, maybe can help you to patch your ROM.
[Nexus 5 Android Development] androcraze:
Thank you, thank you!

First, can you write-up a detailed setup procedure for what you needed to do? Assume a clean ROM, with no GApps.

I'll see if there's a build patch for this, and perhaps I can include it as well. My only concern is.... if I patch it during the build and a user doesn't want to do this install, is anything else affected?

EDIT: I'm seeing build instructions for AOSP. I'll look at this....
[Nexus 5 Android Development] alessio89g:
I would not know, as I said before, I'm not a dev.

However, the procedure is simply the one that I described in my previous post, it's simply to install the two apps.

The only thing I didn't write (and I couldn't describe in detail, because, after installing the Xposed module, UnifiedNlp is no longer an executable app and is no more visible in AppDrawer, so I can't reproduce it) is that you have to enabled in UnifiedNlp settings Network-based location.

Anyway, I'm glad could help. :)

---------- Post added at 01:51 ---------- Previous post was at 01:46 ----------

Any idea of the cause I get the "Starting Apps" message, every time I boot the device?

I have tried to wipe cache and dalvik with the same result.
[Nexus 5 Android Development] androcraze:
I get the "Starting Apps" when I flash something new, but it's gone on subsequent reboots.
[Nexus 5 Android Development] alessio89g:
The HTML Test returns Chromium WebView 56 as result; is it the AOSP app or the Play Store version app?
[Nexus 5 Android Development] androcraze:
Should be the PlayStore version. At last check it was at v52 for AOSP, but it could be at v54.

v56 is "current"..
[Nexus 5 Android Development] alessio89g:
Can it depends because I used this script in a flashable zip for remove some system apps?

#!/sbin/sh
rm -rf /system/app/DownloadProviderUi
rm -rf /system/app/LatinIME
rm -rf /system/app/Music
rm -rf /system/app/OpenWnn
rm -rf /system/app/PicoTts
rm -rf /system/app/QuickSearchBox
rm -rf /system/priv-app/Launcher3
[Nexus 5 Android Development] androcraze:
Look at my debloating scripts here:

http://xdaforums.com/google-nexus-5/themes-apps/gapps-debloating-scripts-aosp-t3457204

I just build a custom one off these for myself. The removal scripts are in two places:

/system/addon.d/74-br.sh

/META-INF/com/google/android/updater-script
[Nexus 5 Android Development] alessio89g:
I already tried this zip a few time ago, but when I try to flash it, I get an error (error 6, I think) before the process begins.

But could be this the cause of "starting apps" message, at boot?
[Nexus 5 Android Development] androcraze:
I've had no error reports nor experienced error reports with these scripts and this ROM (or any other).

Something is amiss. Removing apps shouldn't be the culprit; only adding them. The "starting apps" message is the system building the Dalvik cache I think; once it does it's magic, you should be good.

Odd.
[Nexus 5 Android Development] androcraze:
Sometimes wiping everything but storage and re-flashing is a more graceful solution; you could spend forever trying to diagnose this.

I'm guessing something got corrupted somewhere.
[Nexus 5 Android Development] alessio89g:
When I have a bit 'of time I will try to edit your script to debloat only apps that I want to remove; maybe first time I made a mistake with editing.

Anyway, I don't think it's a dalvik related, because Android doesn't say "Optimizing apps", but only "Starting apps".

Furthermore, also wiping dalvik, doesn't change anything (after second boot, of course).

So, I will try soon to wipe system, cache, dalvik and re-flash the ROM.

I'll let you know about everything
[Nexus 5 Android Development] BreckZeBoulay:
I had this kind of "issue" with TimeService.apk
[Nexus 5 Android Development] alessio89g:
Do you mean that you solved it after flashing the Time Service fix in OP?
[Nexus 5 Android Development] BreckZeBoulay:
Make a few tests (with or without, try different versions), this apk is a mystery for me...
[Nexus 5 Android Development] alessio89g:
At the moment I running this ROM without the fix, because I thinked I don't need it, since I haven't the time resetting issue; so I can deduce that I can solve flashing the fix. But in OP I see only a version in add-on section.
[Nexus 5 Android Development] androcraze:
That's the one! 6.1.

I also have a link for "Older versions".

The 6.1 version should do the trick; you don't need to "test" earlier versions.

TimeService is a mystery for me as well. All I can say is that when users are having time-related issues between TWRP and the system, this APK seems to fix it. Snake oil? Nah.

It could be an increasingly greater requirement as you delve deeper into the "proprietary" realm. Dunno.
[Nexus 5 Android Development] alessio89g:
But I haven't time-related issues, neither between TWRP and System, because of this I didn't flash it.

But if I can solve my "Starting apps" issue, I can flash it.
[Nexus 5 Android Development] BreckZeBoulay:
Then forget my answer, flashing timeservice is not the solution for your problem.

---------- Post added at 01:36 PM ---------- Previous post was at 01:33 PM ----------

Timeservice is not installed in my rom (AOSP) and I don't have your problem.

So I think flashing Timeservice is not the solution.
[Nexus 5 Android Development] alessio89g:
Okay, I tried to wiping and re-install the ROM with no new result… I always get the damn "Starting apps" message!

One good news, I properly edited your debloter script (following your useful tips) and now it works like a charm!
[Nexus 5 Android Development] androcraze:
Good on the debloating script.

I'm suspecting your install procedure isn't working.

1. Boot to TWRP

2. Reboot to recovery (TWRP) from within TWRP

3. Wipe everything but storage

4. Flash the ROM

5. Flash a bootanimation, TimeService, Green line fix

6. Reboot to System

7. Configure Time, WiFi, APN, Reboot Menu

8. Reboot to TWRP

9. Flash GApps

10. Reboot to System

11. Set permissions for GApps (Contacts, Play Store, Google Play Services)

12. Reboot back to System

13. Setup Google Account

14. Install Play Store Apps

15. Install APKs manually

16. Reboot to TWRP

17. Run debloat script.

18. Reboot to TWRP

19. Install SuperUser (PHH's is fine)

20. Reboot to System.

21. Done

#6 is VERY important.
[Nexus 5 Android Development] alessio89g:
Why I can't flash all ZIPs in a once?

I always follow this procedure with no issues:

- Boot to TWRP

- Wipe cache, Dalvik, system, data

- Clean up sdcard (no-personal directories and files)

- ROM

- Kernel

- SuperSU

- Xposed

- Fixes

- Open GApps Pico

- Debloater

- Boot Animation

- System Sounds Replacement

- Reboot to System
[Nexus 5 Android Development] androcraze:
Based-on my experiences with multiple AOSP ROMs:

1. Reboot to TWRP from within TWRP (unmounts things properly)

2. Boot to ROM, then back to TWRP before flashing GApps (initializes ROM properly)

3. Flashing the ROM, then GApps, and then other flashable apps should mostly be done in different stages and successive reboots.

This is essentially straight AOSP. I have no special patches for installing GApps, nor will I build them into the ROM.

I use the above procedure and it works EVERY TIME with this AlmostAOSP, UntouchedAOSP, RastaPop, etc.; I've developed this sequence over the years using the advice of others and my own personal experiences and experimentation.

All I can recommend is to try this process; if it works for you, then something is not working with your procedure.
[Nexus 5 Android Development] alessio89g:
I'm tired of flashing and re-flashing; for now I give up, but the next time that I flash a ROM I'll try your sequence (I look at AOSP Nougat by Santosh M, but I wait Xposed for N, or EFIDroid for Hammerhead).
[Nexus 5 Android Development] razzor1984:
[MENTION=5061138]androcraze[/MENTION]

It would be nice if you can signe youre build. For example PGP signing or the easy approach - post strong hashes (sha256/512) from the current builds :)

best regards Razzor
[Nexus 5 Android Development] androcraze:
I'll take a look at this. AndroidFileHost already has md5 checksums based-on what I've uploaded; the checksum and the time stamp should work fairly well to mitigate odd things.
[Nexus 5 Android Development] androcraze:
Hopefully there will be another N6 MM update. If there is, you can play then.
[Nexus 5 Android Development] razzor1984:
Md5/sha1 is good to make basic file integrity checks - noting else. To check against tampering with the source file, the best path is sign it with

your private key (PGP). I can then check it out with the signature file and your public key if the file is legit ;) (good or bad signature)

By the way - md5/sha1 is an obsolete hash standard that is broken, its good to detect crc failures (file integrity) but your cant

tell if somebody tampered with the file !

https://shattered.io/

https://www.schneier.com/blog/archives/2005/02/sha1_broken.html

Md5 is brocken since 1996
[Nexus 5 Android Development] androcraze:
AlmostVanillaAOSP [6.0.1_r79-MOB31T] - 20170418

- A new build based-on 6.0.1_r79 (MOB31T).

Changes:

- Built-in support for UnifiedNlp(GAPPS) app; this addition will allow using troublesome apps (Chronus, f.lux, Google Fit, etc.) requiring location. Users no longer have to install Xposed to get this function working.

- Created flashable UnifiedNlp(GAPPS) app zip that installs to /system; this should allow smooth functioning of UnifiedNlp location (see "Add-on Downloads in Post #1).

- Removed AOSP Calendar from the build. It's been broken for a while now, and Etar Calendar (F-Droid | Play Store) is a much more reliable option.

- Added SHA256sum hash for paranoid users.

Users NOT using UnifiedNlp will NOT see a benefit in upgrading from AlmostVanillaAOSP[6.0.1_r79-MOB31T]Hammerhead-20170306.zip. But really, you're itching to try it, aren't ya?!
[Nexus 5 Android Development] dandyzakii:
7.1.2 please?
[Nexus 5 Android Development] androcraze:
The video driver situation for Nougat and the N5 hasn't improved; I was hoping someone would have dropped a miracle.

I'm still watching and waiting-out the Nougat issue(s), but in the meantime, Marshmallow will have to suffice.
[Nexus 5 Android Development] androcraze:
I've created a guide for using UnifiedNlp(noGAPPS) in Post#2 of this thread.

I'd be interested in knowing what backends and configurations other users are implementing.

Thoughts?
[Nexus 5 Android Development] dandyzakii:
where are people?
[Nexus 5 Android Development] androcraze:
I'll need more detail on what you asking for....

If you're meaning, why is the thread quiet, it's always been mostly quiet.

That's good. My threads may be quiet, but I see plenty of downloads. That's better.
[Nexus 5 Android Development] SteveMurphy:
After all this time still enjoy the simplicity of this, and the set of patches you've included. A great base ROM with which to have fun with.
[Nexus 5 Android Development] tom0769:
Yep, that's it.

Just this rom + GravityBox, no need for any other fancy rom.
[Nexus 5 Android Development] androcraze:
Thank you very much.

Simplicity and openness are my targets, and I've fortunately been able hit the mark on each.

I have to give credit where credit is due: the users that test and give feedback to help make this ROM better.

We're part of an awesome community, and I'm grateful that I can give back in some way.

Thanks to all those who embrace open source software and collaboration. You guys rock!
[Nexus 5 Android Development] Piereligio:
Could you please add OMS support? This is the only Marshmallow ROM that is still under development for n5...
[Nexus 5 Android Development] androcraze:
OMS?
[Nexus 5 Android Development] Piereligio:
Substratum. Substratum Lecacy is RRO (the one that your ROM runs since every aosp does), Substratum is OMS, which brings many advantages, which the main is the fact that you can change overlays without rebooting. They recently made many commits (on march the main ones) and from that month to now, there doesn't exist any Marshmallow updated OMS ROM. Latest OMS marshmallow roms are lastly updated on january it seems.
[Nexus 5 Android Development] androcraze:
Substratum. Ugh. I'll have to think about this. So much work to make Android "pretty".

The name "Almost Vanilla" was a bit of humor on my part.... If you do a search for the term, everyone who takes AOSP and mangles it seems to say "I've created this almost vanilla ROM....". And that's the issue.... I've stuck with the concept of "almost vanilla" religiously: remove or repair broken items, enhance security, and enhance in-the-field functionality/utility. Anything else is fluff.

AlmostVanilla will stay as-is; most users of this ROM like it for the fact that it doesn't stray too far from source code. Where the ROM strays, there has to be a valid, sane reason for doing so.

Were I to do something with Substratum, it wouldn't be called Almost Vanilla.

Again, I'll stew this over.
[Nexus 5 Android Development] forb'S:
Made any progress in the question of supporting OMS, mate?

I would like to add a question: Is the project AVAOSP dead when Google drops their support for the N6? Or will you change your concentration? E.g., if it is possible, change the device and port Googles N6P or similar to the N5?
[Nexus 5 Android Development] androcraze:
For the Substratum support, I'm still looking at it. If you look at my patch setup in this thread, I have a particular method for patching so others can view and see what's going on when patching. Implementing Substratum involves modifying MANY files; an initial rough look indicated potentially over a hundred.

I haven't excluded the OMS support, I just need to create the patches to a point where I'm comfortable with them. As I stated in an earlier post, if I add OMS, I'll call it something other than Almost Vanilla, even in this thread.

Is AlmostVanilla dead? No. I'll give two examples where Almost Vanilla will continue:

1. Any update to AOSP Marshmallow code (6.0.1_rXX). Version r79 was originally intended to the N6, and it built fine for the N5. I check weekly to see if there's been an updated AOSP tag. Hasn't happened since March, but it might happen again.

2. A security, bug, or function fix is found or suggested that keeps the original "vanilla" flavor of the ROM. I've already done this with UnifiedNlp: location was broken with newer apps, and a simple fix allowed the addition of an open source alternative to allow these apps to work.

For #2, I'll consider just about anything "sane". OMS is outside #2, and that's why it's something I'll consider doing as a side-project.

For 7.0+, I just don't see it as a viable option on the N5 right now. Video is broken, and unless someone figures-out a reasonable work-around for the Qualcomm drivers, it's probably a losing battle. One user reported success with the Unlegacy ROM; it's supposed to be like this project, but with the newer sources.
[Nexus 5 Android Development] SteveMurphy:
Well, you have a base that supports your decisions, and applauds them. There is no point in updating just for those worthless monthly "security" patches, so I personally appreciate your methods and reasoning.
[Nexus 5 Android Development] androcraze:
Thank you. I'm very happy with AlmostVanilla right now. In battery-saving mode -- with Doze -- the ROM "sips" at the battery; I'm getting incredible standby times. I can enable UnifiedNlp, at will, for accuracy when I want it. KitKat was solid and stable, but this current version of Marshmallow is incredible.

I'm for the security patches, if they can be found. There are some rather nasty things out there.... Another bug like stagefright could cripple Marshmallow.

Google dropped Marshmallow much faster than I though they would. You'd figure that they'd keep a "legacy" branch for vendors. There are many, many Lollipop and Marshmallow phones out there. The decision not to push Qualcomm drivers was regrettable.
[Nexus 5 Android Development] forb'S:
Do not geht me wrong. Both questions were asked because of interesting. And they were asked snaply :) I am happy with this Rom and OMS is a feature wich is nice to have. Not more.
[Nexus 5 Android Development] androcraze:
They're questions I have about the ROM too. My N5 is still running great, but I've been forced into a position where I have few options. I'll ride it out as long as I'm able.
[Nexus 5 Android Development] donz_Simon:
Is this rom continue development?
[Nexus 5 Android Development] androcraze:
It's still under development.

I've taken Marshmallow as far as Google has updated AOSP. If AOSP has further updates, I will update the ROM.

If there's something that's a security bug, functional bug, or broken feature, I'll update the ROM (links to patches would be swell).

What do I need to add? Everything is working as I'd expect it to, in keeping with my guidelines in the OP.
[Nexus 5 Android Development] donz_Simon:
Is this rom fully support OMS?
[Nexus 5 Android Development] androcraze:
No.

If you read through the last couple of posts, we discussed Substratum. I'm considering it, but need a bit of free time.

"Almost Vanilla" means just that; it's a fairly bare-bones AOSP.
[Nexus 5 Android Development] androcraze:
Syncing. I'll build 6.0.1_r80 this evening.

EDIT: Strange.... No platform is listed:

https://source.android.com/source/build-numbers

MOB31Z	android-6.0.1_r80

Perhaps a gift to the community?
[Nexus 5 Android Development] androcraze:
Updated ROM to AlmostVanillaAOSP [6.0.1_r80-MOB31Z] - 20170719

Notes:

- Doze works

- WebView works

- Reboot Menu works

- UnifiedNlp works

Only "issue" is that Candy Crush (from the Play Store) now says it's incompatible with my N5; I was able to manually install the APK fine.

EDIT: Manually installing Candy Crush allows the Play Store to show "compatible" again.

The changelog shows many, many, many security bug fixes and stability fixes.
[Nexus 5 Android Development] CHEFINHO1:
location not working ://
[Nexus 5 Android Development] androcraze:
With what app?

Did you follow the information in post #2?

I've had no issue with Google Maps (without using UnifiedNlp), and had success with UnifiedNlp with an app that works much better with it.

Is Location set to "High Accuracy" or "Battery Saving"?
[Nexus 5 Android Development] Unsteady:
Great to see that someone is still developing for Marshmellow (especially since xposed does not run on Nougat yet). Thank you!

One question, are all the Android Security Updates (the last big one was July 2017) included in the ROM?