yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] fizbanrapper:
Good feedback, and I've made a decision that should satisfy everyone.

NIGHTLY = Bliss kernel. I'll build these frequently.

EXPERIMENTAL= Candy kernel. Still frequent, but less so.

I suggest clean flashing if you ever switch between the two. Flashing a NIGHTLY over a NIGHTLY should be fine, but flashing a NIGHTLY over an EXPERIMENTAL (or vice-versa) is not suggested. If you don't take my advice and dirty flash when crossing versions, no :crying: about the consequences.

Build size

I figured out what the problem was with the size of my builds. I hadn't been including the vendor/cm repo. It was building just fine without it, and the builds were working just fine for me, but I've included the repo in the latest build and will also include it in future builds (I'm going to add it to the dependencies file to make SURE it always gets picked up). This may also address some of the compatibility issues people have been having.

WiFi

Between my own experience and feedback I've gotten from others, the build with CM's kernel, 4.8 toolchains and several dropped build flags, WiFi connectivity was a non-issue. My latest build (Bliss kernel) was also built with 4.8 toolchains and without the optimization flags. So far WiFi seems to be working just as well as it was with the CM kernel. From 6/24 on, PLEASE let me know the minute you encounter WiFi issues. Assuming there are no further problems with the Bliss kernel build, I'm going to add back the 4.9 sabermod toolchains, with build flags coming after that. Basically I want to figure out exactly what's breaking WiFi and make sure I don't use it in my builds.

OTA

The only thing holding up OTA is for my IP address to be entered into the system. I can't upload until that's taken care of.

Until then, you can find the latest build here:

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

And here's the link which shows all Bliss folders:

https://www.androidfilehost.com/?w=files&flid=33709

Both nightly and experimental builds will be uploaded to the root directory. I trust that you'll be able to figure out that NIGHTLY=Bliss kernel and that EXPERIMENTAL=Candy kernel.
[One (M8) Android Development] fizbanrapper:
No problem! My response may have come across like I was annoyed with your questions. Sorry. I wasn't annoyed and didn't think you came across as rude. We're good.

The changelog isn't on AFH. Click the button in my post and you'll see the changelog there.
[One (M8) Android Development] mcwups1:
Just tried the 625 build nightly. It goes through optimization and then boots off to the battery screen.

Sprint M8 Converted HK 4.25.654.14
[One (M8) Android Development] fizbanrapper:
Clean flash?
[One (M8) Android Development] Blindie:
hmmm, use your new nightly, when i restore from titaniumbackup (no system apps) my phone is shuting down and my data partition is broken. In logcat, there is no error. The last lines looks like tis:

I/qtaguid (20099): Failed write_ctrl(u 30) res=-1 errno=22
I/qtaguid (20099): Untagging socket 30 failed errno=-22
W/NetworkManagementSocketTagger(20099): untagSocket(30) failed with errno -22
D/Finsky (20099): [1] 2.onResponse: Verification id=62 response=0
D/DefContainer(9214): Copying /data/data/com.keramidas.TitaniumBackup/files/install.apk to base.apk
D/Finsky (20099): [1] PackageVerificationReceiver.onReceive: Verification requested, id = 62
W/CursorWrapperInner(1877): Cursor finalized without prior close()
W/CursorWrapperInner(1877): Cursor finalized without prior close()
W/CursorWrapperInner(1877): Cursor finalized without prior close()
W/CursorWrapperInner(1877): Cursor finalized without prior close()
W/CursorWrapperInner(1877): Cursor finalized without prior close()
W/CursorWrapperInner(1877): Cursor finalized without prior close()
W/CursorWrapperInner(1877): Cursor finalized without prior close()
W/CursorWrapperInner(1877): Cursor finalized without prior close()
W/CursorWrapperInner(1877): Cursor finalized without prior close()
W/CursorWrapperInner(1877): Cursor finalized without prior close()
W/ResourceType(9349): For resource 0x01030224, entry index(548) is beyond type entryCount(16)
W/ResourceType(9349): For resource 0x01030224, entry index(548) is beyond type entryCount(16)
W/ResourceType(9349): For resource 0x01030128, entry index(296) is beyond type entryCount(16)
W/ResourceType(9349): For resource 0x01030237, entry index(567) is beyond type entryCount(16)
W/ResourceType(9349): For resource 0x01030237, entry index(567) is beyond type entryCount(16)
[One (M8) Android Development] _moelle:
same to me, but clean flash fixed it.
[One (M8) Android Development] mcwups1:
Of course.

Sprint M8 Converted HK 4.25.654.14
[One (M8) Android Development] fizbanrapper:
Last night they bumped Bliss up to tracking AOSP 5.1.1_r5, but I didn't know that until this morning. Even though I did a clean build, I did a clean build using prebuilt chromium... and 5.1.1_r5 had lots of changes to chromium. That could explain it, though I don't know why I'm not having any problems with the build.

Blissful kernel was originally forked from Slim. I'm currently attempting a very experimental build which replaces the following CM repos/HALs: audio, display, media, BT, FM, GPS, keymaster, powe, wlan & RIL with Slim sources. In all likelihood it won't even compile. If it does, I'll flash it and run it for a while before posting it for others. If it works (20% chance, is my estimate), this could address some compatibility issues when using Blissful kernel.
[One (M8) Android Development] mcwups1:
I'm not making it up. Also, I'm not saying you're assuming I didn't. However, I always clean flash from ROM to ROM. I wiped cache, dalvik, system, and data, 3 times before installing ROM, and then gapps. This is a tradition I've kept doing since the HTC OG Evo.

It starts with the optimization after the boot animation, and then it craps out to the battery screen.

I have the latest TWRP, my carrier and my radio information is in my signature, which are updated.

I can assure you, that I will have clean flashed everytime to avoid problems, and I usually give you a logcat to look at if I can.

Sprint M8 Converted HK 4.25.654.14
[One (M8) Android Development] italynstylion:
I'm running Bliss version 3.5 the official 6/18/2015 release and I'm unable to receive calls. I can make calls just fine. Anyone else have this issue?
[One (M8) Android Development] italynstylion:
Latest build (nightly OR official) is from 6/18; is that right?
[One (M8) Android Development] remix92:
it would be very nice if you can add iin quick settings the inactive display :)
[One (M8) Android Development] Wasabi Ice Cream:
My Home button doesn't work at all.

