yashsingh1/xdaforums huggingface dataset:
[Nexus 5X Android Development] ideaman924:
Hey all! A new update is going out today.

Changes?

- r44 (finally!)

- Some improvements here and there

There are a couple of outstanding bugs I'm still trying to track down. In the meantime, try out the new build and tell me if you notice anything amiss.
[Nexus 5X Android Development] jeremywh7:
Dirty flash 0802 then 8/3 gapps; still had to switch to the other ims.apk to get calls working of course. Looks good so far!
[Nexus 5X Android Development] ideaman924:
Heya can you link me the ims.apk you used? Might be able to do something about that.
[Nexus 5X Android Development] deMonte01:
Hello. Did Someone discover non-working headset after last update? (5.8.)? After plug-in the headset I can hear somthing like crack-bubbles-sound-in-the-distance, but then nothing. Mic also does not working.
[Nexus 5X Android Development] jeremywh7:
I believe it is from here:

https://gitlab.com/Pixel2ROM-P/device/lge/bullhead-vendorimage/tree/pie/vendor/app/ims

Based on this, as I am using mh0520's posted file:

That is where the Pixel3ROM vendor/ repo points to. :)
[Nexus 5X Android Development] ideaman924:
Hi all! A Beta release is going out today with some important changes. Please read this fully before continuing.

First of all, this is a Beta release, which means it will not be on our official download server directory. You cannot obtain this release with an OTA update (unless I release it officially after testing.) And, as with every Beta release, there are chances of bricking your device. So please do not flash this on a production/daily driver device.

With this build, I've changed some of the connectivity/cellular parts. Most notably, the ims.apk will no longer make the phone crash during a call. There are a couple more tweaks here and there.

If you had problems before with cellular connectivity, please test this build and report whether or not the problem was fixed for you. If you did NOT have problems with cellular connectivity, please test this build anyway because the changes might have broken existing devices. I'm guessing that the breakage comes from the different variants of the Nexus 5X and that's why the cellular portion isn't playing nice. You should check LTE connectivity and call connection (the ability to successfully initiate a call, confirm that audio is working from the earpiece, confirm that the recipient can hear you over the microphone/speakerphone, etc). If any of these is NOT working, please file a bug report in this XDA thread WITH a logcat.

Again, you flash this at your own risk. Download link is here: https://downloads.blissroms.com/BlissRoms/Beta/bullhead/
[Nexus 5X Android Development] jeremywh7:
Ha, where's the fun in that!?! :P

Yup, calls now work by default - thanks!

One issue I'm having now though; Google Photos no longer opens. Anyone else having that issue on the beta? Last build was fine. I did also update Gapps though, be so that could be why.
[Nexus 5X Android Development] ideaman924:
That's great, because that means now I can move along with the general availability release.

Regarding Google Photos not opening, not sure about that, please attach a logcat. I don't use Google Photos anymore after I found out how much data Google is retaining with Google Takeout. Really creepy! But anyway, if it's causing an issue please send me a logcat.
[Nexus 5X Android Development] jeremywh7:
Attached... thanks! I tried opening it directly 3 times, then once via Camera. Just exits.
[Nexus 5X Android Development] ideaman924:
Hmm, found the issue. Says it can't find a drawable (this is most likely an image that is displayed in-app, such as a save icon.)

Where did you get Google Photos from? (Gapps or Play Store)

(if from Gapps) Did you update it in the Play Store?

Can you try uninstalling the app and then reinstalling it?

Also, which Gapps are you using? Thanks!
[Nexus 5X Android Development] jeremywh7:
It was installed from Gapps. I used this:

open_gapps-arm64-9.0-stock-20190810.zip

Btw, I had also previously tried clearing storage and cache to no avail. It does not have the "uninstall updates" option available, and I see the latest play store version is from July 25th. Aug10 is currently still the latest Gapps. Try the next one when available...
[Nexus 5X Android Development] ideaman924:
It's either part of the drawable library of Android or bundled with the app itself. My advice is to try a different apk, preferably from the Play Store, so you know your local install is good. And yes, storage and cache deletion will have no effect as it's failing to find the drawables required to launch.

