yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] rubic_cube:
Hmmm... this topic was discussed before. Here's the search link for posts on this topic: http://xdaforums.com/search.php?searchid=339378684

Also, I assume this is just a label issue. You do have an active network connection, right? i.e. the network bar shows up on the right side of status bar (or wherever you have chosen to display it)

If it is a cosmetic issue, here are some options:

1) Toggling airplane mode resolves the issue (Thanks to [MENTION=1009129]eunique[/MENTION])

2) Checking "preferred network" under Settings

3) Settings->Bliss Interface->Status -> there is an option to display mobile network name or edit it. I like displaying "1+1" and so have permanently edited that. That also solves this problem, but is really a workaround.

4) Wait for 30 minutes to see if it auto-resolves. Sometimes it does.

5) I have also heard on this thread that a clean flash resolves this issue. I have done that before and it did clear it. But #3 above works as well. Depends how eager you are to see that label display correctly.
[ONE Android Development] Nandeh:
Don't understand why you quote me. I don't have any problem ;)
[ONE Android Development] wilbarger:
OK, gonna ask this and duck my head to dodge the flack coming my way. I have been flashing every build for the last several weeks and have , obviously clean flashed and have the latest firmware. Here is my issue. The last 2-3 days, the proximity sensor has quit working when I am on a call. When I take the phone away from my ear, the screen never turns on again until I hit the power button. I have tried with the Prevent accidental wake on and off. I have blown out the area around the sensor with clean air and still no help. Yes! I did search and this issue was resolved a long time ago, but is back again for me.

Any ideas????
[ONE Android Development] troublekick:
[MENTION=5441627]rubic_cube[/MENTION] thank you, I've read the posts and I know it was brought up in the past, and you are right, network connection is active... Only a cosmetic issue. It has always worked fine for me with all dirty flashes [emoji6], now it just reappeared after the latest unofficial build being dirty flashed,

It was just an FYI post.

Actually, I personally don't mind even if it doesn't show in lock screen, as long as I've an active network connection [emoji687],
[ONE Android Development] rubic_cube:
If you have flashed the last official build posted by [MENTION=5168118]Vortex1969[/MENTION] or the nightlies by [MENTION=4877142]tobitege[/MENTION], this issue has been resolved. Or atleast, I do not have this anymore. [MENTION=5168118]Vortex1969[/MENTION] did indicate that he had taken the code for proximity sensor out, but all is well with the recent builds.
[ONE Android Development] mapolidori:
You don't happen to be running multirom with a cm11s primary?
[ONE Android Development] rubic_cube:
Hmmm... surprising indeed. I thought I was quoting [MENTION=3116305]troublekick[/MENTION]. Sorry about that. I have now edited that post to correct the quote reference.

---------- Post added at 09:25 PM ---------- Previous post was at 09:14 PM ----------

On other news, authorities were closely watching a group of XDA members that seemed to be experiencing too much "bliss". Common speak amongst the thread participants included terms like being BlissPopped and Blissed'Out. Authorities were concerned if there is a new addiction taking roots and how to manage it. Last night, a "Flashing" party (no, not that mardi gras kind although that would be blissful in a different way) was convened that many users were invited to freely participate. Upon detailed investigation, authorities determined that experiencing "BlissPop" is fine indeed. The case has since been FC'ed without comments.
[ONE Android Development] cerealguy:
Let's begin another SUNDAY FUNDAY!! :D
[ONE Android Development] flyaway718:
1/5 build. Text msg look mess up in landscape mode
[ONE Android Development] david72262:
Ok on yesterdays build just checked
[ONE Android Development] suaverc118:
I've had this issue the last few builds and none of that resolves it. Well I haven't clean flashed but it's not worth the trouble right now .
[ONE Android Development] raptor402:
Hey, forum

I finally decided to jump to Lollipop. I wiped system/data/cache/dalvik via TWRP (multirom) and then tried to flash the ROM. I got the following error:

Comparing TZ version TZ.BF.2.0-2.0.0109 to TZ.

BF.2.0-2.0.0096

assert failed: oppo.verify_trustzone("TZ.BF.2.0-2.0.0109") == "1"

E:Error executing updater binary in zip '/sdcard... blah ... 2.0-bacon-OFFICIAL-20150205-2058.zip;

Error flashing zip '/blah/blah/blah.zip'

I tried flashing PA 4.6 again after that and it worked fine. What should I do?

Thanks.

Raptor

