[ROM] [7.x] nAOSProm for Xperia S

Search This thread

mickybart

Senior Member
Sep 22, 2014
1,122
5,628
Montreal
I just tried to install BusyBox in order to play around with kernel toolkits and adjust the clockspeed, but I cant get BusyBox to be installed.
anyone advice?

What commands are missing on your side ?
You have toybox included on the ROM which should cover a lot of things done by busybox. For now at my knowledge, there is no busybox available for 7.0.

EDIT: I'm wrong, there is already a compiled version for 7.0 at least on Omnirom project but not on CM project. I will check to integrate it if that make sense.
 
Last edited:

heavens dragon

Senior Member
Nov 4, 2010
295
95
7.0 b02 released

  • Bluetooth (thanks @millosr) - All incoming files supported
  • FMRadio
  • Camera slow start issue fixed
  • Flashlight
  • Camera2 : crash and portrait issue fixed
  • DeskClock : crash on World button fixed
  • Email: Fake security for Exchange

Substratum fails to install any overlay seems to be either storage or SU related, any thoughts ? it was working fine in b01.
Also Gallery is empty.


Re-flash seems to have fixed this issue. One issue is still present which is bluetooth doesn't turns on B02

Edit 3: after clean flashing 3 times i moved back to b01, the overlays are getting created but they are not copied to system/vendor/overlay in fact 'overlay' folder is not there in vendor. Nothing comes up in log of substratum so I'm at lost here.
 
Last edited:

frov

Senior Member
Dec 31, 2014
436
195
Tilburg
Google Nexus 10
Google Pixel C
I just tried to install BusyBox in order to play around with kernel toolkits and adjust the clockspeed, but I cant get BusyBox to be installed.
anyone advice?

When it is on fiddling with CPU/GPU clock speed I normally use this app:
https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor

---------- Post added at 11:59 AM ---------- Previous post was at 11:57 AM ----------

I now have this funny effect on 1 of my B01 phones (I flashed 2 with B01): it refuses to switch off.
When I order for shutdown it will do so, but then it still starts to boot (showing the Sony logo, etc).
The only way to kill it is to give it a hard reset. I will flash in B02 to see whether that makes a diff.
And thanks for B02 of course :)
 

impradeepy

Senior Member
Aug 24, 2012
115
92
new delhi
When it is on fiddling with CPU/GPU clock speed I normally use this app:
https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor

---------- Post added at 11:59 AM ---------- Previous post was at 11:57 AM ----------

I now have this funny effect on 1 of my B01 phones (I flashed 2 with B01): it refuses to switch off.
When I order for shutdown it will do so, but then it still starts to boot (showing the Sony logo, etc).
The only way to kill it is to give it a hard reset. I will flash in B02 to see whether that makes a diff.
And thanks for B02 of course :)
B02 working fine you can shutdown:)
 

patrol-cz

Senior Member
May 15, 2013
428
224
Prague
This is basically already AOSP.

Hi!
Yes, _basically_ it is. The possibility to modify the DPI value is really a good thing now. However, there is a problem that it's neccessary to do it PER APP, together with font size changing.
For example, for the Settings app I'm setting the "densiest" possible layout (i.e. the lowest DPI - in the App Settings module I had 240) but I'm specifying the fonts as "big" (in App Settings, there was 140%).
It then renders Settings as I like. However, another application - GO59C (Calculator emulator) is now only hardly usable, because it draws too big fonts. I had the same DPI setting in App Settings, but no font rescaling, and it was perfect for this particular application. So, it's definitely a step ahead, but we need more of such steps :).
BTW I cannot find a way how to hide the trace of unlocking pattern. I'm afraid that it was in the Gravity module, so it's not available now, and I think that visible unlocking trace is a security risk. The passwords are also not displayed normally...

---------- Post added at 03:58 PM ---------- Previous post was at 03:40 PM ----------

