yashsingh1/xdaforums huggingface dataset:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] tst1212:
I've been using Pixeldust since January and love it, however it seems the last few releases have not been as stable as some of the earlier ones. I recently got a "brand new" pixel off eBay, and yes, it appears legit Brand New. New packaging, AccuBattery shows health over 2500mAH, so it's new. I Unlocked, TWRP, etc and all went off perfect, however after installing the new version of Pixeldust, I'm getting random reboots. I can't reproduce it, I've just noticed when i pick up my phone after sitting a while it appear to have rebooted. I'm considering rolling back to a previous version, but don't see any links.

Has anyone else rolled back, and if so to which version do you find most stable?

I'm happy to try and pull a logcat, never done it but will try if it'll help.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] kkjb:
Roll back, to what? For me this current build is fine. In fact first one (for me) to allow data on google Fi through the 3 carriers in my area. Sometimes hit or miss. Freezing is a rather nebulous description. Logs please... And don't say how, look it up. I like current kernel too, your choice of king...great...Thanks :)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] tst1212:
Rollback to a previous version, if you don't know what 'Rollback' or 'previous version' is, look it up.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Ilko:
For people having troubles, try to flash the latest twrp 3.3, not the one linked in OP, then do a clean flash of the latest factory image before installing the ROM.

TWRP 3.3 installer

TWRP 3.3 img
[Google Pixel ROMs, Kernels, Recoveries, & Other De] kkjb:
Wow, really?!? I KNOW-HOW. It was a oblivious hint that what version is perfect or not buggy! Really, since as seen by dev comment. Logs to help. Of course very few people say thanks, just b.t.h. caution on 3.3 twrp, it gets errors sometimes so be prepared. Trying to correct with 3.2.3-1 no the way to recovery from 3.3. Just a heads up
[Google Pixel ROMs, Kernels, Recoveries, & Other De] r29:
I shall do that =)

attached logcat but not 100% sure as the device has froze yet but ill wait for it to happen and pull another one

Ima do a clean flash and test.

Thank you for the amazing rom and support though =)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ztotherad:
about to download and flash this! I'm excited because I'm sick of stock lol
[Google Pixel ROMs, Kernels, Recoveries, & Other De] r29:
Hi,

I did a clean flash on factory image and rom and I am getting random freeze and then it reboots itself. Attached logcat from after the phone rebooted itself after crashing.

Hope someone can help me figure this out =)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Master Cylinder:
I had people trying to call me today on latest build but no ringing or notification of calls. They tried to leave a message and were not allowed to. When I heard of it, I rebooted and there were the notifications of missed calls. I have had problems with not receiving texts and connecting to the network for calls that a reboot cured on the last version. I have no idea about when it becomes disconnected - I could reboot everyday, maybe that would ward it off?

Gotta bail - can't be missing calls and texts anymore ...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Geofferey:
Experience

Hey guys, just wanted to come back and share my experiences with Pixel Dust... Since re-flashing stock rom and reinstalling Pixel Dust v8 things have been great. GPS works terrifically and I have not seemed to experience any crashes or random reboots in past week or two. I've basically changed every setting I can think of and haven't noticed anything awry. I get all my calls and notifications as well.

For those who are experiencing problems like apps not opening etc, do you have Magisk installed? I literally started noticing issues once Magisk was installed with hide enabled and modules that place files in system "system-lessly" by use of "mount --bind". These problems also occured in Lineage... After making sure magisk does not utilize mount bind for must haves like busybox etc (I have ways) and disabling hide I have not had a issue. For some reason I still pass all safety net checks & I can utilize gpay. For really... Having a re-locked bootloader might be partly why tho.

Also [MENTION=5091819]spezi77[/MENTION] I have a suggestion... If at all possible can you set these params in default.prop next build? For a daily driver these should be set to the secure defaults. Users who want to use ADB to interface with

their device should enable manually and accept request. If not I am perfectly content with setting these myself after each install, I'm just thinking about the safety of other users data.

ro.adb.secure=1
ro.secure=1
persist.service.adb.enable=0
persist.sys.usb.config=none

One more thing haha, I really miss sliding across my status bar to adjust brightness when going outside on a bright day. I'm not really a fan of automatic brightness cause I think it's counter intuitive for CPU to process LUX sensor data in an effort to save battery by wasting it. Just a thought. Thanks again for everything man. I really do love this ROM! I even felt a bit guilty when I had to switch to Lineage to test if issues weren't isolated to your ROM lmfao. Anyways, I've been back for about two weeks now and I'm loving it.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bleichtman:
How do I change from Celsius to Fahrenheit for the weather?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Master Cylinder:
Turns out my network problems were probably not related to this ROM. How things got so balled up I don't know, but using 7 digit dialing I was calling people across the country! After chatting online with a Google fi tech and inputting some codes, things seem normal for now. I'm going to put this back on if for no other reason than for Slim Recents - there is nothing more dysfunctional than stock recents for me. I wish I could just flash that over stock.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] WelldonePL:
Hi all,