EDIT: So I searched again properly. Flashing firmware update. Quick question - will I be able to use 4.4 ROMs again after the firmware update?
[ONE Android Development] david72262:
Yes if you flash the kitkat firmware
[ONE Android Development] wilbarger:
Yep, I am on the current build. I have even flashed CM of 1/31. I am also not running multirom. For the life of me, I cannot figure out why the proximity sensor just quit working. I may flash back to one of the nandroids from earlier and see if it gets corrected.

Since no one else seems to have this problem, I will work on a resolution and post back with what I find.

---------- Post added at 11:05 PM ---------- Previous post was at 10:38 PM ----------

OK, figured it out. I flashed the 1/29 firmware and the proximity sensor works fine. Not sure what would be in the 1/31 CM firmware that would cause the failure, but I will leave it as is for now. Tomorrow, I may flash the 2/8 CM rom and see if this kills the proximity sensor for me also.
[ONE Android Development] paarkhi:
Just a small Feedback from a first time BlissPop user -

I flashed [MENTION=4877142]tobitege[/MENTION] 0207 unofficial (1st one) and coming from CM12 nightlies I must say that Blisspop overall is a simply a beautiful ROM with lots and lots of features to tweak.

Felt blazing fast compared CM12.

Just to inform Default Carrier label on lockscreen shows correctly in my case.

Proximity Sensor working fine (checked during call)

Features request (if you consider request else please ignore and don't start firing)

* Per App DPI

* Omni Multiwindow (coming from a Samsung Note2 I miss it, I was a Note2 user 10 days back, this is a new device for me)

As beautiful the ROM is so are the Devs and people here (not so uptight as seen in some threads)

Thanks to [MENTION=5168118]Vortex1969[/MENTION] and [MENTION=4877142]tobitege[/MENTION] for doing a wonderful service to the XDA community. (8 thanks are simply not enough after seeing this thread so I post from XDA Premium App). ;)
[ONE Android Development] jatinarora:
Known solution: Turn on touch sounds.

Please don't ask how it's related, but it will fix your call waiting problem :)

J
[ONE Android Development] geekynoob:
Whatever I do.. I am unable to change to way the softkeyz look.. Themes aren't changing them.. Tried softkeyz app that dint work as well.. Any heads up on this..?
[ONE Android Development] t3chn0s1s:
Just flashed this awesome ROM (again)... Its certainly come a long way from a short time ago. Its actually now my favorite! Anyways... As a result of the stock heads up being dark is it just an accepted fact that they won't ever theme right if the theme displays them as white or light? (Specifically he text color)
[ONE Android Development] tobitege:
Strangely, Settings|Language & input|Advanced options|Disable fullscreen keyboard... toggling it doesn't do anything for me (using stock keyboard, no other keyboard installed), I always have full-width layout instead I'd expect to see it shorter like in your screenshot.
[ONE Android Development] suaverc118:
I wonder if the carrier name has anything to do if you're using a theme or not? Clean flashed and all was OK until I applied a theme. Could be wrong
[ONE Android Development] paarkhi:
[MENTION=4877142]tobitege[/MENTION], do we get a OTA update on this rom or is there any utility which can provide the OTA updates to BlissPop like Cyandelta?

Sorry New here so asking questions.
[ONE Android Development] kalpik:
Nothing as such as of now.

Sent from my A0001
[ONE Android Development] tobitege:
Currently there's no OTA. I assume that until development is on weekly releases, it'd be just extra workload for the device maintainers. It still may never come. :)
[ONE Android Development] xanthrax:
I will never agree this ota be it delta, alpha or omega getting updates in blind, without reading the development thread, without knowing what you flash, without giving feedback

Get into the thread, read what's all about and flash knowledgeable

Sent from my Darkside of 1+1
[ONE Android Development] @xDeepS:
Did you flash the firmware upgrade thats been required the past few builds?
[ONE Android Development] chris264:
Good morning, someone Uses the kernel on the Boeffla Rome ? If so what are the experiences? About an answer I would be delighted
[ONE Android Development] Stylez Ray.:
Clean flash fixed my theme issues but now changing display density and reported density doesn't work. I can change the numbers but after a reboot it resets to 0=disabled. Can someone confirm?!
[ONE Android Development] tobitege:
Boeffla kernel works wonderfully, yes. But you should then also download the Boeffla app from his thread so that all the settings are correctly configurable.