Hi!
So, I installed V 7 B02 this morning with a clean flash.
The two errors about unknown commands were written on the recovery screen, as already reported. However, it worked well. I'm using micro opengapps with the ROM.
The first boot was relatively quick (I think quickier than in V6.0, probably because of less applications in the micro package) and no problems encountered at all.
I then cleanly installed all the obvious apps (i.e. no recovery from a backup). All went well. I also think that installation is now faster than in 6.0.
After that I set overclocking in Kernel Adiutor, installed a (legacy) Substratum dark theme, and rebooted the phone. My feeling is that it booted again quicker than in V6.0.
My personal opinion is that the phone is not as hot as it was with 6.0. And it looks that there is really more RAM available (thanks to SVELTE ?)
It's also too short time to be exact but I think that the battery draining will not be bigger than in 6.0.
I didn't find a serious problem in the ROM. Just a few small ones, which really don't prevent regular usage.
- Face unlock is crashing again (a faceunlock library gets SIGILL again). It did long ago in V 6.0 as well but then it repaired magically :). So now it's back.
- Is there a possibility to show arrows for data activity ? I was using Gravity but Xposed is not available for 7.0 and I cannot find the option in the ROM itself:).
- Is there a possibility to hide the unlocking pattern ? The same as above.
So, for now, really EXCELLENT ROM, even it's in the second release!
Many thanks for it!
Pavel
 
  • Like
Reactions: kin9nothin9

jgilalonso666

Senior Member
Oct 4, 2010
177
33
Hi!
Yes, _basically_ it is. The possibility to modify the DPI value is really a good thing now. However, there is a problem that it's neccessary to do it PER APP, together with font size changing.
For example, for the Settings app I'm setting the "densiest" possible layout (i.e. the lowest DPI - in the App Settings module I had 240) but I'm specifying the fonts as "big" (in App Settings, there was 140%).
It then renders Settings as I like. However, another application - GO59C (Calculator emulator) is now only hardly usable, because it draws too big fonts. I had the same DPI setting in App Settings, but no font rescaling, and it was perfect for this particular application. So, it's definitely a step ahead, but we need more of such steps :).
BTW I cannot find a way how to hide the trace of unlocking pattern. I'm afraid that it was in the Gravity module, so it's not available now, and I think that visible unlocking trace is a security risk. The passwords are also not displayed normally...

---------- Post added at 03:58 PM ---------- Previous post was at 03:40 PM ----------

Hi!
So, I installed V 7 B02 this morning with a clean flash.
The two errors about unknown commands were written on the recovery screen, as already reported. However, it worked well. I'm using micro opengapps with the ROM.
The first boot was relatively quick (I think quickier than in V6.0, probably because of less applications in the micro package) and no problems encountered at all.
I then cleanly installed all the obvious apps (i.e. no recovery from a backup). All went well. I also think that installation is now faster than in 6.0.
After that I set overclocking in Kernel Adiutor, installed a (legacy) Substratum dark theme, and rebooted the phone. My feeling is that it booted again quicker than in V6.0.
My personal opinion is that the phone is not as hot as it was with 6.0. And it looks that there is really more RAM available (thanks to SVELTE ?)
It's also too short time to be exact but I think that the battery draining will not be bigger than in 6.0.
I didn't find a serious problem in the ROM. Just a few small ones, which really don't prevent regular usage.
- Face unlock is crashing again (a faceunlock library gets SIGILL again). It did long ago in V 6.0 as well but then it repaired magically :). So now it's back.
- Is there a possibility to show arrows for data activity ? I was using Gravity but Xposed is not available for 7.0 and I cannot find the option in the ROM itself:).
- Is there a possibility to hide the unlocking pattern ? The same as above.
So, for now, really EXCELLENT ROM, even it's in the second release!
Many thanks for it!
Pavel
Hi,

I want to add to issues that I have:
1) Bluetooth is activating/deactivating all time. I can't pair my speaker.
2) it seems that the CPU can't enter in deep sleep. Reviewed with Kernel Adiutor

Anyone have the same issues??
I've done a dirty update (without wipe data) but all the rest of apps work without problems.

Thanks!!
 

mickybart

Senior Member
Sep 22, 2014
1,122
5,628
Montreal
Substratum fails to install any overlay seems to be either storage or SU related, any thoughts ? it was working fine in b01.
Also Gallery is empty.