is there any way to lock band in this ROM?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] TheArkive:
Very nice ROM. Just one issue I'd like to report.

When dial pad sounds are disabled, and when making a call and trying to interact with an automated voice prompt, pressing numbers seems to have no effect.

When I enabled dial pad sounds, I was able to proceed with the voice prompts on my phone call.

I was calling my bank in this case. I tried the call several times. Each attempt to proceed failed until I enabled the dial pad sounds.

Can anyone else verify this?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ziouzitsou:
No root periodically - Magisk v19.2

Hello all,

Do you lose root with Magisk v19.2?

I have to flash the Magisk zip via TWRP every time, which happens almost once per month.

I have tried to hide it from apps, but problem remains. Also no extra modules are installed.

This is Pixeldust, release 4.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] WishMi:
I had the same problem a while back, probably with V4. You should update. I'm on V6 and everything is perfectly stable.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] tst1212:
I had the same issue on an earlier version, random reboot, lost root, missed calls. It was so bad I switched to a different ROM., however I recently came back for the Google Dialer features. I'm on the Pixeldust v8, Magisk 19.3, and so far none of the previous issues. Uptime is 40 hours, with no reboots or loss of Magisk.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] churchmice:
Great ROM, however, some apps will FC, can any guru take a look ?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ovu85:
Automatic brightness in low light varies a lot.

In about 30 sec gets a little brighter, stays for 2-3 seconds and then again at the lowest level for another 30sec and the whole process repeats. I've blocked the light sensor and the result is the same.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] spezi77:
Hey there,

we're proud to announce the arrival of release nine:

- Android 9.0.0_r41 (PQ3A.190605.003, June 2019)

- Switched to my personal PD-CAF-Kernel (most stable & reliable)

- Welcome back PD Launcher (now running stable)

- Japanese translations added (credits to [MENTION=6449979]mamarama9904[/MENTION])

Enjoy the PixelDust Goodness!

;)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] spezi77:
AOSP issue. :rolleyes:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] spezi77:
There is no root cause in the sauce code. Try a clean ROM install incl. clean app installation (do not restore the affected apps via Titanium or Gdrive). :fingers-crossed:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] churchmice:
Thanks, I have tried a clean install already, still no gain.

I think I have no way but to wait for the vendor to update the app, not sure what is causing it to FC, could due to the june security update.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] toasterboy1:
Anyone else with lag on the latest build? Dirty flashed. Magisk after initial boot. No other mods that I am aware of. Some apps take over 1 minute to load and then are almost unusable. Trying to ride it out. Tried rebooting this morning, not something I usually do, my phone is usually on 24/7. Love the ROM and not trying to complain. Willing to provide any logs or help to continue to make this the best ROM for the Pixel.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Master Cylinder:
I have been experiencing A LOT of lagginess and stuttering performance. I put the latest version of ElementalX on but after awhile, same thing. Really seems off.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] r29:
I was having issues on dirty flash. I did a clean flash with factory image then latest build everything is good
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Alexisnotfrommars:
I'm getting a lot of lag in this build, idk what's causing it tho
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Master Cylinder:
The same is being reported on the Marlin thread. Lagginess. Getting stuck sometimes.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] toasterboy1:
Appreciate the heads up. I just clean flashed when I went to build eight because I had been trying a few other ROMs. I know it sounds like I am wining but I hate setting everything back up. As it is now TWRP has problems with fingerprint + pin so I have to disable that and set it back up every time I want to flash an upgrade. Which in turn means I have to setup the fingerprint in at least 3 other apps. Not sure if I would run into the same problems on the stock builds too or not. I will just deal with it until the next build comes out.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Master Cylinder:
I wonder if you could use Titanium Backup to backup and restore the data for those apps, and perhaps the initial fingerprint security as well?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] igorhh:
I have issues

Hello. I use the latest build of Pixel Dust on my Pixel, and i have poor UI perfomance. I have big glitches, when im scrolling content. But on other Pie roms i dint have this issues. What i should to do? Thanks, Igor.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] jontxo:
Hello

Hello.

For me the performance of this rom is better with the last version ( I have done a clean install).

I have tried to install francos kernel but it gives me an error saying that the kernel is bigger than the boot partition. How could I solve it ?

Regards
[Google Pixel ROMs, Kernels, Recoveries, & Other De] r29:
anyone have issues with sms not sending or receiving on latest build?

Edit: problem fixed seemed to be a faulty android message app update. reinstalled and rebooted seems to be okay now
[Google Pixel ROMs, Kernels, Recoveries, & Other De] igorhh:
I have no issues with sms on this build.

