yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] Elevate08:
Wake Issue

I'm having a issue where the device won't wake up immediately (using double tape or the power button) it takes about 10sec or so of pressing the button in or tapping on the screen in order to get it to wake up.

About Phone:

BlissPop Version 2.2

Baseband version MDM9625_104335.118.02.55.03R

Kernel Version 3.10.40-franco.Kernel v19

Build Number bliss_Shamu-userdebug 5.0.2 LRX22G 973bb41245 test-keys

Let me know if you need anything else and i apologize if this has been addressed already.
[Nexus 6 Android Development] chris6278:
I was experiencing this the last several builds before i switched to stock 5.1 an terminus.
[Nexus 6 Android Development] buschris:
Wug's Nexus Root Toolkit
[Nexus 6 Android Development] elevatorguy:
Will this zip allow you to run 5.1 roms and if so do you have to worry about the oem unlock button? Does the bootloader or radio effect being able to use xposed? Sorry for all the questions. TIA
[Nexus 6 Android Development] zige:
Yes it's allow to run 5.1 roms and don't need to worry about oem unlock button. Bootloader can be causing Xposed to not work. I'm not sure, but Xposed isn't working for me with any kernel with Bliss Pop and 5.1 bootloader can cause it but i'm not 100% sure. You can always flash back old bootloader and radio if you are not happy.

But you must remember that for some reason newest Bliss Pop build don't work with old bootloader. We don't have any confirm from Bliss Pop devs why it's like that but someones has reported it here and was able to flash newest build after flashing that zip which contain new 5.1 BL and radio.
[Nexus 6 Android Development] elevatorguy:
I thought once you upgrade bl you were stuck that you can't downgrade it. If it can be done do you have a zip for that?
[Nexus 6 Android Development] zige:
I don't have zip for that, hadn't need ever. But you can flash stock 5.0.1 img example with toolkit which was mentioned couple post above. It also flash older bootloader and radio. But as i mentioned i haven't flashed older BL back because i haven't had reason for that.
[Nexus 6 Android Development] abjexstallion:
My issue is probably theme related, but just checking if anyone has it; if i set a bootanimation through themes, it sets up, but i can only view it if i soft reboot; regular reboot shows the original ROM bootanimation. Any suggestions? Thanks in advance.

The screenie shows SeLinux is Permissive...

P.S. As you can see it's a 5.1 ROM but it was doing the same on my DD which is BP!!
[Nexus 6 Android Development] zige:
Update your rom. You have 22-3 build and it was fixed on newer builds. I had same issue on 22-3 build.
[Nexus 6 Android Development] Burkettacb:
Just updated to 3/22 build. 3g broken on sprint. Only doing 1x and LTE. Just downloading the latest 3/26 build to see if that fixes it. Not sure if other sprint users are experiencing same. I can call out, text, use data. Just can't receive incoming calls.

---------- Post added at 10:15 AM ---------- Previous post was at 09:55 AM ----------

Update. Flashed 3/26build. On sprint carrier for nexus 6. 3g still borked. Only 1x and LTE. So can't receive incoming calls...?? Suggestions?
[Nexus 6 Android Development] chris6278:
If your using the new radio then you cant recieve calls on lte with 5.0.2 roms. I suggest moving to a 5.1 rom until blisspop updates
[Nexus 6 Android Development] PhattyMcGee:
For what it's worth, it works just fine on Verizon

Sent from my Nexus 6
[Nexus 6 Android Development] zige:
It's easier move to other rom if there is CM roms which is using 5.1 but i haven't found any.
[Nexus 6 Android Development] ithamatam:
same on metropcs
[Nexus 6 Android Development] Burkettacb:
Unfortunately, I wish I could say that the issue arised with a radio update. But it did not. For whatever reason, I couldn't use 3g, and only 1x or LTE is working. That sounds great, but then I noticed and confirmed I was no longer able to receive calls. Text was sending hundreds of duplicates to recipients (yes I know duplicate text are a known issue with the sprint nexus, but not sending over a hundred of the same thing.) Data works and I could place calls. Just very buggy. Had to restore my original backup of stock rooted. It seems to have fixed the issue but just. Something stuck I suppose in the system, so I will be returning to pure stock tonight and rerooting later.
[Nexus 6 Android Development] C00lBeanz:
Im back to Blisspop again! I flashed the newest 3/26 rom and it seems like I can't change the LCD density natively in the settings? And some apps that require reboots to do there thing like adblocks reset everytime I reboot, any fixes?
[Nexus 6 Android Development] chris6278:
The last few builds ive tried have been very buggy and had all the things happen that your going thru so i moved on to a 5.1 rom until blisspop updates to 5.1 which i hope is soon
[Nexus 6 Android Development] nicholaschum:
DPI settings never worked in Settings. It's just a small bug. Use Texdroider DPI for now
[Nexus 6 Android Development] PhattyMcGee:
If your rooted, you can use a terminal emulator and type:

