[ROM][6.0.1] Android 6 - Marshmallow (August 5, 2016) [P605]

[Schischu]

[ROM][6.0.1] Android 6 - Marshmallow (August 5, 2016) [P605]

Android 6.0 Marshmallow coming to a Note 10.1 LTE (2014)!
This ROM is for P605.

It is directly based on vanilla Google Android sources. Real AOSP.
This ROM is stable and can be used as a daily driver.

Download

• Note 10.1 LTE (2014) (P-605) - aosp-6.0.0-latest-lt03lte.zip (md5sum)

Download GApps

• OpenGApps (Tested with open_gapps-arm-6.0-nano-20160723)
  Do not use Stock or higher. Nano is recommended.

Download SuperSU

• SuperSu 2.76 (Tested with UPDATE-SuperSU-v2.76-20160630161323)

Prerequisites

• TWRP 2.8.6.2 or higher
• Applied bootloader update, e.g. by
  • flashing the stock 4.2(or higher) samsung rom or
  • by applying bootloader directly with odin

Instructions

1. Flash TWRP 2.7.1.1 or higher (Note: 2.8.7.0 does not work).
   
2. Reboot into recovery. Go into wipe menu. Select "Advanced Wipe". Check
   • Dalvik Cache
   • System
   • Cache
   • Data
   and wipe them. Don't reboot just yet.
   
3. Go into install.
4. Flash aosp-XXX.zip
5. Reboot to Recovery. Else flashing GAPPS will FAIL!
6. Flash GAPPS.zip
7. Flash SuperSU.zip
8. Reboot to System
9. Check Settings->System Updates (Creates /sdcard/OpenDelta/FlashAfterUpdate)
10. Copy SuperSu and Gapps zip to /sdcard/OpenDelta/FlashAfterUpdate so that they are automatically applied after OTA update. Else your system will be unusable after an OTA!

Issues

• No major issues
• Camera takes 30sec to start
• Bad GPS performance

Tips'N'Tricks

• If you install Gapps after the ROM has been booted for the first time you either need to wipe data or manually delete /data/system/users/0/runtime-permissions.xml and reboot. Without this Gapps will crash constantly. This is due to the new permissions-system in M.
• Probably just a developer tip, but if you dirty flash without cleaning /cache it could be that flashing fails. This is probably due to the /cache partition being full. Delete /cache/backup and reflash. Dunno why android fills this partition so much.

Screenshots


Source

• Kernel
• Android

/*
 * Your warranty is now void.
 *
 * I will not accept responsibility for any adverse effects to your device,
 * including, but not limited to: bricking, dead SD card, bootloops etc.
 *
 * You mod your device at your own risk.
 */

Please Donate
If you like my ROMs please donate by pressing the "Donate to Me" button below my name on the left side. It takes a lot of my spare time developing these ROMs for the community and every penny is greatly appreciated .

XDA:DevDB Information
AOSP Marshmallow, ROM for the Samsung Galaxy Note 10.1 (2014 Edition)

Contributors
Schischu
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: AOSP

Version Information
Status: Stable
Current Stable Version: >= 20151222.201844
Stable Release Date: 2015-12-22

Created 2015-11-22
Last Updated 2016-08-02

 

[Schischu]

Reserved

 

[Schischu]

There is still a lot todo. For example we should move to the newer vendor blobs.

But I think this version is a good base and I am excited to get your feedback.

Note: I recommend doing a backup of your old ROM before testing.

 

[Maritus1]

Hi,

at first thanks a lot for your hard work.
Can you please give me the link to the threads, from which you've got the Gapps,
because i'd like to know, which parts of gapps are inside those packages.

Thank you

