yashsingh1/xdaforums huggingface dataset:
[BLISS ROMS Development] buschris:
so far, so good on 5-09. I haven't had a call to test but no FC and no reboots so far *knock on wood
[BLISS ROMS Development] BakedFiend:
When I dail the number XXX-XXX-XXXX it shows that number for the duration of the call. But, when you check the recents call log it shows 'Unknown'. I did edit out the acutal number in the screenshots.
[BLISS ROMS Development] ph0tiC:
Just curious but how are you flashing/wiping when you flash? System/data/cache/davlic? How are you restoring settings? Sorry if its a dumb question :/
[BLISS ROMS Development] BakedFiend:
The above photos are just from a clean flash. I didnt even enter my google account or restore anything. I always do a clean flash.
[BLISS ROMS Development] apophis9283:
can you go into your build.prop and look for force eri from xml. See if its set to true, if it is set to false, reboot and see if that does anything
[BLISS ROMS Development] BakedFiend:
It is set to true.
[BLISS ROMS Development] apophis9283:
set it to false and reboot
[BLISS ROMS Development] BakedFiend:
Changed to false. Still displaying as unknown
[BLISS ROMS Development] apophis9283:
Im wonder if this is the issue. If i remember correctly it was merged aroound the same time
[BLISS ROMS Development] BakedFiend:
Let me know if you would like me to test anything else for you.
[BLISS ROMS Development] apophis9283:
I will, if you want you can take a look

https://github.com/TeamBliss-LP/and...mmit/14cacf6832c60a54e777027c812a61e34ba7a35b

I also found maybe another culprit. I reverted it too
[BLISS ROMS Development] BakedFiend:
Okay cool. Do you want me to try and test something?
[BLISS ROMS Development] apophis9283:
It takes about 35 minutes to compile and almost 10 years to upload because living in the country can suck. After that ill have a build for you to test
[BLISS ROMS Development] BakedFiend:
Okay no problem. I will be around.
[BLISS ROMS Development] apophis9283:
Had some errors to work through. I looked at your log nothhing relevant to the issue. It shows you starting the volte call but no more usuable info after that.
[BLISS ROMS Development] BakedFiend:
Oh okay. Let me know if there are any logs I can grab for you to help narrow it down
[BLISS ROMS Development] esincho:
Sooooo just in case any one comes across the auto rotate problem I reported earlier, I found through a Google Search, a lot of people have this issue. The fix? Slapping the back of the phone hard. (seriously, it works)
[BLISS ROMS Development] apophis9283:
Im trying. I really dont know whats causing it. Could it be that dialer doesnt know how to handle volte calls? Im trying, but not sure exactly where the issue lies.
[BLISS ROMS Development] farms:
Just installed on a verizon nexus 6 with banks gapps, during the setup wizard i get instant FC's and cannot do anything?
[BLISS ROMS Development] BakedFiend:
Oh I know you are trying. I just want to help any way I can. I don't mean to rush you or anything.
[BLISS ROMS Development] apophis9283:
Did you wipe everything? Did you flash another kernel when you flashed the rom?
[BLISS ROMS Development] farms:
wiped everything, still running stock kernel from cleanrom
[BLISS ROMS Development] apophis9283:
if you flashed the zip it would have flashed over the cleanrom kernel.
[BLISS ROMS Development] ac3theone:
Try a different gapps, banks always gives me problems
[BLISS ROMS Development] farms:
just got it going, installed the prior version of the rom and got past it. I noticed Volte isnt enabled on this rom, any way to get that fixed?
[BLISS ROMS Development] apophis9283:
who is your service provider
[BLISS ROMS Development] farms:
Verizon Wireless
[BLISS ROMS Development] apophis9283:
As far as i know, tmobile is the only one on the rom that can get it. dont know why. the op has verizon and hes been working on it
[BLISS ROMS Development] farms:
i gotcha, no worries.... has anyone had issues with the keyboard not popping up properly, as well as the back key in the bottom left not working right :/
[BLISS ROMS Development] apophis9283:
here guys. this is just another shot in the dark, sorry i havent got it yet, if it worked at one point and isnt working now then something got merged that broke it.