su

wm density 493

stop && start

Remember to press enter after each line of the code

The first line gets you to the root directory

The second line sets your density (493 is native for nexus 6 but you can use whatever you want)

The third line reboots your device with the new density settings

Sent from my Nexus 6
[Nexus 6 Android Development] zige:
You are wrong. I have used it all the time. You just need to set selinux to permissive and it works.
[Nexus 6 Android Development] nicholaschum:
Incorrect.

http://review.blissroms.com:8081/#/c/43/

My SELinux is always permissive.
[Nexus 6 Android Development] zige:
You can think what ever you want but i haven't NEVER used Texdroider app to change dpi with Bliss Pop. I have used only that build in thing. It didn't work first but then changed selinux to permissive (because for some reason almost all kernel, including which came with rom is defaul enforcing) and rebooted and it worked. Maybe then it's just working for me. It can be issue with newer build but it was about week ago when i flashed Bliss Pop back and it worked then and after every update.
[Nexus 6 Android Development] nicholaschum:
That's great for you, it doesn't work for everyone. I personally am a Team Bliss member, working directly with the code, as well as working in the Support Staff channel to help other people. I know of a bunch of people throughout many devices that haven't gotten DPI properly configured in their build and thus needing to use Texdroider. Only yesterday did the last complaint about it go through and Tobi decided to merge the new DPI settings.

Also there's a reason why people are asking about the DPI if you search DPI, there was something that wasn't configured properly for high DPI devices and that was shown above. Regardless, whether your SELinux is permissive or not, try pushing it to permissive, and setting the DPI. If it doesn't work, you know why.
[Nexus 6 Android Development] apophis9283:
I assume no one is having any issues with all the device/moto/shamu commits ive pushed?
[Nexus 6 Android Development] PhattyMcGee:
So far so good. I've flashed everything up to the 3/28 build and had no issues. Have you guys (devs) officially stated that we need the updated bootloader and radio to continue flashing these updates? I ran into an issue a few builds ago that zige addressed by providing me with the flashable zip for the bootloader and radio and everything has been peaches since. Also, is there any kind of abbreviated change log that we can view for future updates? It's not essential, but nice to view some of the changes. This ROM is solid and by far my favorite! You guys do a great job!! Thank you!

Sent from my Nexus 6
[Nexus 6 Android Development] apophis9283:
Ive flashed the new bootloader and radio, these are still 5.0 builds. I havent noticed any difference to be honest
[Nexus 6 Android Development] PhattyMcGee:
I agree. I found that you cannot flash these build if you don't update the bootloader and radio. TWRP throws an error and fails the flash.

Sent from my Nexus 6
[Nexus 6 Android Development] apophis9283:
as long as it flashed :)
[Nexus 6 Android Development] elevatorguy:
Looked in the xposed thread couldn't find the answer. If you update bootloader and radio will xposed still work?
[Nexus 6 Android Development] zige:
I think it isn't working. I tried many times with new BL and can't get it work. But dunno if it is Bliss Pop or BL. Eitherway can't test anymore because changed rom. But by my experience Xposed isn't working with new BL.
[Nexus 6 Android Development] elevatorguy:
Thanks for the quick response. Guess I'm sticking with what I got, can't live without my youtube ad block ?
[Nexus 6 Android Development] elevatorguy:
Do you or anyone for that matter know what the last build is that will work without the 5.1 bl?
[Nexus 6 Android Development] lasphyxial:
I'm on 3-29 with the same BL from the 5.0.1 ota I got when first bought my phone...
[Nexus 6 Android Development] elevatorguy:
Guess I'll give it a shot. I asked because there's has been a few people post after a certain date rom won't flash without updating BL
[Nexus 6 Android Development] nicholaschum:
http://review.blissroms.com/#/c/76/

Just fyi. Shaun's working on it
[Nexus 6 Android Development] zige:
What is in there? Can't see without login.
[Nexus 6 Android Development] nicholaschum:
Merge Android 5.1.0_r1 tag

HOT Stuff

+723378, -237562	changes
[Nexus 6 Android Development] plasticarmyman:
3/29 is getting a whole lot of Google Play Services FC's and Whisper Push FC's on boot.