Re-flash seems to have fixed this issue. One issue is still present which is bluetooth doesn't turns on B02

Edit 3: after clean flashing 3 times i moved back to b01, the overlays are getting created but they are not copied to system/vendor/overlay in fact 'overlay' folder is not there in vendor. Nothing comes up in log of substratum so I'm at lost here.

I have not yet tested Substratum but Patrol-cz report that it is working fine. I will give it a try and let you know.

About Bluetooth, strangely I have the issue this morning !! In fact for an unknown reason the interface do not update the real state.
Press On on Bluetooth application and after that press recent app and go back to Bluetooth and the state is updated !
I tested it before the integration of FMRadio so maybe I introduced a bug somewhere. I will check !

what are the three sensors pickup, significant motion and accelerometer, for? :confused:

Pickup is used by Ambiant display.

Significant Motion WAS used by Doze on 6.0 but this is not the case anymore. I suppose that significant motion sensor can be used again by location service to reduce power consumption for a static device but I have not yet checked if this is always the case on 7.0

Accelerometer is what permit to detect some devices move (eg: rotation and trigger screen rotation / landscape-portrait)

Hi!
Yes, _basically_ it is. The possibility to modify the DPI value is really a good thing now. However, there is a problem that it's neccessary to do it PER APP, together with font size changing.
For example, for the Settings app I'm setting the "densiest" possible layout (i.e. the lowest DPI - in the App Settings module I had 240) but I'm specifying the fonts as "big" (in App Settings, there was 140%).
It then renders Settings as I like. However, another application - GO59C (Calculator emulator) is now only hardly usable, because it draws too big fonts. I had the same DPI setting in App Settings, but no font rescaling, and it was perfect for this particular application. So, it's definitely a step ahead, but we need more of such steps :).
BTW I cannot find a way how to hide the trace of unlocking pattern. I'm afraid that it was in the Gravity module, so it's not available now, and I think that visible unlocking trace is a security risk. The passwords are also not displayed normally...

---------- Post added at 03:58 PM ---------- Previous post was at 03:40 PM ----------

Hi!
So, I installed V 7 B02 this morning with a clean flash.
The two errors about unknown commands were written on the recovery screen, as already reported. However, it worked well. I'm using micro opengapps with the ROM.
The first boot was relatively quick (I think quickier than in V6.0, probably because of less applications in the micro package) and no problems encountered at all.
I then cleanly installed all the obvious apps (i.e. no recovery from a backup). All went well. I also think that installation is now faster than in 6.0.
After that I set overclocking in Kernel Adiutor, installed a (legacy) Substratum dark theme, and rebooted the phone. My feeling is that it booted again quicker than in V6.0.
My personal opinion is that the phone is not as hot as it was with 6.0. And it looks that there is really more RAM available (thanks to SVELTE ?)
It's also too short time to be exact but I think that the battery draining will not be bigger than in 6.0.
I didn't find a serious problem in the ROM. Just a few small ones, which really don't prevent regular usage.
- Face unlock is crashing again (a faceunlock library gets SIGILL again). It did long ago in V 6.0 as well but then it repaired magically :). So now it's back.
- Is there a possibility to show arrows for data activity ? I was using Gravity but Xposed is not available for 7.0 and I cannot find the option in the ROM itself:).
- Is there a possibility to hide the unlocking pattern ? The same as above.
So, for now, really EXCELLENT ROM, even it's in the second release!
Many thanks for it!
Pavel

For now, I can't integrate some stuff like data arrows etc because I'm focusing on bug fixes and stability improvement.
But I'm not close to do it in the future if Xposed for 7.0 will not be developed.

About hide pattern, just select Pattern in Security/Screen lock. Once done, on the right of Screen Lock you have a settings button (wheel). Press on it and you can uncheck 'Make pattern visible'

For TWRP, I fixed the issue about Log error and adb shell which failed when /system is mounted. That will be available on b03.
 
Last edited:

heavens dragon

Senior Member
Nov 4, 2010
295
95
Hi,

I want to add to issues that I have:
1) Bluetooth is activating/deactivating all time. I can't pair my speaker.
2) it seems that the CPU can't enter in deep sleep. Reviewed with Kernel Adiutor

