[ROM][6.0.1_r79] nAOSProm for Google Nexus 7 (2012)

[millosr]

+1 nosound
With clean flash in multi ROM as secondary

my all nexus

What is your primary ROM? What is the kernel of your primary ROM?

Have you tried other AOSP - 6.0 based roms?

 

[PinoDG]

My primary rom 1) in tilapia: vanir 5.1.1 111715 with DCkernel+ SElinux permissive + supersú 2.65 systemmode, no parrotmod and other...
2) in grouper: BSZAospLP 1.98 full + SElinux permissive + supersú 2.65 systemmode, no other
always openGapps nano use on all.
Other aosp rom M6.0.1 (DU,omnirom) working ok
tonight I try other solutions Naosp b04

 

[millosr]

My primary rom 1) in tilapia: vanir 5.1.1 111715 with DCkernel+ SElinux permissive + supersú 2.65 systemmode, no parrotmod and other...
2) in grouper: BSZAospLP 1.98 full + SElinux permissive + supersú 2.65 systemmode, no other
always openGapps nano use on all.
Other aosp rom M6.0.1 (DU,omnirom) working ok
tonight I try other solutions Naosp b04

Can you send me logcat output?

 

[PinoDG]

Can you send me logcat output?

What do you need exactly the logcat? I tried to do a full backup with syslog ... you need this complete?
I tried all possible variants ... but after installing all fine and sound ok, the first restart of the sound system disappears (even leaving everything default)

my all nexus

 

[millosr]

What do you need exactly the logcat? I tried to do a full backup with syslog ... you need this complete?
I tried all possible variants ... but after installing all fine and sound ok, the first restart of the sound system disappears (even leaving everything default)

my all nexus

I want to see if something went wrong during android startup.
When you boot the nAOSP and sound is not working connect tablet to the pc, do the
adb logcat -d > logcat.out
from the pc and send me the output file.
You can also do the
su
logcat -d > /sdcard/logcat.out
from the terminal emulator on the tablet.

 

[PinoDG]

I want to see if something went wrong during android startup.
When you boot the nAOSP and sound is not working connect tablet to the pc, do the
adb logcat -d > logcat.out
from the pc and send me the output file.
You can also do the
su
logcat -d > /sdcard/logcat.out
from the terminal emulator on the tablet.

I extracted this, after the first restart. if it helps, I also made the logcat of the first installation http://cloud.tapatalk.com/s/577146441fcec/logcat2.out.zip
http://cloud.tapatalk.com/s/5771465937988/1logcat.out.zip


my all nexus

 

[noleng]

Great ROM - My only problem is that my device is not showing any sort of location info. Regardless of the setting I select within the location/settings page. Before switching to this ROM my device allowed GPS and wifi for locations.. I have fully made certain that my permissions, as well as all Goggle tracking is enabled for this function to work.. None of my apps that attempt to use location such as WAZE, UBER, Google MAPS, give no response/feedback for location.

Anyone else have any sort of issues like this. I am using a Wifi only model.

 

[millosr]

Great ROM - My only problem is that my device is not showing any sort of location info. Regardless of the setting I select within the location/settings page. Before switching to this ROM my device allowed GPS and wifi for locations.. I have fully made certain that my permissions, as well as all Goggle tracking is enabled for this function to work.. None of my apps that attempt to use location such as WAZE, UBER, Google MAPS, give no response/feedback for location.

Anyone else have any sort of issues like this. I am using a Wifi only model.

I'm having 3G version - tilapia, and never had issues with gps. Both model have the same gps receiver and use the same broadcom proprietary library for it, so there should be no difference.

You can test GPS satelite visibility with GPS Test application.

You can send me logcat log if you want.

 

[noleng]

I'm having 3G version - tilapia, and never had issues with gps. Both model have the same gps receiver and use the same broadcom proprietary library for it, so there should be no difference.

You can test GPS satelite visibility with GPS Test application.

You can send me logcat log if you want.

Thanks for the response. I actually did the GPS Test with that app and a couple other apps. My GPS does work.

