yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] tiny4579:
I just completed a build and am flashing so I'll let you know if this helps.

EDIT:

Error: system partition has unexpected contents after OTA update both when wiping and not wiping system. Not sure why this happened. It didn't with the clang update.

Not sure what's going on here right now.

EDIT 2: Seems to flash now after wiping cache and system. I'm not sure everyone will need to do this but that's what I did.
[ONE Android Development] tilaksidduram:
Are u flashing in multirom, if so then u need to edit the updater script to remove a few lines from it. Refer to the OP for the details.
[ONE Android Development] tiny4579:
Nope, and I just edited my post after figuring it out. With all the times flashing updates, even with wiping system, I haven't run into that error before.
[ONE Android Development] tilaksidduram:
Just edit the updater script and try flashing again. Mostly it should work.
[ONE Android Development] katinatez:
Confirmed working, I got rid of all other commits, straight cm sync and picked this http://review.cyanogenmod.org/#/c/117928/ clobbered build, gives a stable daily, back to enforcing also

this is what I reverted on device

bacon: Build the BoringSSL compatibility wrapper

add permissive selinux

Working

CMFileManager

Camera & video (stock & Google camera)

Google sync (contacts)

On Tap hardware button

Titanium Backup

No storage error!

Flashed as primary on Philz recovery, on clean wipe , latest slim gapps, uploading now
[ONE Android Development] :
Please upload your build [emoji2]

Edit: downloading ... thx
[ONE Android Development] katinatez:
You could find my build in Android File Hosting/Experimental, I did a clean wipe to make sure everything was good. If you dirty flash and run into errors try wiping phone.

SuperSU is no longer needed

All my sources are already pushed to github for dev reference.

Enjoy :D
[ONE Android Development] :
Running great! SuperSu not needed is fine too.

Thx
[ONE Android Development] miguepereira77:
[MENTION=5291611]CraZY_BoY^[/MENTION] [MENTION=539770]tilaksidduram[/MENTION] [MENTION=4406894]vinman12[/MENTION] [MENTION=3814731]katinatez[/MENTION] Can u guys add this to your builds so we can use brand new 6.0 open gapps? Thanks in advance :good:

https://github.com/TeamExodus/frameworks_base/commit/9c36be651e83fb039a262682839bd920b033007a
[ONE Android Development] Karel VH:
http://review.cyanogenmod.org/#/c/116418/

That's the commit, haven't implemented it in my latest builds though.
[ONE Android Development] tiny4579:
The teamexodus one might be needed. The cm one bootlooped but only with opengapps.
[ONE Android Development] Karel VH:
I'll implement it in my build tomorrow. I'm gonna call it a day and get some sleep.
[ONE Android Development] matze222:
For me the Rom is not rooted and flashing su 2.50 is causing a bootloop. What can i do?
[ONE Android Development] ming3r:
Dev Options -> Root Access
[ONE Android Development] iRhyiku:
Clean flashing for me results in a bootloop, which GAPPS are everyone using for it?

I tried the slim gapps that was included in the folder
[ONE Android Development] Karel VH:
Did you flash SuperSU?
[ONE Android Development] iRhyiku:
Nope just ROM and GAPPS
[ONE Android Development] question.com:
I had the same issue. I flashed the slim gapps in the OP. works great. open gapps do not work
[ONE Android Development] tilaksidduram:
Good to know that the clang commit was the cause of the out of storage error. We are back to normal now, at least we can now use the rom.
[ONE Android Development] katinatez:
Hello everyone asking developers opinion here about the patch for gapps, actually there are a few.

Here is a reason why we need it and 2 commits

https://plus.google.com/u/0/+Seanhoyt/posts/GkdKpSDHQa4

And opengapps here posted earlier

https://github.com/TeamExodus/frameworks_base/commit/9c36be651e83fb039a262682839bd920b033007a

And an abandon one here

http://review.cyanogenmod.org/#/c/116418/

Any insight on which one to add, and why?
[ONE Android Development] FloorFox:
Hey your rom works with multirom?
[ONE Android Development] katinatez:
No, but multirom commits are in the kernel just flash a custom kernel for cm-13.0 or edit updater-script like everyone else is doing.
[ONE Android Development] FloorFox:
So i can flash with multirom after updater script changes on stock kernel too right?

Do you mind telling me what needs to be deleted in updater script?
[ONE Android Development] fards:
Looking at the cm comments, that commit is not needed.

Running pre-set permissions based on just name isn't a good idea anyway.

That's like saying anyone called bob can have access to your bank account.