Running the Official 6/19 build from a clean flash.
[One (M8) Android Development] computercarl:
version

So, the thread says 5.1.1r3, but is that accurate anymore? I see the src for 5.1.1r5 is out, have we moved to it for nightlies? The changelog on blissroms is from the 16th. Thanks to all the mods and builders, this rom is really nice, cutting edge, and really lets me use my m8. Keep up the great work.

Also, whoever is building the nightlies with slim and cm kernels, keep it up, when I was running nightlies a week or so ago, I was running the candy kernel and keep hbooting at 3a like a bunch of others have listed. I'm now running the bliss kernel on 6/22 nightly, and hasn't done it since. Only bug I've seen on 6/22 was with white on white notifications, but applying a theme fixed that, and being this theme is black, saving some more battery.
[One (M8) Android Development] bacon612:
Thanks for reporting that you were also getting the 3am hboot. What variant m8 are you using. What firmware?

Mind sharing what theme you are using? I have never used themes before but if it fixed the white on white, im in.
[One (M8) Android Development] computercarl:
https://play.google.com/store/apps/details?id=com.blazze11.euphoria.dark&hl=en
[One (M8) Android Development] computercarl:
see attached screenshot.
[One (M8) Android Development] ckvisme:
Not that it's my business... But you know you can update your os ( firmware) to verizon 5.0.1 lollipop?

Verizon update