https://www.androidfilehost.com/?fid=23991606952601175
[BLISS ROMS Development] BakedFiend:
Downloading now, will report back with results

Edit: still showing unknown
[BLISS ROMS Development] apophis9283:
Do you know if its happening on other roms? Im pretty burnt out at the moment. Gonna take a break.
[BLISS ROMS Development] BakedFiend:
It doesn't happen on Benzo Rom, Chroma, or Euphoria.
[BLISS ROMS Development] bdorr1105:
What is the best tool to use to install the framework for decompile the systemUI specifically for this ROM......Have had trouble with the latest version of apktool
[BLISS ROMS Development] aalupatti:
Anybody with issues with the calls getting disconnected . The signal suddenly drops and there is loss of network. Network comes back in a few seconds. I am on rogers ( Canada ) now.

Only happens during calls and not when using data.

Thanks
[BLISS ROMS Development] aalupatti:
What ever u did worked. 3Minit battery works...

For everyone here who wants 3minit battey mod to work see the post below by [MENTION=1195110]bdorr1105[/MENTION]

Just flash the zip in recovery and voia. This opens the door to hundereds of different battery styles.

see screen shot
[BLISS ROMS Development] apophis9283:
nvmd
[BLISS ROMS Development] minieod:
cant...handle...the app drawer button...off centered....ahhh

love it otherwise....is that all DPI or nova/launcher padding changes?
[BLISS ROMS Development] ffchampmt:
For those with VOLTE issues in the Euphoria thread several users flashed a very stock based ROM, turned the flag on, enabled it in the call settings, then reflashed the custom ROM and got VOLTE working. This did work for me on Verizon. I dont have it working now but I haven't had time to try it with this ROM.

Sent from my Verizon Nexus 6 running Euphoria
[BLISS ROMS Development] chrristin:
Yes! I am having this issue as well!

Also if i press twice on the end call button, then it FCs. ( After a call, press the end button twice, it happens more often than not ).
[BLISS ROMS Development] aalupatti:
off centered app drawer.. ;) ... Actually I was in the process of changing out some settings.

I use DPI 480 and also decrease the size of the icons in nova
[BLISS ROMS Development] apophis9283:
I think its time for me to move on. Do something else. Not worry about Android anymore. Its been fun. Im actually going to have my account disabled. My son is going to start his first year of school, I would like to start hanging out with the wife more. Hell, even work more over time for more money. I will of course still make my own builds as I like doing it. Thank you all for your patience with me and Patrick will completely take over from here on out. Android has just stopped being fun. I always swore the day I didnt enjoy it, I would stop. I hope the best for you all. Have fun!
[BLISS ROMS Development] sonofevil77:
The reboot on incoming call is back. Noooooooooooooo lol.

Chromatose
[BLISS ROMS Development] caspersfi:
Do what you gotta do for you and the family. I've seen plenty of guys get burnt out on Android. It's time consuming. Especially if you care about the users and want to help out as much as you can.

It's just a hobby, nothing more nothing less. Take a break for a while, and hopefully you'll be back to help the users out and some point. Thanks again for everything.
[BLISS ROMS Development] PhattyMcGee:
From my experience, it's kernel related. I use Code_Blue kernel and haven't had incoming call reboots since I switched. I'd gotten the reboots on stock, vindicator, and despair, but never on code_blue. Give it shot and just see if works for you. http://www.engstk.org/code_blue/
[BLISS ROMS Development] sonofevil77:
Yeah I went back to blue after flashing the 5-11 build. My phone was getting hot on code blue so I went to stock for a few builds.
[BLISS ROMS Development] akellar:
Again?
[BLISS ROMS Development] XDAcube:
Help?