The aosp commit should be in already, and the second commit on the g+ post is for the build script for generating gapps. Which i presume is on the open gapps release now?

So what isn't working ?

Edit: if its permissions then it would be better to have a start up script asking user permissions as part of the set up wizard.
[ONE Android Development] matze222:
I dont have mobile data connection on this rom. Only wifi works to access Internet.

Does anyone else have this Problem or does anyone know how to fix this?
[ONE Android Development] AcmE85:
Check the APN settings.
[ONE Android Development] matze222:
There are no apns in it and when i try to add an apn i get FC.
[ONE Android Development] AcmE85:
So you found the reason. Maybe you should consider a clean flash.

Adding an APN works fine on the latest build (06/11) on my device.
[ONE Android Development] pjgowtham:
I am on the 6/11 build

Dirty flashed it on the prev 5/11 build, it somehow erased gapps and only the rom with data booted. So i cleaned all partitions, flashed the rom and slim gapps and seperately restored data and it worked.

Its faster compared to the previous one

Open gapps aroma didnt even start for me on TWRP latest official

Camera works, Cm file manager works

Press and hold status bar icons to get into the related setting doesnt work

Mobile data gets disconnected frequently and no upload/download symbol indicators
[ONE Android Development] paarkhi:
[MENTION=3814731]katinatez[/MENTION]

Just a feedback (No complaining)

1. Settings crash when trying to change the Battery Charging light Colour

2. CM Native SuperUser works but doesn't remember the given Permissions, even though the checkbox is selected to Remember, the dialogbox for Deny, Allow.pops up again and again.

3. Mobile data doesn't appear even though I have a APN in the settings.

Binary cannot be updated on SuperSU 2.56 (New method in which /system partition is not touched).

After flashing SuperSU 2.52 (the old traditional method) the phone remains on the boot animation and doesn't boot any further.

Can you please make it compatible with SuperSU

Thanks for the build
[ONE Android Development] iRhyiku:
Go into developer options and enable superuser there, works fine.
[ONE Android Development] Karel VH:
Btw guys, added the commit from exodus to CM, but it still bootloops with OpenGapps.
[ONE Android Development] noahvt:
[MENTION=4406894]vinman12[/MENTION]

Can confirm that issue 1 also exists on your latest build: Trying to change the notifcation light color or battery light color causes settings to crash:

Seems like a missing icon...
[ONE Android Development] paarkhi:
Please read my post once again... I already said that Native SuperUser is working for me.
[ONE Android Development] suaverc118:
Yes flashing SU 2.52 causes a boot loop and would love to be able to flash SU of we choose to.
[ONE Android Development] tiny4579:
It needs to be built with selinux permissive if you want that.
[ONE Android Development] paarkhi:
SElinux Permissive is good if possible and if it's not a lot of trouble for the ROM Developer.
[ONE Android Development] vinman12:
Building now been busy.
[ONE Android Development] question.com:
where do you post your builds? the link the op has is only 10/29

edit, found your android file host page. downloading now.
[ONE Android Development] vinman12:
New build https://www.androidfilehost.com/?fid=24269982086990176

---------- Post added at 10:00 AM ---------- Previous post was at 09:59 AM ----------

Should fix Facebook.

Anyways fresh synced and built.

Has my added init.d support, and adb support.
[ONE Android Development] geekynoob:
Dear Mr epic.. Thanks for the build.. I guess all works.. No low storage error and upto date commits..???
[ONE Android Development] vinman12:
Lol, I have not tested yet, lol so you tell me.

I hope its fixed...
[ONE Android Development] geekynoob:
Downloading sir..!
[ONE Android Development] vinman12:
Its set to permissive also
[ONE Android Development] paarkhi:
It'd be very helpful if you post here your findings after flashing the Vinman's latest ROM because I'm on slow Metered connection and cannot afford to download all the builds

1. Titanium Backup restore works?

2. Google Contact Sync?

3. SuperSU working?

Thanks
[ONE Android Development] question.com:
just finished flashing it from a clean wipe. all good. i enabled the on screen buttons. how do I get to now on tap?

---------- Post added at 10:31 AM ---------- Previous post was at 10:28 AM ----------

I never use titanium, so cant test

contact sync is working fine