Im on sprint and updated mine in a similar fashion (0P6BIMG.zip flashed via bootloader)... Just sayin'
[One (M8) Android Development] fizbanrapper:
So the above experiment actually worked out a lot better than I expected. Everything worked well for me, except WiFi was spotty. It's the build in the "test" folder, if anyone is interested.

In case you're curious what was changed in that build, see below:

<!-- SWAP AUDIO, DISPLAY & MEDIA HAL-->

<remove-project path="hardware/qcom/audio/default" name="CyanogenMod/android_hardware_qcom_audio" groups="qcom,qcom_audio" />

<project path="hardware/qcom/audio/default" name="SlimRoms/hardware_qcom_audio" remote="github" revision="lp5.1" />

<project path="hardware/qcom/audio-caf/msm8974" name="SlimRoms/hardware_qcom_audio" remote="github" revision="lp5.1-caf-8974" />

<remove-project path="hardware/qcom/display" name="CyanogenMod/android_hardware_qcom_display" />

<project path="hardware/qcom/display" name="SlimRoms/hardware_qcom_display" remote="github" revision="lp5.1" />

<project path="hardware/qcom/display-caf/msm8974" name="SlimRoms/hardware_qcom_display" remote="github" revision="lp5.1-caf-8974" />

<remove-project path="hardware/qcom/media/default" name="CyanogenMod/android_hardware_qcom_media" />

<project path="hardware/qcom/media/default" name="SlimRoms/hardware_qcom_media" remote="github" revision="lp5.1" />

<project path="hardware/qcom/media-caf/msm8974" name="SlimRoms/hardware_qcom_media" remote="github" revision="lp5.1-caf-8974" />

<!-- SWAP BT, FM, GPS, KEYMASTER, POWER, WLAN & RIL HALs-->

<remove-project path="hardware/qcom/bt" name="CyanogenMod/android_hardware_qcom_bt" />

<project path="hardware/qcom/bt" name="SlimRoms/hardware_qcom_bt" remote="github" revision="lp5.1" />

<remove-project path="hardware/qcom/fm" name="android_hardware_qcom_fm" />

<project path="hardware/qcom/fm" name="SlimRoms/hardware_qcom_fm" remote="github" revision="lp5.1" />

<remove-project path="hardware/qcom/gps" name="CyanogenMod/android_hardware_qcom_gps" />

<project path="hardware/qcom/gps" name="SlimRoms/hardware_qcom_gps" remote="github" revision="lp5.1" />

<remove-project path="hardware/qcom/keymaster" name="CyanogenMod/android_hardware_qcom_keymaster" />

<project path="hardware/qcom/keymaster" name="SlimRoms/hardware_qcom_keymaster" remote="github" revision="lp5.1" />

<!--remove-project path="hardware/qcom/power" name="CyanogenMod/android_hardware_qcom_power" /-->

<project path="hardware/qcom/power" name="SlimRoms/hardware_qcom_power" remote="github" revision="lp5.1" />

<remove-project path="hardware/qcom/wlan" name="CyanogenMod/android_hardware_qcom_wlan" />

<project path="hardware/qcom/wlan" name="SlimRoms/hardware_qcom_wlan" remote="github" revision="lp5.1" />

<remove-project path="hardware/ril" name="CyanogenMod/android_hardware_ril" />

<project path="hardware/ril" name="SlimRoms/hardware_ril" remote="github" revision="lp5.1" />

<!--remove-project path="hardware/ril-caf" name="CyanogenMod/android_hardware_ril" /-->

<project path="hardware/ril-caf" name="SlimRoms/hardware_ril" remote="github" revision="lp5.1-caf" />

After that, I compiled another build with Blissful kernel and a modified device tree, but WiFi is spotty again. next build will be with Candy Kernel.
[One (M8) Android Development] fizbanrapper:
Glad you like it. It seems that while I can edit the OP, I can't edit the title to reflect the bump. Looks like we're stuck at _r3 for eternity.