I have no issues with sms on this build.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] toasterboy1:
From the man himself off the Pixel XL thread. Seems to work. Just not sure if there is an easy way to change all cores at once without an app and survive reboot.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Master Cylinder:
As toasterboy1 has indicated, on the Marlin thread the cpu governor is being targeted for the problems. Mine was set to 'Performance' but I have put it on 'Sched' as recommended by the shagbag913 post above. Used the free Kernel Audiutor to set it and apply on boot. I'm putting it through it's paces now...

Hopefully this solves the problems.:good:

EDIT: I'm definitely seeing immediate improvements!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] spezi77:
Sorry for the "lag" in this build caused by not adjusting the CPU gov while switching to a new kernel. #facepalm

P.S.: I have great news for PixelDust fans. You may have noticed that there were not too many ROM feature updates, but more or less an increase in the security patch level. The reason is that we were working in parallel on a CAF based version of PixelDust.... coming soon! ;)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ThePhoneGeek:
No worries... Some us didn't update to this build when we saw others were having issues. Is there a revised one coming or should we just wait for the next build?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] royerhdz:
Hi guys just installed this rom on my pixel, is battery good?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ab4nk:
Sure for daily usage ,i got 18 to 19 hours oh batt life
[Google Pixel ROMs, Kernels, Recoveries, & Other De] royerhdz:
Do you have a group on telegram or whatsapp?

I want to join to stay tuned about new releases of anything for this device since I got mine a few days ago
[Google Pixel ROMs, Kernels, Recoveries, & Other De] pangolin.rollin:
Can't wait! ;P appreciate all your hard work. Can confirm in the meantime tho switching kernel governor to sched helps a lot! Cheers.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] honeybear81:
Are you doing that with the stock kernel? I did it with Franco kernel and still had issues
[Google Pixel ROMs, Kernels, Recoveries, & Other De] pangolin.rollin:
Yeah I'm using stock (whatever came with rom). I used EX kernel manager to change to sched and enabled at boot. If francos isn't working maybe try exkernel? I might play around with others now.

Edit: Ex kernel works fine as well.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] honeybear81:
OK thanks. I reflashed and left the stock kernel and its doing much better.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] tst1212:
I know it's frowned upon to ask "when?", but I noticed Marlin got CAF recently. I'm currently on PixelDust 8 and want to do a clean install to 9, however would prefer to go straight to the CAF version. If I update to 9 today, is CAF gonna be out tomorrow?

Thanks for your great work!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Silicon42:
Having a problem with the screen staying asleep.

I just recently installed this ROM and now it seems that whenever my Pixel falls asleep the screen almost never wakes up again. It still vibrates when long holding the lock button as it would when the power menu is brought up but the screen stays dark and touch input doesn't seem to work. Occasionally the screen will wake up after a couple seconds and then it will work, but otherwise if I don't catch it or I've pressed the button again, it will go back to sleep. Any idea of how to fix this issue or what might be wrong here?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Master Cylinder:
Hmmm .... This was a widespread problem a few builds back, but has since disappeared. I don't remember if there was a fix other than a new build, but I'm not sure. You might search the thread on that and you'll find numerous references to it.

EDIT: And on the Marlin PixelDust thread.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Silicon42:
It doesn't seem to be the same issue. That issue is about the phone not going into deep sleep whereas I'm having problems getting it out of sleep. I went through a fresh install just to make sure I wasn't doing something wrong, but the problem has persisted. It's possible that this has something to do with this being a Verizon Pixel, but as far as I know those are exactly the same hardware and model number wise and use the same stock firmware. They're just a bit more finicky about when you are allowed to unlock the bootloader.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Jesse402:
Failure to wake has plagued me on certain roms on Pixel. I've never been able to nail it down when it happens or what causes it. It is difficult to log because the consequence of the glitch is that you must force reboot a lot of the time and it's not something like a FC where you can go reproduce it whenever you want. Do you by chance use expanded desktop? That's the only thing I've ever thought might be related, but I have been off Pixel Dust for awhile and have not been dealing with the glitch as of late.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Silicon42:
Yes, I do use expanded desktop. It's one of the main reasons I wanted to install a custom ROM since I was hoping to use it to help prevent burn in since I just replaced the screen. If that's the cause behind it, I might be able to live without it, but I think I'd rather try another ROM first. Do you know of any other ROMs for Pixel that are based on Android 9 and don't have significant issues with them?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Master Cylinder:
I never used expanded desktop and I had this issue on a couple of builds of this ROM. Your search terms may need tweaking because I

know

that is was widely discussed. However, there never was a solution as far as I can remember, so probably no point anyway. If you are having that on build 9 it's the first I've heard of it.

EDIT: Are people on the Marlin thread reporting this for build 9?