Tried without changing kernel and tried with different gapps and still the same problem.
[Nexus 6 Android Development] PhattyMcGee:
I'm on the 3/29 build also, however I'm using Franco kernel and everything is running very smooth. I've only had 1 FC on reboot, but that was the messenger app for whatever reason. I remove many system apps right after I flash the update though. Maybe one (or more) of those apps are conflicting. That's just a SWAG on my part though. Sorry I couldn't help further.

Sent from my Nexus 6
[Nexus 6 Android Development] plasticarmyman:
I'll try again, but 3/22 is working fine.

i did not update my BL, it could be that
[Nexus 6 Android Development] PhattyMcGee:
I couldn't even flash anything after 3/22 without updating the boot loader. TWRP just errored out with a boot loader compatibility problem. At least that happened on the 3/23, 3/24, and 3/25 builds. Once I updated, it's been great. I'm not sure how some people were able to even get it to flash without the update. Give the BL update a shot and report back. Things should work just fine after that.

Sent from my Nexus 6
[Nexus 6 Android Development] plasticarmyman:
after i get my coffee and whatnot i'll give that a try..

*yawn*

edit: Must have been the gapps i was flashing...i flashed an older build not from banks and it worked fine...

i'm on T-Mo, i shouldn't run into the lack of LTE with the new radio should i?
[Nexus 6 Android Development] plasticarmyman:
double tap to wake is not sticking on 3/29
[Nexus 6 Android Development] PhattyMcGee:
I'm on Verizon and my LTE is solid

Sent from my Nexus 6
[Nexus 6 Android Development] pjgraber03:
Ota updates

Hey guys we have integrated OTA updates into the builds... the 3-30 build that is posted will updated everything u need... I'm getting ready to flash the build and I don't assume there will be any issues. Thanks for all your support
[Nexus 6 Android Development] jlokos:
Looking forward to trying it out.
[Nexus 6 Android Development] nicholaschum:
Built in OTA Updater has been added on the newest release as Pat said above

Check out the "Updates" icon that will appear in your drawer on your next flash!
[Nexus 6 Android Development] chris6278:
Been a lil while since i used this rom, has it been updated to 5.1 yet?
[Nexus 6 Android Development] chrristin:
The OTA updates have the full sized ROM? ( The OTA update for 0331 says 390Mb. )
[Nexus 6 Android Development] nicholaschum:
Yes, OTAs are still full sized.

---------- Post added at 05:23 AM ---------- Previous post was at 05:23 AM ----------

Not yet
[Nexus 6 Android Development] plasticarmyman:
on 3/29..

unable to receive phone calls or send texts if on wifi...

i have never had this problem before..i'm going to be switching to resurrection remix to try that out...
[Nexus 6 Android Development] PhattyMcGee:
Do you clean flash or dirty flash? Also, the 3/31 build is out and I haven't had any problems with it. What kernel are you using? Did you get your phone from a carrier, play store, or Motorola? I'm just trying to help figure out where the issue may lie.

Sent from my Nexus 6
[Nexus 6 Android Development] plasticarmyman:
Clean flash.

Stock ROM kernel.

Carrier, T-Mo.

i'm also switching because of a feature that used to be on Bliss has been removed.

I don't need a dedicated Recents button...i don't know why anyone does, IMO it is the stupidest dedicated button for anything ever.

I want my Dedicated Menu Nav button back, long press for recents, i don't want to have back, home, menu, recents.
[Nexus 6 Android Development] PhattyMcGee:
Mine is dirty flash, Franco kernel, Motorola store, Banks gapps 3-5-2015 (I forgot to ask about the gapps package). Have you taken a logcat and sent that to someone like nicholaschum or pjgrabber? Sometimes those guys can find issues looking through the log. Just a suggestion.

Sent from my Nexus 6
[Nexus 6 Android Development] plasticarmyman:
FML resurrection forces encryption....i think i just lost all my internal data....
[Nexus 6 Android Development] PhattyMcGee:
That $ucks - I didn't even think about that

Sent from my Nexus 6
[Nexus 6 Android Development] plasticarmyman:
for some weird reason it didn't touch my internal data...so i still have that...

i'm going to go back to Bliss because of battery life, but i'm going to try and flash LMY47M BL and Radio since i am on T-Mo and see how that works...
[Nexus 6 Android Development] ithamatam:
Totally weird.. How is my rom not supported

Leannkernel

DPI 460

Dirty flash

Slim gapps 3/26
[Nexus 6 Android Development] nicholaschum:
You're probably running an early build with the wrong build prop value. Try updating to the latest version.
[Nexus 6 Android Development] x0nar:
Seems like Bliss for Android 5.1 is out.