I'll keep building it both ways for a while, but I'm really annoyed with the WiFi issues with the Blissful kernel.

I'll be uploading NIGHTLY builds to the site soon. The dude who has to add my credentials is crazy busy right now, so I don't have access yet.
[One (M8) Android Development] NiXiNiX:
FYI

Non of the latest builds are working for me.

Every build results in a reboot to battery symbol and partitions are corrupted.

Doesn't matter if clean or dirty flashed. :confused:

Edit:

Haven't tried BlissPop-v3.6-m8-EXPERIMENTAL-20150627-0050.zip , though.

Will give it a try later
[One (M8) Android Development] TheKnux:
[MENTION=5676253]fizbanrapper[/MENTION] if you have some time, do you think you can make and experimental test build built with [MENTION=3018567]Damacy[/MENTION]'s Blackbird kernel found here? http://xdaforums.com/showthread.php?p=57080564

Also, if you can, possibly port multi-window from CyanideL from here? http://xdaforums.com/showthread.php?p=56542821

I used to use it all the time on Bliss and it worked perfectly fine. No issued with WiFi, lag, responsiveness, etc.

Just figured you could build a test ROM using it and see how things go.
[One (M8) Android Development] bacon612:
He is running the lolipop firmware...

---------- Post added at 08:52 AM ---------- Previous post was at 08:51 AM ----------

You are up to date here. I am running the same phone with the same firmware.
[One (M8) Android Development] ckvisme:
OK, OK, I noticed the 3 at the start of the os number, I thought that was kitkat ...i thought that lollipop os all start with 4. My bad but thank you for the info ?
[One (M8) Android Development] COMpulse:
I seem to have turned on Floating Windows for chrome and now maps as well. Anyone know how I disable floating windows?

Thx
[One (M8) Android Development] fizbanrapper:
I know builds still haven't been quite right. I know some of the reasons why, but I've been trying to fix the problems without having to start over fresh... Something I'm strongly considering doing now.
[One (M8) Android Development] mcflyrk01:
anyone have an issue on the latest nightly where disabling auto-rotate doesn't seem to be respected? no matter what i set it will always rotate.

EDIT: nevermind, working fine on the official
[One (M8) Android Development] TheKnux:
Listen man, I know you just started doing this, and BlissPop is way different than the other ROM's you work on cause of the features and stuff, but there's a first time for everything. You've only been doing this for a little and you're doing way more than any dev I've seen do. What I mean is, you literally made a build with every possible kernel that's out right now, AND your managing to keep them all up to date when you can. You're doing a great job man. As long as you're just merging and syncing commits and changes and doing all the stuff you're supposed to, you're doing the best you can. I don't think what your doing is your fault. A lot of people have been saying lately that CM is full of bugs and what not. Plus with everything going on in BlissPop, yeah, there's gonna be things broken here and there. Hell, I wouldn't want to do this, my brain would explode. Anyway, just continue doing whatever it is, however you're doing it and you'll be just fine. Thanks again for stepping up to give us the best ROM that could ever be built. ?
[One (M8) Android Development] nocturnoz:
Unknown Icon

Hey there,

since I clean flashed Build 20150617 / Kernel Candy from 20. June I've got that weird prohibition sign (Screenshot)

Do you know where it comes from and how to disable it?

Another question: Is it safe to dirty flash the experimental build (candy)?
[One (M8) Android Development] TheKnux:
I've been dirty flashing between nightlies (Bliss kernel) and experimental (candy kernel) and haven't had a single problem yet. You should be good. Just make sure you make a backup and deny kernel auditor root permissions if you switch between the two kernels just to be safe. That way it can't apply a setting that isn't there cause it's missing from a certain kernel. I had that problem when Candy first came to Bliss but now, everything has been running smooth as butter.

---------- Post added at 04:08 PM ---------- Previous post was at 04:07 PM ----------