-->Did you change the CPU Governor as indicated on the previous page of this thread for build 9 to Sched?<--
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Jesse402:
I have never had a wake failure running 9.0 Bootleggers w/ expanded desktop. I have not tried Evolution X yet. I have run into the issue on Pixel Dust, and older versions of ResRemix and crDroid.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Silicon42:
I am having the problem on build 9. I suppose I'll have to try different search terms but I can tell now that it definitely is occurring when I have expanded desktop turned on. With it turned off, there doesn't seem to be any issue. I have not changed the CPU Governor but I will make a note to do so. Thanks for the help!

I also have a separate issue where if I attempt to re-lock the bootloader so I don't have to wait through it's complaint screen, it goes into a boot and instant crash loop

Hmm I'll consider checking those out. My main concern is performance in VR, battery life, and burn-in protection, although a good camera app would be a nice to have as well.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] tst1212:
Don't relock your bootloader, it'll prevent you from installing custom ROMs. Besides, I think you have to be on stock to relock.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Silicon42:
A bit of an update on the problem I'm having: I've done some testing and it seems that this only affects whether or not the display itself wakes up. If I manage to touch one of the buttons that are supposed to be on the lockscreen or swipe up to unlock it, it will still unlock and the screen will turn on at that point and behave normally. I've also slightly narrowed down the cause. This only occurs when the nav bar (bottom) is hidden due to expanded desktop/immersive mode but does not effect apps that use it on a case by case basis. The issue is not effected by if the status bar (top) is hidden in this way. When trying to open the lock screen, I've also managed to get the screen to wake up occasionally and when I have, the navbar seems to be flickering while overlaying the bottom shortcut buttons. Perhaps there is an app that I can blacklist from expanded desktop mode to fix the issue completely, but I'll look into that later.

I also have a new problem. The System UI app uses an overlay that I can't disable which is preventing me from changing permissions in some apps and from logging in Google's Daydream app. If I force stop it, it just immediately starts back up. I know it's the system UI app because I've disabled drawing over other apps on all the other apps that were allowed to do so and that is the only one left. Does anyone have a solution or workaround for this?

Edit: Found a root level permission editor and turned off it's draw over other apps permission, but I still get an overlay detected issue so maybe it's not the System UI app but something else that is hidden.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] vovabulatnikov95:
Waiting CAF builded Dust for sailfish with anticipation!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Master Cylinder:
Ditto!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] tst1212:
So I have a weird error.

I have used the same pattern password for years, I know it's right. However now it doesn't seem to work. Whenever I try it, it says "Wrong Pattern" but it opens anyway. I can't remove the pattern either, same thing happens "Wrong Pattern" . If I goto TWRP "Wrong Pattern" again and if I try to reinstall, all is encrypted. Do I need to go all the way back to flashing stock, and complete setup?

Nevermind: After a reboot, I couldn't get past the pattern / phone is booting screens, so I went ahead and started fresh. Seems to be working now.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] kanwaradil94@gmail.com:
Not sure if anyone else is facing the same issue. But when I flash the rom and Magisk, I boot into the system set it up but then when I try to access the internal storage I am unable to since it is encrypted. I always get put the password in to decrypt storage, however, I even format the data storage always before and after installing the rom. Could someone guide me incase I am doing something wrong.

---------- Post added at 05:06 PM ---------- Previous post was at 05:04 PM ----------

Im having the same issue just wrote about it now. As soon as I install the rom and set up everything. I am end up with the same thing occurring again even after clean installing the rom. Any ideas.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] tst1212:
I had to go back to the beginning, flash stock, NOT the ROM...Google Stock image, the "flash-all" script. You are going to lose everything, /data pictures etc, but it does work. Mine got to the point where I couldn't boot into the phone, it got stuck on "Phone is starting".
[Google Pixel ROMs, Kernels, Recoveries, & Other De] kanwaradil94@gmail.com:
But I'm the end were you able to flash the rom and get access to the internal storage again after flashing is the question. You mentioned it works but what does

---------- Post added at 01:34 PM ---------- Previous post was at 01:34 PM ----------

But in the end were you able to flash the rom and get access to the internal storage again after flashing is the question. You mentioned it works but what does
[Google Pixel ROMs, Kernels, Recoveries, & Other De] tst1212:
Yes, I'm back on Pixeldust r9, HOWEVER ...and a giant however, it erases all your data. It completely formats Internal data, but you can use your phone again. The issue is, the internal data is encrypted, and somehow the password got screwed up., so no way to decrypt it. This was not a big deal for me, as all my data is backed up somewhere, ie onedrive, outlook, etc.

It will be like starting with a new phone.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] spezi77:
Here we go:

https://xdaforums.com/pixel/development/rom-pixel-dust-caf-sailfish-release-one-t3957926