Edit:
I just installed it, really excited Works great so far, no lags, very smooth.
Open Gapps Pico (http://forum.xda-developers.com/android/software/pa-gapps-continuation-t3098071 marshmallow is not mentioned in the thread, but you can download the packages from their download website)
The only issue so far - besides camera - is a force close of Exchange services after booting, but i freeze this service anyway, so no problem for me
This is probably a noob question, but why aren't we using SuperSu 2.52 Beta?

 

[drchohan]

Great work, I followed your excellent work on Lollipop, Now with Marshmallow, I have no reason to swap my P605. A big Thank You from Prague!.

 

[Ben81]

Does this support exfat sdcards please?

 

[Maritus1]

Issue found: Rotation doesn't work, only in horizontal mode, because Sensors don't work for me (In other roms this often was modem related, I'm on stock LP modem, which one do you use?).

XPosed v78 works in this Rom.

Edit: I've done some research, maybe it's related to the new "Sensor Hub" implemented with 6.0

Edit2:
Issue 2, already present in 5.1.1: After reboot clock is set back to a date in 2014.
Issue3: After switching to flight mode (I do not use Data), the clock is not synced with the network. So i have to set the clock manually. Though the clock in clock settings shows the right time, the clock in the upper corner and in the pull down menu remains on that time which has been set. Only when i set the clock again, it is synced with the clock in the upper corner, after that it remains on this time again. This seems a bit weird, and might be a bug in GravityBoxMM. Update: Now clock is working correctly, strange....

 

[Kybic]

I had some insurmountable problems with updating twrp, so I performed clean flash following the instructions with obsolete 2.8.1.0.

It seems to have worked, exchange services stopped on boot as reported above.

Edit: Google play crashed once during initial setup, but account configuration and play store works. Maybe caused by the ****ty wifi I am currently using.

Observed issues:
* backlight control is not fuctional
* screen rotation is not fuctional (as poster above)
* exchange service crash (as poster above)

 

[jasonm253]

Great rom..been using your first one since day one. Only thing I can see is the Screen rotation like some have mentioned. Great start and looking forward to the changes.

 

[OlafLostViking]

Encryption failing

So, I was trying out encryption and would like to share my experiences:

First try

• flash TWRP 2.8.6.1 with Odin (2.8.6.2 was not available on twrp.me)
• boot into recovery
• flash Schischu's ROM (incl md5sum check)
• reboot into recovery (w/o installing TWRP's SuperSU)
• flash SuperSU 2.52 (it seems I forgot to flash gapps here; no google "welcome" later on)
• reboot into ROM
• set password
• start encryption

Results: After initiating the encryption, the Android encryption screen is shown for just a few seconds and the tablet reboots. When now starting Android, it asks for a password. But every password (incl. the correct one) is accepted as valid but the data is claimed to be corrupted on a Decryption unsuccessful screen. I can reset the tablet from here (it boots into TWRP for a data wipe) and that's it. A wipe seems to fail, though, as the tablet continues to boot into the decryption dialog.

Second try

• wipe everything from TWRP 2.8.6.1
• flash Schischu's ROM (incl md5sum check)
• reboot into recovery (w/o installing TWRP's SuperSU)
• flash gapps and supersu 2.52
• reboot into ROM
• set password
• start encryption

Results: the same as above...

Third try

• wipe everything from TWRP 2.8.6.1
• flash TWRP 2.7.1.1 as recovery using the currently installed TWRP 2.8.6.1
• reboot into recovery
• flash Schischu's ROM (incl md5sum check)
• reboot into Schischu's ROM directly
• start encryption (without setting a password first)

Results: the same as above... (including asking for the password, even though none was set during setup)

Fourth try

• format everything from TWRP 2.7.1.1 (creating new filesystems where possible)
• reboot into recovery
• flash Schischu's ROM (incl md5sum check)
• reboot into recovery (w/o installing TWRP's SuperSU)
• flash gapps
• flash SuperSU 2.50 (not combined with gapps but in a second step)
• reboot into ROM
• skip any Google or internet setup
• set password
• start encryption

Results: the same as above...

Until now I wasn't able to get encryption to work with Schischu's ROM on the P605. Any hints what I should try? Did anybody else successfully activate tablet encryption with this ROM? Thanks.

 

[mcfisch]

My menu key works only as a "recents" key. Does anyone have an idea how to remap it?

Edit:
Changing the following line in /system/use/keylayout/sec_touchscreen.kl:

key 139 APP_SWITCH VIRTUAL

to:

key 139 MENU VIRTUAL

fixed the behavior.

 

[Maritus1]

My menu key works only as a "recents" key. Does anyone have an idea how to remap it?

Use GravityBoxMM for XPosed

 

[Schischu]

My menu key works only as a "recents" key. Does anyone have an idea how to remap it?

Edit:
Changing the following line in /system/use/keylayout/sec_touchscreen.kl:

to:

fixed the behavior.

The Recent key had to be moved, as long pressing the Home key now calls Now On Tap.
The Menu key isn't really needed anyway.

 

[Kybic]

Anyone having problems with sd card access? I have it running in external storage mode and I don't seem to have write permissions. Reading contents is fine though.

 

[kutulu32]

Anyone having problems with sd card access? I have it running in external storage mode and I don't seem to have write permissions. Reading contents is fine though.

I get a message of unsupported sd card.
My sd card is falsely recognised as samsung and i should format it if i want to use it with this rom.
My card is transcend 64gb fat32 though.
With previous rom(5.1.1) it is recognised ok
In twrp it is recognised ok
I dont know if it is a marshmallow thing and not roms fault.
I will try to reformat it

 

[Schischu]

Marshmallow changed several things, I recommend reading the following
SD-Card
System UI Tuner
Doze
Now On Tap
Permissions

 

[mcfisch]

The Recent key had to be moved, as long pressing the Home key now calls Now On Tap.
The Menu key isn't really needed anyway.

That's only true for apps already adjusted to handle the new behavior properly. Titanium backup for instance doesn't seem to correctly detect the absence of a working menu key and therefore keeps hiding the menu button. So I have no chance to setup the data folder and can't restore anything from it. And that's just one example, there are plenty of apps who get same issues.

Besides that I just don't need "now on tap" at all.

However, I think the best compromise - at least for me - would be having "recent" bound to menu-long-press.

 

[Mussels84]

subbing to follow progress. sounds like in a few versions i'll be updating to this.

 

[jacauc]

Rom works fine. After flashing opengapps 6.0 stock, I get Neverending force closes on Google play services, setup wizard and a few others... No means to fix it except reflash without gapps

 

[Maritus1]

Rom works fine. After flashing opengapps 6.0 stock, I get Neverending force closes on Google play services, setup wizard and a few others... No means to fix it except reflash without gapps

pico opengapps work just fine, maybe try a smaller package.