Ok so i want the latest blisspop on my phone i flashed it yesterday and now i got a notification saying theres a rom update. i swiped it away :confused: anyway now i want the lastst do i just flash the new rom zip and the kernel? is that it?
[BLISS ROMS Development] droidxxxxx:
Being this is the official rom will there be any more updates to it? I'm kind of excited about being off of a beta.
[BLISS ROMS Development] droidxxxxx:
Well, nevermind, I can't use it because VoLTE doesnt work on tmobile.... drops to 3g when I place a call..strange because it works on Benzo rom..
[BLISS ROMS Development] abjexstallion:
It does work. With issues, but it does. And it stays on "LTE". If you reboot, make sure to go to settings/mobile networks and check and uncheck advanced lte settings. If you're the one making the call, you'll see the bug on the recents call tab saying " unknown".
[BLISS ROMS Development] CrashTestDroid:
I can report incoming call reboots on 20150512-0809 build and the last few nightlies, with stock, Vindicator 2.3 and Blue v222 kernels. Glad it's working for you tho.
[BLISS ROMS Development] aalupatti:
I would recommend flashing the stock google image 5.1 and then coming back and flashing the ROM.

Solves most of the telephony related issues
[BLISS ROMS Development] ManikandanGuru:
Need Blurred Lockscreen

Hi Devs,

I wonder if the blurred lockscreen available for the upcoming build. Because Cyanogen OS 12.0 got it. It looks amazing and treat to watch.

Hope any Developer look into this.

Waiting for Blurred Lockscreen in next Blisspop build
[BLISS ROMS Development] nicholaschum:
Most things in Cyanogen OS 12.0 are closed source. Especially App Themer.

---------- Post added at 09:59 AM ---------- Previous post was at 09:57 AM ----------

Just a small report, clean flashed on latest BlissPop 3.2 - 12052015 build with code_blue kernel. Everything is working flawlessly!

As I'm not from US, there's no problems with calls/VoLTE (I believe on ROGERS) on my end.
[BLISS ROMS Development] Othoric:
Hi, I'm new to Blisspop. I'm coming from Chroma because I wanted to try out a CM based ROM and I absolutely love it so far. Now when I used Chroma, I also used Hells Core kernel and was wondering if anyone who has used Blisspop for awhile had any suggestions on kernels to use. I do some gaming so I like kernels that give very good performance as well as good battery life.
[BLISS ROMS Development] e29:
Give zen kernel a try
[BLISS ROMS Development] rush420:
I've been using elemental x since I first flashed Bliss
[BLISS ROMS Development] nicholaschum:
[MENTION=5346868]pjgraber03[/MENTION] and I are both using code_blue after trying ElementalX, Lean, Vindicator, Franco, Sensei.

I give up on the kernel hunt, as long as it doesn't give me random reboots and lasts long on standby/SOT, I'm happy.

You should give code_blue a try: http://www.engstk.org/code_blue/shamu/
[BLISS ROMS Development] ac3theone:
Hello core give amazing battery life and performance but it has the reboot on call issue sometimes. Right now im using code blue kernel, all is good but I like the blisspop kernel and helps core better because they give better battery life
[BLISS ROMS Development] Othoric:
Thanks. I guess I'll give code blue a try. I've heard good things about it also!

---------- Post added at 07:20 PM ---------- Previous post was at 06:28 PM ----------

Getting ready to flash code blue now. Do I also need to dirty flash ROM before flashing the kernel? And do I need to make any changes to kernel adiutor before doing so? Thanks very much for the help!
[BLISS ROMS Development] nicholaschum:
Nope, just flash it on top.
[BLISS ROMS Development] BakedFiend:
Im still seeing 'Unknown' caller ID on latest build. Want me to try and get logs somehow?
[BLISS ROMS Development] CrashTestDroid:
I've done that 3x now with LMY47D, LMY47E and LMY47I, even wiped userdata, then cleanflashed Bliss. Always the reboots when a call comes in and I don't get it in the first 1 or 2 rings. There are 2 roms that don't reboot: Euphoria has totally different APNs for my provider Rogers, and Spring has a different kernel from other CM-based roms. One day I'll be near a computer when the reboots happen and grab a log of it.

