yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] 875295391:
Does anyone test the rom with vindicator kernel？？？
[BLISS ROMS Development] nicholaschum:
It runs great, just grab the latest kernel available on this app

https://play.google.com/store/apps/details?id=com.mcswainsoftware.vindicator.ota

---------- Post added at 05:06 PM ---------- Previous post was at 05:05 PM ----------

Alright, will tell Pat to look into it. There's probably something in the automator that prevents any stock kernel from working perfectly.
[BLISS ROMS Development] aussie1234:
Signal dropping out

It's not only this ROM but some others - the reception signal just drops out every 30 to 40 seconds. That's both call and data reception. The signal icon just disappears and eventually returns and while it is gone there is no reception.

I have correct APN and did the register on network with the correct network selected.

I had updated firmware and radio to the 5.1 version also.

Currently on my phone I have no third party apps that would be affecting reception as all I have is this ROM, Blue Code Kernel and minimal GAPPS. But like I mentioned I have noticed this problem with other ROMS.

Does anyone have any ideas??

Cheers

Aussie
[BLISS ROMS Development] aalupatti:
I had similar issues with some kernels... I think it was code blue kernel...

I changed to another Kernel and all good
[BLISS ROMS Development] abjexstallion:
The unknown bug still present but [MENTION=3605033]nicholaschum[/MENTION] already stated that pat and the team will check on it.
[BLISS ROMS Development] nicholaschum:
Oh, I meant about the kernel. It's probably some upstream CM code collision, so we'll try to isolate it down as best as we can
[BLISS ROMS Development] BakedFiend:
I will test for you if you would like me to
[BLISS ROMS Development] pjgraber03:
What features are you looking for? There aren't very many features that we don't have.
[BLISS ROMS Development] pjgraber03:
Unknown Caller Issue

I'm still looking into the issue....Possibly a fix coming I will let you guys know so you can test it out for me
[BLISS ROMS Development] aussie1234:
Signal Loss

Yes, very odd as it happens across some ROMS and different Kernels.

Aussie
[BLISS ROMS Development] pjgraber03:
If someone would like to test the latest build and let me know if caller unknown issue is still present that would be cool
[BLISS ROMS Development] 875295391:
Year,Thanks.I used pushbullet and i will have a try it tonight.
[BLISS ROMS Development] BakedFiend:
Unknown bug is still present on latest build
[BLISS ROMS Development] JohnnyMontana_:
Probably a stupid question, but is there a way to change the lockscreen wallpaper without using a wallpaper from a theme?
[BLISS ROMS Development] nicholaschum:
There are quite an amount of these apps on Play

Here's one: https://play.google.com/store/apps/details?id=com.miniprepumen.cm12.changelockscreencm12
[BLISS ROMS Development] sonofevil77:
Latest build has perpetual system ui FC. Went back to 5-18-0641 and np.

Chromatose
[BLISS ROMS Development] JohnnyMontana_:
I can't explain why I didn't think to try an app lol.. Thanks a bunch!

Works great too.
[BLISS ROMS Development] nicholaschum:
TO ALL USERS: WE WILL BE PAUSING OUR BUILDS UNTIL FURTHER NOTICE DUE TO HEAVY CODE CLEAN UP AND REBASING.

Thank you all for the support!

This means that the next major upgrade should be a clean wipe build as a lot of changes will be made.

EDIT: Since this post is seen device-wide, the "rebasing" has been clarified on Pat's end as shamu's kernel problem:

Builds will be paused for devices while we clean up Bliss interface, optimize it on devices having problems (depending on your device, like shamu, has some "Unknown" bugs for phone calls, and backporting of new features such as nav bar customizations, 5.1.1r3, etc. As always, we want to deliver a clean, blissful experience.

To keep up with what we're doing, check out: http://review.blissroms.com:8081/#/q/status:merged

Development never stops, baby!
[BLISS ROMS Development] sonofevil77:
Nice!
[BLISS ROMS Development] pjgraber03:
Clarification

just to clarify we are cleaning up the code to reorganize things and rebasing kernel to try and clear up any issues with kernel. So builds should resume fairly soon. I didn't want anyone to think we were pausing building for an extended amount of time. Thanks everyone for your support. Keep it blissful =)
[BLISS ROMS Development] chuckz2016:
You guys are the best! hands down! :) keep up the good work....
[BLISS ROMS Development] minieod:
Flashed the 5/19 build and getting these super condensed buttons on the nav bar.