Although, I don't see a problem with your Gapps... OpenGapps, fairly recent, correct architecture and Android version. Try getting something like a nano (without Google Photos) and then install the application from the Play Store. If it still crashes then we have a definite problem.
[Nexus 5X Android Development] ChemBot:
I've been trying out the beta and I'm having the same issues as before when I replaced the ims.apk on previous releases with T-Mobile. LTE data works, I can make calls, but I can't receive calls. I started playing around with my Preferred network type and noticed that in some modes I was able to receive calls. Usually when a call is started the network switches from LTE to H+ and then back to LTE after the call ends. This works normally when I make an outgoing call, but when receiving a call this doesn't always happen and I don't receive calls. I found that setting the Preferred network type to one that does not include LTE allows me to receive calls reliably, but obviously with much slower H+ data rates. Attached is a logcat of me switching to various network modes and making/receiving calls for 10-15 minutes.
[Nexus 5X Android Development] ideaman924:
Very interesting. Usually carriers with VoLTE have this "behavior" where phones switch from LTE to 3G (H+, HSPA, etc) in order to provide more bandwidth for the call. (Don't quote me on this, though!) Obviously we live in a world without standards and carriers love differentiating just for the sake of it so we have a lot of different implementations. I remember it was a huge issue back in 2015/2016 in Korea - carriers were advertising how their devices would "maintain" LTE while calling. Of course, this wasn't really special because you could force LTE by changing the Dialer settings (Samsung provided a toggle).

Now, I am not sure if this "feature" is enabled by the carrier, or the phone. You might be wondering what the heck this has to do with your case, but hang on for a second. If (theoretical) this is a carrier-side feature, then the carrier (again, theoretically) instructs your phone to switch from LTE to 3G, and then passes on the call. If this is a phone-side feature, then the phone automatically switches from LTE to 3G when there is an incoming call. Problem is, I have no idea of knowing since I'm not an expert in radio (:P) If it's the former, then it's a matter of figuring out why the phone *won't* change from LTE to 3G - maybe it doesn't understand the instructions from the carrier? Maybe the switchover disrupts cell traffic so the calls bounce? If it's the latter, then maybe the calls are bouncing because the phone won't automatically transition from LTE to 3G and begin the VoLTE call session, or some other issue is present.

I'll take a look at your logs but can't promise anything. This is not something I've experienced here (calls work OK most of the time :P)

EDIT: Took a quick look. Nothing stands out currently. I see some problems with Jibe (Google's RCS service) but I don't think this is the problem as you mentioned you're on T-Mobile and that incoming calls are failing. Don't see any major issues...
[Nexus 5X Android Development] ChemBot:
Is there anything I can do to help you pinpoint the issues I'm having? Additional / more verbose logs? Testing different network modes or different combinations? Maybe my sim card is too old to support your implementation. I can try swapping my sim with my girlfriend's iPhone, also on T-Mobile but much newer. It's possible her phone plan supports volte while mine does not.
[Nexus 5X Android Development] ideaman924:
Right now the logs point every which way so it's hard for me to figure out what is causing the issue :P

Here's what you can try. I'm not sure if I can fix this though, so if you don't want to or if you don't have the time then it's totally OK not to do this.

1. Boot into safe mode to disable logging from all other apps. To do this, hold the power button, and then hold down either the "Restart" or the "Power Down" option until you get the prompt "Reboot to safe mode?"

2. Once the phone is in safe mode, verify that it connects to the mobile network, and make sure that adb is on (sometimes it turns off in safe mode).

3. Begin capturing logcat.

4. Call the 5X from another number. Try and call it only once, or if you can't replicate it in one try, then try and replicate it in the lowest number of attempts possible.

5. Once you've successfully replicated the issue, stop the logcat capture ASAP and post it here.

Again, totally voluntary. You don't have to do it if you don't want to :D
[Nexus 5X Android Development] ChemBot:
I was bored on my lunch break at work and away from a computer so I went a different route. I thought it was odd that it was switching to h+ during calls and looked into exactly what network mode it was switching to. According to the network diagnostic tool (by dialing *#*#4636#*#*) it switches to UMTS as the voice network and HSDPA as the data network. It also said VoLTE is provisioned, but if I set the preferred network to only LTE calls immediately fail. After googling for a bit I found this page:

https://xdaforums.com/nexus-5x/themes-apps/enable-volte-flashable-nougat-phone-t3693152

I first tried adding the "persist" lines someone mentioned a few posts down to my build.prop with your beta release, but that didn't help with receiving calls. Then I checked the flashable zip from the first post and it contained a replacement ims.apk along with some other stuff, but I remembered that you said the beta isn't using that anymore. So I downloaded the last Bliss release from 08-02, replaced with the known good ims.apk from this thread, and flashed that zip on top. Now I can make and receive calls reliably with LTE enabled, but it still switches to UMTS voice network during calls. It also never showed the enhanced LTE option in the menu, but I assume that's because the zip was made for an older ROM. So does that mean I'm not actually getting VoLTE during calls? Either way, for now I don't need to choose between receiving calls and LTE data. I'm happy it works, but not sure what to make of my solution.
[Nexus 5X Android Development] ideaman924:
That really is a weird solution, lol! I'll take a look at the contents of that zip and see what it modifies.
[Nexus 5X Android Development] bharaniboss:
Proximity sensor is not working

my proximity sensor is not working
[Nexus 5X Android Development] ideaman924:
How... is... it.. not.. working...? Please... attach... a... bug.... report... and... be... more.. specific.... about... your.. issue...
[Nexus 5X Android Development] o0vampire0o:
Hi guys is there a way for personalize the notification led blink for each app?
[Nexus 5X Android Development] berom:
Hello, what's the difference between this build and pixel experience? I see more changes on the builds provided here but less discussion.

Are you also affected by ims issues in this build? Is the ims.apk a sustainable solution for it? I had some issues on pixel experience roaming on some network in europe.

Looks like there will not be a LineageOs build due to this ims and Volte issue (https://xdaforums.com/showpost.php?p=80081956&postcount=1623).
[Nexus 5X Android Development] jeremywh7:
Read the past couple pages. ;) An older ims.apk from Pixel3ROM has been pulled into the 02aug2019 build to fix call issues for certain carriers using that protocol.

I previously used PE but always had lots of random reboots (1-5 a day) while Bliss has been much more stable (1-3 a week).
[Nexus 5X Android Development] :
No gestures navigation option

There doesn't seem to be any support for stock android pie gestures and the recents is in oreo style.
[Nexus 5X Android Development] berom:
Thanks Jeremy, I had a look at the previous posts and it looks like this is on the way to be improved/fixed. This could help the whole Nexus 5x on pie community.

On my end, I don't have that much reboot with PE on a regular basis with my phone provider. I only have them when using 4g when roaming in Europe. But I would really like to avoid them.
[Nexus 5X Android Development] ideaman924:
Not yet, I think.

These random reboots shouldn't be happening with current builds as the kernel is very conservative. Previously we had issues with the kernel but now it should be quite stable.

Yes, it's the default for the 5X. To enable the Pie style gestures, go into Settings, scroll all the way down to System, tap on Gestures, and then enable "Swipe up on Home button" to try the new experience.

To whoever posted about the Google Photos issue, yes I've confirmed it, the app does indeed crash with the latest version, *not sure why*. It's missing a drawable so I have no clue as to what the heck it's missing. My guess is still with a faulty apk or something else specific to bullhead. I'll keep digging.
[Nexus 5X Android Development] jeremywh7:
It was me; actually a day or two after we discussed it, I got a "Google ____ Services/Framework" or something update, and it's been working fine since...but now my camera driver has issues sometimes. After a couple pics, it stops working, and then both the stock and Google Camera (6.3) will just exit when trying to run. Will retry on the new build shortly, and if I still have issues I'll get a log.

Edit: I just got a notification that "Lawnchair crashed!", which is odd since I'm using pixel launcher. It says "Java.Lang.IllegalStateException" and it's log content is attached.

Update: No issues with the camera nor Google Photos in this build. Also just updated to the latest Google Camera v6.3.020 beta, and still fine (though Video still doesn't work, but never has with v6.3; video is fine with the stock camera app). Oh, and I see Themes are working now, along with the user-selectable accent color. Nice :cool:

Update2: Ambient Display is also now working. I noticed a language issue in the Bliss Themes creator; see pic...
[Nexus 5X Android Development] ive9th:
Hotspot Tethering Option Grayed Out

I am experiencing the same thing on my nexus. I have had the rom for about a month and to be honest, I dont know if it every worked because I was using another phone to tether for the last 30 days.

Id like to believe it worked at some point so I went back to one of my first backups and it didnt work there either. It also may be noteworthy that I have a nexus 5x on the slower cores because of the bootloop of death BLOD.
[Nexus 5X Android Development] ideaman924:
Cool, thanks for the input! The incorrect language in the Bliss Themes creator might be due to incomplete commits - it will probably be addressed next build.

I'm not sure what's going on with the tether option, but I'll try and check out if I can reproduce the issue.

All right everyone time for an announcement :D

As you all know, Q dropped two days ago with the moniker Android 10. What does that mean? It means that I will be shifting gears toward creating Q builds for our bullhead.

That means reduced development time on Pie - or even none. Some builds may eke out over the coming weeks, but they will gradually be phased out for Q.

For now we will keep this thread open. We will close the thread once a Q build is released for the 5X.

Finally we will no longer accept bug reports or feature requests. Kind of pointless when a Q release is right around the corner.

Thanks for using BlissRoms! And as a personal, developer stance, remember what happens to that guy who asks for the ETA. Don't be that guy. All right peace out
[Nexus 5X Android Development] jeremywh7:
Fwiw, I got a random reboot on the 20190822 build; it seems to always be related to using a music player and Google Maps, but possibly with only either. In this case though, I had both; music playing and using Maps. I've attached a zip with dmesg, anr, and ramopps files. I also attached a tombstone file for "name: CAM_img_msg >>> /vendor/bin/mm-qcamera-daemon <<<" from before (not related to the reboot), wondering if this might indicate why Google Camera crashes when trying to use video...?

Thanks for the update on A10; looking forward to it! ;)
[Nexus 5X Android Development] Pitel:
Move from LineageOS?

Hi,

since LineageOS 16 for our beloved bullhead will probably never happen, I'm considering moving to some other, more Pie/Q friendly ROM. What is the state of this Bliss ROM? Is it stable? No WiFi/camera/GPS issues? How about this list of tricky things, will those work?

Google Pay

Google Camera (HDR)

Magisk

Thanks.
[Nexus 5X Android Development] FinlayDaG33k:
Long wake time?

Hii there,

Thanks for making this ROM.

One issue though, is it a known thing that the device takes ages (can easily be half a minute) to wake at times?

I went to bed yesterday and had set an alarm.

When the alarm went off, I grabbed my phone, turned on the screen and had to wait a pretty long time for it to actually turn on for me to stop the alarm... all while the alarm was ringing...

This issue is prevalent every single morning I wake up or when I have not touched my phone for a little while.

When I use my phone regularly (like check it once every 10 mins or so), it works fine but when it actually goes to sleep it takes ages to wake.

Didn't have this issue with the stock ROM :\
[Nexus 5X Android Development] ideaman924:
Make sure you don't have an app muddling with wakelocks. It can cause the lock screen to show up slowly.

On my 5X this has never happened, but I get frequent bug reports about this from my users anyway. Sometimes it's not something that's ROM-related.

---------- Post added at 01:43 PM ---------- Previous post was at 01:42 PM ----------

No.
[Nexus 5X Android Development] FinlayDaG33k:
I don't seem to have any app that could cause this that I didn't have before flashing my ROM.
[Nexus 5X Android Development] ideaman924:
Clean flash? Does the same thing happen on a device with no apps installed? Are Gapps installed? What happens if you try the alarm without Gapps?

Please test the above things and report back if you can still replicate the issue. A video might be very helpful.
[Nexus 5X Android Development] FinlayDaG33k:
I have already done a clean flash but no result (it has always done this since I flashes Bliss last week or so).

I do have OpenGApps installed yes (though I did test it afterward without OpenGApps but the issue didn't solve itself).

I don't think it has to do anything with the alarm since this behaviour occurs every morning (I don't set an alarm every morning), when leaving for work (so having not used it again for a while) and when going back home (again, after having not used it for a while).

I have currently tweaked some settings in the Doze menu to not have it go into that "deep-sleep" state but I can't do too much testing and re-flashing because this phone is my daily driver :\
[Nexus 5X Android Development] ideaman924:
This is really interesting because I tweak the hell out of my phone with Opengapps and what not and have yet to seen this issue you're describing. A lock screen that takes a minute or so to appear is definitely not normal. I suggest going back to stock if it bothers you because Pie ROMs on the 5X isn't really daily-driver ready. Either some tweak or setting you have is messing it up, or your board has a hardware defect that is exacerbating the issue (maybe the eMMC chip is going bad).
[Nexus 5X Android Development] FinlayDaG33k:
I just came home again and immediately re-flashed my phone with the stock ROM since it lasted only two hours to bring my phone from a 100% charge to 26% charge and it runs like a charm again.

Quite a bummer it had to end like this because I want pretty happy with it until these issues popped up :\

Definitely will give it a try later when I don't rely on this particular unit as a DD.
[Nexus 5X Android Development] jeremywh7:
Since nobody else has, I'll mention that the 20190920 build is working a-ok; I'm mostly indifferent to the new icons, though I notice the battery text % isn't grayed out anymore.

I also noticed it's still on the Aug security patch, if that matters. Hope things are going well in 10-land. ;)

EDIT: And today there's a new thread for Bliss v12 Q-beta. ;)
[Nexus 5X Android Development] ideaman924:
Good eye! That's maintained by Jack now since I am no longer working with the ROM department. Asking a mod to close down this thread
[Nexus 5X Android Development] aringler:
Sorry to ask, but what vendor, bootloader and radio image we need?

This is the most up to date one I can find, but it's for Android 8.1....

8.1.0 (OPM7.181105.004, Nov 2018)

Thank you for your help.!
[Nexus 5X Android Development] cris_webb:
Since Nexus 5x doesn't received Android Pie and November patch was the last then that's the vendor, radio and bootloader we need
[Nexus 5X Android Development] ideaman924:
Use the last radio/bootloader available on the Nexus image page. Oreo was the last build Google supported, so that's the only prerequisite.

We automatically patch the vendor when you flash our ROM so that it works with Pie ROMs.

---------- Post added at 01:27 AM ---------- Previous post was at 01:25 AM ----------

"New" build going out today! (New as in November 27th)

Changelog:

* device/lge/bullhead/
51e1097 bullhead: Blissify

* hardware/qcom/display/
af897939 Revert "display: msm8994: replace %zd with %ld for ssize_t argument"

* manifest/
a5c9704 Track new Pulse repo
1dc338e Merge "Track new SmartNav repos" into p9.0
f777c94 Merge "AmbientPlay: Introduce history manager [1/4]" into p9.0
916acf4 Track new SmartNav repos

* packages/apps/SmartNav/
0b567be New Fling icon thanks to @ROGERdotT
c881a33 Use offload thread (ExecutorService) to start pulsing
897a794 Smartbar pixel animation: Ability to customize the dots [2/3]
a4d9665 Make Smartbar Pixel Animation Durations Customizable [2/3]

* packages/apps/SmartNavSettings/
346508a Pulse: add back color from album art preference
e7da151 Pulse: Allow Pulse for all bar modes
2c72f0a Smartbar pixel animation: Ability to customize the dots [3/3]
29e91a2 Settings: Make Smartbar Pixel Animation Durations Customizable [3/3]

December builds will be coming soon, just have to make sure everything works. Find the latest builds on downloads.blissroms.com .

NOTE: I just started the upload process, so wait until you see the .md5 file before downloading, as there is a chance you might have an incomplete build. ALWAYS remember to check digest files in TWRP!

Thank you for using our ROM!
[Nexus 5X Android Development] kaso911:
Can I use dirty flash?
[Nexus 5X Android Development] ideaman924:
Depends on a number of things... if the previous base was a different ROM or stock, then you should clean flash. If it was Bliss, then you should be able to dirty flash.

In some cases, if the firmware isn't that different you might be able to get away with dirty flashing, but expect nasty bugs and instabilities if it goes wrong. We can't help anybody with dirty flashes.

TL;DR - at your own risk, and we don't recommend it. Always clean flash!

EDIT: I realized after posting you were asking if you could flash this on top of the Nov. 26th build. There shouldn't be any problems, but let us know if something is amiss.
[Nexus 5X Android Development] kaso911:
I punched the dirty flash but Google services stopped working properly. So I'm doing a clean flash.thanks
[Nexus 5X Android Development] mperezm77:
Where could I find that ROM?
[Nexus 5X Android Development] Josh:
Nowhere yet. Soon™
[Nexus 5X Android Development] kaso911:
yes with chromecast, it works for me right.
[Nexus 5X Android Development] Weathered:
I was asking about Miracast (Settings > Display > Cast OR Settings > Connected Devices > Cast), like casting without a Chromecast. Lineage has that. I frequently use it so I wanted to be sure before I switch.