Hi, sorry for my bad english.
I'm using my galaxy note 8 for permanently home entertainment. I wish if this rom support x launcher ( google TV home AKA android TV ) please add google TV home. Thank you for your excelent job.
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 ROM 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.
Some personal thoughts:
- you should read at least install instructions stated in this post - i won`t offer support for any issues regarding installation - for extra questions read #4 post;
- press 'Thanks' button instead of saying it - it will keep the thread clean and keep me motivated to do more;
- if you like my work and want to support the development, you can always send me some pizza/coffee/drugs/drinks or anything else via paypal; - if you take any of my work without my permission i'll report you, and you'll probably get banned.
Rom Features Only for G950F / G950FD / G950N / G955F / G955FD / G955N / N950F / N950FD / N950N
Full N950FXXS9DTA1 February release
Proper S8/S8+ integration with files from G95*FXXS7DTA6 - February release
Q: Phone is showing YYY model but my phone is ZZZ model, is that normal? A: Yes, that is very normal and very intented. Do not change it or you will break features.
Q: How to revert back to Oreo?
A1: Download Oreo modem and bootloader from here, flash as normal zip in twrp and flash the Oreo rom of choice.
A2: Download full stock Oreo firmware for your region and flash it with Odin v3.13.*.
Q: Why OEM toggle is missing in this rom?
A: I disabled it to be sure nobody gets locked by mistake.
Q: Magisk app not showing, what to do?
A: Download latest Magisk Manager from here and install as normal app.
Q: My phone shows locked because "Payment services was uninstalled without authorization", how to get rid of it?
A: Unfortunately you need to reflash rom, no wipe needed. Also don't try to debloat the rom again or you will have same issue.
Q: Installation failed, what to do now?
A: First of all make sure you have the official twrp. If the probelm persists try to redownload the zip and/or select less things in Aroma installer. If you still have the problem, probably your device is not supported.
Q: How to report bugs?
A: If you want to report a bug make sure you include:
-device variant / modem version / bootloader version / region
-detailed info about the encountered issue
-steps to reproduce the bug
Been a while since i didn't write anything to these threads so i'm gonna shoot it now.
First of all i would like to thank all the donators, followers, lurkers and haters of my projects for 8895 series, without all of you nothing would have been possible.
I've been busy lately with personal life and with other projects that i couldn't find time to come and read here all that was posted and neither to post some inside infos, i can't guarantee i will be here in the future on a daily basis but i know most of the things from telegram where people drawn my attention if core things surface, and people from telegram know all my progress since i write there whenever i can. I also rather prefer to work on something than answer all the questions i receive, which most are redundant/already answered questions.
Yes i still work on this platform, most likely my Note8 is the most pleasant device to dev for, i have projects ongoing and i didn't forget about it. As many of you already know from this post, i ported indeed Android 10 for my Note 8 at first and yes, i will support S8/S8+ including Korean (N) devices in the future without any trace of doubt as soon as i sort all the things out on my Note8. For the past 2 months since i first booted i've been working on narrowing down the buglist.
For the moment only things not working on Android 10 are stock camera, face/iris recognition since both of them are camera related and flac/hdr video playback (codec related), maybe some other things are screwed too, this is what i noticed in my own tests. As working list i have many things including and not limited to wifi, nfc, sensors, pen, fingerprint, gps, sound, hwcomposer, camera on 3rd party cams (gcam, opencamera), sim and related (calls/text/data), other ported things like DexOnPc feature seenable here and here and the list can go on, maybe there are working things that i didn't even thought about them.
Disregarding the stated bugs and working list, we (me, ananjaser1211, morogoku, ivanmeler) have other 3rd party issues which we trying to sort but they might never get fixed. Since we aren't booting sw made for our board/device we need to force SELinux to Permissive state in order to accept hals conflicts and allow it to boot. The problem with Permissive is that it can't be rooted because Samsung init has conflicts with Magisk and Permissive state and it gets stuck at splash. So the current options are to use Permissive without root and everything will work as should, or switch to Enforcing state and never properly boot again (which i don't really consider an option). Ofc there are some ways like always, but the workarounds are not as good as a full Permissive state and they cause bootloops, random reboots and things not working. Coming back to the first mentioned - Permissive and Magisk don't get along - without Magisk a Permissive kernel will boot without any kinds of issues. We have an issue reported on Magisk github seenable here, but it doesn't really seem that it will get any attention, which leads me to the conclusion that any kind of Android 10 ports, for a phone that didn't got Android 10 from Samsung, will not have Magisk support given the fact that Enforcing kernel isn't booting. I'm not trying to rant, i don't blame Magisk for the issue (this is more likely caused by extra security coming from Samsung), i'm just trying to simply state some facts.
Nevertheless, it will take a more time because of board differences translated in sw that can't be ported, but i am not giving up on it and for sure something will get released at some point in the future, with or without Magisk support. Please understand this can take 1 week or 3 months more, for those who don't know this port took me 2 months to have a decent state for a release with lot less features than Note8 has and can handle, or this who took 5 months to get in a 95% working state.
A word on the other projects on this device/platform, this rom hasn't reach yet EOL just that i didn't had what to add, as you can notice on samfrew even the february security patch has same changelist as v11.1 release so it wouldn't be much of a change. However i am working on an update of rom and kernel and will try to deliver it next week. Regarding treble and its threads, i will reopen them in the near future and hopefully i'll find some time to update the vendor a bit to adapt to Android 10 gsis, or post a separate vendor just for Android 10, will think about it furtherly. On a side note i'm also working on updating TWRP trees and build to Android 9 build along with Pie kernel, hopefully compatible with encryption on aosp and maybe on other setups
Thanks again to all of you here, sit tight and enjoy pie while i try to get things sorted. Also don't forget if you like my work and want to support developement you can always send me some pizza/coffee/drugs/drinks or anything else via paypal.me/corsicanu
TL;DR - Android 10 is not coming anytime soon and most likely it will not have Magisk support, sorry.
I'm still working for this platform - new PIE rom/kernel to come next week, treble to get updated in the future, no ETA, i will post further info by the time i will have.