Anyone else have this happen? I can't seem to find in settings a place to space them back out to normal
[BLISS ROMS Development] nicholaschum:
It's the new nav bar implementation we added into the rom. You can check it out in Button options.
[BLISS ROMS Development] minieod:
Ah OK. I saw that menu earlier but didn't see anything applicable.

Its the "legacy" option.

Thanks!
[BLISS ROMS Development] kenbrownstone:
If you guys need a test for signal coming in and out I'm in...My phone has done it for months...Unfortunately its on every ROM and kernel no matter cm or asop....Its getting old..Actually thinking of getting rid of the nexus because of it....
[BLISS ROMS Development] Clark Joseph Kent:
Thread Cleaned, and if you are here to support the Team, do so...but the bash/comments regarding BP cleanup is not needed...
[BLISS ROMS Development] ManikandanGuru:
One quick request. Instead of bliss icon in status bar, please consider giving option for custom icons. That would be cool.
[BLISS ROMS Development] nicholaschum:
Thanks a lot, JJD! :)
[BLISS ROMS Development] chrristin:
I have too. Reverted to yesterday's buid. ( But when tried t dirty flash over todays' it went into bootloop. ) A clean install of todays version ( with xposed ) gave system UI crashes. Now on a clean install of yesterdays ROM.
[BLISS ROMS Development] nikiboy420:
Phone Reboots most of the times when a call is recieved

Anyone knows about a problem where whenever the screen is off, and I receive a call, most of the times the phone hangs and the ringer keeps ringing. Screen does not come on and then the phone reboots.
[BLISS ROMS Development] ac3theone:
Yup that's a known bug, only fix so far is to change kernel to code blue kernel
[BLISS ROMS Development] casonswag:
The first build 19 is working great for me i didnt try the latest build 19
[BLISS ROMS Development] ManikandanGuru:
Exactly the same problem I encountered today. Going to try the first 19 build.
[BLISS ROMS Development] ph0tiC:
Like I said before, when I first got my N6 at the beginning of April, I tried Terminus, Benzo, Chroma, and Temasek. This is my first time running custom ROMs on my phone, and I needed one that just worked out of the box. BlissPop was it! I even tried out DU a while back, but at that point I was so spoiled by BPs customization that it didn't even get a fair try (so vain, its just colors!!). I've seen the BS with DU burn out Apophis and that sucked. And now this....

DO NOT STOP working on this ROM. Take a break to clean, fine. But don't cease development and close up shop! The mere fact you have people here VOLUNTEERING to be guinea pigs with their own personal equipment to fix issues shows that people outside the Bliss team definitely love/support this ROM.

That said, I ran the 08apr build for a month, then moved to 06may with code_blue. I'll be updating again probably in the next day. Its a daily driver thing for me; I'll back up the entire phone, flash the new stuff, and if it doesnt work ill just go back and wait more. Think I'm going to ditch TBO, too much of a security concern running it (and auto updates from Google itself gives a warm n fuzzy)

Only issues I have is:

!! Have to hit the power button/DT2W repeatedly to get the screen back on (too deep a sleep?) possibly code_blue.

!! Too many running apps will FC/lag the foreground app/systemUI and the wallpaper resets. I have to go and clear out my recent apps; I note that memory is under 500 free when I have to do this. (code_blue)?

!! Wish "OK Google" global setting would survive reboots.

Minor annoyances:

- Keyboard silent FC? app comes to foreground with text input, I select, KB doesnt show up but down icon is on the nav bar. have to hit it and then reselect text input.

- Bluetooth stutters (code_blue/the price of 36 hour battery life?)

Issues not seen:

? Not sure on the LTE thing. My phone says LTE, and the data speed backs it up! (TMobile)

? No crash on incoming calls (kernel change fixes)

? No unidentified caller issues (TMobile)

Love:

* Current battery life is phenomenal!!! On a full charge and little less than my average use the battery will last almost 24 hours. For a smartphone, that's saying a *lot*!

* Love the dark theme, wish I didnt have to use TBO for Google apps. Feel that saves more battery with AMOLED but I don't know - I only play a doctor on TV.

* It's slick, and it's fast; things just work. and that is spectacular! I dont have time to download ROMs and reinstall apps every day, but I don't like the default Shamu ROM either.

* Issues above aren't show stoppers, just minor annoyances.

I'll try a new mix of ROM and kernel, and let ya'll know how it goes. And if you hate this long post, now ya know why I don't comment too often ;)
[BLISS ROMS Development] buschris:
Code Blue Kernel, ElementalX, Stock. Can't answer phone calls at all. Going back to stock (praying) or getting a different phone, this shouldn't be happening on a premium phone, on Verizon of all carriers!