I use the system SU, so cant test
[ONE Android Development] vinman12:
Su works I use it plus I made permissive, tibu is fine I use it, contacts are fine, no more fc on changing notification led colors Facebook should work
[ONE Android Development] kingfiras:
Thanks vinman and the team for the great work .. I was wondering if we can dirty flash from 1105 to this 1107 build .. When I tried with different builds few days ago I got all kinds of errors .. But hoping we are at a point we can do dirty flash .. Thanks :)
[ONE Android Development] question.com:
onyl thing I cant figure out is how to get ontap working with the on screen buttons. works fine when I use the hardware buttons.
[ONE Android Development] itslels:
Be careful applying themes in Vin's latest build (11/7). The one I applied caused constant system UI FC.
[ONE Android Development] suaverc118:
That happened to my with katinatez build yesterday. I think the more themed the theme is the more it will cause a system ui crash.
[ONE Android Development] iRhyiku:
Does open gaps work on the latest build?
[ONE Android Development] :
[MENTION=3814731]katinatez[/MENTION]

A new build of yours is uploaded a couple of minutes ago, any specialities merged?
[ONE Android Development] katinatez:
Permissive

Advanced reboot in Developers

SuperSu in Settings if you flash v2.52

Fresh sync

V2.56 need commits in kernel, and have not touched the kernel yet.
[ONE Android Development] Lord*Andre:
I have done a dirty flash from 1105 to 1107 and everything is working perfectly. Just flash new build, gapps (im using gapps-mm-mini) and wipe dalvik and cache.
[ONE Android Development] nicholaschum:
Will push a CM13-ready Dark Material theme in a few minutes once [MENTION=3814731]katinatez[/MENTION] reports back on my test build (soon)
[ONE Android Development] suaverc118:
Latest [MENTION=3814731]katinatez[/MENTION] build, on tap doesn't work. Long press home and nothing happens

Edit:: it works, took a while to work.
[ONE Android Development] katinatez:
Themes work or at least [MENTION=3605033]nicholaschum[/MENTION] running todays build cm-13.0 Nov 7

theme devs need to update theme .apk
[ONE Android Development] nicholaschum:
Alright, confirmed, CM13-ready Dark Material has been confirmed, thanks A LOT to [MENTION=3814731]katinatez[/MENTION]!

Link to download is here: https://www.androidfilehost.com/?fid=24269982086990502

Any other problems, please tell me. Hopefully can assure me that the Do Not Disturb tile looks great :)

Changelog from official build is in my community, click my team banner to be linked there.

TO THEMERS:

The problem here is if you try to use the NON-SCALABLE notification background header, the one where it expands when you expand your notification background. There is an issue with the Java calling a preset drawable format, which is RippleDrawable, and when it detects you using a BitmapDrawable, it will cause an error. Thus, you must use a RippleDrawable, shown below.

You cannot use this:

<?xml version="1.0" encoding="utf-8"?>
<bitmap xmlns:android="http://schemas.android.com/apk/res/android" android:gravity="top" android:src="@drawable/shaded_stones" />

YOU MUST USE THIS:

<?xml version="1.0" encoding="utf-8"?>
<ripple android:color="@*common:color/theme_color_ripple_dark"
xmlns:android="http://schemas.android.com/apk/res/android">
<item android:drawable="@drawable/shaded_stones" />
</ripple>
[ONE Android Development] suaverc118:
Will you post this for other themers as well? Great job fellas! Sorry I couldn't do more, had a birthday party and sick infant now.
[ONE Android Development] nicholaschum:
You can link that to other themers if they have a broken mm6.0 theme.
[ONE Android Development] Floyd_Flivercod:
Curious question: I just tried to compile myself tonight. I get a successful build - "Package Complete: cm-13.0-20151107-UNOFFICIAL-bacon.zip" but when I try to flash it I get stuck on the boot splash screen. Am I missing something simple? I hate to ask this in your ROMs thread, but I'm scratching my head trying to figure out why it sticks when I flash.
[ONE Android Development] suaverc118:
Did you wipe cache and dalvik after? Just throwing something out there
[ONE Android Development] Floyd_Flivercod:
Yes. I don't think the boot.img or radio is compiling even though there are no errors maybe?
[ONE Android Development] tiny4579:
Radio is shipped separately and only available with official builds like nightlies.

If bootanimation loads at all, boot.img is working.
[ONE Android Development] paarkhi:
[MENTION=4406894]vinman12[/MENTION], [MENTION=3814731]katinatez[/MENTION],

Just a feedback, may not be a bug

No Up and down data transfer arrows in the statusbar, but ofcourse the data traffic works (Mobile and WiFi)

Thanks to both of you for tag teaming and squashing the bugs and providing us with CM13 (unofficially:) )
[ONE Android Development] tiny4579:
Open Gapps should work with tomorrow's open gapps. There was an issue with having duplicate Package Installers which was breaking the boot. I saw it committed today to their installer scripts. Tomorrow should include that fix.

