yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] evronetwork:
I avoid doing a full wipe(it's bit pain in the a$$ for my other stuff and no I don't like google synch my data) :p last time I did a clean flash was with the 18/12/16 rom which I currently use
[ONE Original Android Development] fmc000:
There is no need to perform a full wipe, I'm just talking about wiping data for the Phone app, not the whole phone. Settings/App/Phone , select the first option from the top and then wipe data.

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] evronetwork:
Well [MENTION=4435460]NoSpamDan[/MENTION] said it properly I guess :p thats what I did and now I'm good - thx anyway, I was seeing wipe data, wipe data and I was ...why do full wipe? :p
[ONE Original Android Development] NoSpamDan:
I found there is still something off as it's supposed to now work with the recovery no-kexec patch option enabled. If the Primary has the kexec patch, then it seems to work fine. I haven't had time to dig into why, but maybe [MENTION=2605798]nkk71[/MENTION] can enlighten us... The MultiROM thread is here.
[ONE Original Android Development] arh2o:
To get AdAway working on Nougat ROMs you need the November 19 version: https://www.androidfilehost.com/?fid=313042859668275788. Here's the corresponding thread: https://xdaforums.com/showthread.php?t=2190753
[ONE Original Android Development] nkk71:
I dont have the device, so dont follow the developments here. Maybe you can give me a small summary of what works and what doesn't?

Also, don't rely on the MultiROM Manager app, since it's just a "front end" for the deeper work done by the MultiROM-TWRP and MultiROM itself.

So things of interest would be:

