License and Disclaimer:
Code:
Copyright © 2016 <Jesse Chan>
Permission is hereby granted, free of charge,
to any person obtaining a copy of this software
and associated documentation files (the “Software”),
to deal in the Software without restriction,
including without limitation the rights to
use, copy, modify, merge, publish, distribute,
sublicense, and/or sell copies of the Software,
and to permit persons to
whom the Software is furnished to do so,
subject to the following conditions:
THE SOFTWARE IS PROVIDED “AS IS”,
WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO
THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS
BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
WHETHER IN AN ACTION OF CONTRACT, TORT
OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE
OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
In a word:
You are free to kang, use this ROM as base, modify or redistribute WITHOUT ask my permission.
You are recommended to give me credit but you are NOT forced to do so.
You shall not point finger at me if this ROM bring any trouble to you.
Special Features:
True Full Note 7 Port.
ODEXED.
Jesse Semi-Stock Kernel R1. (Source)(Already uploaded several days before, but seems some of you never check Github )
N7's cgroup-based SchedPolicy per-app scheduling bandwidth control algorithm.
Almost all libs are N7's.
Blue light filter working.
True Resolution Scaling(kernel-level).
BUGs:
None.
ROM Download:
Version 1.6
CSC is NOT included in this version in order to prevent CSC conflicts.
YOU MUST FLASH A CSC AFTER FLASH ROM.
About CSC:
CSC is the abbreviation of "Country Specific Configurations"
You are recommended to flash XEU CSC if you are European, for example.
Mount system partition(in TWRP's Mount Tab) and then flash.
CSC Download:
Android File Host
Telegram Discussion and Beta-Test Group:
Invite Link
Contributor:
Samsung and Google for Touchwiz and Android
Linux Community for Linux Kernel
Chainfire for Root.
XDA:DevDB Information
Jesse's Note 7 Port for S7 Edge and Flat, ROM for the Samsung Galaxy S7 Edge
Contributors
jesec
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Stable
Created 2016-08-27
Last Updated 2016-11-11
Changelog
Version 1.3 -> 1.6:
Rebase to BPIA.
Update blobs.
This should be the final version of this ROM because:
1. N updates will be launched much sooner as expected. (Beta version will be available in at most 2 weeks)
2. Official Development to Note 7 firmware was already stopped. (there is no Note 7 anymore, also no new base)
Version 1.2 -> 1.3:
1. Camera bugs fixed.
2. 3-dot menu lag fixed.
3. Rebase to BPHA.
TBD.
Reserved
First. And my first.
Downloading now.
I have tested it and it is really good and solid rom
https://1drv.ms/u/s!Akl7SdZjMCx7g5QVyZ2AJZDyYi9tMQ can you make flashable zip for this csc? to test if it can enable VoLte. greatly appreciated..
Sent from my SM-N930F using Tapatalk
i am crazy about the rom
those who have problems with updating galaxy apps from galaxy store or play store, extract the given rar file, replace the build prop file and grant permissions then reboot. thank @sac23 for the build prop.
版本有什么改进吗
Is there any improvement in the version
shazore said:
those who have problems with updating galaxy apps from galaxy store or play store, extract the given rar file, replace the build prop file and grant permissions then reboot. thank @sac23 for the build prop.
Click to expand...
Click to collapse
You need to edit build.prop and look for ro.build.official.release=true and change it to false ...
Sent from my SM-N930F using Tapatalk
aod is very dark totally unusefull
Repulsa said:
You need to edit build.prop and look for ro.build.official.release=true and change it to false ...
Sent from my SM-N930F using Tapatalk
Click to expand...
Click to collapse
thanks :good:
Thanks man, what a fine ROM release
Bravo bro!!!
Thanks Jesse... ☺
Sent from my SM-G935F using Tapatalk
tnx bro...
will try
there is no csc file to download on the given link. https://www.androidfilehost.com/?w=files&flid=93388
Sent from my SM-N930F using Tapatalk
So far so good, clean flashed the rom and everything feels smooth and stable. Things that don't work on other ports like camera modes, blue light filter and Mic issues seem to work well in this rom.
One thing I did notice so far is the lack of contact info in dialer, when.one of my contacts calls I only see the number instead of the name
Verstuurd vanaf mijn SM-N930F met Tapatalk
Does the microphone work to make more than one call without restarting the device?
megatooth said:
Does the microphone work to make more than one call without restarting the device?
Click to expand...
Click to collapse
Yes made 4 calls in the last 25 minutes without any issues
Verstuurd vanaf mijn SM-N930F met Tapatalk
Related
Guardian Rom by x942Thanks to:
The Guardian Project
Cyanogen Mod
Android Open Source Project
Open-Pdroid Project
Any one else I am missing
Click to expand...
Click to collapse
What is Guardian Rom?
Guardian ROM is a custom android ROM multiple devices. The ROM is completely Open Source and based off of the CM10.1. While this build is stable because it's based on CM10.1 it is a preview so please expect some bugs, & missing features (i.e updater).
What Features does Guardian Rom have?
Kernel is hardened with SecDroid Tweaks.
ROM is patched with and includes OpenPdoird for
permissions management.
Guardian Project apps are pre-installed – These include Orbot (Tor), Gibberbot (Secure IM),
and more.
CSSimple and OStel (https://guardianproject.info/wiki/Ostel) are included as replacements to the
built calling apps. providing encrypted communications.
If encryption is enabled and password is entered wrong 10 times the phone wipes user data.
Click to expand...
Click to collapse
Coming Soon:
Including support for Deniable Encryption (similar to Truecrypt hidden volumes).
Including GRSecurity for exploit mitigation and more secure phone.
Including SQLCipher to ensure all data is encrypted whenever possible
Including a customer “app store” for our repos.
Different lockscreen pin and Pre-Boot authentication password.
Auto-Prompt for encryption setup on first boot.
Click to expand...
Click to collapse
How to use:
Simply flash the flashable zip through your favorite custom recovery. (TWRP is recommended as it supports encrypted devices). Once flashed you should enable Full Disk Encryption by doing the following (may very depending on device):
Code:
Settings --> Security ---> Password [enter a strong 8-16 char password]
Than
Code:
Settings --> Security ---> Encryption --> Enable Encryption
Downloads:Downloads are over here.
Please verify the downloaded file with the attached GPG signature to ensure is is a legit copy.
GAPPS
Google Apps are NOT included and before you flash them you may want to read this article.
UPDATES:
Since this is a preview I have not had a chance to remove or modify the CM Updater. Please do NOT use it as you will be flashing a stock CM10.1 build and not Guardian Rom. This will be fixed shortly.
Reserved.
you could cherrypick some stuff from here
selinuxproject.org/page/SEAndroid
baz77 said:
you could cherrypick some stuff from here
selinuxproject.org/page/SEAndroid
Click to expand...
Click to collapse
I may use SeAndroid. Right now I am focusing on the encryption side of things instead of the exploit mitigation side. That will come later.
Been following your work on sec Droid, this looks like a very very good start! May I know which version of CM that you used for this? Or it is based on the latest repo when you built it.
Thanks!
Flowed from my Nexus⁴
azrash said:
Been following your work on sec Droid, this looks like a very very good start! May I know which version of CM that you used for this? Or it is based on the latest repo when you built it.
Thanks!
Flowed from my Nexus⁴
Click to expand...
Click to collapse
Awesome! Thanks! It's is based off the latest repo. I simple pulled and than modified the sources. I am currently getting some hosting for our own repo and Tor Hidden service for downloading. Stay tuned much more to come.
TimeAndroid said:
Look'in good, might try.
Click to expand...
Click to collapse
The next build will have an AOSP 4.2.2 base with Mobiflage built in. Also Lock screen PIN and Pre-Boot PINs are now separated. So you can use a simple 4 digit pin on the lock screen and a 32 character pin at boot.
Also for more security you have to passwords one for the "outer volume" which you use as you daily usage and one as "hidden volume" which is your hidden os. You use the second for anything sensitive. That way if an attacker tries to force you to give up your password you just give up the outer volume (decoy) password. There is no way to prove the hidden volume exists.
Encryption also uses AES-256-XTS now instead of AES-128-CBC. Better key length and protection against watermarking attacks.
EDIT: If anyone wants early access please PM. The build is not ready for prime time as there is no GUI for encryption but can be used as a daily driver.
SecUpwN said:
No, I'm sure you're right. But since he explicitly stated that he won't build an ('unofficial') AOKP version, I'm looking for a way to get in the favor of the securiry modifications without gaving to switch to another ROM. It's just that AOKP has so many cool simplifications compared to CyanogenMod, I'd like to avoid a switch backwards. Maybe he could create an unsupported AOKP version every month? Possible?
Click to expand...
Click to collapse
Or you could compile your own. Not trying to sound like a d**k but he had already stated numerous times he is only doing Cm base and yet u and others keep saying do this for aokp. There is a reason he is using cm as a base.
Sent from my Nexus 4 using Tapatalk 4 Beta
DontPushButtons said:
I'm guessing the modifications he has been making go a little further beyond a flashable zip. Otherwise he would've done that instead of making a whole rom around privacy.
Could be wrong..
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes. I custom kernel is needed at the very least. Not to mention removal of Google Apps and tweaked UI for encryption (mobiflage). All of these are OS level tweaks and cannot be made into a ZIP.
droidkevlar said:
Or you could compile your own. Not trying to sound like a d**k but he had already stated numerous times he is only doing Cm base and yet u and others keep saying do this for aokp. There is a reason he is using cm as a base.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
This. AOKP will NOT be supported. EVER. If anyone wants a different base download the source code from my github and compile it yourself. Build documentation is on there. Furthermore AOKP and CM10.1 are both great roms, however there are too many variables. Both have a ton of unneeded binaries and settings. We cannot guarantee security are these builds. We choose CM10.1 because it's fully open source and has fewer complications then AOKP. On NEXUS devices we are using AOSP modified with our security tweaks. On non-nexus we use CM10.1 for now for simplicity.
I am hoping with the recent Google Edition devices it will be easier to port/compile AOSP onto those devices.
TL;DR:
WE WILL NEVER OFFICIALLY SUPPORT AOKP.
Thanks for understanding.This message is only meant to stop these requests, not to be rude so please don't take it that way.
Cleaning
This thread is in the DEVELOPMENT section. And is for the "Guardian Rom [Secure] [Privacy] [Preview]".
If you need to report an issue or bug then READ THIS POST ABOUT BUG REPORTS
Keep ALL posts aimed at the ROM development.
This thread is NOT A Q&A thread.
So don't ask why the WiFi won't work, post a LOGCAT of the actual event or it did not happen.
I have cleaned this thread.
If you repeatedly make junk posts, then INFRACTIONS will follow.
~JAB
Hey @x942, where is our Android 4.3 version of this funky ROM?
SecUpwN said:
Hey @x942, where is our Android 4.3 version of this funky ROM?
Click to expand...
Click to collapse
We are working toward this. The issue we are having is that while 4.3 is latest 5.0 may be just around the corner. We don't want invest a ton of effort just to have re-port everything to 5.0 if it's released 2-3 months from now. That's not to say 4.3 won't happen. It's just we are focusing on adding more security. For now stable is 4.2.2.:good:
Am I missing where to find the flashable zip?
Sent from my Nexus 4 using xda app-developers app
Will this ever come to a Samsung Galaxy 3, or are your plans only for Nexus devices?
koz said:
Will this ever come to a Samsung Galaxy 3, or are your plans only for Nexus devices?
Click to expand...
Click to collapse
S3 is underway. We have support for:
S3, HTC One, Nexus 4, Galaxy Nexus, S4, Nexus 7 and soon Moto X, Note 3 and Nexus 5.
Request
Hi,
Please add the new moto g xt1032 to your list of planned devices - it would be a great way to get more people secured as it is a very popular handset
Thanks for all your hard work!
x942 said:
S3 is underway. We have support for:
S3, HTC One, Nexus 4, Galaxy Nexus, S4, Nexus 7 and soon Moto X, Note 3 and Nexus 5.
Click to expand...
Click to collapse
Has this ever been developed for the Galaxy S3? I haven't been able to find a download anywhere...
@X942 gaurdian rom sounds very interesting to me. would also like the att slll i747 to be added on list for consideration for dev.
am not a dev myself.
thank you for your work/time/energy. :thumbup:
err on the side of kindness
good
Sent from my Nexus 4 using XDA Premium 4 mobile app
x942 said:
S3 is underway. We have support for:
S3, HTC One, Nexus 4, Galaxy Nexus, S4, Nexus 7 and soon Moto X, Note 3 and Nexus 5.
Click to expand...
Click to collapse
I cant find a download for the Note 3 ROM. The only thing I read about it is an update on http://shadowdcatconsulting.com/blog/ saying that support will come soon.
/* Intro */
3 months after the first functional Xposed for Lollipop by @rovo89 was introduced,
now here comes *somewhat* functional Xposed for Samsung Lollipop firmware.
Embrace yourself.
/* Technical background */
Why were Samsung users left out of the Xposed party?
Because Samsung has massively customized ART runtime included in their firmwares compared to AOSP.
And plus, because the system partition has so little space left, they have additionally implemented xz decompression on top of ART.
Those 2 main reasons has differentiated Samsung's ART from the rest of the ROM's ART.
More technical information on post 2.
/* Disclaimer */
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this project
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
/* Prerequisite */
Due to my skills limitation, only deodex'ed ROMs are supported for now.
For more explanations, checkout post 2.
/* Supported firmwares */
Every ARMv7(32-bit) Samsung Lollipop Android 5.0 deodex'ed firmware should work.
But please note that I have tested this only on Galaxy S4, Note 3 and S5.
For 64-bit, please check http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960 by @wanam
For 32-bit on Android 5.1, I cannot develop on it as I don't have any 32-bit devices capable of running Android 5.1.
/* Before you download ... */
Donate to @rovo89
Donate to @wanam
Show your thanks to @_riddle
Without these people, this would not have been possible at all.
/* Details about binaries */
CyanogenMod's ART runtime changes merged - Performance improvements
Compiled using Linaro GCC 4.8
Method in-lining optimizations made in Android 5.1 merged
Few Android M ART runtime changes which were early-adopted by Samsung merged
-O3 and other compiler optimizations added
Release separated to "exynos" and "snapdragon" versions for more compiler optimizations
Optimize everything enabled
/* Download */
Attached below on XDA
/* How to install */
1. No matter what you do, back-up first.
2. Install XposedInstaller app from http://forum.xda-developers.com/showthread.php?t=3034811
3. Flash the attached Xposed framework zip on the custom recovery.
/* How to uninstall for V1 ~ V7 */
1. Flash the attached Xposed uninstaller zip on the custom recovery.
/* v75+ sticky note */
With v75 and up, this port do not longer touches core-libart.jar, thanks to @wanam.
This would potentially increase compatibility and fix other weirdness such as malfunctioning email app.
However, this introduces some variables.
First, there are more versions that you should choose.
Exynos and Snapdragon is quite self-explanatory, but there are now new "requestConcurrentGC" version for maximizing compatibility.
Don't know what to choose? Don't worry, it won't break your device if you install a wrong one.
If you install a wrong one, the installer will simply tell you that you should go with the other version.
As far as my testing goes, only the Korean Note 3 firmwares should install "requestConcurrentGC" version.
Uninstaller part have changed too.
You need to use uninstaller provided directly by @rovo89.
Do not use my uninstaller for v75 and up.
/* Technical information and Q&A */
Q: What took you so long?
A: @rovo89 has explained himself. http://forum.xda-developers.com/showpost.php?p=58949255&postcount=3
Q: Okay, you don't seem like a better developer than @rovo89. How did you do it?
A: Of course not. This is the main reason why deodex'ed ROM is a prerequisite.
Samsung has implemented all sorts of funny stuffs on their version of ART. See the link above.
To workaround this, converting a ROM to deodex'ed format somewhat brings back the oat formats to *AOSP-like* dex format(Huge thanks to @_riddle).
After deodexing is done, we can use source-built ART binaries with minimal modifications.
But due to my coding skills, I had to modify core-libart.jar to make it work again.
The core-libart.jar differs from every single device out there and it'll be a real headache to match with 1 ART binary version. That's why I've included the core-libart.jar on the installation zip file.
The included core-libart.jar has 2 different versions to correspond on the type of ROM user is using.
1 : Firmwares with appStartup
2 : Firmwares without appStartup
After deodexing, installing new ART stuffs, we can start the boot-up sequence.
Unfortunately again, /system/bin/installd passes some arguments that AOSP version of dex2oat do not understand. To bypass this, I've patched oat tools to ignore unimplemented arguments.
Now we can see the good old "Android is upgrading" pop-up and go have a cup of coffee while it dexopts all those hundreds of bloatwares.
Q: Fantastic, but now I get a continuous logcat burps - http://pastebin.com/MxeAE76n
A: To avoid that, that's why I've put 2 different versions of core-libart.jar. But unfortunately on those cases, my installer has failed to recognize which version your ROM uses.
During the installation, the installer will output a message on which core-libart.jar is installed on your system.
After you see that logcat stuffs, please change to the opposite version of core-libart.jar the installer told you.
So for example, if the installer says core-libart1.jar is installed, extract the zip and replace /system/framework/core-libart.jar with core-libart2.jar within the zip.
Q: How do I deodex my ROM?
A: @joeldroid and @svadev have an awesome tool for you to deodex your ROM.
Go check http://forum.xda-developers.com/and.../script-app-joeldroid-lollipop-batch-t2980857 and http://forum.xda-developers.com/galaxy-s5/general/tool-deodex-tool-android-l-t2972025
Both worked flawlessly for me.
Q: Gimme tha sources!
A: https://github.com/arter97/android_art/tree/samsung-lollipop
Q: AAA and BBB modules are incompatible!
A: Most likely because they don't support Touchwiz Lollipop *yet*.
Q: You mother father gentleman, you bricked my phone!
A: Unfortunately, I had tested those only on 3 devices which, ironically, has the same processor. Maybe Exynos family is not support, I don't know.
I told you to back-up beforehand. Post log and we can probably work together and add your device/ROM supported.
/* Changelog */
v75
Xposed v75 merged
(Fixes boot issue with latest Android 5.0 firmwares)
Method changed to use @wanam's XposedBridge
/* v75+ sticky note */
With v75 and up, this port do not longer touches core-libart.jar, thanks to @wanam.
This would potentially increase compatibility and fix other weirdness such as malfunctioning email app.
However, this introduces some variables.
First, there are more versions that you should choose.
Exynos and Snapdragon is quite self-explanatory, but there are now new "requestConcurrentGC" version for maximizing compatibility.
Don't know what to choose? Don't worry, it won't break your device if you install a wrong one.
If you install a wrong one, the installer will simply tell you that you should go with the other version.
As far as my testing goes, only the Korean Note 3 firmwares should install "requestConcurrentGC" version.
Uninstaller part have changed too.
You need to use uninstaller provided directly by @rovo89.
Do not use my uninstaller for v75 and up.
V6
Xposed v71 merged
Possible performance degradation issue fixed
Releases renamed to "exynos" and "snapdragon", now the "exynos" version is properly optimized for Exynos processor
Uninstaller added
Optimize everything enabled
V5
Xposed v65 merged - Now compatible with alpha4
Do not attempt to use uninstaller provided by rovo89, it will brick your device for now - TODO
V4
ART runtime & Xposed binary changes by rovo89 merged - Fixes logging and some other misc issues
CyanogenMod's ART runtime changes merged - Performance improvements
Compiled using Linaro GCC 4.8
Method in-lining optimizations made in Android 5.1 merged
Few Android M ART runtime changes which were early-adopted by Samsung merged
Few core-libart.jar smali durps fixed
-O3 and other compiler optimizations added
Release separated to "generic" and "krait" versions for more compiler optimizations
Generic - Devices with Exynos or other non-Krait Snapdragon SoCs; If you don't know which to choose, go with Generic.
Krait - Devices with Quadcore Krait Snapdragon SoCs.
V3
Another version of core-libart.jar added for GT-i9505 compatibility
(Firmwares without isMdfEnforced)
This update is unnecessary for devices which already runs Xposed with no issues.
V2
Source code modification attempted to hopefully fix boot issues with devices like Galaxy Alpha.
https://github.com/arter97/android_art/commit/eed217701cc2d3a57f940c5bd69b393c768777a9
This update is unnecessary for devices which already runs Xposed with no issues.
/* Known issues */
- Galaxy Alpha users apparently get a bootloop with this.
A kind user provided a logcat, will look into it ASAP.
Solved with V2.
- GT-I9505 users apparently get a continuous Google Apps FCs with this.
Solved with V3.
Thank you!!!!! How do we go about reverting it just in case anything were to happen? Does this have the same issue as darkera13's guide where you can't install apps?
Sweet! Any chance of supporting the S6 in the future?!
Damn no support for s6 edge
---------- Post added at 05:55 PM ---------- Previous post was at 05:54 PM ----------
Looks great though. No decomiling involved
SuperSmashedBro said:
Thank you!!!!! How do we go about reverting it just in case anything were to happen? Does this have the same issue as darkera13's guide where you can't install apps?
Click to expand...
Click to collapse
Exactly same .
Goood good
works fine on my galaxy s5 dous BOC2
xposed moudle and install apk normally works fine
darkera13 said:
Exactly same .
Click to expand...
Click to collapse
Which one is the original method yours or arter's?
I'm confused?
AMAZING!!!!!
arter you're genius!
noobiedev83 said:
Which one is the original method yours or arter's?
I'm confused
Click to expand...
Click to collapse
Me. I show a demo video 1 week ago. I public it first, even dont say but he base on my work is the true.
Xposed dont work with Samsung Lollipop Roms long time ago, the long time enough for all of you think this mission is impossible until i public my guide and he public after that about few hours.
darkera13 said:
Me. I show a demo video 1 week ago. I public it first, even dont say but he base on my work is the true.
Xposed dont work with Samsung Lollipop Roms long time ago, the long time enough for all of you think this mission is impossible until i public my guide and he public after that about few hours.
Click to expand...
Click to collapse
It should at least give you credit for that because I do remember seen your post a week ago
darkera13 said:
Me. I show a demo video 1 week ago. I public it first, even dont say but he base on my work is the true.
Xposed dont work with Samsung Lollipop Roms long time ago, the long time enough for all of you think this mission is impossible until i public my guide and he public after that about few hours.
Click to expand...
Click to collapse
Um, no offense but your method quite differs from mine.
I left out String.clear() and modified core-libart.jar to be compatible universally.
Your guide did not help me in anyways.
And I was also working on this weeks ago. Just didn't share it with the world which were *not-working* then.
arter97 said:
Um, no offense but your method quite differs from mine. And I was also working on this weeks ago. Just didn't share it with the world which were *not-working* then.
I left out String.clear() and modified core-libart.jar to be compatible universally.
Click to expand...
Click to collapse
You know what you do. Dont lie yourself.
To be honest, i tried both methods and @arter97 's methods worked for me without any hassle.
Kudos to you for making this work.
noobiedev83 said:
It should at least give you credit for that because I do remember seen your post a week ago
Click to expand...
Click to collapse
Here http://forum.xda-developers.com/showpost.php?p=60747729&postcount=2645
and here http://forum.xda-developers.com/showpost.php?p=60748574&postcount=29
darkera13 said:
You know what you do. Dont lie yourself.
Click to expand...
Click to collapse
Stealing is the least thing to do on my mind, as I have gone through the same thing over and over.
Ask my Twitter's followers.
I can personally guarantee you that I have not stolen anything from you.
Ask me how I did it more specifically, I'll happily explain it to you.
Working on Note 4 PopRocks Rom N910T
arter97 said:
Please note that I have tested this only on Galaxy S4, Note 3 and S5.
Click to expand...
Click to collapse
You think this will work on Albe95 S6 Rom port (GT-I9505)? :fingers-crossed:
The Unlegacy-Android ProjectIntroduction
Unlegacy-Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy-Android was born.
Installation
It's important that /system needs to be unmounted before installing the ROM - some recoveries tend to leave it mounted after performing operations on it.
If you're planning to install GApps, be sure to read the second post!
Aside from these, installation and upgrading is no different than on other ROMs. As usual, 'espresso' goes for all non-3g versions, 'espresso3g' goes for all 3g versions.
Problems
- Occasional sound stuttering in some games
- No hwrotation (meaning the boot animation is landscape on p31xx). I don't consider this as a problem, as autorotation will take effect after bootup anyways... and most 7" tablets, like the Nexus 7 work this way as well.
- The 7.1 builds are experimental! Means: modem not working perfectly yet.
If you notice anything else, be sure to report it in this thread. While I'm kind of busy, I usually read the thread and acknowledge the bug reports, even if I don't reply directly to them.
Downloads
See: http://builds.unlegacy-android.org
Always use the latest TWRP, to flash Android 7.x, you must use TWRP 3.0.3-0 or newer.
Features?
There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices. The aim of this project is to create a fast and stable ROM - although, one could use Xposed to add extra features.
As usual, feedback is appreciated
Want to support development? You can consider donating, I spent countless of hours with this
XDA:DevDB Information
Unlegacy Android Project, ROM for the Samsung Galaxy Tab 2
Contributors
Ziyan, Android-Andi
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 7.x Nougat
ROM Firmware Required: The latest bootloader for your device.
Version Information
Status: Beta
Current Stable Version: 4.4, 6.0
Created 2016-07-03
Last Updated 2017-10-22
GApps
If you want to install GApps, we recommend Open GApps Nano or BaNkS GApps.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. After the initial bootup finished, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
siealex said:
One more note. DO NOT set up your Google account until you grant all permissions, otherwise you will be stuck on the initial setup.
Click to expand...
Click to collapse
Rooting
You can flash either the latest SuperSU or OpenSource SuperUser to get rooted.
Ziyan said:
GApps
If you want to install GApps, we recommend Open GApps Nano or BaNkS GApps.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. After the initial bootup finished, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
Rooting
You can flash either the latest SuperSU or OpenSource SuperUser to get rooted.
Click to expand...
Click to collapse
Wow, i saw this rom on galaxy nexus section. Does this rom included CMA?
Bastiary said:
Wow, i saw this rom on galaxy nexus section. Does this rom included CMA?
Click to expand...
Click to collapse
No, at least not yet. I think that the big thing for this will be 3.4 in the near future - I made some very good progress with it, aside from camera not working yet, there are only minor problems remaining
Thank you for everything , dear friend ! And for the support of the old device , and what you are doing and Andi for us ordinary users .
I understand correctly , that support will only 6.0.1 Android N and we do not see , because the device and its old base ?
Az-09 said:
I understand correctly , that support will only 6.0.1 Android N and we do not see , because the device and its old base ?
Click to expand...
Click to collapse
Before every new Android release, we devs get all sorts of questions like this. I'd like to say it once and for all: there's no such thing as 'we do not see' the next versions and whatnot. People are being negative for some reason, but we always try and succeed in the end... I'm sure that if you start reading past posts, you'll find a lot of people saying that we1l never see Lollipop or Marshmallow due to the device being too old, lol.
Download link?
It just says look at the top of the page? Is it soon?
Thanks for the new ROM....keep it up!
All the best...
radz_ said:
Download link?
It just says look at the top of the page? Is it soon?
Thanks for the new ROM....keep it up!
All the best...
Click to expand...
Click to collapse
check download tab section.
Hello! The ROM with the codename "espresso" is for the version: Galaxy Tab 2 7.0 Wi-Fi P3110 / P3113 and Galaxy Tab 2 10.1 Wi-Fi P5110 / P5113. Namely we talk about all versions with codename "espressowifi"?!
pickmod said:
Hello! The ROM with the codename "espresso" is for the version: Galaxy Tab 2 7.0 Wi-Fi P3110 / P3113 and Galaxy Tab 2 10.1 Wi-Fi P5110 / P5113. Namely we talk about all versions with codename "espressowifi"?!
Click to expand...
Click to collapse
Yes, that's correct.
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Screeshots
Astro Noid said:
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Click to expand...
Click to collapse
no need for this, it's aosp there isn't any custom features and everybody know how aosp looks
Astro Noid said:
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Click to expand...
Click to collapse
Oh don't worry, I'm working extremely hard in the background almost since like a year... I know a lot about these devices (bought a P5100 specifically for testing 3G on the builds and kernels)
Feature list: well, this is AOSP, and I'd like to keep it this way. Imagine this like the stock ROM on the Nexus devices (with GApps flashed, of course).
Changelog: don't expect anything other than AOSP updates and hardware related fixes and updates - of course, I'm going to write a post each time I release an update, just like I do in the Galaxy Nexus thread however, it's unlikely that I'll add a changelog to the OP (I just don't see the usefulness in it).
Screenshots: will do, but then again, don't expect anything special. Stable and fast pure Android, that is AOSP. As a side note, it's Xposed compatible
I hope everybody likes the new shiny unified forum section! There's still a bit of a work left to do, but I think it looks great and eases maintaining the threads; blame me if you think otherwise :silly:
Thak you for your effort to keep tab 2 alive . Amazing work. Are RRO Layers compatible with this rom?
Ziyan said:
I hope everybody likes the new shiny unified forum section! There's still a bit of a work left to do, but I think it looks great and eases maintaining the threads; blame me if you think otherwise :silly:
Click to expand...
Click to collapse
Hi Ziyan,
I'm glad you mentioned this, as I thought that I was going insane this morning (or just slightly more insane than usual).
Just browsing the new "Unified" forum (to verify my subscriptions) and noticed that the "Dhollmen" threads could be clarified (just like the "Linaro" threads), for example ...
This thread: http://forum.xda-developers.com/showthread.php?t=2176563 could be titled: [KERNEL][P51xx][AOSP] Dhollmen Espresso
This thread: http://forum.xda-developers.com/showthread.php?t=2183830 could be titled: [KERNEL][P31xx][AOSP] Dhollmen Espresso
Just to avoid confusion (I freely admit that I am easily confused).
Thanks.
@mentat no need to have 2 threads, one is enough now in unified section
I also don't know what your question hast to do with this rom [emoji14]
~ All my work, news etc. on http://andi34.github.io ~
Android-Andi said:
@mentat no need to have 2 threads, one is enough now in unified section
I also don't know what your question hast to do with this rom [emoji14]
~ All my work, news etc. on http://andi34.github.io ~
Click to expand...
Click to collapse
Hi Andi,
I only suggested renaming the existing "pair" of threads (they both exist in the Unified Forum) ... Just like the "pair" of Linaro threads (that also both exist in the Unified forum).
The download links in (all four) of the threads (mentioned above) link to unique builds on AFH (for both P31xx and P51xx devices) in this forum: http://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified
@Ziyan, while we're on the subject, the CandySix for P51XX thread: http://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candysix-v1-1-t3331598 should also be moved to the new Unified forum as well (the CandySix for P31xx thread has already been moved).
Sorry for all the edits (I put the blame on OCD).
Thanks.
mentat said:
@Ziyan, while we're on the subject, the CandySix for P51XX thread: http://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candysix-v1-1-t3331598 should also be moved to the new Unified forum as well (the CandySix for P31xx thread has already been moved).
Click to expand...
Click to collapse
Done; I guess this is it then. Like the XDA forum admin said, the best way to handle moving both threads is to move them both to this unified section, and close one of them (preferably the one with the less posts). While we could merge them into one thread, the posts would get all mixed through the other threads posts (because of the date order) and we would lose any sense of a flow in the conversation...
Minimum Custom Recovery version?
@Ziyan @Android-Andi Thanks for bringing new life to this old tabs
Is there any minimum requirement for recovery for flashing this ROM? I'm running pretty old CWM v.6.0.5.1. Is it sufficient?
THIS PROJECT IS NO LONGER SUPPORTED.
Code:
# <Module name goes here>
## Copyright (C) 2017-2018, VR25 @ xda-developers
### License: GPL v3+
---
#### DISCLAIMER
This software is provided as is, in the hope that it will be useful, but without any warranty. Always read/reread this reference prior to installing/upgrading. While no cats have been harmed, I assume no responsibility under anything which might go wrong due to the use/misuse of it.
A copy of the GNU General Public License, version 3 or newer ships with every build. Please, read it prior to using, modifying and/or sharing any part of this work.
To prevent fraud, DO NOT mirror any link associated with this project.
---
#### DESCRIPTION
Hide USB Debugging notification, enable tethering, HDMI (& HDMI mirroring), and wireless display mirroring (Miracast). More features may come.
---
#### PRE-REQUISITES
- Magisk v15+
---
#### SETUP STEPS
1. Install/upgrade from Magisk Manager or custom recovery.
2. Reboot.
3. Go to Settings > Display > Cast > 3 dots; tick the "Enable wireless display" checkbox.
---
#### LINKS
- [Facebook Page](https://facebook.com/VR25-at-xda-developers-258150974794782/)
- [Git Repository](https://github.com/Magisk-Modules-Repo/<repo name goes here>/)
- [XDA Thread](https://forum.xda-developers.com/apps/magisk/module-miracast-tethering-enabler-adb-t3611335/)
---
#### LATEST CHANGES
**2018.10.4 (201810040)**
- Magisk 15+ support
- Set prop values aggressively.
You should note it's for marshmallow mainly. Doesn't work on Nougat for many devices. Untested on android O.
LazerL0rd said:
You should note it's for marshmallow mainly. Doesn't work on Nougat for many devices. Untested on android O.
Click to expand...
Click to collapse
I've tested only on Moto Z Play stock Nougat and LineageOS based ROMs. You may be right. Perhaps some manufacturers hardcode their ROMs to bypass this kind of modification. I don't have any other device to test this on. I'll post a poll to see how that goes. Thanks.
VR25 said:
I've tested only on Moto Z Play stock Nougat and LineageOS based ROMs. You may be right. Perhaps some manufacturers hardcode their ROMs to bypass this kind of modification. I don't have any other device to test this on. I'll post a poll to see how that goes. Thanks.
Click to expand...
Click to collapse
Well, ik on Nexus it doesn't work in any stock based Nougat ROM.
Will it work in Kitkat or Lollipop?
Raynelfss said:
Will it work in Kitkat or Lollipop?
Click to expand...
Click to collapse
Yes, but it may not work on some devices/ROMs. You should try and report back.
LazerL0rd said:
Well, ik on Nexus it doesn't work in any stock based Nougat ROM.
Click to expand...
Click to collapse
Yes. Miracast on LineageOS only work for now. (It's just fixed this problem, no magisk module, no editing build prop)
VR25 said:
After installing and rebooting, go to Settings > Display > Cast > Click the 3 dots > Enable Wireless Display > Done.
Now you can mirror your phone's screen to any Miracast supported device, such as TVs and Windows 10 PCs.
Note: this may not work on some devices/ROMs.
Click to expand...
Click to collapse
Is there a uninstaller incase it doesn't work on my phone? Running resurrection remix 7.1.2
n0013z said:
Is there a uninstaller incase it doesn't work on my phone? Running resurrection remix 7.1.2
Click to expand...
Click to collapse
Usually, this doesn't cause any issue in case it doesn't work. You can easily remove it from the Magisk Manager app. Alternatively, you can also mount magisk.img from recovery and delete the folder "magiskmiracast" inside /magisk.
Use this recovery flashable zip
https://forum.xda-developers.com/attachment.php?attachmentid=4081169&d=1489956274
to mount magisk.img to /magisk.
Miracast is working for me but only for some minutes I play videos, show some pictures and the screen freeze only in my Smartv.
I play videos and more with Allcast and it doesn't happen
Sent from my Moto G (5) Plus using XDA Labs
No luck for me
Oneplus 2 a 2003 rr 5.8.3
Not working on OP3T on OOS
Tried it and it kills magisk and xposed without mercy. Samsung galaxy on5 stock touchwiz 6.0.1
Shen Ron said:
Tried it and it kills magisk and xposed without mercy. Samsung galaxy on5 stock touchwiz 6.0.1
Click to expand...
Click to collapse
Something is wrong with TouchWiz.
So, do I need to be rooted? Or can it be flashed from stock recovery on my zte blade v7 lite (android 6.0) without damage being done? Also I do believe the device needs specific hardware, correct me if I'm wrong!?...
Has anyone tested this on OnePlus 3T?
gb_14 said:
Has anyone tested this on OnePlus 3T?
Click to expand...
Click to collapse
Heyyo, lol literally four posts above yours.
ThE_MarD said:
Heyyo, lol literally four posts above yours.
Click to expand...
Click to collapse
Oh yeah, sorry, I haven't noticed.
HTC One m9, bad boys one m9 nougat 4.1 rom.
I dont have a display option in the settings (probably because of sense)
Only have display and gestures but no cast option inside.
I installed on my S7 Edge Nougat ... But I did not find in any menu the options to activate. Has anyone had this problem? I also tried to test mirroring with an LG TV and could not.
MoKee Open Source is the biggest non-profit Android Open Source development team in China, with members from all parts of the world. We follow the latest development from Google closely and improve various parts of Android according to the user habits. Being a non-profit organisation, we utilise our spare time and own funds to keep this passion alive. Therefore, the costs for the forum and servers are solely beared by us. In order to provide a good user experience, we only included a few preinstalls in the ROM. Along with the advertisements in the forum; we hardly get enough to pay for the bandwidth. The point is, those are our only source of income, however many developers choose to exclude them when releasing unofficial builds. Unlike CyanogenMod, we did not accept monetary help at the early stages, as in China, most people do not understand the meaning of “making a donation”. They would think of it as buying a service, which is conflicting with our objectives. Anyways, we still made it until today, and even started to provide third party developers a chance to utilise our OTA system. All of these are the fruit of our hard work and passion. We are proud of the happy users, and we are also proud of the support given to MoKee Open Source. Most importantly, we are proud of the improvements we have achieved all these while, and the advancements never stop.
Hit thanks if you like my work.
Downloads : "removed by moderator"
Gapps :== "removed by moderator"
Nano recommended
Twrp :== "removed by moderator"
Don't flash magisk, right now root not supported.
What's working ---
WiFi
Mobile data
bluetooth
mobile data
hotspot
gcam
magisk
If you want to root your pie rom
just simply flash the magisk zip file via twrp.
then install the magisk manager apk manually and open that then you can the installed magisk version.
also you can check your rooot via rootchecker apk
Test this build and let me know the issue, so we could fix those issue.
Special thanks to all oxygen team and all group mates, who provides logs.
Testing thanks
@Cirno
@remicaa
@luciano Henrique
@Mario Resurrected
Credits:
MactavishAO
Hard_rock83
Mokee Development Team
LineageOS
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
Based On: Mokee Open Source Project
Version Information
Status: stable
First android 9? Things are coming! Thank you for the hard work.
Android-9.0(Pie)
It's just first build which booted properly. So there would be lots of bugs.
Let me know the bugs, so we could work on fixing bugs.
fgaurano said:
First android 9? Things are coming! Thank you for the hard work.
Click to expand...
Click to collapse
It's just first build, so there would be lots of bugs, let me know the bugs, so we could fix them.
Gapps?
MI MAX 2 cihazımdan Tapatalk kullanılarak gönderildi
OTA uptades avaible?
Appreciate the effort of developers who bought us PIE flavor for our beloved MAX2
Finally Pie on the Max 2, this is what so many have been waiting so long for. Can't wait for Gcam 6.1.
not
finger print,
double click open the screen
not blutouth
not xposed
Theseusperse said:
Finally Pie on the Max 2, this is what so many have been waiting so long for. Can't wait for Gcam 6.1.
Click to expand...
Click to collapse
GCam 6.1 working on oreo
Which twrp to be used?
ridershahmir said:
GCam 6.1 working on oreo
Click to expand...
Click to collapse
How?!?! What APK are you using for the Mi Max 2? I've tried everything, even wiped my phone and used every ROM out there and can't get anything to work. I'm specifically talking about the latest 6.1 GcCam from the Pixel 3 (Pixel3Mod) with the latest low light enhancement features from the new photo core. I'd love to know how you got it working on the Mi Max 2 on Oreo.
None of the ones on this list work for me so far:
https://www.celsoazevedo.com/files/android/google-camera/
And that's literally all of them as far as I know, including highly specialised device variants. As far as I'm aware it's Pie only.
cem_uar said:
not
finger print,
double click open the screen
not blutouth
not xposed
Click to expand...
Click to collapse
What can you expect from an alpha build .lol. isn't it enough you got pie.
scissordragonboy said:
What can you expect from an alpha build .lol. isn't it enough you got pie.
Click to expand...
Click to collapse
Is camera working on pie?
reversegear said:
Appreciate the effort of developers who bought us PIE flavor for our beloved MAX2
Click to expand...
Click to collapse
If you want to handle this Pie project you can compile from source.
My trees are open on GitHub.
Downloading. Is there a problem with IMEI?
Hucksley said:
Downloading. Is there a problem with IMEI?
Click to expand...
Click to collapse
IMEI -- no problem is rest regarding this issue -- mobile data is working properly, just don't play with network section
And add access point in data section then mobile data will work properly.
scissordragonboy said:
IMEI -- no problem is rest regarding this issue -- mobile data is working properly, just don't play with network section
And add access point in data section then mobile data will work properly.
Click to expand...
Click to collapse
Camera? Totally not working?
scissordragonboy said:
IMEI -- no problem is rest regarding this issue -- mobile data is working properly, just don't play with network section
And add access point in data section then mobile data will work properly.
Click to expand...
Click to collapse
I'm already using rom and I want to thank you for your great work.
I will use it until the next updates come out and I will notify any unknown bug so far.
Thanks again for the work!
(Sorry for the English)
hard to download