I like thos ROM otherwise, it's the most customizable of all

the ROMS. I just gotta have the phone portion working!
[BLISS ROMS Development] sonofevil77:
I restored a backup. I don't use xposed.
[BLISS ROMS Development] Othoric:
I just wanted to report that the latest 5-19 build does cause system ui crashes for me as well. The first of the 5-19 builds (20150519-1002) however does work with the only issue in my case being that I cannot get the navbar to disable since I use pie controls. I can get it to disable if use expanded desktop however. Does anyone also have that issue with the first 5-19 build?
[BLISS ROMS Development] Kchitown1977:
Searched ROM no luck play services keeps stopping on me
[BLISS ROMS Development] galaxy s4 nutjob:
I can't get past the first boot is been about an hr and still stuck on bliss boot screen. Did a clean install
[BLISS ROMS Development] aalupatti:
What is happening with all the development being stopped ? Where can i find more information ?
[BLISS ROMS Development] DopeShotz:
No problems!

I have been running this ROM from day one since I got my Nexus 6. While I have had my fair share of almost heart attacks (PROBLEMS), I have to say this is the best ROM I have ever ran on a phone. I read everyday the problems that other people are running into but honestly I just think that sometimes people are just too lazy to try and fix the problem themselves. I am no ROM genius but I have been around the block a time or two. If you take sometime to take a deep breath and do some research a lot of the time you will find a solution. Instead people are quick to jump on developers and start bashing them when the problem was really caused by the end user doing something they weren't supposed to. I truly love this ROM and look forward to future builds. Remember there is no such thing as a perfect ROM, although BLISS is pretty close. They all have their pros n cons. Bravo Zulo to the developers you guys rock!
[BLISS ROMS Development] wrongway213:
I can't give a clear answer, as I have seen three different ones given by members of the team. It appears from this thread that it was a code cleanup due to kernel issues, particularly with booting. However, the G3 thread appears to allude to a bricked device of the maintainer causing the stop in development. However, the BlissPop G+ page says it is due to "XDA Staff actions". I have not seen confirmation beyond these three separate staements. Maybe someone from Team Bliss will opt to clarify the situation for everyone - if not I suppose the G+ page, the G3 thread and this thread are the only three places I can point for you to find information.

Edit: It appears the Hammerhead/N5 thread gives a reason most closely in line with G+, citing "XDA Staff actions". However, this was corrected by a moderator within the thread to reflect it was actually "due to some BP Team members". This post is where I found said information if anyone is interested: http://xdaforums.com/showpost.php?p=60847504&postcount=2663
[BLISS ROMS Development] ibilln:
Call Quality

I posted this in the AICP thread just now.

---

Have not seen other posts on call quality; have searched in Q&A; etc.. -Probably- is my own issue. But the call quality in AICP (and BlissPop) seems quite poor. The phone seems to be fighting to start a call, with uneven ringing, then the audio is over-modulated and garbled - to me and to my caller/callee. Sometimes the call is dropped before I get a chance to answer. I mention this, and I say probably, above, because this happens on BlissPop too, in exactly the same way. It does -not- happen on Stock (with/wo xposed).

Again, even given the latter, I fully realize the problem could be, um, me. But perhaps this rings a distant bell for someone. Thnx...
[BLISS ROMS Development] nicholaschum:
We are fixing builds currently, cleaning up the layout, interface, packages and mainly for user experience. There are some clean ups too for devices such as shamu about kernel or failed builds on bacon.

However, shamu still gets updates so we're safe.

---------- Post added at 12:04 PM ---------- Previous post was at 12:03 PM ----------

Flash a custom kernel, we mentioned this in the announcements while we are trying to get this fixed. Thanks.

---------- Post added at 12:05 PM ---------- Previous post was at 12:04 PM ----------

Reflash gapps

No issue here on the 20th build. Never had SystemUI FC. Are you on stock set up or custom kernel set up? Try code blue.

---------- Post added at 12:06 PM ---------- Previous post was at 12:05 PM ----------

I heard this was a Version issue. You can try turning off the VoLTE provision flag in *#*#4636#*#* - > Phone Information then find the button
[BLISS ROMS Development] mdayjr:
I usually just reflash my radio if I end up with issues. Seems to fix most problems. Worst case, wipe all clean including system,not internal storage, and reflash ROM with either vindicator or Franco kernel. Both kernels work.
[BLISS ROMS Development] nicholaschum:
Dt2w is kernel, but on code blue it works great for me.