Anyone have the same issues??
I've done a dirty update (without wipe data) but all the rest of apps work without problems.

Thanks!!

bluetooth doesn't turn on for me.

@mickybart log here for bluetooth from b02:-

Code:
09-20 20:04:14.822 1827-1827/com.android.bluetooth D/BluetoothMapAppObserver: createReceiver()
09-20 20:04:14.824 1827-1827/com.android.bluetooth D/BluetoothMapAppObserver: initObservers()
09-20 20:04:14.824 1827-1827/com.android.bluetooth D/BluetoothMapAppObserver: getEnabledAccountItems()
09-20 20:04:14.854 1827-1827/com.android.bluetooth D/BluetoothAdapterService: getAdapterService() - returning com.android.bluetooth.btservice.AdapterService@8b03cb
09-20 20:04:14.862 1827-1827/com.android.bluetooth V/BluetoothAdapterState: isTurningOff()=false
09-20 20:04:14.862 1827-1827/com.android.bluetooth V/BluetoothAdapterState: isTurningOn()=true
09-20 20:04:14.862 1827-1827/com.android.bluetooth V/BluetoothAdapterState: isBleTurningOn()=false
09-20 20:04:14.862 1827-1827/com.android.bluetooth V/BluetoothAdapterState: isBleTurningOff()=false
09-20 20:04:14.862 1827-2007/com.android.bluetooth D/HeadsetPhoneState: sendDeviceStateChanged. mService=0 mSignal=0 mRoam=0 mBatteryCharge=3
09-20 20:04:14.864 1827-1827/com.android.bluetooth V/BluetoothAdapterState: isTurningOff()=false
09-20 20:04:14.864 1827-1827/com.android.bluetooth V/BluetoothAdapterState: isTurningOn()=true
09-20 20:04:14.864 1827-1827/com.android.bluetooth V/BluetoothAdapterState: isBleTurningOn()=false
09-20 20:04:14.864 1827-1827/com.android.bluetooth V/BluetoothAdapterState: isBleTurningOff()=false
09-20 20:04:14.864 1827-1827/com.android.bluetooth V/BluetoothAdapterState: isTurningOff()=false
09-20 20:04:14.864 1827-1827/com.android.bluetooth V/BluetoothAdapterState: isTurningOn()=true
09-20 20:04:14.864 1827-1827/com.android.bluetooth V/BluetoothAdapterState: isBleTurningOn()=false
09-20 20:04:14.864 1827-1827/com.android.bluetooth V/BluetoothAdapterState: isBleTurningOff()=false
09-20 20:04:14.865 1827-1827/com.android.bluetooth V/BluetoothAdapterState: isTurningOff()=false
09-20 20:04:14.865 1827-1827/com.android.bluetooth V/BluetoothAdapterState: isTurningOn()=true
09-20 20:04:14.865 1827-1827/com.android.bluetooth V/BluetoothAdapterState: isBleTurningOn()=false
09-20 20:04:14.865 1827-1827/com.android.bluetooth V/BluetoothAdapterState: isBleTurningOff()=false
09-20 20:04:14.865 1827-1827/com.android.bluetooth V/BluetoothAdapterState: isTurningOff()=false
09-20 20:04:14.865 1827-1827/com.android.bluetooth V/BluetoothAdapterState: isTurningOn()=true
09-20 20:04:14.865 1827-1827/com.android.bluetooth V/BluetoothAdapterState: isBleTurningOn()=false
09-20 20:04:14.865 1827-1827/com.android.bluetooth V/BluetoothAdapterState: isBleTurningOff()=false
09-20 20:04:14.865 1827-1827/com.android.bluetooth V/BluetoothAdapterState: isTurningOff()=false
09-20 20:04:14.865 1827-1827/com.android.bluetooth V/BluetoothAdapterState: isTurningOn()=true
09-20 20:04:14.866 1827-1827/com.android.bluetooth V/BluetoothAdapterState: isBleTurningOn()=false
09-20 20:04:14.866 1827-1827/com.android.bluetooth V/BluetoothAdapterState: isBleTurningOff()=false
09-20 20:04:14.866 1827-1841/com.android.bluetooth D/BluetoothAdapterState: Current state: PENDING_COMMAND, message: 2
09-20 20:04:14.866 1827-1841/com.android.bluetooth D/BluetoothAdapterProperties: ScanMode =  20
09-20 20:04:14.866 1827-1841/com.android.bluetooth D/BluetoothAdapterProperties: State =  11
09-20 20:04:14.867 1827-1841/com.android.bluetooth D/BluetoothAdapterProperties: Setting state to 12
09-20 20:04:14.867 1827-1841/com.android.bluetooth I/BluetoothAdapterState: Bluetooth adapter state changed: 11-> 12
09-20 20:04:14.867 1827-1841/com.android.bluetooth I/BluetoothAdapterState: Entering OnState
09-20 20:04:14.870 1827-1847/com.android.bluetooth D/BluetoothAdapterProperties: Scan Mode:21
09-20 20:04:14.870 1827-1847/com.android.bluetooth D/BluetoothAdapterProperties: Discoverable Timeout:120
09-20 20:04:14.871 1827-1827/com.android.bluetooth D/HeadsetPhoneState: sendDeviceStateChanged. mService=1 mSignal=0 mRoam=1 mBatteryCharge=3
09-20 20:04:14.871 1827-1827/com.android.bluetooth D/HeadsetPhoneState: sendDeviceStateChanged. mService=1 mSignal=0 mRoam=1 mBatteryCharge=3
09-20 20:04:14.872 1827-1827/com.android.bluetooth D/HeadsetPhoneState: sendDeviceStateChanged. mService=1 mSignal=4 mRoam=1 mBatteryCharge=3
09-20 20:04:14.876 1827-1841/com.android.bluetooth D/A2dpSinkService: getA2dpSinkService(): service is NULL


