yashsingh1/xdaforums huggingface dataset:
[Nexus 5X Android Development] ideaman924:
Hi all, quick announcement. Build 20190512 (and possibly build 20190511) was released yesterday. The full changelog is available on the download server.

With this build, the NFC tile error has been fixed (and possibly other NFC-related bugs, such as NFC tags not working). The problem was a SELinux policy denial for platform_apps, which was restricting platform_apps from accessing the NFC service handler. The commit that fixes this bug is here: https://github.com/BlissRoms-Device...mmit/49837d4fb416eee0b4aa01b3928742fc0429d2c8

As always. please test and let me know if anything is broken. Specifically, for those of you with NFC tag problems, please test the latest build and report if there are any issues. Thanks!

EDIT: Just realized how awkward my first sentence was. I meant that build 20190511 might also have the patch for NFC. Sorry!

That is news, because phone calls work just fine here. Please post a logcat.

"Playing Now" is broken because the API is blocking all non-Pixel phones. We are working on a solution.
[Nexus 5X Android Development] aaannntoinee:
None of my calls connect

I have been using this ROM, hoping for a daily driver and all I am met with is constant disappointment regarding the cellular service (everything else works amazingly and I love it), I am just hoping for some potential fixes/tips thanks for the ROM, keep up the good work!
[Nexus 5X Android Development] ideaman924:
That is really confusing, because phone calls work just fine on my 5X. What carrier are you using in which country?

I've heard of LTE not working because of APN issues, but phone calls failing is a first. How does it fail? Does it crash the phone app? Lock up the phone? Does it reboot on its own or do you have to hold down the power button?

And also, PLEASE attach a logcat. I cannot debug issues telepathically, especially with a phone.

---------- Post added at 08:56 PM ---------- Previous post was at 08:47 PM ----------

Sorry for the delayed response.

I see some crashes within the rendering kit but not sure exactly what it's failing on. Something about the surface not being properly initialized. In the meantime, please just download the apps from the Play Store. Thank you!
[Nexus 5X Android Development] Kvothe1810:
Hi, i find a problem with environment screen, it doesn't work, is all on but when i up the phone or receive a notification nothing happens

Enviado desde mi Nexus 5X mediante Tapatalk
[Nexus 5X Android Development] ChemBot:
I'm also having call issues with this ROM. I'm on T-mobile USA with a full wipe and fresh install. On first boot I get LTE data and SMS, then when attempting to make a call my signal disappears and it says no sim card detected, then the phone app crashes over and over. Attached is a logcat from after restoring my apps and then attempting a phone call.
[Nexus 5X Android Development] punkwhan:
I had the same problem.

I'm on Verizon.

It lost the data connection too frequently.

It lost connection when attempting to make calls, and calls didn't go through.

I tried 3 Pie roms and had the same experience on all 3.

I've returned to Oreo stock since then.

I would love to stay with Pie, but no data & no call are tough.
[Nexus 5X Android Development] aaannntoinee:
Same problem here

I have tried more than 3 Pie ROMs and none let me make any calls and the exact same thing happens. I have T Mobile as well through the MVNO called Mint, and it's quite annoying because I want to get Pie on my device.
[Nexus 5X Android Development] ideaman924:
You need to provide more information. WHAT is an "environment screen", WHAT doesn't work, WHAT is on and WHAT is upping the phone? A video reproducing the issue might be helpful if you can't explain. Thanks!

Thank you for the logcat! Look down below.

Thank you for the bug report! (Without logcat though, would be really helpful for diagnostics, don't you think?) Look down below.

Thank you for the bug report, but please, logcats. I like cats.

----------------- Enough with user responses let's get down to explanation ---------------------------

All right, so I've been digging through the logcat kindly supplied by [MENTION=3040934]ChemBot[/MENTION], and it seems like the reason I cannot reproduce the issue is because this is carrier specific. Specifically, carriers that make use of the IMS protocol, with the IMS APK within the vendor directory. Now, because the vendor "blobs" are all from Oreo, some of the methods/symbol tables don't correctly translate through to Pie, and sometimes Pie has more methods/symbols that the APK must support.

I'll have to write a shim for this. As it currently stands, the phone cannot find the class com.android.ims.ImsReasonInfo, which is required for proper phone functions with carriers that utilize IMS. For more information on this, visit this page: https://source.android.com/devices/tech/connect/ims

If you're curious, here's the portion that shows the error from the above logcat: https://pastebin.com/sDf19Q2H

Not sure why it's complaining but will get to the bottom of this. Thank you all for the bug reports, and PLEASE send me MORE logcats. It is VERY helpful when diagnosing issues like these, when bugs are sporadic and only reproducible on certain carriers.

Steps to take logcat:

1. Connect phone to computer

2. Clear boot-up cruft from log (run adb logcat -c)

3. Run logcat on computer (run adb logcat > log.txt)

4. Reproduce issue (place a call)

5. Stop logcat logging (Ctrl-C) after waiting ten seconds for the log buffer to come through

6. Zip up that log and send it to me! Post it here or email it, whichever works.
[Nexus 5X Android Development] jeremywh7:
I just did a clean install of Bliss to grab a log and help with this issue, after sending logs for Pixel Experience several times months ago, and getting no reply. ;) I eventually gave up trying to update PE, and reverted to the last build before it broke (18 Jan 2019). If it's any help, I could also send the links to the PE logs I took back then.