--

update after a full day, took a few calls before the incoming call reboot happened. Seems like it happens when shamu has been sleeping for a long time. Stock kernel, no mods, Slim GApps 20150511, current modem 2.98
[BLISS ROMS Development] blueyes:
Getting it working isn't the problem, its getting it to stick on reboot.
[BLISS ROMS Development] BakedFiend:
what?? Sorry i am confused
[BLISS ROMS Development] abjexstallion:
Sorry... Just saying that i'm having tje same issue lol. I've been in a hospital for almost a week and i just noticed what i posted. Even i tried to hit thanks to your post and it was denied!

---------- Post added at 08:29 PM ---------- Previous post was at 08:24 PM ----------

So [MENTION=3605033]nicholaschum[/MENTION] Does your voLTE settings persists after a reboot? And what about the "unknown" bug on dialer when you make a call?
[BLISS ROMS Development] BakedFiend:
oh haha, no big deal! I just want to help get to the bottom of this for anyone who has it and seeing as i am not a developer, all i can do is help with logs and testing
[BLISS ROMS Development] XDAcube:
Help?

How do i update my rom? i have a older version and when i try the OTA it boots into twrp but nothing runs? also do i just download the latest rom from here and flash it and my kernel (LeanKernel)? do i need to wipe cache? or what first please help thx.
[BLISS ROMS Development] lotddragon:
When you download the ROM, from the website, you can dirty flash the ROM then flash your kernel. No need to wipe anything but if you start getting some issues, try a clean install.
[BLISS ROMS Development] XDAcube:
Ok thanks!
[BLISS ROMS Development] aalupatti:
Does anyone have v4a working after flashing the zips ?

I cannot get it work. Everything installs but nothing happens when music is playing and driver status is saying no for enabled and no for processing

Please advise
[BLISS ROMS Development] nicholaschum:
Yeah, sorry, it didn't work on VoLTE, something happened and it just switched back to 3G.

Since I don't get VoLTE anymore, I can't test the "unknown" bug on dialer, but normal calls work fine.
[BLISS ROMS Development] Macusercom:
When I wake up my device from sleep/standby my homescreen flickers for a short time and then I see the normal lockscreen. It happens only sometimes, but is very annoying. The display activates itself and then it suddenly flashes. Is this a known bug? Happened on BlissPop based on 5.0 too on the OnePlus One. It's still there and I did a clean flash.
[BLISS ROMS Development] Mistertac:
I do on the build from the 12th. Works great.
[BLISS ROMS Development] aalupatti:
What files did flash ?

Also what kernel ?
[BLISS ROMS Development] Mistertac:
I have been using this Viper zip for a while now :

https://www.dropbox.com/s/qqq066z9ac2mewv/viper_v2.3.4.0 - remove fx build fix.zip?dl=0

Also I'm currently on a test version of Hells Core Kernel, but I think he still has Hells baked in as stock kernel?! Maybe I'm wrong though. Also, not sure it matters anymore but I have SELinux set to Permissive as well.
[BLISS ROMS Development] CrashTestDroid:
Got a log from the last incoming call reboot.