---------- Post added at 08:09 PM ---------- Previous post was at 08:05 PM ----------

I have not yet tested Substratum but Patrol-cz report that it is working fine. I will give it a try and let you know.

About Bluetooth, strangely I have the issue this morning !! In fact for an unknown reason the interface do not update the real state.
Press On on Bluetooth application and after that press recent app and go back to Bluetooth and the state is updated !
I tested it before the integration of FMRadio so maybe I introduced a bug somewhere. I will check !

yeah I'm back on b02 after seeing someone else reported that substratum is working and about bluetooth i tried the recent switch thing but still it's not working
 

patrol-cz

Senior Member
May 15, 2013
428
224
Prague
Hi,

I want to add to issues that I have:
1) Bluetooth is activating/deactivating all time. I can't pair my speaker.
2) it seems that the CPU can't enter in deep sleep. Reviewed with Kernel Adiutor

Anyone have the same issues??
I've done a dirty update (without wipe data) but all the rest of apps work without problems.

Thanks!!

Hi!
Regarding bluetooth, I'm using it width telephony headset, and it works well. After trying to start BT, the application crashed once but then resumed operation, paired successfully with the headset and now it can be used for both making and receiving calls. No other usage planned with BT here.
Regarding deep sleep, the phone sleeps a lot here, see the screenshot.
 

Attachments

  • scrn.png
    scrn.png
    92.4 KB · Views: 211