[MENTION=5676253]fizbanrapper[/MENTION] where are the floating/multi window settings found if there are any?
[One (M8) Android Development] ahpatel:
I dirty flashes the 6-27 experimental over the 6-20 experimental and lost wifi. Then, I flashes the 6-15 candy kernel boot image on top of the 6-27 build and wifi is back.

Did anything change in the candy kernel over that time that could have impacted wifi?
[One (M8) Android Development] pstrang:
He made clear a page or two ago that dirty flashing between the two kernels is a bad idea.
[One (M8) Android Development] TheKnux:
Okay? Just because he said it was a bad idea doesn't mean that he said don't do it. If it worked for me, chances are, it'll work for someone else. Life's too short bro, don't be afraid to take chances.
[One (M8) Android Development] E30Nova:
If you're talking about the circle with a line through it, it's because you're in super quiet mode with no notifications/interruptions. You just have to hit volume up and then choose "silent" or "always".
[One (M8) Android Development] nocturnoz:
Oh, well... explains a lot of anoying stuff. x) Thanks!
[One (M8) Android Development] _moelle:
can anyone tell me how to disable this weired keyboard style? or isnt it editable?
[One (M8) Android Development] nocturnoz:
Its hardcoded. You only can change it by installing another keyboard (ex.: swiftkey)
[One (M8) Android Development] pstrang:
The kernels have different ramdisks. Your advice to the user who posted the question is not good. Here's what the dev said:

I suggest clean flashing if you ever switch between the two. Flashing a NIGHTLY over a NIGHTLY should be fine, but flashing a NIGHTLY over an EXPERIMENTAL (or vice-versa) is not suggested. If you don't take my advice and dirty flash when crossing versions, no :crying: about the consequences.
[One (M8) Android Development] _moelle:
cant find multiwindow setting (to turn it off) on latest build uploaded on androidfilehost by OP
[One (M8) Android Development] TheKnux:
Dude, chill. I just stated what worked for me. I never specifically said that it is absolutely okay to do so. I just said I did it and everything has been fine. That is all.
[One (M8) Android Development] fizbanrapper:
It's a gamble. I've had almost no issues with it, but seems like some others have had some really bad issues with it.

Anyway, here's the latest build with candy kernel

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

I started over with a fresh device tree, and WiFi is working flawlessly for me. I caution that since this is working from a fresh device tree, there's a higher risk of problems. Please report your issues. I expect that there will be some, but this is my best Bliss build yet (on my device anyway).
[One (M8) Android Development] fizbanrapper:
Thanks for the support. It is appreciated.

This is my first time building Bliss for M8, but I had build BlissStalk and BlissPop for my last device. What's been tough for me is that I've never taken over for someone else before. M8 is also tough because there are many variants that all share a common kernel and device tree.

I know he changed some stuff from what CM was using, but it's hard to tell what. It's easy to identify his original commits, but if he cherry-picked a commit from invisiblek's device tree, it most likely got merged into CM, but some of invisiblek's commits are experimental and don't get merged. It's hard to tell the difference between the two. Now that I'm starting over, when there are issues, I should have a better idea of how to fix them.
[One (M8) Android Development] andrew378:
Same, on 6-27. Chrome keeps opening in a small window
[One (M8) Android Development] GRIDSpawn:
Where are the new builds because in the official page I can't find it

http://downloads.blissroms.com/BlissPop/Nightlies/m8/
[One (M8) Android Development] fizbanrapper:
Check again :)

No biggie, but if you've read any of the last 7 or 8 pages in the thread, you probably would have found your answer. I just now got access to upload builds.

I've updated the OP to add the link for the new folder for the Candy builds. http://downloads.blissroms.com/BlissPop/Experimental M8/

Again, the builds with Candy kernel will be uploaded as Experimental builds, while Blissful kernel builds will be uploaded to the Nightlies folder.