If you want to use it now, you can flash 11/07 and manually remove /system/priv-app/PackageInstaller prior to rebooting.
[ONE Android Development] paarkhi:
[MENTION=3814731]katinatez[/MENTION], in your latest build Advance Reboot

Reboot to recovery shows the text "Factory Data reset" but boots to recovery and Factory Data is NOT reset, it's just the text you need to correct (cosmetic error)
[ONE Android Development] Spaulding89:
On [MENTION=4800121]Sultanxda[/MENTION]s Build it is the same.

Sent from Bacon with AK CAF Power
[ONE Android Development] kingfiras:
Thanks vinman .. For whatever reason that is not working for me .. I ended up with the same result I experienced in the past .. Zillion play services error .. Forcing me to go back to recovery and do a clean install .. Not sure I'd I am missing a step in the process .. But I flashed both the rom and gaaps
[ONE Android Development] katinatez:
Compiling again this should fix it

http://review.cyanogenmod.org/#/c/118278/
[ONE Android Development] Shiningbro:
Many Thanks [MENTION=4406894]vinman12[/MENTION] Build (11/7) works fine but i miss the Option to Change the Resolution (DPI). Is it Deleted or on a another place?
[ONE Android Development] AcmE85:
It just hasn't been merged by cm yet.
[ONE Android Development] Shiningbro:
okay thanks, i helped me with "texdroid".
[ONE Android Development] tiny4579:
While this will work in the interim it seems opengapps issue still hasn't been fixed with package installer. There is a pull request that once merged should most certainly address it. Next time I do a self build if it's not merged into the latest opengapps I can do an opengapps build to resolve it.
[ONE Android Development] AcmE85:
Is there any progress in dirty flashing without losing gapps or play services?

Even flashing the build + gapps does not help.
[ONE Android Development] fermasia:
[MENTION=3814731]katinatez[/MENTION] first of all thanks for building for us, and anyone else chipping in with builds or anything for the benefit of the community :good:

I'm trying to pinpoint cm13 kernel source for our device, but I'm not sure what's been pushed into github or what's missing. For instance, can I be sure that everything in here

https://github.com/katinatez/android_kernel_oneplus_msm8974/commits/cm-13.0

is exactly what's under the hood in your latest build?

Thanks.
[ONE Android Development] pa.pn2:
I don't know think so. Had to clean flash nearly any build now. That big **** isn't it?
[ONE Android Development] vinman12:
Been running around past few days, so not sure where we are at with commits, anything special I should no that is needed.
[ONE Android Development] vinman12:
ok well i just went ahead and synced and built so here ya go.

feedback please.

https://www.androidfilehost.com/?fid=24269982086991017

---------- Post added at 09:52 AM ---------- Previous post was at 09:39 AM ----------

sorry here is the build for multirom users.

https://www.androidfilehost.com/?fid=24269982086991042

---------- Post added at 10:06 AM ---------- Previous post was at 09:52 AM ----------

Built on 4.9 toolchain, recovery message fixed.
[ONE Android Development] tiny4579:
I think when opengapps are fixed they shouldn't have that problem. I dirrty flashed from gapps-mm-mini and Google play services are still there.

I'm not sure if they are automatically preserved. I can check next flash of rom with opengapps.
[ONE Android Development] :
Thanks for fresh builds [emoji2]

Quick question for clarification: which of these two builds is the right one for "single" users, the first one?
[ONE Android Development] katinatez:
Don't use that it is missing many commits, or use but git pull to bring it up to date. Have been syncing Straight into CyanogenMod for kernel.
[ONE Android Development] question.com:
making a quick nandriod then will try to dirty flash . will report back
[ONE Android Development] hunter0389:
I had the same issue with Google play services. But instead of clean flash, I downloaded the latest 8.3 apk from apkmirror. After installing the apk, you will need to reboot. The phone will ask you to "update" google play services back to the current version. That was my way of getting around clean flash and setting up the phone again.
[ONE Android Development] question.com:
Wish I saw this before I flashed lol. Just downloaded it, will try again
[ONE Android Development] paarkhi:
Yes, the first one for single users
[ONE Android Development] katinatez:
There I updated the kernel repo. You can use it
[ONE Android Development] tiny4579:
Opengapps should be fixed. There was an issue with a Google package installer being added without removing the aosp one. This was causing boot looping. The issue with permissions is a non issue on cm.