Top Liked Posts

  • There are no posts matching your filters.
  • 106
    nAOSP ROM 7.x for Xperia S

    The purpose of this rom is to provide a rom not so far of the AOSP with some cool features (nAOSP means "near AOSP").

    In addition to my work, I'm using some external works to do this rom so I first want to thanks the community and specially millosr,billchen1977,ViPER4Android Team ,Cyanogenmod Team , FXP Team

    nAOSP 7.1 Nougat Changelog
    b04 (7.1.2)

    sdcardfs is used by default. In case of an issue with a specific application (old one ?), you can revert to fuse.
    IMPORTANT: It is now possible to use ext4 again as some of you (me either) encountered some corruptions after few month with f2fs.

    • October security patches (android-7.1.2_r36)
    • kernel update (from Xperia S AOSP 8.1 work)
    • sdcarfs : replace fuse (see Settings/nAOSProm)
    • sdcardfs: reduce IOs and memory usage
    • /cache and /data: ext4 and f2fs supported

    b03 (7.1.2)
    Please cleanup data and cache of Substratum after ROM update. If it is not working, please read post #1457 and #1458
    • June security patches (android-7.1.2_r17)
    • Rebase Substratum support on mr2 branch (Rootless mode)
    • TWRP 3.1.1

    b02 (7.1.2)
    • May security patches (android-7.1.2_r10)
    • Gallery2 reintroduced @millosr)
    • Wallpaper picker fixed @millosr)
    • Google Assistant by default @millosr)

    b01 (7.1.2)
    • Android 7.1.2
    • April security patches (android-7.1.2_r5)
    • Su: security patches
    • PowerHAL
    • Lightbar: Low power mode (by default)
    • MPDecision: disabled. CPU1 controlled by PowerHAL exclusively
    • Governor: Interactive by default (automatic switch to conservative or powersave by PowerHAL)
    • Dev: rebase to mr2 branch
    • TWRP: 3.1.0 (OTA, official support for android 7.1)
    • FS: Update f2fs user tools to 1.6 (from omni)
    • Traduction: update for Simplified Chinese, Spanish and Russian (send me your nicknames and I will add credits :))
    • libcore: SafetyNet workaround (basicIntegrity and ctsProfileMatch support) - will not work in every case

    b03 (7.1.1)
    • android-7.1.1_r22 (February security fixes)
    • Settings: enable Gestures (into Device section after User) to manage pickup, double tap on power to run camera and wakeup
    • Sensors: Pickup: stable and enabled by default

    b02 (7.1.1)
    Please clean flash to fix battery drain visible on b01
    • android-7.1.1_r9 (January security fixes)
    • OTA: Support addon.d (Gapps and hosts file will be restored so you don't need to flash gapps anymore during a dirty flash) @millosr)
    • OTA: Support resize /system automatically for those with bigger /system (compatible with addon.d as the resize occurs before addon.d restore)
    • QS: Number of columns configurable @millosr)
    • Status bar: bring back support of custom battery style @millosr)
    • Navbar: Pixel style + fix crash when enabled for some applications @millosr)
    • RIL: fixed manual network selection requests @millosr)
    • Launcher3: Search bar not displayed anymore for those without search provider (not tested when a service provider is available). Dark icons on status bar if the top wallpaper is not dark.
    • Eleven, Gallery, ...: Switch from CM to LineageOS repos

    b01 (7.1.1)

    • android-7.1.1_r4 (December security fixes)
    • Themes: Pixel blue by default
    • Settings, WakeUp, ROMUpdater: fix for Pixel blue @millosr)
    • QS: Fast Charge tile removed. Fast Charge integrated with Battery tile. Properly handle the fact that a fast charge change require an unplug/plug to be effective.
    • Tethering usb/wifi fixed @AdrianDC)
    • Launcher3: Give it a try, looks like Pixel Launcher
    • Round Icons enabled

    b02
    • SeLinux: Offline charging fixed
    • OMS7: few fixes like doze invert for dark theme
    • Themes/Audio: fix StrictMode issue with theme files (fix issue like SystemUI crash with Low battery sound)
    • MTPDocumentProvider crash fixed

    b01
    • android-7.1.0_r6 (November security fixes)
    • initial release - same level than 7.0 b06
    • Power Off fixed
    • kernel: Supplementary patch for Dirty COW (thanks @millosr)
    • Gapps: Wizard issue fixed (clean flash) (thanks @Jurn_Software, @Adrian DC)
    • FMradio fixed
    • selinux: fix suntrold permissions
    • Substratum: full support (bootanim, fonts..., OMS7)
    • OTA: ROM Updater back online

    nAOSP 7.0 Nougat Changelog (DISCONTINUED)
    Previous versions


    b06
    Please remove your themes before flashing the ROM as Substratum is now fully supported (but not the legacy one)
    • android-7.0.0_r19 (November security fixes)
    • kernel: security updates
    • OMS7 support

    b05
    • android-7.0.0_r14
    • SELinux: Enforced
    • Fix camcorder
    • Fix battery draining when screen off
    • Audio: incall: port voice session and volume/mute control from nAOSP 5.1
    • Navigation bar tuner (see System UI Tuner)
    • Dialer: automatic proximity speaker
    • New audio sounds from Google Nexus devices
    • Tethering: Available for everyone (no provisionning, bypass tethering plan)
    • Ui: QS USB Tethering
    • Ui: QS Sync
    • Ui: Press on Clock or Date from status bar will start Alarm or Calandar Apps (new alarm or new event on Long press)
    • Time: Disable uneeded proprietary time_daemon which causing unexpected clock change
    • Themes: full substratum themes support (base, dialer, contacts, settings...)
    • Exchange: bring back support from Android 6.0
    • Jack: add manual plug/unplug control for broken jack detection (see nAOSProm settings and Quick Settings) - thanks to @sne and @heavens dragon for the icon
    • su: include supolicy (from SuperSU)
    • Night mode: Automatic mode and rework for 7.0/Kcal support - see System UI Tuner/Color and Appearance
    • SafetyNet: experimental workaround (working fine with SafetyNet Helper but not with Android Pay. don't know for PokemonGo)
    • TWRP: not included (please use the one from nAOSP 6.0 b13)

    b04
    • android-7.0.0_r11 (October security patches)
    • Bluetooth: fix that permit to toggle on the bluetooth after a clean flash @millosr)
    • fix multiple soft reboot (eg: video playback on Gallery) @millosr)
    • TWRP: include twrp (fix adb shell when /system mounted, log alert...) - in case of an issue to flash opengapps you will have to revert the recovery to the one provided on nAOSP 6.0 b13 or your fota backup
    • gapps-config.txt: do not install GooglePackageInstaller (needed for integrated Superuser)

    b03
    • Kernel : multiple security fixes + sdcardfs support
    • Busybox included
    • Adaway, Susbtratum legacy apps supported (some time Adaway is not able to write and need a second try)
    • diag: Fix permissions for /dev/diag and services that need it
    • GPU: Enable tiled
    • 2D: Support 60 fps + managed by the GPU to reduce CPU load (improve global responsivness).
    • OMX: Hw encoder support
    • Webview provider (Developer Settings)

    b02
    • Bluetooth (thanks @millosr) - All incoming files supported
    • FMRadio
    • Camera slow start issue fixed
    • Flashlight
    • Camera2 : crash and portrait issue fixed
    • DeskClock : crash on World button fixed
    • Email: Fake security for Exchange

    b01

    • android-7.0.0_r6 (September security fixes)
    • Selinux : PERMISSIVE (temporary)
    • telephony: opensource libril and rild (thanks @millosr)
    • Memory: Malloc SVELTE mode (reduce memory space but slower allocation speed)
    • Pretty much everything already into nAOSP 6.0 b13



    Download
    Release available under :
    https://www.androidfilehost.com/?w=files&flid=49217

    Overclocking
    Overclocked kernel are tested on my own device BUT I won't be responsible for any damages on yours.
    By default the ROM will use stock frequencies.


    Thermanager
    By default if the device is too hot it will reduce the screen brightness and CPU clock. When the device will be cool enough it will restore brightness and CPU clock but at 1.5Ghz only.
    If you want to force thermanager to restore the clock to a specific value defined by an external overclocking tool, you can edit /system/etc/thermanager.xml.
    See http://xdaforums.com/showpost.php?p=62419397&postcount=2465

    ViPER4Android
    All credits go to ViPER520 and the amazing works.
    You should read detail and go to thanks developers.
    xda : http://xdaforums.com/showthread.php?t=2191223
    website: http://vipersaudio.com/blog/?page_id=31

    Themes
    Themes are supported with Substratum only (OMS).
    This is not a CM Theme Engine and so you can just use Substratum OMS themes.

    Howto flash
    flashing procedure for 7.x

    Translation help
    Translation for 7.x

    Known issues
    Maybe never an empty list but we are trying !

    Source
    nAOSP 7.0
    nAOSP 7.1
    nAOSP 7.1.1
    nAOSP 7.1.2

    Release
    Kernel: 3.4.0
    Android: 7.x

    Thanks
    - millosr
    - billchen1977
    - ViPER4Android Team
    - Cyanogenmod Team
    - FXP Team
    - TWRP Team
    - All the community around Android

    FAQ
    31
    Camcorder fix

    We have finally succeed to fix the camcorder in android 7 :)
    @mickybart found some necessary commits and cm change proposals and integrate them in our source tree, and I did some debugging and compile parameters tuning so I have finally succeed to save the video :).

    Technically, in android 7 camera and media servers are separated in two processes so official way to handle this is to update vendor HAL to allow that:
    http://source.android.com/devices/camera/versioning.html#hardening

    Since our vendor HAL is closed source we can't do that easily. Luckily guys from Cyanogenmod team (big thanks to them) found a way to re-integrate these 2 servers:
    http://review.cyanogenmod.org/#/c/165008/

    There were also some necessary changes for frameworks/av and qcom/media projects (thanks to RonGokhale) :
    https://github.com/mickybart/android_frameworks_av/commit/b51845c31ff3f8a53f05f1401e39ea4c52babd71
    https://github.com/mickybart/androi...mmit/18914a00cd87b192dd74012419961b4d5591f118

    I have build incremental OTA update for the fix. You should flash it only if you have nAOSP-7.0-b04. It just updates necessary libraries, adds integrated media/camera server, removes old camera server, and appends one property to /system/build.prop. You don't have to flash gapps and to clean caches. If something goes wrong you can return to recovery and reflash original nAOSP-7.0-b04 and gapps to return to previous state.

    Btw, twrp recovery included in b04 didn't work fine for me so I had to extract and flash recovery from nAOSP-6.0. For your convenience I have share it. You can flash it from adb shell while android is running:
    dd if=/sdcard/recovery-6.0.img of=/dev/block/mmcblk0p11

    Downloads:

    nAOSProm-7.0-b04-camcorder-fix.zip
    Google drive: http://bit.ly/2dTZqiY
    Dropbox: http://bit.ly/2eetefC
    md5sum: 2a3823e01142784a7e07439c8c08076a

    recovery-6.0.img
    Google drive: http://bit.ly/2e6Wi5l
    Dropbox: http://bit.ly/2eAwU78
    md5sum: a40e75e743616890a09d1c75c303cd9c

    Cheers :)
    26
    Hi Guys,

    First of all, thanks to the community and specially to @jgilalonso666, @nageswarswain, @luer, @frov , @Geert G, @frantisekz, @millosr about their proposition to find another device, compiled ROMs and shared.

    I will update the ROM Updater to push @millosr version.
    I accepted the proposition of @Geert G to ship me a 2nd device and I want to thanks a lot @frov and @Geert G. This is really appreciate ! I have no words.

    So yes, I decided to go back in dev on the device and I have now a running boot.img that should be compatible with Oreo.

    Thanks again for your support and PM.
    26
    7.1.1 b01 released

    • android-7.1.1_r4 (December security fixes)
    • Themes: Pixel blue by default
    • Settings, WakeUp, ROMUpdater: fix for Pixel blue (@millosr)
    • QS: Fast Charge tile removed. Fast Charge integrated with Battery tile. Properly handle the fact that a fast charge change require an unplug/plug to be effective.
    • Tethering usb/wifi fixed (@AdrianDC)
    • Launcher3: Give it a try, looks like Pixel Launcher
    • Round Icons enabled

    OTA available
    About wallpaper change on the default Launcher3 : please use Gallery and set image as Wallpaper. I have not yet fixed the wallpaper link from the Launcher3.

    EDIT: Sorry for the possible small confusion between 7.1-b01 and 7.1.1-b01. I just realized it after the publication but I need to change ota file and rom build.prop to rename it... so that will stay like that :). Take care of 7.1 vs 7.1.1.
    26
    Good news for 7.1 !

    I have a ROM working with the same level of integration than nAOSP 7.0

    Everything seems to work except the FMradio that I need to debug and a crash of Settings when I try to go into Storage.
    Phone call not yet tested

    The official support of Night mode on 7.1 is better than on 7.0 and I ported it to use Kcal with success.

    I will release a preview really soon