E/AndroidRuntime( 3451): FATAL EXCEPTION: MessagingNotification.nonBlockingUpdateNewMessageIndicator
E/AndroidRuntime( 3451): Process: com.android.mms, PID: 3451
E/AndroidRuntime( 3451): java.lang.IllegalStateException: unstableCount < 0: -1
E/AndroidRuntime( 3451): at android.os.Parcel.readException(Parcel.java:1554)
E/AndroidRuntime( 3451): at android.os.Parcel.readException(Parcel.java:1499)
E/AndroidRuntime( 3451): at android.app.ActivityManagerProxy.refContentProvider(ActivityManagerNative.java:3401)
E/AndroidRuntime( 3451): at android.app.ActivityThread.releaseProvider(ActivityThread.java:4891)
E/AndroidRuntime( 3451): at android.app.ContextImpl$ApplicationContentResolver.releaseUnstableProvider(ContextImpl.java:2545)
E/AndroidRuntime( 3451): at android.content.ContentResolver.query(ContentResolver.java:519)
E/AndroidRuntime( 3451): at android.content.ContentResolver.query(ContentResolver.java:422)
E/AndroidRuntime( 3451): at android.database.sqlite.SqliteWrapper.query(SqliteWrapper.java:59)
E/AndroidRuntime( 3451): at com.android.mms.transaction.MessagingNotification.addSmsNotificationInfos(MessagingNotification.java:926)
E/AndroidRuntime( 3451): at com.android.mms.transaction.MessagingNotification.blockingUpdateNewMessageIndicator(MessagingNotification.java:329)
E/AndroidRuntime( 3451): at com.android.mms.transaction.MessagingNotification$1.run(MessagingNotification.java:290)
E/AndroidRuntime( 3451): at java.lang.Thread.run(Thread.java:818)

Is that helpful or should I be doing something different?
[BLISS ROMS Development] CrashTestDroid:
FINALLY I got a useful kernel log. When incoming calls trigger reboots there's no /proc/last_kmsg so I had to babysit shamu while she was plugged in running adb shell, output of /proc/kmsg going to terminal.

Kernel log for your viewing pleasure. It doesn't always reboot so I thought maybe a race condition or driver malfunction. Only happens on CM-based roms too.

Ideas/suggestions welcomed cuz I have no idea where to go from here.
[BLISS ROMS Development] jdee323:
Anybody able to get the new xposed working on this rom yet?
[BLISS ROMS Development] aalupatti:
Working great here
[BLISS ROMS Development] jdee323:
It's working now, i installed the app first before flashing the zip. All i needed to do was uninstall the app and then reinstall.
[BLISS ROMS Development] WhiteEVO:
For the life of me I cant get the newest 3.3 5/14/15 build to install. it just keeps spinning at the Bliss Pop screen...
[BLISS ROMS Development] gregou:
The same thing happened for me, i installed the last update and it's booting on the BlissPop screen and that's it.

I'm confident that a next update will fix it very soon ;)
[BLISS ROMS Development] ManikandanGuru:
My phones' dialer stopped working after the call ended.

Can anyone suggest what's the reason?

Exception log below.

java.lang.NullPointerException: Attempt to invoke virtual method 'boolean com.android.incallui.ProximitySensor.isScreenOffByProximity()' on a null object reference

at com.android.incallui.InCallActivity.dispatchTouchEvent(InCallActivity.java:528)

at com.android.internal.policy.impl.PhoneWindow$DecorView.dispatchTouchEvent(PhoneWindow.java:2594)

at android.view.View.dispatchPointerEvent(View.java:8667)

at android.view.ViewRootImpl$ViewPostImeInputStage.processPointerEvent(ViewRootImpl.java:4135)

at android.view.ViewRootImpl$ViewPostImeInputStage.onProcess(ViewRootImpl.java:4001)

at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:3556)

at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:3609)

at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:3575)

at android.view.ViewRootImpl$AsyncInputStage.forward(ViewRootImpl.java:3692)

at android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:3583)

at android.view.ViewRootImpl$AsyncInputStage.apply(ViewRootImpl.java:3749)

at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:3556)

at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:3609)

at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:3575)

at android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:3583)

at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:3556)

at android.view.ViewRootImpl.deliverInputEvent(ViewRootImpl.java:5819)

at android.view.ViewRootImpl.doProcessInputEvents(ViewRootImpl.java:5793)

at android.view.ViewRootImpl.enqueueInputEvent(ViewRootImpl.java:5764)

at android.view.ViewRootImpl$WindowInputEventReceiver.onInputEvent(ViewRootImpl.java:5909)

at android.view.InputEventReceiver.dispatchInputEvent(InputEventReceiver.java:189)

at android.os.MessageQueue.nativePollOnce(Native Method)

at android.os.MessageQueue.next(MessageQueue.java:143)