Anyway, so here I am. :P I'm on AT&T, and took a log running Bliss 20190517 (attached), after clearing then making a call, which failed and resulted in the typical toggling 'No SIM card' and com.android.phone error messages. Thanks!
[Nexus 5X Android Development] mh0520:
Thanks for looking into this! I've been having this issue for a while with PE ROM and I've been hoping that someone could sort it out. I at least think it's the same issue.

I have a log that I took using PE ROM when I was having call issues with it. Here's a link to it: https://del.dog/balicuyale.

I'm not sure if that's helpful since they're different ROMs but maybe if it's the same issue it will give you some insight. As a side not, Pixel3ROM doesn't seem to have this issue. Maybe there's something from that ROM that can be merged into this and the other Pie ROMs that seem to be having trouble to resolve it.

EDIT:

I'm currently running an old build of Pixel3ROM and I went into the vendor directly and I see the ims.apk file there. If I were to copy that over, install this ROM, then replace the ims.apk file in that directory with the one from Pixel3ROM could that possibly resolve the issue or is it much more complicated than that?
[Nexus 5X Android Development] ideaman924:
Thank you for the logcat! Glancing at it quickly, same IMS issue, but different method call. Your phone is looking for the class "com.android.ims.internal.ImsVideoCallProvider" and failing. That's a new one, so I'm more puzzled.

Same issue as above, class "com.android.ims.internal.ImsVideoCallProvider" not found for your PE ROM. I suspect Pie has added new methods for the IMS implementation and the vendor app is old.

If the Pixel3ROM is Pie you can try it. If it works please send me the build or reply here so I can check out their vendor repository. Thanks!
[Nexus 5X Android Development] erfan khan:
[MENTION=5815168]ideaman924[/MENTION] sir during calling status bar and dialer background are different. Can you make matchable?

Thanks for stable smooth rom.
[Nexus 5X Android Development] mh0520:
To do this, should I just copy the ims.apk file over or should I use the whole vendor directory form the ROM? I'm on it now and i can try to copy it off in case I need to fill it in but switching back and forth is difficult so I want to make sure I know exactly what I need to do before I do the switch. Thanks!
[Nexus 5X Android Development] mh0520:
I tried this in the PE ROM, copying the ims.apk from Pixel3ROM over to the vendor directory in PE ROM. I haven't had any issues so far but I've only been on it for a few hours so I'll post back once I've had more time on it.
[Nexus 5X Android Development] mh0520:
Since doing this, I haven't noticed any call drop issues with my phone. I attached a copy of the apk that I got from Pixel3ROM. I'll update again if I start to see issues.
[Nexus 5X Android Development] punkwhan:
This is promising.

If this works on this Bliss Rom, I'll try again.

Thanks for your experiment.

I hope this can be baked in to this Rom.

Which carrier are you on?

I'm on Verizon and had the call drop and the loss of data connection before.
[Nexus 5X Android Development] ChemBot:
I tried this with the latest Bliss ROM and it appeared to be working. I could make calls and still had data. However I noticed later that I couldn't get incoming calls at all. When someone tried to call me, nothing happened on my phone. There was no log activity during the call, as though I didn't have cell service, but I could still make calls. Restoring my backup restored full functionality to my phone. This is on T-mobile US.
[Nexus 5X Android Development] mh0520:
I'm on Verizon. I haven't noticed that issue at all. Maybe there's something different between how T-Mobile and Verizon implement this.
[Nexus 5X Android Development] jeremywh7:
Replacing ims.apk is working for me too (AT&T US) on the 20190601 build. I took a logcat (Verbose level): cleared the log, made a successful call, waited 10s, then saved the log [attached]...if this helps to compare against my previous logcat with the previous ims.apk that was failing. I did notice this in the log (though the outgoing call worked):

