Database Users

[ROM][DISCUSSION][GT-N7000] CyanogenMod 10.2 Discussion Thread

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.3 (Jelly Bean), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* 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 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. Hard. A lot.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
IMPORTANT INFORMATION
Click to expand...
Click to collapse
If this thread becomes a mess, I'll lock it immediately
We'll not support users and answer questions from users which:
- are running a custom kernel
- have flashed mods
- modified system files
- didn't follow our intructions word by word
- are unfriendly
Even if you tell us that your problem is not related to your custom kernel /mod / magic => WE DON'T CARE!
Your mod => your problem!
WIKI
Click to expand...
Click to collapse
Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/w/N7000_Info
HOW TO INSTALL
Click to expand...
Click to collapse
First time installing CyanogenMod 10.2 to your Galaxy Note, or coming from another ROM:
- Read known issues ans FAQs
- Make sure you're running a proper working ClockworkMod-Recovery
- Copy GApps and CM10.2 ZIPs to your SDCard
- Boot into Recovery
- Flash CM10.2 zip from SDCard
- Flash GApps zip from SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
Upgrading from earlier version of CyanogenMod 10.2:
- Copy CM10.2 ZIP to your SDCard
- Boot into Recovery
- Flash CM10.2 zip from SDCard
- Reboot
Upgrading from CyanogenMod 10/10.1:
- Read known issues ans FAQs
- Copy GApps and CM10.2 ZIPs to your SDCard
- Boot into Recovery
- Flash CM10.2 zip from SDCard
- Flash GApps zip from SDCard
- Wipe data, we're not sure if everything will work yet.
- Reboot
SCREENSHOTS
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
KNOWN ISSUES
Click to expand...
Click to collapse
Known bugs:
- some minor graphics glitches
- no camera fix has been merged
Remember we just merged yesterday (26th july), expect bugs in apps
DOWNLOADS
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2381499
CHANGELOG
Click to expand...
Click to collapse
http://changelog.bbqdroid.org/#/n7000/next
SUPPORT
Click to expand...
Click to collapse
Chat:
http://webchat.freenode.net/?channels=teamhacksung-support
irc.freenode.net #teamhacksung-support
Don't expect any support if you:
- are not running stock cm-kernel
- have installed any mods
- have modified system files
DEAR KANGERS
Click to expand...
Click to collapse
If you're going to reuse our work, which we're doing for free, be fair and give proper credits.
This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.
Open-Source doesn't mean Out-of-Respect!!!
SUPPORT US
Click to expand...
Click to collapse
If you want to donate a few bucks for the work we're doing in our freetime:

I will get new battery today and test this 4.3
Wysłane z mojego GT-N7000 za pomocą Tapatalk 4

So dev thread got locked within just three days.
I see, Note N7000 people are the craziest and notorious trolls here in XDA. :laugh:
Thanks for your support @XpLoDWilD.

Thanks and sorry at the same time...

M3TALLICA said:
So dev thread got locked within just three days.
I see, Note N7000 people are the craziest and notorious trolls here in XDA. :laugh:
Thanks for your support @XpLoDWilD.
Click to expand...
Click to collapse
Cause Note1 got the worst official JB update from all devices out there...therefore everybody is praying for a hero that makes a rom that works as it should....
As long as I keep the N1, cm ROMs are far better then any other tw ROM out there...
Running latest build cm10.2...some small glitches already mentioned but looks promising so far...
Thanks a lot for devs that try to bring this to work...
Sent from my GT-N7000 using xda app-developers app