With any other device including this one, I always noticed that while I am inside, or in an area where the GPS doesnt work due to being inside, usually apps like Google Maps, Uber, Waze, etc would fallback on getting an approximate location via the wifi. This function usually includes a setting/option within the Location settings or within the wifi settings. It would give me the option to allow google to use wifi to determine location, even if I am not connected to a wifi.

It seems that not only is this option nowhere to be found in this rom settings, but even with the Location settings with the selection that includes wifi, well, it doesnt seem to work. I did notice better app functionality after the initial GPS location was found. So the apps now use the last GPS point, but i dont think my device is giving out any location info from wifi networks.

Edited: just found a screenshot of the network location services setting I am speaking of (This rom does not seem to have this setting I am speaking of. Here is an image that may help bout what I am speaking of. Anyway.. Maybe we do not need the option to be shown, as I assume it should be enabled by default, but could this maybe be an option that could be added or is it old function that isnt used anymore by android. This I do not know.

 

[millosr]

Thanks for the response. I actually did the GPS Test with that app and a couple other apps. My GPS does work.

With any other device including this one, I always noticed that while I am inside, or in an area where the GPS doesnt work due to being inside, usually apps like Google Maps, Uber, Waze, etc would fallback on getting an approximate location via the wifi. This function usually includes a setting/option within the Location settings or within the wifi settings. It would give me the option to allow google to use wifi to determine location, even if I am not connected to a wifi.

It seems that not only is this option nowhere to be found in this rom settings, but even with the Location settings with the selection that includes wifi, well, it doesnt seem to work. I did notice better app functionality after the initial GPS location was found. So the apps now use the last GPS point, but i dont think my device is giving out any location info from wifi networks.

Edited: just found a screenshot of the network location services setting I am speaking of (This rom does not seem to have this setting I am speaking of. Here is an image that may help bout what I am speaking of. Anyway.. Maybe we do not need the option to be shown, as I assume it should be enabled by default, but could this maybe be an option that could be added or is it old function that isnt used anymore by android. This I do not know.

I think that is option from Android 5.1. It is removed in 6.0.
Settings > Location > Mode - High accuracy or Battery saving should use wifi networks to determine location.

 

[millosr]

nAOSProm b06 released

New build has been released.

Changes:

• AOSP android-6.0.1_r52 - July security patch
• Themes: Full support of Layers 4.0
• SystemUI: Added battery percentage text to status bar
  You can configure it from Settings/nAOSProm/More.../Battery Percentage

Download:

• Nexus 7 (2012) WIFI: nAOSProm-6.0-grouper-b06.zip
  md5: bf182340b01989238b999260a24ef91d
  sha1: f6f8b226670e8f009a7f2183a5243de21897a8db
• Nexus 7 (2012) WIFI+3G: nAOSProm-6.0-tilapia-b06.zip
  md5: 26633a10d68bc6a8bf5f638675a9a1f6
  sha1: f7d5df2305596eabcb50f4e2553cc65155b9b5f3

Since Open Gapps size has grown, recommended open gapps package now is nano due to small system partition in N7 devices.

 

[frov]

Wauw, I now see this ROM for the N7 for the first time!

I am a big fan and user of the Mickybart nAOSP ROMs for the Xperia S and today I checked what is all available for the Nexus 7 2012, and I see the same ROM
And done by a familiar name: :good: millosr !

I know and also suffer of the slowdown issues of the aging Nexus 7 for its NAND (glad that Xperia S has better components and does not suffer the same).
So a few hours ago I flashed parrotmod into my Nexus 7 that was stock 5.1.1 but of course Rooted/TWRP3/TitaniumBackup. And Parrotmod helps!
https://github.com/parrotgeek1/ParrotMod_Grouper
The Nexus 7 is a lot smoother with Parrotmod. Before Parrotmod it would freeze severely sometimes.

So I wonder what happens when I wipe all and flash in this nAOSP: do I miss on all the smooth&speed tweaks that the Parrotmod guys collected over the months, specifically for the Nexus 7 ?
Maybe interesting to check what Parrotmod exactly does, at the XDA thread here:
http://xdaforums.com/nexus-7-2013/orig-development/beta-1-parrotmod-improve-2013-nexus-7-t3375928
Maybe I just need to flash nAOSP and then Parrotmod over it. Would like to know whether it is useful, or not.

Anyway, I will revive my old Nexus 7 with Marshmallow and I will start with this ROM !

 

[millosr]

Wauw, I now see this ROM for the N7 for the first time!

I am a big fan and user of the Mickybart nAOSP ROMs for the Xperia S and today I checked what is all available for the Nexus 7 2012, and I see the same ROM
And done by a familiar name: :good: millosr !

I know and also suffer of the slowdown issues of the aging Nexus 7 for its NAND (glad that Xperia S has better components and does not suffer the same).
So a few hours ago I flashed parrotmod into my Nexus 7 that was stock 5.1.1 but of course Rooted/TWRP3/TitaniumBackup. And Parrotmod helps!
https://github.com/parrotgeek1/ParrotMod_Grouper
The Nexus 7 is a lot smoother with Parrotmod. Before Parrotmod it would freeze severely sometimes.

So I wonder what happens when I wipe all and flash in this nAOSP: do I miss on all the smooth&speed tweaks that the Parrotmod guys collected over the months, specifically for the Nexus 7 ?
Maybe interesting to check what Parrotmod exactly does, at the XDA thread here:
http://xdaforums.com/nexus-7-2013/orig-development/beta-1-parrotmod-improve-2013-nexus-7-t3375928
Maybe I just need to flash nAOSP and then Parrotmod over it. Would like to know whether it is useful, or not.

Anyway, I will revive my old Nexus 7 with Marshmallow and I will start with this ROM !

I'm also a big fan of Mickybarts rom . I'm still using my Xperia S as my only phone, thanks to him. When I installed that rom I was surprised how stable it is, and after it I started to play with aosp building/development. I tried then to port it to N7, with success, so I'm sharing my builds now.

There are kernel related stuff, that I didn't implemented here, like color profiles (day/night) and Wake Up gestures, but other things are all build here so you should have similar experience like on Xperia S with nAOSP.

I haven't try ParrotMod here, I read that it's optimizations are mostly related with ext4 optimizations, and I'm using f2fs so I'm sure there will be any benefit of it. If you want you can try it and give us your impressions here. For me this rom works pretty smooth without ParrotMod, so I didn't wanted to experiment. Also I prefer build in Superuser over SuperSU, and as I read that ParrotMod requires SuperSU.

I'm not using Xposed on this rom on N7, because it seems that it slows down the tablet. Layers should work fine - I have merged latest layers 4.0 changes to the rom.

I'm hoping you will like the rom

 

[frov]

Flashed B06, SuperSu 2.76, Gapps

Thanks for the reply in the previous post. Now it is clear to me what the relation is between this nAOSP rom and Parrotmod. More about that later.

I flashed this nAOSP yesterday evening late (Dutch time) and installing was quite easy (when you have seen it all before).
The N7 was running: stock 5.1.1 / TWRP 302 / SuperSu 2.65. So that gave me ahead start for flashing in this nAOSP ROM.
I redid the filesystem types to F2FS in TWRP (no problem at all).
I flashed in B06 and for the rest this: (post from Xperia S): http://xdaforums.com/showpost.php?p=67682131&postcount=4831

Result of this was a very nice running Nexus7 with SuperSu 2.76 and Gapps. :good:
Already a huge improvement over stock 5.1.1 that hangs at times; now with nAOSP it feels a lot faster already.
Apps were installing bleeding fast, I was delighted. A lot faster than the Nexus 5X that my wife has.
(I am the poor husband that wants to use a 4+ years old Xperia S, haha).

Next, I am tempted to install this Parrotmod over this ROM.
However, I first want to 'feel' this nAOSP.
After some time (when I do not know yet) I will flash over it the latest Parrotmod and assess what has improved, for smoothness / speed.
And will report here of course.

For now, I am happy :laugh:

 

[myxomop25]

Hi everyone! The ROM is great, works fast and smoothly. Battery life is surprisingly incredible.

But there's one problem, which spoiled everything. Geolocation doesn't work at all. Neither by Wi-Fi, neither by GPS. First it showed if I was in another town, later is stopped show any location. I thought that there was a problem with Google Services, but with OMNI all worked great. The new version of Gapps also didn't help.

Also the thing is, I'm not a developer, so don't know how relevant it is. When I wiped data from TWRP 3, there was one problem occured:

Error opening: '/data/data/com.google.android.gms/shared_prefs/com.google.gms.playlog.uploader.xml' (No such file or directory)

. When tried to repair the data partition, another problem happened:

Repair data (f2fs) the process /sbin/fsck.f2fs/dev/block/mmcblk0p10 finished with an error. Unable to repair data.

Because of not working geolocation I had to switch to OMNI, even though I like this ROM more. Does anyone know, how to fix the problem with geolocation? Has anyone encountered this?

 

[mickybart]

@millosr

I think that the issue with geolocation is that no device override (overlay) "config_locationProviderPackageNames".

Under :
https://github.com/millosr/device_a...rameworks/base/core/res/res/values/config.xml
https://github.com/millosr/device_a...rameworks/base/core/res/res/values/config.xml

You should need to add :

<string-array name="config_locationProviderPackageNames" translatable="false">
<!-- The Google provider -->
<item>com.google.android.gms</item>
<!-- The standard AOSP fused location provider -->
<item>com.android.location.fused</item>
</string-array>

I have encountered this issue on Xperia S and that fixed the geolocation for every one.

 

[millosr]

Hi everyone! The ROM is great, works fast and smoothly. Battery life is surprisingly incredible.

But there's one problem, which spoiled everything. Geolocation doesn't work at all. Neither by Wi-Fi, neither by GPS. First it showed if I was in another town, later is stopped show any location. I thought that there was a problem with Google Services, but with OMNI all worked great. The new version of Gapps also didn't help.

Also the thing is, I'm not a developer, so don't know how relevant it is. When I wiped data from TWRP 3, there was one problem occured:

Error opening: '/data/data/com.google.android.gms/shared_prefs/com.google.gms.playlog.uploader.xml' (No such file or directory)

. When tried to repair the data partition, another problem happened:

Repair data (f2fs) the process /sbin/fsck.f2fs/dev/block/mmcblk0p10 finished with an error. Unable to repair data.

Because of not working geolocation I had to switch to OMNI, even though I like this ROM more. Does anyone know, how to fix the problem with geolocation? Has anyone encountered this?

Hi myxomop25,

What device do you have Groper or Tilapia? I will try to rebuild the rom with the change mickybart suggested.

For f2fs conversion do you have any other log message before the one you sent? Are you using twrp 3.0.2?

 

[millosr]

@millosr

I think that the issue with geolocation is that no device override (overlay) "config_locationProviderPackageNames".

Under :
https://github.com/millosr/device_a...rameworks/base/core/res/res/values/config.xml
https://github.com/millosr/device_a...rameworks/base/core/res/res/values/config.xml

You should need to add :

<string-array name="config_locationProviderPackageNames" translatable="false">
<!-- The Google provider -->
<item>com.google.android.gms</item>
<!-- The standard AOSP fused location provider -->
<item>com.android.location.fused</item>
</string-array>

I have encountered this issue on Xperia S and that fixed the geolocation for every one.

Thanks a lot. I will try to rebuild the rom with the change.

Btw, I'm not experiencing geolocation problems.

 

[mickybart]

Thanks a lot. I will try to rebuild the rom with the change.

Btw, I'm not experiencing geolocation problems.

That was the same for me on my device when some other users reported issues. This was a strange situation ! (in fact the same than the one reported here).

For information this configuration is also present on some other ROMs :

https://github.com/CyanogenMod/andr...rameworks/base/core/res/res/values/config.xml
https://github.com/omnirom/android_...rameworks/base/core/res/res/values/config.xml

 

[myxomop25]

Hi myxomop25,

What device do you have Groper or Tilapia? I will try to rebuild the rom with the change mickybart suggested.

For f2fs conversion do you have any other log message before the one you sent? Are you using twrp 3.0.2?

Hi, millosr,

Thanks for your answer. I forgot that the thread is about both Tilapia and Grouper when was writing the message. I have Tilapia.
What is about f2fs, unfortunately, I have no other logs, because except the logs I've mentioned other were all right. I use TWRP 3.0.2.