Memory problem can be easily solved by limiting the amount of apps in the background, try services and check your Battery Chart in settings.

No experience with OK Google system wide, but works on Nova Launcher main screen no problem.

Bluetooth stutters were reported when your kernel runs at a very low frequency. I usually keep the min at either 300 or 400.

The dark theme was removed, but you can try search on play store for my theme. Just search theme engine on Play and the first one is it. Dark Material. If you want a fully blacked out experience, check out Blacked Out!
[BLISS ROMS Development] nicholaschum:
Can't turn that off, but it worked on my OnePlus One, I'll tell pat to take a look into this.
[BLISS ROMS Development] Othoric:
Thank you very much for helping me confirm that its wasn't just my device not being able to disable the navbar. I've also discovered that my problem with applying themes to the navbar seems to only occur with certain themes. For example, the deep darkness theme does apply to the navbar, but the black octopus theme does not apply to the navbar. Very odd...
[BLISS ROMS Development] nicholaschum:
Well, I only tried with my theme and can guarantee mine works perfectly. [emoji4]
[BLISS ROMS Development] sonofevil77:
I'm having the reboot on incoming call randomly on the 5-20 build clean install. I just tried to turn off the volte provisioning flag but it does not toggle off.

BlissPopped
[BLISS ROMS Development] nicholaschum:
Hmm very strange, but then again I see you're on Verizon too. Yeah we're having issues with Verizon users but we're fixing it :)
[BLISS ROMS Development] sonofevil77:
Leave it to Verizon Ugh lol. They kill me sometimes. I'm just glad it's not every call like it was quite a few builds back. I'm still loving Bliss more than any other so I'm good. Take your time, I know you guys will give us something beautiful!

BlissPopped
[BLISS ROMS Development] devilleave:
Bootlooping

I flashed the rom last night and tried using minimal/banks gapps. I let it bootloop for 30mins 2x in a row then 2x for a hour. Does anyone have suggestions
[BLISS ROMS Development] RanceJustice:
Did you try flashing a kernel as well (CodeBlue, LeanKernel etc.. seem to be well supported. Vindicator seems like a good choice as well?) There is an issue with bootlooping, but if you read back a page or two the BlissRoms team is working on it! For now, be sure to flash a custom kernel ; I hear this is the way to stave off bootlooping issues.

Oh and to TeamBliss members: Thanks for your continued work on making this ROM great! Does BlissPop have Disabled Tethering Checking included? Or is it perhaps built in to CM12.1? If it isn't in either case, would this be something feasible to add? It would be nice not to have to worry about tethered data use being flagged differently. Thanks!
[BLISS ROMS Development] RayMcGrath:
Flashed this today. Flashed ROM, Franco kernel, gapps from 051415 (in that order) booted to BLISS! Wow! Super smooth, fast and responsive! Restored apps and accounts via TiBu - update.zip. I'm amazed. Thanks for a great ROM! No issues thus far.
[BLISS ROMS Development] devilleave:
Thanks for the knowledge. I got it working now. Been working on this all week
[BLISS ROMS Development] r1ndr3w:
FCs Google Play Services

Blisspop v3.3 20150521

Leankernel

Banks Gapps 0522, 0521

Getting regular and ongoing FCs on Google Play Services.

Anyone else seeing this?
[BLISS ROMS Development] buckmarble:
Its a gapps issue. Use an older gapps package.
[BLISS ROMS Development] r1ndr3w:
Thanks.
[BLISS ROMS Development] devilleave:
Noob with BlissPop

I just read about RRO themes. Is BlissPop compatible or can you personalize themes yourself
[BLISS ROMS Development] Othoric:
AFAIK Blisspop uses only CM Theme engine. From what I've seen layers is only found on AOSP based ROMs like Chroma or AOSiP. To be honest though, after using both pretty extensively, I prefer CM theme engine. For one, it isn't necessary to reboot every time you want to change a theme like with layers. And for two, it seems development on layers is very slow and there just aren't as many themes available for layers as CM at the moment. That's just my two cents though.
[BLISS ROMS Development] nicholaschum:
Do check out mine (shameless self promoting haha), but my theme is usually keeping up to date with Bliss' newest commits, and shamu pushes out more updates than any other device (even though we're still squashing a ton of changes) :good: :highfive:
[BLISS ROMS Development] Othoric:
I'm actually running it now [emoji1]. It's easily one of my favorite themes. Great job!
[BLISS ROMS Development] nemofbaby2010:
Blisspop running perfect only issue is still the unknown bug on T-Mobile whilst using volte
[BLISS ROMS Development] ffchampmt:
I think i tried every which way to get this update running from 5/12 build. Dirty flash w/kernel, dirty flash with permissive zip w/kernel, clean flash + kernel, clean flash + permissive + kernel. Read the last 10 pages of posts, tried tips from other users.