I haven't seen them showing anything different than 0. The 0 just means, that the current/default DPI values are used.
[ONE Android Development] chris264:
Thanks Tobi, then I will test the kernel.
[ONE Android Development] raptor402:
Hello, forum

I just set up the ROM and restored all my apps. I've noticed an issue - everyone I unlock the screen, I get a black screen for a second or so before I get the lockdown. Any clues?

Thanks

Raptor
[ONE Android Development] paarkhi:
No such issues here, using Display density 300DPI and it works perfectly.

---------- Post added at 02:34 PM ---------- Previous post was at 02:30 PM ----------

Using pin lock and no black screen even for a second
[ONE Android Development] enaybee:
wow ... that's a reall small DPI you are using. I can't personally go under 400 otherwise its too small for my use.

Anyways, anybody figure out how to make the screen colors work? I tried doing a search in this thread and didn't see a definite answer.
[ONE Android Development] tobitege:
[MENTION=1308602]enaybee[/MENTION]: screen colors are still w.i.p., the controls are there, but not yet functional.
[ONE Android Development] eunique:
Carrier label shows "no service" on lock screen , after latest unofficial build! , dirty flash<br />

<br />

The carrier name problem has a solution...

Just toggle airplane mode ON, then back OFF then you will have carrier name in lockscreen
[ONE Android Development] paarkhi:
Yes first when I started using 1+ I was on 360DPI then 320DPI and now since last 2 days I'm on 300DPI, I can't use the phone anything above 320 because everything looks so big and ugly.
[ONE Android Development] cerealguy:
Pleaseee.... Read some posts before yours!! It's been answered 1000000 times!! [emoji29]
[ONE Android Development] maorgit:
I have done that and read about many requests of getting this but I never found the "why" it isn't inserted... If so many want this why not make it as a default in the rom? Instead of copying and editing from other roms... And thank you for your pleasant and informative answer to my question....
[ONE Android Development] xanthrax:
First of all you didn't ask "why" ...

Second, even if someone would answer, how much it would help you? Are you into development? Nor do I... But, considering that a second ROM, as you may have read on the dedicated thread about, doesn't have the system mounted as read only and encryption isn't possible so, most probably this is the way should be with L and the development is focused on less issues possible

There may be some more other implications that I'm not totally aware of, some kernel modifications as well that cm isn't keen to do it

So take it or leave it in the end, there is an option which I personally use it, swap ROM's

I keep my favorite cm11 as secondary, I try the CM12 on primary with the available option to wipe system which is not the case for a second ROM, I always use a custom kernel just because... So, get used to it, try and you'll see

L is different and maybe it will be even more, we must adapt and move forward according to, with a little effort, anyone can change his habits {though I've failed to quit smoking...}

Sent from my Darkside of 1+1
[ONE Android Development] jejemc:
Hi, and all agree with you xanthrax :good::good:
[ONE Android Development] Fabioo123:
I think cyano has added the ability to switch quickly to the last app without having to recent.

I hope to be adding this feature in the latest build
[ONE Android Development] MortenHeck:
Zip file corrupt?

Downloaded the latest build, and the ZIP file is corrupt. am I doing something wrong?

http://teambliss.x10host.com/BlissS...ssPop-v1.2-bacon-UNOFFICIAL-20141211-1922.zip
[ONE Android Development] DevilmaycryTR:
Xposed framework not compability , is it ?
[ONE Android Development] Vortex1969:
That's because it's not done uploading. Need to wait until I post upload ready. I post with every new build.
[ONE Android Development] Khizar:
Haven't had a chance to check but think that was added recently so should be in next build.

It's not uploaded completely. Be patient.

Xposed doesn't work on ART. And L obviously uses only ART.
[ONE Android Development] MortenHeck:
Tnx!! I got so excited when I saw there was a new release....

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

Just got so excited when i noticed the new build! Patience is not one of my qualities.

But thanks for your answer!
[ONE Android Development] Vortex1969:
New Build Uploaded

BlissPop-v1.2-bacon-UNOFFICIAL-20141211

http://teambliss.x10host.com/

TeamBliss

Changelog

-Fix blacklist setting crash

-Last app action in long press

-Add default slim actions for screen off gestures

-Add a default slim actions array

-Add user config lockscreen shortcuts

-Fix Navy Bar dimensions FC

-Add central slim ActionListViewSettings class

-Add listview animations

-Updates nav bar strings

-Allow last action to be assigned to HW keys

-Configurable 0, 90, 180 and 270 degree rotation

-All CM updates and more

Flash:

ROM

Gapps I use Thanks to Banks

http://fitsnugly.euroskank.com/?rom=banks&device=gapps

Enjoy....Happy flashing

Clean flash before reporting any problems..

Regards,

Vortex
[ONE Android Development] kroogar:
Setup wizard stopped

Just flashed this and the setup wizard keeps FC'ing. So I cant setup the phone...

Any clues?
[ONE Android Development] jejemc:
Hello thank you for the update;)