W/BroadcastQueue(760): Permission Denial: receiving Intent { act=android.intent.action.NEW_OUTGOING_CALL flg=0x11000010 (has extras) } to com.google.android.ims/.receivers.PhoneStateChangedReceiver requires android.permission.PROCESS_OUTGOING_CALLS due to sender android (uid 1000)

Afterward, I called the wife then she called me back; no problems. [Other than the typical terrible call quality of normal phone calls versus Hangouts or Skype. ;) ]

Just updated to the 20190605 build with June '19 patches, and booted fine.

Separate note: I had upgraded to the 20190525 build last week by dirty flash onto 20190517, and it messed up my gapps. Reset my Gmail, removed Pixel Launcher (now had Lawnchair v2), Google Camera was no longer a system app (stock Camera now was), and I had to un- and re-install several apps to get them to work, including Hangouts (and I think some non-Google apps, don't recall). Anyway, was this expected? Was a clean flash required for somewhere between 17 and 25 May builds? Not a big deal, just curious as I've never had Gapps get messed up from a dirty flash before.
[Nexus 5X Android Development] punkwhan:
I'm on Verizon as well and can't get the incoming calls.

No problem with the outgoing calls.
[Nexus 5X Android Development] punkwhan:
Could you tell me which preferred network mode you're using?

I set mine to global.
[Nexus 5X Android Development] ideaman924:
Sure, can you take a screenshot and post it here? Thanks! I'll have to ask the ROM team on that one though.

Too late of a reply, sorry! But yeah both of the approaches would work - the second, entire vendor flashover would be cleaner but I guess if the APK replacement works no harm done.

That's very promising, now I have to find out what's different between the two vendor repositories...

That's a normal Logcat entry. You can ignore that.

As for the Gapps breaking, it's possible we had a lot of framework changes that broke something in the process during that time period. Sorry for the inconvenience.

------------- MAIN ---------------

OK, hi guys. Sorry for the long period of silence. I have a lot going on right now but rest assured bullhead is still on my to-do list and support for it is not going anywhere. Well, unless the battery dies or the MB starts boot-looping, of course!

Thanks to [MENTION=4532162]mh0520[/MENTION] for finding out that Pixel3ROM's vendor's ims.apk works fine. So as a temporary workaround, until I can find a fix please try out the APK attached in [MENTION=4532162]mh0520[/MENTION] 's post, or better yet, get it directly from Pixel3ROM if you're more security-conscious.

More updates will come soon. Stay tuned :D
[Nexus 5X Android Development] oneoftwo:
Talking of carrier-related bugs... I get the same looping reboot described by [MENTION=3040934]ChemBot[/MENTION] described here, but under different conditions -- I get it with mobile data, and I don't seem to have ims.apk involvement:

logcat

Specific behavior: On my Swedish SIM card, everything works fine (calling, text, data). I just switched to an AT&T MVNO SIM in the US, and encountered the looping soft reboot any time I turn on mobile data (and am not connected to Wifi). Calling and texting works fine though. I confirmed the bug in 2G only, 3G only and 2G/3G/LTE modes. This is on Bliss 11.5, and confirmed after dirty-flash to 11.8 latest build (sorry, currently don't have time to test it on a clean-flash 11.8 just now). Might also be relevant to mention that I have the global H791 version of the phone.
[Nexus 5X Android Development] ideaman924:
I tried replicating this inconsistency but am unable to do so. My background is all white and so is my status bar. Can you show me how it looks on your end?

Hmmmm... That's really weird. I'll take a closer look at it. Thanks for the logcat!

-------------------------------------

OK all, I did some troubleshooting over the last couple of days. It seems like the Google Assistant bug is caused by incorrect audio HALs. Fixing this is going to take some time because I have no idea on this portion.

Here's the relevant bit I captured from the logcat. You can replicate it by saying "OK Google" or "Hey Google" at the phone.

https://del.dog/qehahixusu.sql

I'll do some more testing and fixing over the upcoming weeks.
[Nokia 7 Plus Questions & Answers] mzm70:
Afternoon,

I have a TA-1062 bought from China, it has developed a really bad case of ghost touching and now has a vertical thin black line the length of the screen, Nokia Care won't entertain it even at my own expense.

Can anyone recommend an OEM repairer that can fix it, visually the phone looks perfect, never knowingly dropped etc?

Thanks
[Nokia 7 Plus Questions & Answers] ankit112:
Hey man, Not able to enable OEM Unlocking after getting pie update. Any solutions??
[Nokia 7 Plus Questions & Answers] k3dar7:
For unofficialy unlocking is need downgrade to Oreo before august update...
[Nokia 7 Plus Questions & Answers] ankit112:
How could I do that. Please assist me I'm new here in this family. Thanks in advance :)
[Nokia 7 Plus Questions & Answers] k3dar7:
unfortunately, i know only method if you not have already Pie update, but only Pie first stable from September :(

https://www.techmesto.com/how-to-downgrade-nokia-7-plus-from-stable-pie-to-stable-oreo/amp/
[Nokia 7 Plus Questions & Answers] ankit112:
Should I just wait :(
[Nokia 7 Plus Questions & Answers] k3dar7:
Maybe you can try contact service center for downgrade to Oreo?
[Nokia 7 Plus Questions & Answers] ankit112:
Yaa this can help me! Anyway thankyou so much for your help :)
[Samsung Galaxy S8 Questions and Answers] gtrs36:
I don't know why but when i receive SMS my screen wakes up by itself.

How can i turn it off?
[Moto G5 Plus Questions & Answers] engtika:
I was rooting my device and was successful l in that. I flashed TWRP and Magisk and after that I decided to install a custom ROM. While going for it I again wiped the - Delvik Cache, System, Data and Cache. And when I tried installing that ROM it doesn't gets install. Moreover I can't boot into System anymore and now I'm stucked at the screen saying "Your device has been unlocked and can't be trusted." Also the screen is showing "ID:N/A"

So please please please help me with this problem ASAP. I can't use my phone now please and I regret for what I've done. :(
[Moto G5 Plus Questions & Answers] NZedPred:
Try booting into fastboot mode. Hold down volume down and power for several seconds. If you can get there, you can flash the stock ROM and hopefully get back to normal. There are other threads that show you how to install. Make sure you use a version that is greater than or equal to what you last had installed.
[Moto G5 Plus Questions & Answers] engtika:
So this means my Stock ROM is gone? and I've to install it again?:rolleyes: Can u explain me what my problem is?
[Moto G5 Plus Questions & Answers] NZedPred:
When you installed a custom ROM your stock ROM was gone. That's how it works. But the reason you're stuck at the screen you're at, I don't know.

Restoring back to stock is the first thing I'd try to see if you can actually use your phone
[Moto G5 Plus Questions & Answers] engtika:
Thanks for the information you provided regarding my problem. Now I've installed the Stock ROM and my dead phone is back to life. ?
[OnePlus 6T  Accessories] ivanegg:
Dear all, I've just received the official OnePlus6T 3D Tempered Glass Screen Protector. Here are some of the photos to share with you guys!

The official protector do have black lines on the long edges, after applying, I think it only cover around 1px screen on each side.

Photos shoot from my OP3.

1. Package

[IMG="package"]https://farm5.staticflickr.com/4835/44242938530_e30f741bb2_b.jpg[/IMG]

2. I bought two

3. For OnePlus6T

4. What's inside

5. Step 2 is interesting, it actually asked you to use the original TPU case to assist in applying the screen protector

6. Perfect fit

7. The moment just after applying the protector, I've spent quite some time to get rid of all bubbles using the tools provided.

8. Finally !
[OnePlus 6T  Accessories] jasons1004:
Showing on oneplus.com now! Thanks for the post.
[OnePlus 6T  Accessories] Demonface.24:
Thanks , might have to order soon.
[OnePlus 6T  Accessories] JelleZon:
Why are there so much bubbles under it?:o
[OnePlus 6T  Accessories] ivanegg:
yes, so many bubbles after applying, need to use the cloth to rub the bubbles away.
[OnePlus 6T  Accessories] TheROMGuy:
Does it have that oily hazing effect that the 5t 3D protectors had?
[OnePlus 6T  Accessories] Nosferatu.:
Slightly off topic but I have one tiny bubble on the stock screen protector. What's the best way to remove it? Didn't see the need to post a brand new thread to have it answered.

Poke a needle to pop it? Any other easy way?
[OnePlus 6T  Accessories] psp888:
does the black boarder cover any part of the screen?
[OnePlus 6T  Accessories] sssarg:
1 px width on each side OP said in his initial post.
[OnePlus 6T  Accessories] prabhat775:
I dont understand the merit of those black borders on four sides, can't they make full transparent one.
[OnePlus 6T  Accessories] crzycrkr:
Typically black boarders are to mask the protector not completely adhering on the edges
[OnePlus 6T  Accessories] jasons1004:
I almost ordered the official one.....I think I may go with the TMobile version glass(no black border)....it's $40 but I can get it today instead of 1.5 weeks for the $20(plus 10shipping)

So I am just considering it as same day delivery surcharge. Ha......I have to make reasoning somehow.
[OnePlus 6T  Accessories] crzycrkr:
I went and looked at the Purearc at TMobile and walked away. It's the same exact width as the crappy ones on Amazon that don't quite reach the edge of the screen. Not worth it in my opinion
[OnePlus 6T  Accessories] borijess:
What does 1 px mean?

---------- Post added at 06:55 PM ---------- Previous post was at 06:54 PM ----------

I don't get the company that makes the phone still can't get the right dimensions to avoid coverage of the screen.
[OnePlus 6T  Accessories] jasons1004:
I hear you but it looks ok in this video.

I have not made my mind up yet....

I had a black border one for the s8 and it was ok but the black border got annoying to me

https://youtu.be/xuoaknZhlGw
[OnePlus 6T  Accessories] prabhat775:
That is very stupid of makers to think, even a full transparent one can do the job when the screen has borders itself so it will overlap. Even accurate Size with screen having black borders in tempered glass would have worked as it would just overlap the screen borders but they tend to make a bit shorter which instead add to the already border making the screen shorter from each side. When a mm is making a difference in screen to body ratio to a device now this is really stupid to think a customer will satisfy with that. I will certainly get a case and screen protector as none of my device ever slipped from my hand ever.,?
[OnePlus 6T  Accessories] ivanegg:
Sorry, I haven't used the 5t 3D protectors. So, I can't compare.
[OnePlus 6T  Accessories] TheROMGuy:
When I was running my 3D protector on my 5t it looked like it had permanent grease from a face after being in a heated conversation.
[OnePlus 6T  Accessories] ivanegg:
I just used the provided cloth and tool trying to rub the bubbles to the edge.
[Xiaomi Poco F1 Themes, Apps, and Mods] oipr:
Introduction:

Hello everyone!

This Module is created with the goal of improving both the battery life and performance of our Mi 8 devices.

Disclaimer:

* I am not responsible for bricked devices, dead SD cards,

* thermonuclear war, or you getting fired because the alarm app failed. Please

* do some research if you have any concerns about features included in this ROM

* before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.

Features:

*Reduced battery consumption

*Device-specific enhancements for the best possible balance between battery life & performance

*CPUSet improvements & optimizations

*I/O tuning for battery and performance

*Configured dynamic stune boost

*Decrease memory latency

*Better partition performance

*Network tweaks for slightly reduced battery consumption when being "actively" connected to a network connection

*Enable bus-dcvs

*Enable Power Efficient Work Queues

Prerequisites:

*Must have Magisk installed.

*Must have either Sphinx or extreme kernel installed.

*Must have Busybox installed.

Download:

https://www.androidfilehost.com/?fid=11410963190603858584

I have dedicated countless hours developing this module so if you like my work consider buying me a coffee to help me stay awake an keep improving it :) Click for coffee
[Xiaomi Poco F1 Themes, Apps, and Mods] tariq2kn:
Will it be compatible with Poco's stock Pie kernel?

If not, could you implement it?
[Xiaomi Poco F1 Themes, Apps, and Mods] afarnedi:
why this mod is here if it's for mi 8 devices? or poco and mi 8 are basically the same? just asking... ;)
[Xiaomi Poco F1 Themes, Apps, and Mods] piyush7243:
Working like a charm on my Poco. Good work man.
[Xiaomi Poco F1 Themes, Apps, and Mods] Stampyron:
It works for both because they're very similar.
[Xiaomi Poco F1 Themes, Apps, and Mods] eLaDiio:
Tested on caf with sphinx 1.9 and while i was listening music on Spotify or YouTube with the screen off from nothing the music or YouTube stop, so I disable from magisk the module and issue solved, so I don't know in what part of the tweaks generate this issue :eek:
[Xiaomi Poco F1 Themes, Apps, and Mods] oipr:
I listen to music all the time on that rom no issue :/
[Xiaomi Poco F1 Themes, Apps, and Mods] eLaDiio:
well i enabled again and nothing, no issues, i don't know what could be, anyway i will testing this days to see if again the issue appears