at android.os.Looper.loop(Looper.java:122)

at android.app.ActivityThread.main(ActivityThread.java:5347)

at java.lang.reflect.Method.invoke(Native Method)

at java.lang.reflect.Method.invoke(Method.java:372)

at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:911)

at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)

at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:117)
[BLISS ROMS Development] sjkramer29:
Glad I wasn't alone on this, I have to give credit to the BlissPop team this Rom paired with ElementalX Kernel is incredible, hands down best Rom I've used on the Nexus 6.
[BLISS ROMS Development] baldingone:
+1
[BLISS ROMS Development] Macusercom:
Asking again: when I wake up my device the screen sometimes flickers with the unlocked screen. I'm experiencing this even on BlissPop 3.3 and it is so annoying that I consider switching back to CM12.1 Nightly :S

Anyone seeing this too? I did a clean flash, nothing's changed :(

[YOUTUBE]eb9rijLbjIE[/YOUTUBE]
[BLISS ROMS Development] abjexstallion:
So latest 3.3 is it or isn't working?
[BLISS ROMS Development] WhiteEVO:
Isn't...
[BLISS ROMS Development] Macusercom:
It is, but you have to upgrade from 3.2 to 3.3. Clean flash of 3.3 won't boot :S
[BLISS ROMS Development] WhiteEVO:
Hmmmm, I tried that... It didn't work...

---------- Post added at 02:19 PM ---------- Previous post was at 02:17 PM ----------

Let me make a backup and it try again...
[BLISS ROMS Development] Macusercom:
Tested it. You have to flash 3.2, boot to the lockscreen and then dirty flash 3.3. This works. Flashing 3.2 and then 3.3 without leaving recovery won't work.
[BLISS ROMS Development] WhiteEVO:
Restoring my backup, did what you said and still cant get it to load...
[BLISS ROMS Development] rush420:
I got it working on multi ROM with clean flash also flashed xposed an v4a working OK so far
[BLISS ROMS Development] WhiteEVO:
I've tried every which way to install 3.3 with no luck... I'll wait till it gets resolved.
[BLISS ROMS Development] 875295391:
isn’t work
[BLISS ROMS Development] ffchampmt:
Mine says "processing: no and sample rate is 48000"

I can hear a difference when I run the eq though. Did you do anything other than flash the zip and install driver? (downloaded v4a from the addons in phone settings)

Edit: checked force v4a and it is processing.

Sent from my Verizon Nexus 6 running BlissPop
[BLISS ROMS Development] pjgraber03:
Sorry Guys

Hey guys sorry I have been MIA.... I got pretty sick and haven't done much of anything... Feeling a little bit better and i'm pumping out an update now... I will look into getting viper reintegrated into the rom.... we used to have to untill 5.1
[BLISS ROMS Development] aalupatti:
Thank you so much for looking into the V4A.

Get well soon.
[BLISS ROMS Development] WhiteEVO:
I was finally able to get 3.3 installed, but I had to do a full wipe including internal storage.

---------- Post added at 08:34 PM ---------- Previous post was at 08:13 PM ----------

Hahaha! Now I cant get the 5-15-15 3.3 to boot up...stuck at the bliss pop screen again!!!
[BLISS ROMS Development] gdonanthony:
please make the keyboard input at stock messaging app change color also when applying themes... because when i apply black themes while the font color will change to white i cant see the input text, all white (background and font color)

and kernel adiutor got a new update in playstore but when i update the app, an error will occur
[BLISS ROMS Development] Othoric:
Just wanted to add that I attempted to dirty flash the 5-15-15 build over the 5-12-15 build and I also got stuck at the Blisspop boot animation.
[BLISS ROMS Development] Burkettacb:
I always clean flash. Successfully running 3.3 5/15 release. Running smooth as glass, battery is still a little wonky on life, but I'm heavily using it. No reboots from calls. Clean wiped (cept internal,) installed banks dynamic gapps and latest 240 codeblue kernel alongside bliss ROM.