Used Elementalx and Franco, tried code blue on the dirty flashes. I've tried nearly a dozen times.

Bootloops, bootloops, bootloops.

:frustrated:

On Verizon Nexus 6. Going to stay on 5/12 build until I hear more positive results from other users.

I don't know if this is a factor, but I never get to the encryption unlock. Is this because the system isn't loading to decrypt internal storage?

Sent from my Verizon Nexus 6 running BlissPop
[BLISS ROMS Development] nemofbaby2010:
Load up cyanogen or something thing to get rid of the encryption and reflash
[BLISS ROMS Development] Othoric:
I'm also on a Verizon bought (and branded[emoji20] ) Nexus 6. Not that it really matters I guess, since all Nexuses are the same. But anyways, the last build that worked for me properly was one of the 5/18 builds. I also dirty flash and use code blue kernel. Of course I ALWAYS make a nandroid before flashing anything, just in case. Its saved me a lot of time and trouble.
[BLISS ROMS Development] ffchampmt:
Sadly, I do need to retain encryption for work stuff that's on the phone.

Sent from my Verizon Nexus 6 running BlissPop
[BLISS ROMS Development] nemofbaby2010:
Reeadd it after you reflash while setting up I do it all the time, I have a flashing addiction lol
[BLISS ROMS Development] RanceJustice:
I know TeamBliss is taking their time and going through a major reworking of BlissPop. I hope that the following can be incorporated as we have some great new news - The Nexus 6 WiFi Calling update is being rolled out! It is noted as being a 5.1.1 version, with the build being LYZ28E! https://support.t-mobile.com/docs/DOC-18109 . There are threads discussing this in general, of course. I've already linked to the official CM12.1 thread, so I hope that it will soon be incorporated into CM. Just giving the Bliss devs a headsup too! Enjoy everyone; if I am given the chance, I'll see if I can pull the URL for the OTA; as of yet, I've not gotten my update notification.
[BLISS ROMS Development] bunnypilot281:
I just tried to flash blisspop, coming from benzo. The boot was taking 20+ minutes nothing happpened. Help? Thanks.
[BLISS ROMS Development] nemofbaby2010:
Flash a kernel
[BLISS ROMS Development] minieod:
im on 5/6 gapps and still having the issue, only came about on the 5/21 bliss rom install
[BLISS ROMS Development] RanceJustice:
Just a heads up to TeamBliss, someone has pulled the OTA update for the 5.1.1 (T-Mobile build) LYZ28E and made it available! http://xdaforums.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 . As of yet, ROMs to be built on the "everyone else" version of 5.1.1 LMY47Z don't seem present. I assume that BlissPop will hopefully be built on one of these new WiFi Calling compatible versions, and at least won't overwrite any radio/baseband/bootloaders etc.... from those of us who need the LYZ28E version.

Edit: I have read that on other posts, those who are using the absolute newest gapps (built it themselves with the brand new Google Play Services) have fixed the issue. I am guessing Banks and whatnot will incorporate these new fixes ASAP; if you can't get things working with old Gapps, then I suggest waiting until a 5/23 or newer Banks Gapps. Maybe that will have the fix.
[BLISS ROMS Development] Joshuastrive:
Volte T-Mobile Confirmed working.

Nexus 6 Owner here reporting that Volte HD Calling is working. At least when calling a metro PCs or other Tmobile number HD Calling seems to work. Also I wasn't able to flash the latest nightly. Got stuck in a bootloop
[BLISS ROMS Development] WhiteEVO:
I'm using the latest 5/22/ banks and the google play services prob is worse than ever...anyone have a link to an older ver of gapps?
[BLISS ROMS Development] Burkettacb:
Hi Gents. Since many are unsure of the Gapps issues. Google just released an updated google play services, one that presumably fixes the GPS lock issue which was causing the FORCE CLOSES ON GOOGLE PLAY SERVICES. If you didn't know, switching your device location from high accuracy to device only and rebooting should stop your issues. But here's your "fix." Many have confirmed force closes have stopped since updating. CHEERS

http://www.apkmirror.com/apk/google...ices-7-5-68-1952143-430-android-apk-download/