It might be for now that opengapps are the only recommended ones for M until the fixes get merged in other gapps packages.
[ONE Android Development] question.com:
Nice. I'll test out tomorrow with the latest open gapps. Already flashed today's build
[ONE Android Development] pa.pn2:
so open gapps from today 08 are safe to flash now?
[ONE Android Development] rogi19:
[MENTION=4406894]vinman12[/MENTION] on your latest build, when i lower the volume or turn it up, it doesnt overlay with the app but instead it shoes me the wallpaper and just the volume panel, no matter what app im in. Any ideas whats causing this?
[ONE Android Development] rogi19:
Screenshots attached
[ONE Android Development] tiny4579:
I should have clarified. It was fixed today but the next automated build is tomorrow. Wait for 11/9.
[ONE Android Development] AcmE85:
It may be caused by the theme you have applied. Try again with the stock theme. I don't have this issue on today's build.

As tiny4579 already said, tomorrow.

But you can help yourself after flashing today's open gapps by removing /system/priv-app/PackageInstaller/PackageInstaller.apk

through TWRP's File Manager (I am using 2.8.6.0.4, I don't know if the official TWRP even has this feature).

Don't forget to mount system to be able to go up to the folder.

Just dirty flashed today's build comming from 11/06 with slimgapps this way:

Wiped System, Cache, Dalvik and flashed the build + opengapps nano.

Then removed the said apk and rebooted back to system.

All the previous issues are gone! Contacts and Play Services up and working!

Also don't forget to update opengapps tomorrow or you will have to delete the said apk again.

edit: [MENTION=4406894]vinman12[/MENTION] something is wrong with the built-in superuser on your latest build.

Textdroider was not able to change the dpi but adaway and titanium backup are working fine. Manually editing the build.prop worked.

Strangely enough, I installed two root checker apps from the play store and was amazed that root permission is granted to the apps without a single prompt.

Statusbar info icon for root access is also missing.

edit: same behaviour on today's build from [MENTION=5551103]Karel VH[/MENTION]

:confused:
[ONE Android Development] AcmE85:
Another "issue" which I have since I switched over to cm13:

Contacts which are using WhatsApp or Threema are shown twice in my contacts list.

One only has the mobile number (with stored Photo).

The other one has the mobile number with additional WhatsApp or Threema information.

All contacts are synced with Google and are listed correctly when opening them on my PC.

Anyone with the same issue?
[ONE Android Development] pa.pn2:
Same here

Its somehow not present in omnirom..
[ONE Android Development] vinman12:
I wish I could answer these questions but I'm only in build mode right now, sync build, post. I cant realy test ROMs until the following day as I maintain 4 devices, andctakes me a day to build and upload all these builds.

But your feedback is good, so some of these other guys can maybe pinpoint some of these problems.
[ONE Android Development] AcmE85:
No worries. That's why I posted to keep anyone informed.

It is not a dealbreaker bug for me so I'm fine with it for the time being.

Thanks for building!

Edit: info for anyone using opengapps, the swypelibs are missing for the keyboard.

I copied the file from slimgapps to get swipe typing back.
[ONE Android Development] extrem0:
There's a way to fix root issues. Just found out that many apps wouldn't get root permissions unless root binaries were updated.

Just download chanifire's supersu app and open it. It will say your root binaries are outdated and will ask to update. Choose normal. It'll say installation failed but it'll work. Reboot device after this isn't necessary.

https://play.google.com/store/apps/d...persu&hl=pt_BR
[ONE Android Development] AcmE85:
Did not change anything on my device. The problem is not that root isn't available.

In fact it is available but it doesn't ask for permission when a new root app is installed and opened,

it does not even show when root is being used in the status bar.

This is a major security flaw if you ask me.

edit: This issue is fixed on [MENTION=4406894]vinman12[/MENTION] latest build (11/09).

Back to normal :)

Texdroider and other dpi apps do not work anymore though.

The dpi has to be set manually via build.prop now.

[MENTION=4406894]vinman12[/MENTION] I did not encounter any issues with your latest build.

Dirty flashed from yesterday's build (without reflashing gapps)

and manually deleted the packageinstaller.apk as described on the previous page.
[ONE Android Development] tiny4579:
For root I suspect the su changes that went in from arcee as the prompt worked before.

With 11/9 gapps you shouldn't need to remove package installer manually. I edited 11/7 manually and found that was the case.
[ONE Android Development] AcmE85:
Opengapps 11/9 are not released yet (pico is but not nano) so I'm still on 11/8 and had to remove the file.
[ONE Android Development] katinatez:
So which commit needs to be reverted for superuser fix?
[ONE Android Development] AcmE85:
[MENTION=4406894]vinman12[/MENTION] should know the answer as his build works fine.