Building your own CM10.2
After building and using a CM10.1 for a few days now I started to try to build the experimental CM10.2 myself.
I used the How To in the CyanogenMod wiki and changed some settings related to 10.2 (or maybe better: I tried to change).
The history:
In the morning my first build succeeded and could be installed on the device. Testing it without factory reset and only cleaning the caches. It booted in the usual way. Then I got the offer to choose between Nova and Trebuchet launcher (I'm using Nova in 10.1). The selection of the launcher resulted in a restart. So not really successful.
After a factory reset I get the restart when choosing the language in the setup. My build configuration is definitely incomplete/wrong.
Now I switched to the provided built and with this one I could boot into CM10.2 without making a factory reset. Using it right now to connect with a ssh client to my build computer at home and trying a new build.
The idea:
Maybe there are other members here who want to make their own CM10.2 builds as early as possible. Or maybe some did already.
So I want to write down the necessary changes to the normal CM10.1 procedure and I hope that this might help to solve some problems.
With the "migration" of this thread from Original Development to General I assume it is ok to do so (if not I will delete it asap).
Changes in the original Tutorial:
How To Build CyanogenMod Android for Samsung Galaxy Note (International) ("n7000")
I followed the tutorial which is a really good one. I will list the changes I made for CM 10.2.
2.3 Initialize the CyanogenMod source repository
Switched from cm-10.1 to cm-10.2
Code:
$ cd ~/android/system/
$ repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
2.8 Prepare the device-specific code
removed this. So if my new build will work this thread might get useless because there isn't much to change in the 10.1 tutorial
With these changes I can start to build CM 10.2 and get an installable zip.
Right now I'm building it again and will try later if "my" restart will disappear or some things more need to be changed.
And of course I hope some members might help me or add necessary parts.
Thanks in advance.

Thanks for the thread and sorry for the OT xplodwild
Sent from my GT-N7000 using xda premium

Yeah thank you XpLoDWilD and i am sorry too

it's a semi off-topic: i almost have one rule when i change/buy my phone: to be CM supported.
By far the best rom out there, not all the fancy things producer does (although NEMESIS project, it is one as the name states)(although i would like a center clock and a ram bar at the recent apps ), CM doesn't care about the age of the phone, or if one company must force end updating a rom, for the people to buy the next model (S thingy).
Thank you CM (i refer the the people, project and everything related to)!
Long Live CM
now you are spamming this thread too

In my oppinion, asking if the possibility of bricking one's device due to a EMMC bug and the fact that the new Android version uses a command that can trigger said bug IS development related. But heck, whatever. Then let me ask the same question here: could this ROM possibly brick my phone or was that taken care of during developement?

DeKubus said:
In my oppinion, asking if the possibility of bricking one's device due to a EMMC bug and the fact that the new Android version uses a command that can trigger said bug IS development related. But heck, whatever. Then let me ask the same question here: could this ROM possibly brick my phone or was that taken care of during developement?
Click to expand...
Click to collapse
i want to think that the developers already thought about that, and if there was any danger it was posted already...
why do we have the experimental builds, just to screw up our phones, see how many ppl flash 10.2 and screw their phones, statistical emmc chips fried?

I asked this question in the closed thread and because of that I took the liberty to repeat it in a PM.
fstrim (it is a part of the CM10.2 sources) command works on eMMC and the developers will check if this is a real threat or only a wrong assumption.
So we'll have to wait a little - the answers will come.

So this is the fun thread?
Sent from my GT-N7000 using Tapatalk 4 Beta

I hope it won't be (ab)used as such. As xplodwild made it clear by closing the other one without further warning.

I love CYANOGEN MODE.
I can't live with cyanamode...
That's why I bought gt n7000
Thank tlyou cm
Long live our CM
Sent from my GT-N7000 using xda premium

To answer the FSTRIM / EMMC brick bug: You should be safe. Right now CM kernels block all erase, and all Sammy kernels translate secure into nonsecure.

I found an info in other kernel development thread - and of course I do not know it this statement is true, but it seems logical:
fstrim won't work with MMC_CAP_ERASE disabled.
So with the safe CM kernels (here it is disabled) we still can't experience the brickbug.
But we won't get the trim benefits with 4.3 (see the XDA Portal today with a report about it).
The source of fstrim.c (in system/vold) is quite simple to read.
The magic is done in this line (part of an if-statement):
Code:
ioctl(fd, FITRIM, &range)
If the fstrim <-> MMC_CAP_ERASE relation is true, we are safe but will still suffer from the increasing lags.
Let's wait for a more reliable analysis by Entropy512 or other eMMC-Gurus.
The complete function here:
Code:
static void *do_fstrim_filesystems(void *ignored)
{
int i;
int fd;
int ret = 0;
struct fstrim_range range = { 0 };
struct stat sb;
extern struct fstab *fstab;
SLOGI("Starting fstrim work...\n");
/* Log the start time in the event log */
LOG_EVENT_LONG(LOG_FSTRIM_START, get_boot_time_ms());
for (i = 0; i < fstab->num_entries; i++) {
/* Skip raw partitions */
if (!strcmp(fstab->recs[i].fs_type, "emmc") ||
!strcmp(fstab->recs[i].fs_type, "mtd")) {
continue;
}
/* Skip read-only filesystems */
if (fstab->recs[i].flags & MS_RDONLY) {
continue;
}
if (fs_mgr_is_voldmanaged(&fstab->recs[i])) {
continue; /* Should we trim fat32 filesystems? */
}
if (stat(fstab->recs[i].mount_point, &sb) == -1) {
SLOGE("Cannot stat mount point %s\n", fstab->recs[i].mount_point);
ret = -1;
continue;
}
if (!S_ISDIR(sb.st_mode)) {
SLOGE("%s is not a directory\n", fstab->recs[i].mount_point);
ret = -1;
continue;
}
fd = open(fstab->recs[i].mount_point, O_RDONLY);
if (fd < 0) {
SLOGE("Cannot open %s for FITRIM\n", fstab->recs[i].mount_point);
ret = -1;
continue;
}
memset(&range, 0, sizeof(range));
range.len = ULLONG_MAX;
SLOGI("Invoking FITRIM ioctl on %s", fstab->recs[i].mount_point);
if (ioctl(fd, FITRIM, &range)) {
SLOGE("FITRIM ioctl failed on %s", fstab->recs[i].mount_point);
ret = -1;
}
SLOGI("Trimmed %llu bytes on %s\n", range.len, fstab->recs[i].mount_point);
close(fd);
}
/* Log the finish time in the event log */
LOG_EVENT_LONG(LOG_FSTRIM_FINISH, get_boot_time_ms());
SLOGI("Finished fstrim work.\n");
/* Release the wakelock that let us work */
release_wake_lock(FSTRIM_WAKELOCK);
return (void *)ret;
}
---------- Post added at 05:47 PM ---------- Previous post was at 05:44 PM ----------
XpLoDWilD said:
To answer the FSTRIM / EMMC brick bug: You should be safe. Right now CM kernels block all erase, and all Sammy kernels translate secure into nonsecure.
Click to expand...
Click to collapse
I just made my post and then saw this statement.
So no brick bug danger because of the blocked commands but we won't get the trim benefits in 4.3 for the N7000

On this ROM you cannot record in full HD but when you install lg camera it is working ok
Sent from my GT-N7000 using XDA Premium HD app

re TRIM, see also @Entropy512 comment here

all is nice with this rom.. cept for some graphical stuff in Feedly and during screen rotation..
it will run hot initially after that this rom runs as per normal
To get root working properly, need to disable root in developer settings, reboot the phone. After the phone reboots, enable root again. Root should work properly. Well, at least thats how i get my phone;s root working!
thanks!
A question, how do i see the list of notifications?

CAF/GIT Find7 bringup

@Entropy512
I hope u dont mind asking me a few questions in here about ur GIT and CAF merges, i follow u daily but i simply lost overview atm as im still not 100% familiar with CAF. Ur descriptions are really nice, but i cant follow them anymore. I dont want to fork ur repo, because the learning curve would drop to zero if i would do.
Ok first of all i look here for the right release. This would be of course in case of FIND 7 -> LNX.LA.3.2.5-02310-8x74.0 all good so far. Then i simply clone me the this tree. I have now correct caf tree for comparing it with the official find 7 Kernel by OPPO. Ok so far no problems... i diff or meld them together.
First thing i dont understand is why u started at 19th_Dec. Is there a sepcific reason why u did this ?? U apply oppo changes on top top of them, ok i get this, but why from 19th ?? I synced the kernel with yesterdays date and would start from here, but im sure u have ur reasons why... im more then interessted
And where i lost overview:
U created a new branch with 3.5 tag, as far as i understand this is because u will bring the changes up to KK because the LNX.LA.3.2.5-02310-8x74.0 is JB. But why then the oppo_kernel branch anyway, why havent u started with AU_LINUX_ANDROID_KK_3.5.04.04.02.003.298.
Dont get me wrong, i dont want to annoy anyone, i just want to understand how this works and why.. i hope u can shed some light in here, I would really highly appreciate it Thanks in advance

n3ocort3x said:
@Entropy512
I hope u dont mind asking me a few questions in here about ur GIT and CAF merges, i follow u daily but i simply lost overview atm as im still not 100% familiar with CAF. Ur descriptions are really nice, but i cant follow them anymore. I dont want to fork ur repo, because the learning curve would drop to zero if i would do.
Ok first of all i look here for the right release. This would be of course in case of FIND 7 -> LNX.LA.3.2.5-02310-8x74.0 all good so far. Then i simply clone me the this tree. I have now correct caf tree for comparing it with the official find 7 Kernel by OPPO. Ok so far no problems... i diff or meld them together.
First thing i dont understand is why u started at 19th_Dec. Is there a sepcific reason why u did this ?? U apply oppo changes on top top of them, ok i get this, but why from 19th ?? I synced the kernel with yesterdays date and would start from here, but im sure u have ur reasons why... im more then interessted
And where i lost overview:
U created a new branch with 3.5 tag, as far as i understand this is because u will bring the changes up to KK because the LNX.LA.3.2.5-02310-8x74.0 is JB. But why then the oppo_kernel branch anyway, why havent u started with AU_LINUX_ANDROID_KK_3.5.04.04.02.003.298.
Dont get me wrong, i dont want to annoy anyone, i just want to understand how this works and why.. i hope u can shed some light in here, I would really highly appreciate it Thanks in advance
Click to expand...
Click to collapse
Let me pitch in here
That specific CAF tag was the starting point for the source that Oppo used for their kernel base. So using that clean source he can compare to Oppo modified source.

kristofpetho said:
Let me pitch in here
That specific CAF tag was the starting point for the source that Oppo used for their kernel base. So using that clean source he can compare to Oppo modified source.
Click to expand...
Click to collapse
- Starting point: LNX.LA.3.2.5-02310-8x74.0 all clear
- but why reseting it to Dec.19th and merge in changes from oppo kernel that was released in april ?
- and why then jumping into KK AU_LINUX_ANDROID_KK_3.5.04.04.02.003.298 ?? and apply changes again ??
thats what i dont get... im sure its a brain bug on my side but whats the benefit of merging first into JB and then jump onto KK ? is it just it merges nicer if u first apply it on JB ?

n3ocort3x said:
- Starting point: LNX.LA.3.2.5-02310-8x74.0 all clear
- but why reseting it to Dec.19th and merge in changes from oppo kernel that was released in april ?
- and why then jumping into KK AU_LINUX_ANDROID_KK_3.5.04.04.02.003.298 ?? and apply changes again ??
thats what i dont get... im sure its a brain bug on my side but whats the benefit of merging first into JB and then jump onto KK ? is it just it merges nicer if u first apply it on JB ?
Click to expand...
Click to collapse
Dec. 19th is the CAF tag Oppo started from.
I set up directories something like this:
gitrepos/f7kernel which had Oppo's original source
gitrepos/msm which had a cloned repo of CAF's kernel/msm
gitrepos/checktag.sh as below:
Code:
#!/bin/bash
git reset --hard HEAD
git clean -f -d
git checkout $1
cp -R ../f7kernel/* .
git diff >../$1.patch
Then I started checking CAF tags from https://www.codeaurora.org/xwiki/bin/QAEP/release that matched msm8974 (the chip in the find7) and 04.03.00 (the Android revision that Oppo's firmware was released with - just as a warning, SOMETIMES an OEM can use a CAF tag from an older Android release. This was common with the Google Play Edition devices - most of them were released with 4.4 but were using 4.3 CAF tags for hardware support)
The smallest diff resulting from above was the tag with the closest match, which is LNX.LA.3.2.5-02310-8x74.0 (Meaning Oppo took a CAF baseline on Dec. 19, and started their work on bringing up the Find 7a from there, finishing in April. It's typical to see CAF tags 3-6 months earlier than a kernel source release.)
If you check out tag LNX.LA.3.2.5-02310-8x74.0, the most recent commit will be Dec. 19
Then I started splitting up the differences between that TAG and Oppo's sources. The process is something along the lines of
Code:
git reset HEAD^ directory/to/split/out
git commit --amend
git add directory/to/split/out
git commit
Then use git rebase -i to put the "big" patch as the most recent one in order to keep carving chunks off of it
That gets you the nice diffchunked oppo_kernel branch - in that phase I'm not merging, I'm splitting
From there, I took each patch, reviewed it, and determined if I even wanted to apply the changes. In most cases I did, but I didn't pull in Oppo's filesystem changes
Then I applied each patch on top of AU_LINUX_ANDROID_KK_3.5.04.04.02.003.298 , which is Qualcomm's latest tag on the kk_3.5 branch, which seems to be their "standard" tree for MSM8974 and MSM8226 devices (Qualcomm branching strategy can sometimes be really confusing...) Some applied cleanly, others needed significant manual effort to merge them properly.
End result: Oppo Find 7a device-specific support applied on top of Qualcomm's latest KitKat CAF tag

Entropy512 said:
Dec. 19th is the CAF tag Oppo started from.
I set up directories something like this:
gitrepos/f7kernel which had Oppo's original source
gitrepos/msm which had a cloned repo of CAF's kernel/msm
gitrepos/checktag.sh as below:
Code:
#!/bin/bash
git reset --hard HEAD
git clean -f -d
git checkout $1
cp -R ../f7kernel/* .
git diff >../$1.patch
Then I started checking CAF tags from https://www.codeaurora.org/xwiki/bin/QAEP/release that matched msm8974 (the chip in the find7) and 04.03.00 (the Android revision that Oppo's firmware was released with - just as a warning, SOMETIMES an OEM can use a CAF tag from an older Android release. This was common with the Google Play Edition devices - most of them were released with 4.4 but were using 4.3 CAF tags for hardware support)
The smallest diff resulting from above was the tag with the closest match, which is LNX.LA.3.2.5-02310-8x74.0 (Meaning Oppo took a CAF baseline on Dec. 19, and started their work on bringing up the Find 7a from there, finishing in April. It's typical to see CAF tags 3-6 months earlier than a kernel source release.)
If you check out tag LNX.LA.3.2.5-02310-8x74.0, the most recent commit will be Dec. 19
Then I started splitting up the differences between that TAG and Oppo's sources. The process is something along the lines of
Code:
git reset HEAD^ directory/to/split/out
git commit --amend
git add directory/to/split/out
git commit
Then use git rebase -i to put the "big" patch as the most recent one in order to keep carving chunks off of it
That gets you the nice diffchunked oppo_kernel branch - in that phase I'm not merging, I'm splitting
From there, I took each patch, reviewed it, and determined if I even wanted to apply the changes. In most cases I did, but I didn't pull in Oppo's filesystem changes
Then I applied each patch on top of AU_LINUX_ANDROID_KK_3.5.04.04.02.003.298 , which is Qualcomm's latest tag on the kk_3.5 branch, which seems to be their "standard" tree for MSM8974 and MSM8226 devices (Qualcomm branching strategy can sometimes be really confusing...) Some applied cleanly, others needed significant manual effort to merge them properly.
End result: Oppo Find 7a device-specific support applied on top of Qualcomm's latest KitKat CAF tag
Click to expand...
Click to collapse
man i cant thank u enough for this aweseome description many many thanks. that helped me a lot

MiPatcher: A MIUI forking utility

No more free rides

Donor is Port Rom?

Black_Eyes said:
Donor is Port Rom?
Click to expand...
Click to collapse
Yes

Tqr said:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
Runs on Windows & Linux with WINE
MiPatcher is designed to append MIUI to any CM base that shares the same 'Build.id'. This can be found in build.prop.
At the same time this will also serve as a technical guide for folks just starting out with porting MIUI in the 4.4 era, those doing this by hand or others who are just returning to the game.
MiPatcher is not a substitute for PatchROM and is not the same in function by any means although it can use Patch components on the most basic level.
This is geared more toward people who are trying to build a functional MIUI for neglected devices and also for people testing various bases who may not yet be configured to build from source to accommodate some of MIUIs functionality.
MiPatcher is as of right now very straight-forward; you pick the resolution for the device you are porting for and it will adjust the Donor MIUI to 'look right' on your device.
Requirements
- Autohotkey (Only if you intend to run the source for this)
- CyanogenMod 11
*Disabled SELinux
*Boot.img edits (for full functionality if not using PatchROM)
*Modified seapp_contexts (At Kernel level for use with PatchROM, at source level for manual porting/using this tool)
**Stock CM with init.d support may also be used; although it will be sloppy.
- MIUI donor firmware with the same 'Build.id' found in /system/build.prop
- PatchROM resources (If your Donor is a different resolution, you do not 'need' them unless things look terrible)
*Or get PatchROM resources here if you intend to grab for every resolution; it's half the size of the one on Github better compression
- WinRAR or 7zip
Features
- Automatically append MIUI to any same code-base firmware.
- Append init.d on supported devices to force boot without changes to the kernel
Prep-work
Only three files must be edited for test-ports, which I'll cover now.
Framework-res.apk
Open your Base and donor Framework-res.apk, navigate to res/xml and import the following XMLs:
Code:
Storage List
Power Profile
Build.prop
Code:
ro.build.version.incremental=x.xx.xx
persist.sys.root_access=0
ro.config.notification_sound=xxx.ogg
ro.config.alarm_alert=xxx.ogg
ro.config.ringtone=xxx.ogg
ro.skia.use_data_fonts=1
ro.miui.ui.version.code=3
ro.miui.ui.version.name=V5
qemu.hw.mainkeys=0 **[U] If you have no physical HW keys.[/U]
Updater-Script
Code:
set_perm(0, 0, 06755, "/system/xbin/lbesec"); ***If LBEsec exists in your donor
set_perm(0, 1000, 06750, "/system/xbin/shelld");
set_perm(0, 0, 06755, "/system/xbin/su");
With these most basic edits, MIUI will boot but with the need to install MIUI Lite to fix themes partially; as native ThemeManager, updater and backup will FC continuously.
Planning to use PatchROM? If you have an unlocked BL device or a device that will accept an unsigned kernel you can split your boot.img's ramdisk and add the following entries to 'seapp_contexts' immediately under user=shell, like this :
user=shell domain=shell type=shell_data_file
Code:
user=theme seinfo=platform domain=platform_app type=platform_app_data_file
user=backup seinfo=platform domain=platform_app type=platform_app_data_file
user=updater seinfo=platform domain=platform_app type=platform_app_data_file
And above anything else that may follow user=shell.
If you are not planning on using PatchROM, you will have to disable SELinux fully and edit your 'seapp_contexts' in source. In CyanogenMod11 source it is located in the following directory:
Code:
external/sepolicy/seapp_contexts
Now it's time to kill SELinux, navigate to your Kernels config folder in source; generally found at:
Code:
kernel/brand name/kernelname-common/arch/arm/configs
and find 'kernelname_defconfig' or 'kernelname_selinux_defconfig', change the following value to 'n':
Code:
CONFIG_SECURITY_SELINUX=[B]n[/B]
This will yield a functional CyanogenMod11 that can be used with PatchROM without issue, and can also be used to just fork firmware which is useful in the case of unified device builds, which Patch does not really like so much.
Now that you've built your base the following edits must be made to the kernel's Ramdisk:
Init.rc
Add this line at the very end of init.rc
Code:
import /init.miui.rc
init.miui.rc
Create this file in the root of your ramdisk and place the following inside:
Code:
#service for shelld
service shelld /system/xbin/shelld
class main
#service for su
service su_daemon /system/xbin/su --daemon
class main
oneshot
service lbesec /system/xbin/lbesec
class main
oneshot
init.superuser.rc
Code:
Delete this file
init.cm.rc
Add a '#' to the following line to disable the calling of init.superuser.rc
Code:
[B]#[/B]import /init.superuser.rc
Default.prop
Change the following values:
Code:
ro.adb.secure=[B]0[/B]
ro.secure=[B]0[/B]
ro.allow.mock.location=[B]1[/B]
Once these edits have been made your base can now be adapted to MIUI.
MiPatcher Instructions
1. Extract the contents of baserom.zip to 'base'
2. Extract the contents of miuidonor.zip to 'donor'
3. Inside of the PatchROM resources zip, extract 'HDPI' 'xHDPI' and 'xxHDPI' into the 'PatchROM' folder
4. Run MiPatcher, select your resolution and if you haven't made any kernel editing or done special source building, use soft-mods.
5. Zip the contents of 'Base' and flash it.
6. If this yields a non-booting build your codebase is too distant from your donor, find another same Build.ID release and try again if not proficient with ADB.
Current version:0.01
0.01: First release, Basic functionality and enough to produce one-shot ports when the base is properly prepared.
0.01: x64 x86 stand-alone .exe
Next Version:0.02
0.02: Clean up redundant/inefficient code.
0.02: Add options for boot.img, build.prop, meta-inf backup and loading.
*to avoid having to edit or manually move these with each attempt on base.
Download
9/28/2014: MiPatcher x86&x64
This is stand-alone and requires nothing to run, PatchROM parts are optional but suggested nonetheless.
Source
To use this source as an executable 'program' you must download and install Autohotkey, after right-click on your desktop to create a new '.ahk' file, paste the contents of this inside of it and save.
Create the following folders in the same folder as your .ahk file, the folder structure should mimic the following in terms of layout with extracting things:
-base
*META-INF
*System
*Boot.img
-donor
*META-INF
*System
*Boot.img
-mod create two notepad++ files with no extension, name them the following and place the respective content inside:
*00lbesec
Code:
#!/system/bin/sh
/system/xbin/lbesec &
*00shelld
Code:
#!/system/bin/sh
/system/xbin/shelld &
-patchrom
*HDPI
*xHDPI
*xxHDPI
AHK source:
http://paste.ee/p/balNM
FAQ
Q: My ROM isn't booting!
A: Try another MIUI that uses the same Build ID as yours, or use ADB to debug your build as it will be really close either way.
Q: Is there any difference between using a .ahk file and a .exe?
A: Yes. It's easier to update by pasting new code into a .ahk text file than to download packed .exe files in the longrun; however when using a .exe you don't need to install Autohotkey.
I will make standalone .exe for this at some point soon today.
Q: Theme/Updater/Backup is FCing!
A: It's a SELinux related error, sounds like you may be using PatchROM or a unified build; in this case build from source with the Seapp_context, and with SELinux turned off.
Q: Storage isn't mounting!/File Explorer is closing!
A: Import CyanogenMod11's 'StorageList' located in Framework-res.apk/res/xml into MIUI's along with the 'PowerProfile' to resolve unreadable storage
Q: [Insert name] App is crashing...
A: Debug using ADB or find another donor if you're feeling lazy, most of the time this yields perfect results but some things will maybe need a little polish depending on how far the codebase from the Donor and your Base firmware are.
Big TY to:
Code:
* Sijav
* Chevelle
* Yun
* All the Russian firmware developers, ahead of everyone else by a bit..
XDA:DevDB Information
MiPatcher: A MIUI forking utility, Tool/Utility for all devices (see above for details)
Contributors
Tqr
Version Information
Status: Testing
Stable Release Date: 2014-10-04
Beta Release Date: 2014-09-30
Created 2014-09-28
Last Updated 2014-09-28
Click to expand...
Click to collapse
What's the "MIUI donor firmware" ? Doest it work on Ubuntu with Wine ?

h2o64 said:
What's the "MIUI donor firmware" ? Doest it work on Ubuntu with Wine ?
Click to expand...
Click to collapse
Any MIUI firmware as long as it has the same build.id as your base
Edit: Yes this tool works in ubuntu with WINE, but only as a .exe, it can't run as a .ahk file I believe.. I mean I've never tried running raw .ahk files in Linux

Tqr said:
Any MIUI firmware as long as it has the same build.id as your base
Edit: Yes this tool works in ubuntu with WINE, but only as a .exe, it can't run as a .ahk file I believe.. I mean I've never tried running raw .ahk files in Linux
Click to expand...
Click to collapse
Okok.. I'll use CM 11 of my Moto G with the Nexus 5 build.
Can I post here if I've trouble with the software?

h2o64 said:
Okok.. I'll use CM 11 of my Moto G with the Nexus 5 build.
Can I post here if I've trouble with the software?
Click to expand...
Click to collapse
Sure, I don't mind Q&A

h2o64 said:
Okok.. I'll use CM 11 of my Moto G with the Nexus 5 build.
Can I post here if I've trouble with the software?
Click to expand...
Click to collapse
Nexus 5 won't be Good
what about a little wait and We will Port from Moto x ? @h2o64

Black_Eyes said:
Nexus 5 won't be Good
what about a little wait and We will Port from Moto x ? @h2o64
Click to expand...
Click to collapse
I'll try from one plus one (4.4.4)
If we need to wait. I prefer waiting for Redmi 1S which have a configuration very near to Moto G's one.
---------- Post added at 04:53 PM ---------- Previous post was at 04:22 PM ----------
Tqr said:
Sure, I don't mind Q&A
Click to expand...
Click to collapse
Works perfectly fine on Ubuntu 14.04 64 bits (I've used x64 one).
I'll flash the zip file. Keep you updated.

Black_Eyes said:
Nexus 5 won't be Good
what about a little wait and We will Port from Moto x ? @h2o64
Click to expand...
Click to collapse
I just made a post for the Moto X, sorry about that lol

Tqr said:
I just made a post for the Moto X, sorry about that lol
Click to expand...
Click to collapse
Which base did You use?
Help us to Boot it on Moto g

Black_Eyes said:
Which base did You use?
Help us to Boot it on Moto g
Click to expand...
Click to collapse
ok, I'll have to build you guys CyanogenMod from my code-base.. give me a few hours and I'll get it built by the end of today
Edit: I'm going to automate this in a very strong way; by the time this tool reaches 'stable' I will have ideally automated everything so that people with a totally unsupported device can have everything done for them from building to having MIUI applied without having to manually do anything.
It will not be as recent as a PatchROM build but it will be a 'sure bet' for anyone looking to use a pretty recent internal version of MIUI; I'm not trying to make a platform to replace PatchROM It's essential but I am trying to make a platform to enable people to just use MIUI without having to pull teeth over it

Tqr said:
ok, I'll have to build you guys CyanogenMod from my code-base.. give me a few hours and I'll get it built by the end of today
Click to expand...
Click to collapse
Ok Thanks i will be waiting
---------- Post added at 08:06 PM ---------- Previous post was at 08:02 PM ----------
Tqr said:
ok, I'll have to build you guys CyanogenMod from my code-base.. give me a few hours and I'll get it built by the end of today
Edit: I'm going to automate this in a very strong way; by the time this tool reaches 'stable' I will have ideally automated everything so that people with a totally unsupported device can have everything done for them from building to having MIUI applied without having to manually do anything.
It will not be as recent as a PatchROM build but it will be a 'sure bet' for anyone looking to use a pretty recent internal version of MIUI; I'm not trying to make a platform to replace PatchROM It's essential but I am trying to make a platform to enable people to just use MIUI without having to pull teeth over it
Click to expand...
Click to collapse
That will be Great :good:

Tqr said:
ok, I'll have to build you guys CyanogenMod from my code-base.. give me a few hours and I'll get it built by the end of today
Edit: I'm going to automate this in a very strong way; by the time this tool reaches 'stable' I will have ideally automated everything so that people with a totally unsupported device can have everything done for them from building to having MIUI applied without having to manually do anything.
It will not be as recent as a PatchROM build but it will be a 'sure bet' for anyone looking to use a pretty recent internal version of MIUI; I'm not trying to make a platform to replace PatchROM It's essential but I am trying to make a platform to enable people to just use MIUI without having to pull teeth over it
Click to expand...
Click to collapse
Amazing ...
Is the source code available ?
@Tqr the tutorial stays a bit un-clear :
Why using patchrom after porting ? Can we use it during porting ?
All the stuff about patchROM is a bit complicated.
We need to re-build an entire CM11 without Selinux ?

h2o64 said:
Amazing ...
Is the source code available ?
@Tqr the tutorial stays a bit un-clear :
Why using patchrom after porting ? Can we use it during porting ?
All the stuff about patchROM is a bit complicated.
We need to re-build an entire CM11 without Selinux ?
Click to expand...
Click to collapse
He will Build for Us

Black_Eyes said:
He will Build for Us
Click to expand...
Click to collapse
I'm a dev. I want to try it myself and to learn how to do.
I've work a lot on it :'( :'( :'(

h2o64 said:
Amazing ...
Is the source code available ?
@Tqr the tutorial stays a bit un-clear :
Why using patchrom after porting ? Can we use it during porting ?
All the stuff about patchROM is a bit complicated.
We need to re-build an entire CM11 without Selinux ?
Click to expand...
Click to collapse
When using PatchROM you can leave SELinux intact, when porting manually/using this tool you must fully disable SELinux or use a base that does not have it to begin with.
You don't even need to touch PatchROM to use this, or Linux honestly.. even the PatchROM Resources aren't required unless you're coming from a device with a different resolution sometimes.. but not always
Edit: Otherwise make the following edits I've outlined to CyanogenMod in source, I feel I was pretty clear on what to change

Tqr said:
When using PatchROM you can leave SELinux intact, when porting manually/using this tool you must fully disable SELinux or use a base that does not have it to begin with.
You don't even need to touch PatchROM to use this, or Linux honestly.. even the PatchROM Resources aren't required unless you're coming from a device with a different resolution sometimes.. but not always
Edit: Otherwise make the following edits I've outlined to CyanogenMod in source, I feel I was pretty clear on what to change
Click to expand...
Click to collapse
You just have to say the two first line of this post because they are perfectly understable and help me a lot .
Can I just re-built the kernel without Selinux ?

h2o64 said:
You just have to say the two first line of this post because they are perfectly understable and help me a lot .
Can I just re-built the kernel without Selinux ?
Click to expand...
Click to collapse
@h2o64 Yes
and i think that's why Rom doesn't boot with manually Porting
---------- Post added at 08:37 PM ---------- Previous post was at 08:33 PM ----------
How can i disable SELinux without Building the Kernel ?

h2o64 said:
You just have to say the two first line of this post because they are perfectly understable and help me a lot .
Can I just re-built the kernel without Selinux ?
Click to expand...
Click to collapse
No; you will still have Fingerprint errors

[Devs] Looking for a kernel base to work with? Start here.

Hello!
I'm hoping to get custom kernel & rom development up and running quickly for the G5 community, and have created a git repository which provides a kernel source base to start with.
What I've done is taken the v10a release sources and modified them to work with build directories and multiple variants. (should they be unlocked or receive the CodeFire treatment at any time)
Here's where to start: https://github.com/jcadduono/nethunter_kernel_g5/tree/stock-6.0
If you'd like a somewhat updated kernel, the stock-6.0.y branch will be patched from Linux 3.18.y branch at kernel.org, see:
https://github.com/jcadduono/nethunter_kernel_g5/tree/stock-6.0.y
Different from the absolute stock defconfigs, I've made the following changes:
Module signature verification disabled
Unnecessary debugging flags separated into debug_defconfig (use EXTRA_DEFCONFIG=debug_defconfig to enable them)
Flags that were previous set to module (=m) have been set to =y (built-in) in case incompatibilities are unable to load stock modules
Each known variant & target is listed in build.sh comments. The default variant when building with ./build.sh is h850 with debugging disabled.
When using the Makefile, VARIANT_DEFCONFIG=variant_xxx_defconfig adds the additional settings per variant to the target defconfig. (by default stock_defconfig)
build.sh is set up to automatically build a dtb.img after creating the kernel Image.gz based on whichever variant you've built for.
You can use ./menuconfig.sh to modify the stock defconfig, or you can copy the stock_defconfig to another name such as my_defconfig and use TARGET=my ./menuconfig or TARGET=my ./build.sh
It's easier to just set the default target in build.sh/menuconfig.sh - each have their configuration options near the top of the files.
Be sure to edit the config variables in build.sh and menuconfig.sh before using. The VERSION file gets appended to the kernel version shown in `uname` when using build.sh.
The toolchain must be pointed to the correct location before it can build. Be sure to have libncurses5-dev and colordiff packages installed for menuconfig.sh.
For a toolchain, I recommend using the GCC Linaro aarch64 5.3 2016.02 release. You can use basically any aarch64 toolchain though.
Download here: https://releases.linaro.org/compone...o-5.3-2016.02-x86_64_aarch64-linux-gnu.tar.xz
You can start by forking my repository on GitHub and giving it your own name if you like. Extra interesting commits are available in the other branches that you should be able to cherry-pick without issues should you be interested in them.
Looking to test your kernel Image.gz + dtb.img?
Look no further than my LazyFlasher repository!
See here: https://github.com/jcadduono/lazyflasher/tree/kernel-flasher
Simply do:
Code:
git clone -b kernel-flasher https://github.com/jcadduono/lazyflasher.git kernel-flasher
cd kernel-flasher
cp /path/to/Image.gz /path/to/dtb.img ./
make
(simply place your kernel Image.gz (optional) and dtb.img (optional) in the root of the repository and type make!)
And you'll have your own dynamic kernel flashing zip for custom recoveries!
The kernel-flasher repository is capable of great things. You can create scripts in patch.d to do anything you like.
Add files to the ramdisk-patch folder and create a script that copies them into the $ramdisk folder and they will be rebuilt into the ramdisk!
By default, no-verity-opt-encrypt is there as an example.
Using setprop in patch.d scripts allows you to set props in default.prop with ease.
Add functions to patch.d-env to make them globally usable across patch.d scripts.
See other branches for more examples, like how to add f2fs lines to the fstab, or patch for system mode SuperSU.
LazyFlasher is the installer used in the Kali NetHunter project. You can also find more examples in the kali-nethunter GitHub!
Good luck, and happy kernel developing!

Thanks so much for posting this.
Code:
./obligatoryn00bstatement
Sorry for not being too knowledgeable here (yet?) and if this sort of comment doesn't belong.
I am a Computer Science major who really wants to learn some skills to hopefully give back to the community.
Is this an area that I could be of use or should I perhaps spend more time going through material on the XDA-U site?

toefurkey said:
Thanks so much for posting this.
Code:
./obligatoryn00bstatement
Sorry for not being too knowledgeable here (yet?) and if this sort of comment doesn't belong.
I am a Computer Science major who really wants to learn some skills to hopefully give back to the community.
Is this an area that I could be of use or should I perhaps spend more time going through material on the XDA-U site?
Click to expand...
Click to collapse
I'm a little tired and somewhat intoxicated here at 3:45 AM so this is going to be a bit of rambling and so on...
While it's certainly a good idea to study up on what interests you before digging into it, sometimes it really can be easier just to dive in to your hobby.
I'm a high school drop out, never made it through college. Everything I've learned is by taking the great work done by the open source community and reading their code and applying it to other projects. That's the great thing about open source and nonrestrictive licenses. Everything is there for you to figure out, make changes, borrow code, run into problems, and the best part - search for solutions that others have already provided in their struggle to do exactly what you're doing.
Have an idea for a great feature? You can probably find it already implemented in another kernel somewhere.
Find the work someone else has done and modify it to fit your needs, but don't forget to give them credit for their work that you've used!
If you're going to start writing your own code, be certain to keep it tidy and variables/functions with meaningful names and comments so that not only others can understand and learn from it, but that you can return to the same code later on and understand it. Confusing code is how bugs tend to show up and become almost impossible to squash.
What I'm trying to get across here is don't be afraid to not be original. Don't be afraid to use others work to accomplish what you want, so long as they receive some attribution. The quickest way to learn how things work is by understanding what's already there and available to you.
You'll notice that there's projects all over XDA with special features ported from one device to another. Isn't it great having the all the best features people have added to other devices on one really nice device that you have?
PS I've never been on the XDA-U site before, so I can't give an opinion there.
I forgot what I was on about so I'll end this here lol.

?jcadduono you're on fire man thank you for everything you've been doing so far with such little resources.
Sent from my LG-H820 using XDA-Developers mobile app

jcadduono, thanks for the info and wonderful words of wisdom!
I totally agree on what you're saying and my goal is to try diving into this as a hobby. The hardest part for me isn't so much the coding part, but just figuring out a starting point to get grounded and build upon and I feel like what you've provided here is perhaps the starting point I need. Now it's just up to me to push myself in my free time.

Hi, i am new to kernel developing, but i did some roms myself before, so no total linux noob.
I cloned your 6.0.y and want to start from there, but im a little bit lost. Do i need to follow the steps @ github, or is your branch kinda pre setup ?
Toolchain path is also set to the one you gave a link too.

Pinu'u said:
Hi, i am new to kernel developing, but i did some roms myself before, so no total linux noob.
I cloned your 6.0.y and want to start from there, but im a little bit lost. Do i need to follow the steps @ github, or is your branch kinda pre setup ?
Toolchain path is also set to the one you gave a link too.
Click to expand...
Click to collapse
Hopefully once the toolchain path is set you should only need to run ./build.sh to actually build the kernel and dtb.
You may be missing some items for menuconfig.sh, which should just be solved by apt-get install colordiff libncurses5-dev
If building inside a ROM tree, it should be fairly simple for developers to adjust their ROM configs to add more to the kernel make command line, such as VARIANT_DEFCONFIG.

No matter what i do, kernel builds, but no dtb.img will be created. Any ideas where to look / what to test ?
I have stock-6.0.y, and did the h850 one.

Hi, is the stock-6.0.y branch removed?
I didnt find it. and need the right defconfig
greetz
mericon

Bliss OS - Pie for PCs (LTS)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
team bliss is pleased to present to you
bliss rom based on Android 9 Pie​
Our focus is to bring the Open Source community a quality OS that can run on all your devices as a daily driver, syncing your apps + settings + customizations across all platforms you run Bliss on.
Bliss ROMs comes with a wide selection of customization options from around the Android community as well as unique options developed by our team. With so many options available, you’ll find it hard not to enjoy the Blissful experience.
Notice
- READ: The OP and most recent discussions will generally help to answer any questions you will encounter. If not, we will do our best to answer your questions & concerns as soon as possible. We will also simply direct you to the OP if the answer is contained there. We encourage community minded interactions: users helping fellow users allows Team Bliss to focus on the work involved to make things Blissful.
- Please do not ask for ETA's;
- We will not tolerate any rudeness or anyone being disrespectful in this thread. Moderators, feel free to enforce anything you feel is necessary to stop bad posts;
- We encourage users to contribute towards this project, and we're openly accepting applications for others to join Team Bliss
First, a little bit about this project...
Starting in Android Pie, Bliss OS will be taking a different approach to building Android for PC's. Taking inspiration from @phhusson 's Treble methods, and Intel's Project Celadon, we have reworked a good majority of the commits from Android-x86 Project and Bliss OS's Oreo release, and packaged it up so that it can work a bit more dynamically. The result was something we could integrate into a single source, along side normal device builds. This is much like our Treble builds that use PHH's Treble methods, and Intel's Project Celadon's EFI builds. Both of which are also buildable directly from the BlissRoms-x86 source: https://github.com/BlissRoms-x86/manifest
These Bliss OS releases will be considered the Bleeding Edge of development for Android on x86, and we will be marking most of our additions to be sent down the ladder to our Android-PC project & hopefully Android-x86 Project as well. For now though, you can stay tuned to this thread for updates on all that.
ROM Porting Details:
Like we mentioned already, things this round will be done a bit differently using the patching system to build for x86 devices, making updating and maintaining far easier than before, and even lowers the bar for understanding how it all works. But things were still complicated enough for us to see room for improvement. So we have also packaged up all the x86 bits we add to Bliss OS, minus a few goodies and are making them available to the entire community to add to their ROM projects. You can find the basics on GitHub already, https://github.com/Android-PC and for those interested in adding x86 support to your own ROM, I was able to squash things down to a single commit in build/make in order to help get the ball rolling. This will also be the source we are helping out Android-x86 Project with, so don't be surprised if things change a bit to reflect that projects branding more.
https://github.com/Android-PC/platform_build/commit/eda2e16b0018c5554f98acaa708f8200a171f206
I'm always open to suggestions on how we can improve upon things too, so don't be afraid to speak up, just remember to be considerate upon doing so
We will be updating our website also over the next few weeks to feature a new downloads section, as well as further information about using our source for commercial projects.
AIO Thread​
Bliss Source
https://github.com/BlissRoms
BlissRoms Devices Source
https://github.com/BlissRoms-Devices
BlissRoms Kernel Source
https://github.com/BlissRoms-Kernels
BlissRoms Vendor Source
https://github.com/BlissRoms-Vendor
BlissRoms-x86
https://github.com/BlissRoms-x86
Bliss' Android-PC Project
https://github.com/Android-PC
Open Gapps Project
!!CONSIDER THESE AS DEVELOPMENT BUILDS FOR NOW!!
These are not to be considered stable in any way shape or form. Please continue at your own risk. Developers and experienced users suggested
This release is a work in progress, and will take community effort in order to iron out all the bugs.
There are no IPTS builds for the Surface devices yet, and there won't be until I am able to fix my SurfaceBook. Sorry :'(
Read the documentation first:
https://docs.blissos.org
Team Bliss is not responsible in any way for anything that happens to your device in the process of installing
Please familiarize yourself with available installation options before attempting to install the OS.
Please make sure you download the correct version of Bliss for your specific device. The links are labeled clearly.
Download the ISO file
Use Rufus or similar to burn to USB drive
Disable Secure Boot, Bitlocker, and any other boot security
Boot into the USB drive.
Run Bliss OS in Live mode to test things out, if all is well, continue to next step
Boot into the USB drive, and choose Bliss OS Install
Pick your poison, but please do this with caution, making sure to fully understand what you are doing.
These are beta builds, so please take that into consideration when reporting issues. We want all the info possible
Packages Manager sometimes crashes the system. This will require you to wait, then open a terminal and use $ su && svc wifi disable , and when it comes back, $ su && svc wifi enable
Screenshots aren't working yet
Video playback does not work right as of yet
Sound issues on many machines still
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you and our team quite some time.
-Download the Catlog app from the Play Store.
There is also a donate version which you can purchase to show appreciation.
-After downloading the Catlog app, go to the app settings, and change the log level to Debug.
-Clear all previous logs and take the exact steps to produce the error you are receiving.
-As soon as you receive the error (probably a force close), go straight into Catlog and stop the log recording.
-Copy and paste the entire log either to Hastebin or Pastebin
-Save the log, and copy and paste the link into the forum with a brief description of the error.
-You can also open trouble tickets on our website for bugs.
A huge thanks to Chainfire, CM/LineageOS, Android-x86, Jide, @farmerbb & all the other developers who work hard to keep all the great features coming!
We really appreciate all your knowledge & hard work!
If someone takes it upon themselves to donate to us, of course it will be appreciated, and all funds will be used to pay our server and upkeep fees.
If someone wants to donate, our PayPal link is below.
PayPal Link
Very Important Information
Team Bliss will allow some minor off-topic comments in our development threads.
Please post in the general forums for off-topic comments and/or questions.
Overall, please keep comments relevant to development, as this better helps you and our team
when trying to determine problems that users are having.
We appreciate all levels of knowledge in our threads, and therefore we ask that
the seasoned members be helpful to those with less knowledge.
Most importantly, do NOT troll those with less knowledge than yourself.
Should you feel inclined to not abide by our request, the XDA Moderators may be called in to remove posts.
We thank you for adhering to our thread rules.
Thank you for using Bliss! And have as always: #StayBlissful​
XDA:DevDB Information
Bliss OS - Pie for PCs (development Beta Preview), ROM for the ROM Central
Contributors
electrikjesus, ElfinJNoty
Source Code: https://github.com/BlissRoms
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: x86 Arch
Version Information
Status: Beta
Current Beta Version: 20181018
Beta Release Date: 2018-10-18
Created 2018-10-19
Last Updated 2019-07-23

The Instructions
We have moved the instructions to be a part of our docs site
For the main instructions to get going with Bliss OS, you can check out our Installation Guide
If you get into a bind with your install, you should see our Troubleshooting section
For the few addons and other info we have for Bliss OS installs, you can check out our Extras section
And if you're ready to start building and testing new things, you can check out the Bliss OS Build Guide.
Thanks, and keep scrolling for FAQ & Updates

Build Types Explained:
Q: Bliss builds come with funny names. Why?
A: Because we felt the need to include the various branches for Kernel, Mesa, & Firmware in the build name.
So, when you see a name like this:
Bliss-v11.1-Beta-x86_64-OFFICIAL-20181018-1457_kernel-4.9_m18.3.0-devel_w40_LLVM70_dev-kernel.org.iso
It can be broken into 3-4 parts.
Build ID: "Bliss-v11.1-Beta-x86_64-OFFICIAL-20181018-1457"
Kernel Branch: "_kernel-4.9"
Mesa Branch: "_m18.3.0-devel_w40_LLVM70"
Firmware Branch: "_dev-kernel.org"
Q: What do the parts of the kernel names mean?
A: When we add a batch of commits to the kernels, we like to save that version with an identifier. So the most common parts to the kernel names are as follows:
-ax86 : Means that this kernel started off from the Android-x86 repo, or has the majority of Chih Wei's commits for that kernel
-ma : Means this started out from Maurossi's repo. (https://github.com/maurossi/linux)
-gal : Means that this kernel also includes compatibility with Chromebook devices, from the peeps at Gallium OS (https://github.com/GalliumOS/linux)
-ipts : Means that we are including some specific commits for the Intel IPTS touchscreens (mostly in the Surface line of devices) These builds likely won't run well on most other devices.
Q: OK, So I have a BlahBlah CPU, with a Such'n'such GPU, what builds are right for me?
A: Well, we have a method to all our madness there. We build Bliss OS with different kernels that work as a way to make it more compatible with different types of devices. Here is the breakdown on those:
Kernel-4.9 These are considered the most "Stable" builds, they will work across most older and recent devices.
Kernel-4.12-14 builds will be hard to come by, but seem to work great for some newer Atom based devices.
Kernel 4.15+ builds will not work on some older devices, so consider these to be a little less "All-In-One"
Kernel 4.18+ Intended for newer devices. adds some newer touchscreen support and added AMDGPU support
kernel 4.19+ Intended for newer devices. Even more touchscreen support and ACPI support
Kernel 4.20+ Intended for newer devices. Even more touchscreen support and added ARM/ATOM support and Vega GPU support
Kernel 5.0+ This is where things will start getting tricky. Even more touchscreen support, and added support for ARM/ARM64/ATOM etc, but also a ton of Android kernel commits start making their way into things.
For all other FAQ's, please check the Wiki or our Telegram Chat
Recent Update Posts:
Updates, Round 1 - 2018.10.28
https://forum.xda-developers.com/showpost.php?p=77999419&postcount=55
Updates, Round 2 - 2018.11.07
https://forum.xda-developers.com/showpost.php?p=78092995&postcount=112
Forgotten Kernel-4.18 build - 2018.11.01
https://forum.xda-developers.com/showpost.php?p=78287782&postcount=175
Christmas Build - 2018.12.25
https://forum.xda-developers.com/showpost.php?p=78287782&postcount=238
Fist Release of 2019!! - 2019.01.16
https://forum.xda-developers.com/showpost.php?p=78691527&postcount=337
Second Release of 2019!! - 2019.01.21
https://forum.xda-developers.com/showpost.php?p=78730287&postcount=363
Updates to kernel-4.20 - 2019.01.26
https://forum.xda-developers.com/showpost.php?p=78768409&postcount=378
Surface IPTS build updates - 2019.01.30
https://forum.xda-developers.com/showpost.php?p=78796749&postcount=396
Update for Bliss OS - 2019.02.05
https://forum.xda-developers.com/showpost.php?p=78841065&postcount=412
Bliss OS Updates - 2019.02.23
https://forum.xda-developers.com/showpost.php?p=78973810&postcount=500
Bliss OS Updates - 2019.03.10
https://forum.xda-developers.com/showpost.php?p=79083283&postcount=549
Bliss OS 11.6 Updates - 2019.03.24
https://forum.xda-developers.com/showpost.php?p=79188758&postcount=576
Bliss OS 11.7 Updates - 2019.04.03
https://forum.xda-developers.com/showpost.php?p=79265706&postcount=616
Bliss OS 11.8 Updates (with GMS) - 2019.04.23
https://forum.xda-developers.com/showpost.php?p=79397531&postcount=676
Bliss OS 11.9 Release (with GMS) - 2019.05.26
https://forum.xda-developers.com/showpost.php?p=79607423&postcount=827
Bliss OS 11.9 (with GMS) -EXPERIMENTAL x86 (32 bit) builds - Build Date 2019-08-01
https://forum.xda-developers.com/showpost.php?p=80044597&postcount=1039
Bliss OS 11.10 x86_64 Generic Vulkan Build - EXPERIMENTAL - Build Date 2019-09-01
https://forum.xda-developers.com/showpost.php?p=80172193&postcount=1130
Announcement - Community Builds
https://forum.xda-developers.com/showpost.php?p=80672909&postcount=1268
Bliss OS 11.10 x86_64 Generic & IPTS Builds - With Vulkan - Build Date 2019-12-14/15
https://forum.xda-developers.com/showpost.php?p=81209911&postcount=1396
Bliss OS 11.10 x86_64 Generic - With Vulkan - Build Date 2020-04-11
https://forum.xda-developers.com/showpost.php?p=82275141&postcount=1675
Bliss OS 11.11 x86_64 Generic - With Vulkan and other graphics options - Build Date 2020-06-24
https://forum.xda-developers.com/showpost.php?p=82967929&postcount=1796
Bliss OS 11.11 x86_64 Generic - Kernel 4.19.122 - Build Date 2020-08-03
https://forum.xda-developers.com/showpost.php?p=83214267&postcount=1841
Bliss OS 11.12 x86_64 Generic - Kernel 4.19.122 - Build Date 2020-09-25
https://forum.xda-developers.com/showpost.php?p=83661769&postcount=1916
Bliss OS 11.12/13 x86_64 Generic - Kernel 4.19.122/5.8 - Mesa-19.3.5/20.1.0 - Release Date 2020-11-14
https://forum.xda-developers.com/showpost.php?p=83919621&postcount=1947
Bliss OS 11.14 x86_64 Generic - Kernel 4.19.122/5.10 - Mesa-19.3.5/20.1.10 - Release Date 2021-05-09
Bliss OS - Pie for PCs (LTS)
team bliss is pleased to present to you bliss rom based on Android 9 Pie Our focus is to bring the Open Source community a quality OS that can run on all your devices as a daily driver, syncing your apps + settings + customizations across all...
forum.xda-developers.com
Downloads
Downloads has been moved for now. Please use the latest link from our website:
http://blissos.org
or
http://blissroms-x86.github.io

Contributing to the project
Bliss OS is in need of contributors. People to help squash some bugs, forward port features and support, and others to help with answering the common questions here in the XDA threads, or on our Telegram chat.
Pull requests are going to be spread out a little. All the commits for the build script will go through http://review.blissroms.com While everything else will have to be in the form of pull requests from https://github.com/BlissRoms-x86 or https://github.com/Android-PC
For anyone interested in joining our team, please visit the Bliss Family page of our site for more information on how to do that
https://blissroms.com/bfor.html
For those with even a little experience, but a lot of drive to learn more, we also offer our services to help people learn the ropes. https://t.me/Team_Bliss_Build_Support
Or for those a little more committed, look into the Bliss Family page of our site and join from there.

Ok, I will be the first to ask, is the ipts thingy compiled on this starting version? Would this be suficient to make it work on a surface? Thanks!

AllanJacques said:
Ok, I will be the first to ask, is the ipts thingy compiled on this starting version? Would this be suficient to make it work on a surface? Thanks!
Click to expand...
Click to collapse
I have another kernel I have working for IPTS on the Surface devices. I will make sure to post a build with that soon

Great work. Almost everything works flawlessly but the wi-fi. It turns on but it isn't able to connect to any network.
Device is HP Pavilion X2 10.
I'll try to get the logs when I have more free time.
EDIT: a little more insight before I get the logs. The Wi-Fi will turn on, as I said, and it will see all the available networks. But when you connect one, it'll just try connecting until it shows the "Disabled" status under the network name.
EDIT2: the chipset is an Intel 3165.

Does not work on Asus t101ha (cherrytrail)

wenna.speedy said:
Does not work on Asus t101ha (cherrytrail)
Click to expand...
Click to collapse
Did you try the old modprobe method? Any of the kernel command line options from Grub? Anything??? With the amount of warnings I put in the OP, I would expect a little more info than what was provided.

vEEGAZ said:
Great work. Almost everything works flawlessly but the wi-fi. It turns on but it isn't able to connect to any network.
Device is HP Pavilion X2 10.
I'll try to get the logs when I have more free time.
EDIT: a little more insight before I get the logs. The Wi-Fi will turn on, as I said, and it will see all the available networks. But when you connect one, it'll just try connecting until it shows the "Disabled" status under the network name.
EDIT2: the chipset is an Intel 3165.
Click to expand...
Click to collapse
Also for your case, can you try booting up with the old modprobe method mentioned in the second post? It may handle that wifi chipset a bit differently.
Another thing to try is to disable and then re-enable wifi service:
$ su
$ svc wifi disable && svc wifi enable

electrikjesus said:
I have another kernel I have working for IPTS on the Surface devices. I will make sure to post a build with that soon
Click to expand...
Click to collapse
I'm not asking for an ETA but do you think it will be a long time until it comes?
Sent from my Pixel XL using Tapatalk

AllanJacques said:
I'm not asking for an ETA but do you think it will be a long time until it comes?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Instead, how about I tell you about this update Microsoft pushed to the surface book that made it to where I can't test my IPTS, or any kernel currently...
So to help with quality assurance, I would rather wait until I can test a build to make sure it works as expected before passing it off to the public.

Hello. I tried to boot by using USB live cd and it worked great on Nitro 5 spin.
Touchscreen, rotation, bluetooth are working.
Wifi sometimes doesn't turn on like oreo version.
But when I tried to boot on ssd using easy install, it didn't boot and boot screen was yellow instead of blue.
It seem to be a mounting issue.

mickey36736 said:
Hello. I tried to boot by using USB live cd and it worked great on Nitro 5 spin.
Touchscreen, rotation, bluetooth are working.
Wifi sometimes doesn't turn on like oreo version.
But when I tried to boot on ssd using easy install, it didn't boot and boot screen was yellow instead of blue.
It seem to be a mounting issue.
Click to expand...
Click to collapse
You got that result when using the easy installer? Did you try using the bootable USB install?

electrikjesus said:
Did you try the old modprobe method? Any of the kernel command line options from Grub? Anything??? With the amount of warnings I put in the OP, I would expect a little more info than what was provided.
Click to expand...
Click to collapse
I tried all boot options - stucked on boot everytime.

electrikjesus said:
You got that result when using the easy installer? Did you try using the bootable USB install?
Click to expand...
Click to collapse
Yes, I tried all boot options. Stuck at boot screen and there is some screen tearing too.
When I use debug parameter, it show mounting issue and it stuck there.
I didn't try USB install yet. But will report back when I have time.

mickey36736 said:
Yes, I tried all boot options. Stuck at boot screen and there is some screen tearing too.
When I use debug parameter, it show mounting issue and it stuck there.
I didn't try USB install yet. But will report back when I have time.
Click to expand...
Click to collapse
The symptoms suggest that some of your hardware isn't being detected right on install

Surface pro 2017 touch screen
I tried all versions of this rom including this latest Android pie. Still No touch screen functionality for Microsoft surface pro 2017. Please how do i manually update the drivers or fix this issue? Will really appreciate any help. Thanks

Eljay227 said:
I tried all versions of this rom including this latest Android pie. Still No touch screen functionality for Microsoft surface pro 2017. Please how do i manually update the drivers or fix this issue? Will really appreciate any help. Thanks
Click to expand...
Click to collapse
I'm just gonna ignore this and ask you to read the OP again, but slower

Eljay227 said:
I tried all versions of this rom including this latest Android pie. Still No touch screen functionality for Microsoft surface pro 2017. Please how do i manually update the drivers or fix this issue? Will really appreciate any help. Thanks
Click to expand...
Click to collapse
You shall wait until we release a build that supports your ipts display, and then rejoice!
Pie is "beta preview" and we build BlissOS to run on 1000's of potential HW configurations. Then we test with the devices we possess. When deemed ready, we share. A build which supports your device specific issue: not ready yet.
The info you requested to do this manually can be found using the search function of XDA(visit the website instead of app and look in a thread for "search this thread" then type: manual driver
.....or just read the OP ?