Here's the link http://bit.ly/1DnXbOi

Enjoy
[Nexus 6 Android Development] freddienux:
[MENTION=3605033]nicholaschum[/MENTION] did 5.1 get merged on latest build? Thx in advance

Sent from my Nexus 6
[Nexus 6 Android Development] pjgraber03:
5.1

We are still working on getting 5.1 out and rolling...And making sure its TOTALLY stable before we release it... We will keep you guys updated on progress of that
[Nexus 6 Android Development] buschris:
anyone having trouble with double tap to wake? I did a fresh 3-31 install full wipe. It turns itself off and never works
[Nexus 6 Android Development] nicholaschum:
I think it's stable, but we need to blissify which is taking the most time. Remember all, we got tons of features to port!
[Nexus 6 Android Development] caspersfi:
^^THIS^^

I'll jump to 5.1 when Team Bliss does.
[Nexus 6 Android Development] :
I just tried to flash the most recent nightly (I generally update my kernel and ROM every month or two), but I got the following message:

Error executing updater binary in zip '/sdcard/Download/Blisspop...'

Is there any reason that this might happen? Would waiting for the 5.1 build to drop resolve the issue?
[Nexus 6 Android Development] PhattyMcGee:
Have you updated your boot loader and radio yet? Builds made after 3/22 require an updated boot loader. That has been my experience at any rate.

Sent from my Nexus 6
[Nexus 6 Android Development] :
No, I haven't. Could you direct me to where I could do this?
[Nexus 6 Android Development] PhattyMcGee:
Here is the link to the update. Read through the posts starting with #2226 by zige so you can get the gist of what happened to me and how we fixed it.

Sent from my Nexus 6
[Nexus 6 Android Development] :
Much appreciated.

The radio shouldn't make any difference, though -- you can (and should) try the radios for all releases, since different ones work better for your phone.

Do you need to flash this every time you update? I can't imagine that you would.
[Nexus 6 Android Development] PhattyMcGee:
I agree. The bootloader is your main issue here. And no. You only flash this once. Then you will be able to flash the newest builds. I'm on Verizon, and this radio has been working great. My lte is great!

Sent from my Nexus 6
[Nexus 6 Android Development] tracerit:
is this safe to use for T-Mobile as well?
[Nexus 6 Android Development] PhattyMcGee:
As far as I know. Look back a few pages in the posts. I think there were 1 or 2 people on T-Mobile who have used this update without any issues

Sent from my Nexus 6
[Nexus 6 Android Development] jewnersey:
PIN secured lock screen and Location smart lock working for anyone?
[Nexus 6 Android Development] :
After finally updating, I'm loving the changes, but I've run into a major roadblock. After five or ten minutes, the power button doesn't turn on the screen. It takes furious tapping and throwing around (activating ambient display) to turn it on. Is there any reason that this would happen?
[Nexus 6 Android Development] PhattyMcGee:
If your using the stock kernel, I've noticed that it can be a bit sluggish. I would suggest flashing a different kernel. I use Franco kernel and I'm very happy with it. You can try Franco kernel updater Free from the play store and give it shot or ask around to see what other kernels people are using.

Sent from my Nexus 6
[Nexus 6 Android Development] :
I'm using Leankernel. There's really no reason for it to happen, so I'm somewhat baffled.

Edit: figured it out. Under display, there's an option called "Prevent Accidental Wakeup." I thought this referred to ambient display, but it's for everything, and apparently it didn't like me turning m my phone very much. It's odd, though, because I think I had it enabled before I updated.
[Nexus 6 Android Development] nicholaschum:
[MENTION=5346868]pjgraber03[/MENTION] and I haven't updated our bootloader/modem to 5.1 yet....still able to update on latest builds.
[Nexus 6 Android Development] zige:
So tell us why 24-26 builds didn't flash without bootloader upgrading? It's said that bootloader wasn't updated. And now someone's is reporting also same with newest builds.
[Nexus 6 Android Development] nicholaschum:
I'm currently on 30th build with old bootloader. I can't explain why, but my flash order goes like this: Flash update, flash 5/3 Banks gapps, reboot.
[Nexus 6 Android Development] pjgraber03:
Ya I haven't updated my bootloader and I'm running 4-1... You shouldn't have to update the BL till Bliss updates to 5.1.... If you could send me a pic er something of the message your getting that would be helpful. Cuz I'm unsure y it would be saying anything about it
[Nexus 6 Android Development] zige:
Do you guys even read posts here? I will quote post from other user which was first to report it.