person call by problems?( when you call) thank you to you for your return.
[ONE Android Development] Khizar:
Clean flash? If so either try different gapps or simply delete setup wizard from the ones you're using now and flash again.

More detail, what problems exactly?
[ONE Android Development] Texan1:
Is it ok to use any of the slim Gapps with your rom?

http://slimroms.net/index.php/downloads/dlsearch/viewcategory/1251-addons/downloads
[ONE Android Development] jejemc:
I call it sounds but can not hear me
[ONE Android Development] Vortex1969:
I just clean flash again with the gapps I posted and setup was fine.
[ONE Android Development] Vortex1969:
OK for lack of better words I'm getting irritated with complaints that are not problems. I just called a friend and they could hear me just fine and I could hear them.

And once again clean flash setup works just fine. With the gapps I suggested.

Regards,

Vortex
[ONE Android Development] jejemc:
Ok so I always put in installation total wipe I am not a beginner;)

I managed to solve the problems here is;)

best regards

jerome

up the rom mega court to which would be difficult;)
[ONE Android Development] AspenSTi:
You did use 5.0 gapps right? I flashed once using 4.4.4 gapps and got the same issue a few roms ago.
[ONE Android Development] shadeofgrey:
I love this ROM. I can't even be bothered to flash anything else. I used to flash a new ROM every couple of days. I've found the treatment for flash addiction. Thank you Bliss team. Best wishes to you all.
[ONE Android Development] hassan_1000:
Dayyyyyyyyyyyummmmmmmmm 300dpi is so beautiful!!! I was scared to go below 360 but I risked it and it was a risk well worth taking. Absolutely beautiful
[ONE Android Development] NickosD:
" Notificaitons "

Sent from my bacon!!!!!
[ONE Android Development] tobitege:
It's slang. :p
[ONE Android Development] Alin CG:
Do 290 ...it's more beautiful :D I use it
[ONE Android Development] alexbk66:
What do you mean? I have the same issue: select SwiftKey, it works for a while, than suddenly it switches back to AOSP keyboard by itself.

It still happens on the latest ROM version.
[ONE Android Development] xanthrax:
I'm saying that the way you flashed /restored /installed your system and apps only you know

You do realise it happens to you only, do you?

Sent from my Darkside of 1+1
[ONE Android Development] alexbk66:
What should be reported DPI? 401? Or it's PPI?

---------- Post added at 02:11 PM ---------- Previous post was at 02:07 PM ----------

After installing BlissPop-v2.0-bacon-OFFICIAL-20150205-2058 still have the problem selecting different keyboard, it switches back to AOSP by itself

[EDIT]: Greenify seems to hibernate SwiftKey, after disabling hibernation for Swiftkey seems to work now.
[ONE Android Development] xanthrax:
This is the third time when you post the same personal issue, actually fault, without giving any other information that I've requested

Are doing this for a purpose?

Sent from my Darkside of 1+1
[ONE Android Development] ikramevan1:
[MENTION=4877142]tobitege[/MENTION] Thank you very much for new update

But i believe screen color is not fixed yet. i think it will be fixed soon right?
[ONE Android Development] rubic_cube:
*deleted*
[ONE Android Development] tobitege:
[MENTION=4307845]alexbk66[/MENTION]: I'd think of 2 reasons: your other keyboard FC's or you accidentally tap a selector key (like the one left of spacebar in aosp keyboard).
[ONE Android Development] rubic_cube:
Sometimes the answer comes before the question. Like this one.
[ONE Android Development] :
turns out I had it Greenified took it off the hibernation list and it worked perfectly
[ONE Android Development] fiz:ik:
I would suggest to set the reported DPI to 480, the stock settings for the OPO.

Don't you guys think that 290/300 is a little bit tiny? I recommend a DPI between 340 and 360! :)

Why are the unofficial versions ~10MB smaller?
[ONE Android Development] fiz:ik:
Yes, you are right. I was using 400 since I've got the OPO. But I settled to 360 finally. 390 should be fine, too. The DPI setting is very individual in my opinion :)