1- Which builds are you running? (twrp, multirom, and the app if you're using it)

2- Do the [problematic] ROMs flash properly to secondary?

3- If yes, what exactly happens when booting the secondary ROM? where does it get stuck, does it bootloop or just hang on splash, or bootanim

4- Do the working secondary ROMs stay working fine, or are they affected in any way.

5- You mention it works with kexec-hb but not with no-kexec, what happens exactly.

Probably recovery.log(s) and kernel logging could shed some light on it.
[ONE Original Android Development] sozofriend1234:
Got that working with the new version mate. Thanks. However, still getting system read only error in many apps. Even after flashing the new version of SU.
[ONE Original Android Development] mustang_ssc:
1- Using MultiROM 3.0.2-0 (2016-12-12 p1) compiled by [MENTION=4435460]NoSpamDan[/MENTION]. Post of his download link here. App version is the latest one from the play store (V.1.88), but i just use it sometimes for switch between roms and change the icon, and the ROM is the official Resurrection Remix 5.8.0 (compiled 2016-12-25).

2- Supposedly they do, as no error message is displayed when the ROM is installed, and the flashed ROM is compatible with MultiROM installation. Example with the latest Slim7 build by [MENTION=4435460]NoSpamDan[/MENTION] : http://i.imgur.com/bQ9Urao.png

3- It simply doesn't boot. It keeps in the bootloader (?) screen (OnePlus logo) without any response, even after waiting more than 5 minutes.

4- The other secondaries ROMs i have already installed (NitrogenOS 7.1.1, Unofficial LineageOS and Sultan's CM13) works without problems before and after flashing any other secondary (or even primary) ROM, counting as well the ROMs which doesn't boot. I don't know about other minor issues like dev. options FCing.

5- About this maybe i didn't explained it well. The secondaries which boot (for example Sultan's CM13) they boot with kexec-hb mode if the kernel has it (tested with RR kernel and Boeffla kernel) or without it if the kernel doesn't have it (tested with Private Kernel) and if the "No-KEXEC workaround" option located in MultiROM menu/Settings is automatically enabled in the case the kernel doesn't support it ("Use no-kexec only when needed" option).

Here it is the recovery.log after the commented problem happens, and not sure if this is the kernel log. Hope it can help.
[ONE Original Android Development] Claudiosvs:
Any chance of integrating Sultan's HAL? Someone ported it to AOSP 7.1: https://github.com/AOSPlusone
[ONE Original Android Development] NoSpamDan:
Which HAL?
[ONE Original Android Development] Claudiosvs:
Sorry, forget to specify the camera HAL + Oxygen blobs.
[ONE Original Android Development] hammer-is:
Not just someone but [MENTION=4986658]freshgiammi[/MENTION] https://xdaforums.com/oneplus-one/development/rom-aosplusone-7-0-t3478326

It seems a lot of effort went into making this work (I'm looking at the github commits). But yes I agree it would be nice to have Sultans HAL as part of Slim7 if it's doable.
[ONE Original Android Development] NoSpamDan:
It is a lot of effort, not just now but with future updates. Do these require his display and media HALs? I think it also removed the ability to flash a custom kernel as well

I started Slim 6 for bacon on his kernel and blobs, but ended up switching to CM since things like Ambient display were not working without custom HAL hacks.

I'm not saying I'll never look at this but right now I'm working on custom ROM features, and don't need any device problems in the meantime.

What is so great about the color OS blobs? I've been using Open Camera and I'm very pleased with it, and Snap camera (which ships with the ROM) has a slow frame rate options, if that's what you're into... :)
[ONE Original Android Development] NoSpamDan:
You aren't, by chance, running F2FS in the ROMs that won't boot, are you?
[ONE Original Android Development] mustang_ssc:
Nope, everything is EXT4, i forgot to mention that :p.

Even if i did that i think that some ROMs i flashed as secondary (like Tugapower's CM14.1) should have booted because they're compatible with F2FS, unless the MultiROM recovery isn't working with that file system.
[ONE Original Android Development] freshgiammi:
They probably require my media/display HAL, yes. Haven't tested AOSP since i've trashed it from the start. CAF repos work better, and without changes. IDK that part about Ambient display.. it works perfectly on my side! Also, if you're using CM's "cm-14.1-caf-8974" branch.. well, we're using the same. Except mine is updated.

And yes, you can't flash custom kernels unless they have the same CAF Camera Drivers. (speaking as an ex kernel dev, it wouldn't be such of a great issue to push two build that differ only in the camera drivers, but that's depending entirely on the dev's will).

ColorOS blobs are great too! The only reason i chose Sultan's over them is the fact that I can update the HAL and try to make it working with nougat's mediaserver/cameraserver division.

But still, yes. Every camera blob that's not from CM is good.
[ONE Original Android Development] nkk71:
Nice, a clear, descriptive, concise reply :good::good: :good::good:

Can you enable "Advanced kernel logging" (in TWRP -> MultiROM section -> Settings -> checkmark the logging),

then try to boot the non-working rom twice, when it hangs:

* reboot system (so back to ROM selection)

* do not power off

* -> otherwise the logs will be gone

finally boot back up to primary ROM, and you should have an /sdcard/multirom-klogs folder, zip that up and upload it for me whenever you get a chance
[ONE Original Android Development] dragsterman:
What did you mean with "slow frame rate options"?

My biggest problem with CM camera blobs that in low-lighting condition the viewfinder has a very laggy frame-rate which cause poor experience.

Do you have maybe a solution for this? (Sultan has, but his modification for the low framerate viewfinder doesn't work with CM blobs)
[ONE Original Android Development] hammer-is:
Have you tried sultans "fix" on Slim7?

I'm shure I've tested it on my own LineageOS build (13.1 or 14 - can't remember as I build both edtions the same evening) by doing this:

cp -v $source/vendor/oneplus/bacon/proprietary/vendor/lib/libchromatix_imx214_default_video.so $source/vendor/oneplus/bacon/proprietary/vendor/lib/libchromatix_imx214_preview.so

before building - and it worked perfect (giving faster preview under low lighting conditions). (I'm not running Slim7 so I can't test it myself)
[ONE Original Android Development] dragsterman:
I have tried this on RR 7.1.1. but I have just made a copy of the libchromatix_imx214_default_video.so renamed it to libchromatix_imx214_preview.so and overwrite it with Root Browser. I did not want to mess with ROM building, but my method does the same. Am I right?

After this I rebooted the ROM but after all camera apps show a black viewfinder.
[ONE Original Android Development] hammer-is:
Yes your method should give the same result as copying before building. Are you sure the "permissions" are set correctly on the copied file?
[ONE Original Android Development] dragsterman:
Thanks bro the permission was the problem. In recovery I give a "644" permission to the file and now I have a smooth viewfinder. :good: :good: :good:
[ONE Original Android Development] NoSpamDan:
Have you tried this on Slim7?
[ONE Original Android Development] Genericxx:
Regarding HAL and blobs:

In terms of Picture Quality in good and bad light conditions: OPPO/ColorOS -> SultanXDA -> CM

In terms of Features: SultanXDA -> ColorOS -> CM

Personally i was happy with jgcaap's implementation of ColorOS Camera Stuff until his Marshmallow Builds came to an end. After this i was truely eager to drive on the Nougat train and i must confess that i'm used to it and won't go back to MM. The Downside of the current Nogat roms for our OPO is, that qualcomm dropped the support for the SD resulting in even more effort to implement custom camera blobs without breaking other things. That camera thingy was always something that i was addicted to but also have to say that i got tired of hunting for roms which suit my personal taste "and" are built with ColorOS blobs or Sultan's ones. So overall i concluded with it, driving a rom which is stable and reliable and neglected the used camera hal. I simply ended up by buying myself a badass DSLR last month to work around that Blob and HAL stuff :silly:
[ONE Original Android Development] dragsterman:
No, I haven't.

I think it should work on Slim7 too, because as far as I know it also has CM camera blobs, and HAL so it has the same "camera " files as RR has.
[ONE Original Android Development] mustang_ssc:
Thanks for your words, just trying to be as helpful as i can :).

After follow your indications i'm not sure if i did this steps propertly: " reboot system (so back to ROM selection)" and "* do not power off"

After enable Advanced kernel logging box and boot twice times the non-working rom i always had to manually reboot the device with the power button because it kept without doing anything in the OnePlus logo, so i'm not sure if you said me to do this or to let the device reboot by itselft (thing that doesn't do).

Any way, after that i booted my primary rom and found the multirom-klogs folder with the txt logs have been created. Here it is the link, but not sure if the logs contain all the records they should have.

In case you need anything else just tell me :good:
[ONE Original Android Development] nkk71:
It's nice when someone answers with a productive post, as opposed to the "it doesn't work" post ;)

So my thanks to you :good:

Logs show a very very old version of no-kexec in there (didn't check exactly how old), but which would leave me to believe that a lot of other commits needed for 7.x are not in there as well.

So from a very brief look, something outdated is in there, that should not be.

[MENTION=4435460]NoSpamDan[/MENTION] would need to check further why there is a pre NO_KEXEC 4.1 in there.

Not that the no-kexec really matters, it just showed me, that the multirom being used is outdated. (including the possible restorecon issue for 7.x roms)
[ONE Original Android Development] dragsterman:
Do you think my problem also could be because the multirom being used is outdated?

Here is my problem what I also wrote in MultiROM thread:

So as I wrote have Sultan's CM13 on primary and No-kexec patch enabled and RR 7.1.1 Nougat on secondary and sometimes (for example if I flash an update to the secondary, or modify some system setting) I can not boot the primary it goes straight to the recovery and the recovery log says: "MultiROM NO_KEXEC: ERROR: couldn't find real primary to restore"
[ONE Original Android Development] musklor:
Use efidroid instead, if you want.
[ONE Original Android Development] fmc000:
Clarification.

[MENTION=4435460]NoSpamDan[/MENTION] : the thread title has been updated to 7.1.1_r13 but the download section still shows the 20170104 release, so I have a few questions if you don't mind :o :

Where can we download the new release?

Is the new Alpha7 completely synced with your builds now?

The Alpha7 changelog shows some updates to sepolicy: does this mean that Selinux is in enforcing mode?

If the answer is no, do you have a _r13 build with Selinux enforced working?
[ONE Original Android Development] :
Alpha 7 is still on Permissive.
[ONE Original Android Development] nkk71:
No idea, but if you want to manually update secondary ROMs boot.img with the "current" version of MultiROM you have installed, you can do it as follows:

1- boot into TWRP

2- mount /data if it's not mounted already (in the Mount menu)

3- open a shell, and run the command:

adb shell

find /data/media/*/multirom*/ -name boot.img -print -exec "/data/media/0/multirom/trampoline" --inject="{}" --mrom_dir="/data/media/0/multirom" -f \;
[ONE Original Android Development] NoSpamDan:
No problem. See my answers below with " *** " in front of them:

Where can we download the new release?

*** Nowhere... yet. I was updating the thread based on current source level...

Is the new Alpha7 completely synced with your builds now?

*** Nope... I have pushed OMS commits and am building Masquerade too, to test OMS themes. Don't expect Slim to include Masquerade, as we have identified security issues. You also need root to use it. We are planning our own theming engine that should work with CMTE or OMS themes, but don't expect that any time soon either. No ETAs... :p

The Alpha7 changelog shows some updates to sepolicy: does this mean that Selinux is in enforcing mode?

*** Nope. It means I pushed updates to fix some denials for testing. I have an enforcing change waiting for confirmation that all is working before I merge it. I plan for the next DEV-DM build I post to be in enforcing mode.

If the answer is no, do you have a _r13 build with Selinux enforced working?

*** I actually have an 0.6 build I'm testing. I think the Jan 5 security updates bumped to r13, so not necessarily a 0.7 build... It's crazy because there have been a few parallel things happening, one of which is a renaming of some internal Slim framework stuff and also some consolidation/simplification. So things happen like my last build having no SOG menu, and such. Time has been tight, but I'm trying to get a build up for sharing/testing with Enforcing.

I appreciate the patience.

Yes, the Alpha is still Permissive. ;)
[ONE Original Android Development] fmc000:
And we all appreciate your work.
[ONE Original Android Development] Zeus20:
True that to spamdan
[ONE Original Android Development] o0vampire0o:
great job [MENTION=4435460]NoSpamDan[/MENTION], i still use your candysix for the great sultanxda camera. If in the future you will merge sultan blobs here i'll switch to the really good slim 7 :). No eta ^_^ i can wait :)
[ONE Original Android Development] jbrukardt:
Having trouble with low mic volume in calls, and cutting in and out with this one [MENTION=4435460]NoSpamDan[/MENTION] I also get this with almost all the other 7.1.1s unfortunately, but the one rom that DOES work is your previous 7.0 alpha rom.
[ONE Original Android Development] Chris.C:
I found the below tip I'm sure in a earlier post in this thread

This works for me

For those who suffer from the microphone issue.

Open the /system/build.prop file using your Text Editor.

Change

ro.qc.sdk.audio.fluencetype=fluence

to

ro.qc.sdk.audio.fluencetype=none

Then, edit /system/etc/audio_platform_info.xml

<device*name="SND_DEVICE_IN_HANDSET_MIC" acdb_id="40" />

to

<device name="SND_DEVICE_IN_HANDSET_MIC" acdb_id="4" />

Reboot.

Another tip that works that is if you want the Pixel Google Assistant

Open the /system/build.prop file using your Text Editor.

Find the line that reads ro.product.model=[YOUR DEVICE] and replace it with the following:

ro.product.model=Pixel XL

Then add the following on its own line:

ro.opa.eligible_device=true

Reboot
[ONE Original Android Development] NoSpamDan:
Can't really comment on the fluence/in-call audio, at the moment. Mine has been fine, although the speakerphone volume seems a bit low...

So, for those who have been waiting, thanks for the patience. The below build has some goodies for you, such as SELinux set to Enforcing, and I've added some theme support: OMS.

Yes, OMS support is present, as well as the Masquerade app is compiled in

as a test

. I will not guarantee I will continue to include it going forward, so make your nandroids. This version is tagged 0.6 but is my own DEV-DM build, based on r13, so you should be able to dirty flash on top of the 0.7 Alpha. Regardless, make your nandroid backups, as it's cheap insurance!

Notes on using the baked-in OMS theme support:

You need to root/flash SuperSU or some root app in order to use Masquerade, and grant root permissions when asked.

You will need to install the Substratum app for now (until we/Slim decide what we're doing for an interface, that will hopefully not require rooting).

There have been security risks identified with Masquerade, and you should know that a malicious themer or other third-party app or script can use it to uninstall user apps. This is mostly an FYI, and not intended to scare anyone. It is the truth.

If you decide to root and/or theme, you do so entirely at your own risk! I will not be responsible for any issues/errors related to this, nor shall the SlimROMs team.

The OMS support is a WIP and you may find screens that are not themed properly. Feel free to report them, but don't expect them to be fixed right away.

You don't have to theme anything if you don't want to. It's your choice. :good:

HAVE FUN!

Here's the build:

Slim-bacon-7.1.1.build.0.6-DEV-DM-20170114-1419.zip

Cheers!
[ONE Original Android Development] Younex:
What camera/ROM are you using ?

I've been experiencing very bad camera performance no matter what camera app I use, and I'm looking for something better. I'd appreciate if you could redirect me to some threads.
[ONE Original Android Development] fmc000:
OMS works fine, I tested with InversionUI without issues. The only "problem" is that it seems Slim lacks the commit(s) that enable the Substratum app integration within Settings.

Edit: it seems that the OMS font framework is missing too.
[ONE Original Android Development] o0vampire0o:
on candysix i use stock camera, sultanxda's one.
[ONE Original Android Development] NoSpamDan:
Well, I wouldn't expect to see Substratum in the Settings for the time being... it's in a testing phase right now. We are discussing ways to do it that minimize or eliminate the security issues.

As for fonts, can you be more specific please? Maybe link to what you are mentioning?
[ONE Original Android Development] fmc000:
That's why I wrote the word "problem" within quotes. For the font problem, just download the TypaFace app, choose a font and generate the apk. Everything seems to work but nothing changes.

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] NoSpamDan:
LOL, copy that... For fonts, I've picked some commits, as well as for system sounds, and I'm building again to test. There are other things but I need to see where they go when I have time.
[ONE Original Android Development] NoSpamDan:
This test DEV-DM build should have the fonts layers fixed (FYI [MENTION=791219]fmc000[/MENTION]):

Slim-bacon-7.1.1.build.0.6-DEV-DM-20170115-1349.zip
[ONE Original Android Development] ppuskas:
Having an issue with google photos force quiting and gallery app showing zero photos. Awsome smooth rom btw.
[ONE Original Android Development] NoSpamDan:
Check the app permissions for those, and make sure they are all granted. What GApps did you use?
[ONE Original Android Development] ppuskas:
yep, no permissions were set for gallery app so we're good there. Photos still crashing. Using full dynamic GApps-7.1.x-20161215
[ONE Original Android Development] NoSpamDan:
I'd recommend nano or pico GApps. I normally install Open GApps nano myself without issues.
[ONE Original Android Development] fmc000:
It does. Many thanks.

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] Zeus20:
Just as a future future request, will the aosp night light come to slimrom. Not asking an eta, but a consideration.
[ONE Original Android Development] shantur:
Does anyone know if Android Pay works with this Rom?
[ONE Original Android Development] NoSpamDan:
Can you point me to a proper updated version of MultiROM please? I may have pulled the wrong branch in my builds... PM is fine too, or the bacon MR thread would probably be better.
[ONE Original Android Development] tye_time:
it doesn't unfortunately.
[ONE Original Android Development] NoSpamDan:
I don't use that, but you probably need to change your build prop from userdebug to user.
[ONE Original Android Development] gaja22:
No SMS app on the lastest build (15.01) ?
[ONE Original Android Development] Zeus20:
You need to install your own, read op
[ONE Original Android Development] suryachandranr:
Advanced reboot not working with the latest build.(selected always show from security)
[ONE Original Android Development] tofu:
encryption broken