The "Nightly" builds could actually wind up being every single night, but will sometimes be more frequent or less frequent, depending on how much time I have and what I'm working on. The more tinkering I do, the more frequently I'll upload.
[One (M8) Android Development] pstrang:
I gave it a shot. Ultraclean flash (dalvik, cache, data, system, and internal mem). The Candy rebooted 4x while optimizing apps on first boot. Then random reboots every 2-10 min. Let it sit overnight, not sure how many reboots. It comes back to ROM, does not stay in bootloader.

I gave up and installed 6-22 unofficial w/ Bliss kernel....no reboots.

I have latest FW, VZW, and have cache and data as F2FS. I try system as F2FS, but installer images it back to EXT4.

Thanks for your dev work!
[One (M8) Android Development] bacon612:
For what it's worth, I dirty flashed it (made a nandroid first) and its been great for me all morning. Curious to see if it hangs in hboot tonight.

---------- Post added at 11:58 AM ---------- Previous post was at 11:55 AM ----------

Edit: ya I have this on 6/27 expirimental too.
[One (M8) Android Development] bacon612:
Edit 2: restored nandroid and flashed 6/28 nightly overtop. No issue with chrome windowed mode and running smoothly.
[One (M8) Android Development] NiXiNiX:
There are two 06/28 builds an hour buildtime apart. Any significant difference, if any?
[One (M8) Android Development] ejswagon:
Both the regular latest (6/28) nightly and the Candy version cause play store FC using MultiRom (ViperRom as primary). Version 6/18 has no problems, so I'm reverting back.
[One (M8) Android Development] pstrang:
You need to clean flash.
[One (M8) Android Development] ejswagon:


---------- Post added at 09:44 PM ---------- Previous post was at 09:41 PM ----------

I did both. First dirty, then clean. Both fail
[One (M8) Android Development] pstrang:
In recovery you wiped data and system?

Otherwise you can download and manually install the Google Play Services APK.
[One (M8) Android Development] ejswagon:
I did. I'm not aware of any other method of installing a clean Rom, save maybe using ADB.
[One (M8) Android Development] ckvisme:
Did you try 'run restorecon' option in multirom twrp? boot to MR TWRP :

click Multirom - < select secondary rom you are fixing > - click run restorecon - swipe to confirm - reboot - ..??.. - profit baby!
[One (M8) Android Development] ejswagon:
I just saw that option and wondered what it did. I'll try that now

---------- Post added at 10:20 PM ---------- Previous post was at 10:11 PM ----------

Ran RestoreCon in recovery for the specific rom. Doing so apparently only causes an endless boot
[One (M8) Android Development] ckvisme:
Strange... I have run it on Exodus, SOKP and Bliss just this week.

I don't know why I've been have issues with play store crashes (on initial setup) .. But I've tried 3 sets of GApps with no luck .

*restorecon has worked everytime.. So far..

PS I guess you been to back and tried wiping cache and dalvik again?
[One (M8) Android Development] TheKnux:
[MENTION=5676253]fizbanrapper[/MENTION], since you now have access to the website, are you going to be pushing the experimental builds to the OTA app or the nightly?

Also, just thought of this, why don't you build the candy and bliss kernels using anykernel that way there will be less compatibility issues when dirty flashing roms.
[One (M8) Android Development] papero68:
[MENTION=5676253]fizbanrapper[/MENTION], sorry but i dont understand one thing : officials versions will be bliss or candy? Thank you

Inviato dal mio One M8 utilizzando Tapatalk
[One (M8) Android Development] fizbanrapper:
Both. Solves the problem for everyone.

Some people even had issues when flashing anykernel zip files. Love the idea in theory, but not so much on practice.
[One (M8) Android Development] fizbanrapper:
Truth be told, I don't know. The official builds are not done by me. They're done by a Bliss team member on a dedicated server. My guess is that they'll keep building it with the same kernel as has been used in the other official releases.