But it's weird how manufacturers set their stock DPI to such a high value. It does not look good when everything is that big. Moreover the display appears cleaner and bigger with a lower DPI :cowboy: :good:
[ONE Android Development] xanthrax:
You're talking from you're perspective but I'm pretty sure that the manufacturers are setting up things based on a deeper research, far more deeper, abisale comparing to our thoughts

Sent from my Darkside of 1+1
[ONE Android Development] tobitege:
Because I can... lol... I'd have to ask my build machine...
[ONE Android Development] bloodonmoon:
Nightmare with Bluetooth

The latest build (I know it's CM problem), it worst than any other build so far, I've SoundCloud, Spotify, Play Music and Default Player. The problem is when I connect any bluetooth device , all the player yes ALL the players will start playing songs, that is worst thing and Phone is freaking heating up and the only solution is to reboot. And the worst is not that, even when I receive call the songs will not stop and will play. I think CM12 is fubard, they literally screwed up the basic functionality that is phone then the all the smart things, so I returned to stock yesterday and it's awesome, no bluetooth issues and battery is much much better. (CM 11s is the best for OPO lollipop sucks period).

But Yes BlissPop is still best when compared to any other 5.0 ROMs for OPO and all credit goes to the team, please keep up the good job and I hope bluetooth issues are resolved.

And I hope Oxygen OS is on par if not OPO will loose the market share.
[ONE Android Development] wilbarger:
Did you even read my post before answering. I clearly stated that I am running the latest firmware.

I have fixed the issue already. It was posted that it was fixed a little later in the day.
[ONE Android Development] @xDeepS:
Yes yes my bad, I some how hit reply like hours later :highfive:
[ONE Android Development] rubic_cube:
Possibly due to differences in byte size calculations depending on OS on the file server. Windows uses 1024 bytes for 1KB and Linux uses 1000 bytes for 1KB. Extrapolate that difference in terms of MBs... :)

A very interesting page on this very topic is available on Wikipedia: http://en.wikipedia.org/wiki/Binary_prefix#Adoption_by_IEC_and_NIST
[ONE Android Development] wilbarger:
Well, after digging into this issue later last night, I have found what caused the issue in the first place. As I had written, I flash the new BP every time it comes out. The proximity sensor had worked very well for all this time and then just quit working. I know that the last CM rom that I flashed to test was on 1/31 and it seems that the problem even happened some time after that.

Well, guess what! My son passed by last night and let me know that he was playing around with my phone and decided to flash a KK rom just to see if he could go backwards. CRAP, now everything makes sense except for why he is flashing on my phone. So, I am the idiot and appreciate the help.

By the way, evidently restoring a LP nandroid over the KK does not bring the firmware fix forward.
[ONE Android Development] tobitege:
Yeah, only a few custom recovieres allow to e.g. backup/restore modem, but that's only a small part of the firmware/bootloader partitions that get flashed (8 in total thus far).
[ONE Android Development] jatinarora:
Sounds like a party!! ;)

Have you tried Boeffla Kernel with the recommended settings? Seems to solve most BT related audio issues.
[ONE Android Development] tobitege:
In this case he was right: the (un)official is indeed smaller, also on different devices, not just a math question. ;) But I haven't checked what exactly was taken out of the build to account for that.
[ONE Android Development] Stylo King:
[MENTION=4877142]tobitege[/MENTION] Audio gitch is happening again..

I disabled Nuplayer also still it was there.

Help..

Last time when I disabled Nuplayer it worked but now it is not doing anything, Music stopped and phone freezes.

Sent from Blisspop's Lollipopified Bacon
[ONE Android Development] magnamentis:
IMO you should report 480 because thats the device's default dpi and this would / should help avoid custom dpi issues with certain apps

EDIT: ninjad that long before reaching the already given correct answer, sorry

---------- Post added at 05:31 PM ---------- Previous post was at 05:24 PM ----------

just want to confirm that for those with BT issues. albeit i'm still not using LP as my every daily driver im testing from time to time on a bike ride with 3 different bluetooth devices and never had any glitch with player pro in combo with [MENTION=947981]Lord Boeffla[/MENTION] his kernel
[ONE Android Development] tobitege:
Sorry, but I'm not doing the development. Actually there were 2 audio-related commits in last unofficial build that should actually "help", not break anything. You could go back to previous official build (dirty flash) till next one comes out.