Ps. It's nice to write pure english, not any shorthand because this is international forum and everyone don't necessarily know what "cuz, y" etc. means.

After that post i posted zip for 5.1 BL and radio and after that [MENTION=5778112]PhattyMcGee[/MENTION] was able to flash mentioned build.

And after that we was thinking did we missed some info about updating bootloader but we didn't see any mentions by devs about updating bootloader.
[Nexus 6 Android Development] apophis9283:
Im using the new bootloader and radio with 5.0 no issues
[Nexus 6 Android Development] nicholaschum:
One thing I'd like to point out, it doesn't matter how someone types on xda-developers, as long as it's legible English, shorthand doesn't, wouldn't and shouldn't matter. Pat was purely pointing out that he had no problems with the bootloader while he's pumping out build after build every single day since we moved from Unofficial to Official in the time of Marc (asianflavor).

Yes we read one and every post here. The bootloader assert commit was placed by [MENTION=4392154]apophis9283[/MENTION], this was the only thing that we can think of regarding bootloaders and limitations.

As shown here, https://github.com/TeamBliss-Device...mmit/db39d75ceef4b7fe17cb8df7ca46ba3e991ab1fa

This means that the phone should have been bugging out since the February 20th build and not only the dates you posted. However proven by the github commit: https://github.com/TeamBliss-Device...mmit/bd82e08322407233f8a6a5a49332e286fe429ed0 the change has been reverted, thus nullifying this possibility.

The bootloader assert commit was designed to prevent you from running on a unspecified bootloader within the 5.0.2 spectrum, if you were running the 5.1 bootloader, 5.0.1 bootloader or the 5.0 bootloader, an error was meant to show up. It could be that the commit hasn't been pulled completely and thus causes problems with non specified 5.0.2 bootloaders from different variants (as there were two that popped up, there could definitely have been more)

We cannot confirm that this is true, but I can guarantee that my set up has not required a BL/Modem update since January. All we were saying is that we didn't need to update, and that updating BL is not a feasible fix in this situation, but a direct contact with us would allow us to see what's wrong and fix it directly in the source - instead of essentially "risking to break your radio from mixed reviews after updating to 5.1".

My set up goes as follows:

Nexus 6 - 32gb - 5.0.2 Bootloader & Kernel

Gapps - Banks - 5/3/2015 edition

BlissPop 2.2, 5.0.2, shamu, Bankai Kernel

One last thing, you need to chill out. We're looking directly in the code and solving issues. Not everyone has issues that some others may have. We address fixes, to things like the DPI changer. It didn't work for half of the variants we supported, yet after the update it finally worked on my device that has been dirty flashing since January 23rd. If you want to argue, we're not people to argue with. But if you want to constructively contribute within the project, flaming us and trying to deny what we show with theory and results (theory=DPI changer was broken, you said no, I said yes. Results=after update, DPI changer worked for me) isn't helpful and Team Bliss would not like any of that.
[Nexus 6 Android Development] zige:
Nice to know, but it wasn't even thing which we was talking about here. It's has pointed here many many times. I have also used 5.1 radio and bootloader with 5.0.x rom without issues.

---------- Post added at 02:59 AM ---------- Previous post was at 02:47 AM ----------

It's good etiquette. I can write also shorthand, even full message like that but is it write style what people want here to read? I don't think so.

To other text i don't have any comments. We pointed out that installer on those build forced to upgrading BL and BL which work for us was than BL which link i shared here to mates.

Which combination i have then? International Nexus 6 64GB (XT1100) and PA Gapps.

And then, i'm not barking your work guys. For my opinion, Bliss Pop is best rom available to Nexus 6, even when it's also buggiest rom available. Fortunately you guys have daily builds so bugs is usually fixed also faster than with others roms. So even when i'm saying my opinions here it doesn't mean i don't appreciate your works.
[Nexus 6 Android Development] pjgraber03:
ok lets stop the attacks here please....It doesn't help ANYTHING to keep picking at each other... if there is an issue with anything....Please post a logcat or a picture of the issue so I can take a closer look into the issue. I'm unable to recreate the problem so i'm unsure what is going on. So if you can post up something for me that would be great and i will look into it further.
[Nexus 6 Android Development] ManikandanGuru:
Need 5.1 LMY47M update

Hi,

Please update it to the latest lollipop version.

Thanks for the work :) :)
[Nexus 6 Android Development] Mistertac:
Lol

I know your intentions are good but usually this kind of post just pisses the devs off. It's not that easy to do everything they're doing, especially updating to 5.1