Clean flashed latest build (formatted the device). Then chose screen pin, and tried encryption through settings--> privacy--> encryption. After some reboots, the device asks for a password, after which is says

"Decryption unsuccessful. The password you entered is correct, but unfortunately your data is corrupt".

EDIT: After reboot the password is suddenly accepted and rom boots fine. Hmm.

2. Though I found another issue: for some reason PHH's superuser works fine with other apps, but FasterGPS claims the device is not rooted. This works normally on NitrogenOS. What might be the cause?
[ONE Original Android Development] fmc000:
I just tried Long-Press-Power-Button -> Reboot -> Recovery and it worked just fine.

Edit: actually I have the opposite problem: it shows up even if I disable the option in Settings / Security and if i select "Show Always" it's still disabled when locked.
[ONE Original Android Development] NoSpamDan:
Fixed in my latest build... Want it? ?
[ONE Original Android Development] fmc000:
Yup ?

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] NoSpamDan:
OK this build should have the following fixed (and more). You can thank [MENTION=4527723]gmillz[/MENTION] for a lot of it...

Screen off gestures preferences theming, back button and sidebar menu action

Status bar battery settings (different appearances, % options)

Advanced reboot menu

Slim-bacon-7.1.1.build.0.7-DEV-DM-20170117-0555.zip

Have fun!

P.S. OMS theming is not 100% complete. There are some apps/screens that may be hard to read. Please feel free to report just the screens/menus that are ROM-RELATED, along with a screen shot if possible. Thanks.
[ONE Original Android Development] o0vampire0o:
[MENTION=4435460]NoSpamDan[/MENTION] will you add in the future the sultan camera hal? I use candysix and is awesome :(
[ONE Original Android Development] fmc000:
Settings / Security / Lock Screen / <enter you PIN > / Choose PIN again . Not only the background is not OMS themed, the color accent is wrong too. The font is themed, though. Maybe it happens only when you're encrypted?
[ONE Original Android Development] NoSpamDan:
Nah, mine does it too. Thanks.
[ONE Original Android Development] NoSpamDan:
[MENTION=4447997]evronetwork[/MENTION] can you check Greek translations in the latest builds please? Should have your work on Greek ported in there. Quite possibly some more to do, but see how it is.