Database Develop

New posts should go to Koush's CM6 thread. Mods, please close.

Koush posted a new thread with the release of CM6 RC3 and this one will no longer be maintained.
Thanks to everyone for their testing and bug reports!
http://forum.xda-developers.com/showthread.php?t=755690

Thx, I hate having to read through all the other pages to get this. PLEASE edit with nightly builds.

Wireless tether works fine if u download it from the market.
Sent from my Incredible using XDA App

Quick question regarding the facebook sync. By reading your summary of the facebook, i wonder if i have a different issue. When i go to accounts and sync, when i click add then facebook. It just goes back to accounts page. Does not even let me enter facebook information. However i am able to use the facebook app.
Is this the bug your referring to, or am i experiencing something different?

killer2239 said:
Quick question regarding the facebook sync. By reading your summary of the facebook, i wonder if i have a different issue. When i go to accounts and sync, when i click add then facebook. It just goes back to accounts page. Does not even let me enter facebook information. However i am able to use the facebook app.
Is this the bug your referring to, or am i experiencing something different?
Click to expand...
Click to collapse
Yes. Does the same to me.

jermaine151 said:
Yes. Does the same to me.
Click to expand...
Click to collapse
Ok, thanks for clarifying. In your summary might want to put something regarding "Unable to add to accounts & sync" , just for others that might be curious.

Wireless tethering worked for me, i just installed the one provided in the 10minute root video again after CM6 was installed. Then tested it and it worked fine. I also have Hydra Rom for stock speed undervoted with wireless N. Noticed when i did tethering it only connected to my laptop in G mode, however i am able to connect to my router in strictly wireless N broadcast.

Had this problem last night which forced me to revert back to stock firmware.
I plugged in my phone to charge at 11 PM. Then at 12.30 ish AM, i heard my phone vibrating. I looked and it rebooted. So i let it be, then few minutes later I heard it again. Then I decided to revert back to Stock.
Thinking that it was maybe caused when charging the battery. That the batt got 100% then rebooted? Not quite sure.
I can test again if needed.

Good idea.
Thanks!

You are most welcome!

Thank You very much

what time is the nightly build and what time standard/zone?
i would love to try this but cant without bluetooth and am hoping it makes it into the next build. in my state they are cracking down on using your cell phone without a handsfree and giving big tickets to make up for budget shortfalls. so i need bluetooth. (i am too deaf for speakerphone, especially on the incredible, its not that loud)
i am excited, especially now i am 90% sure i am keeping the DINC now that the DX is officially going to be a ***** to root and no roms looks likely. and i dont know why blogs that pimp the phone keep saying "root is still inevitable" but i dont agree with that, if you cant get into the boot loader we would have never rooted the incredible and it only makes sense motorola has locked down the backflip root methods and made sure rooting will also be hard.
i just really want a bigger screen and a fast gpu, other than that, the DINC is the best.

cray1000, I edited the OP to answer your question on the build times.
You guys are all VERY welcome! I'm glad I can help make any of this easier. I can't develop (yet ) So this is my contribution for the many things I get from XDA, Koush and the other developers!

jermaine151 said:
cray1000, I edited the OP to answer your question on the build times.
You guys are all VERY welcome! I'm glad I can help make any of this easier. I can't develop (yet ) So this is my contribution for the many things I get from XDA, Koush and the other developers!
Click to expand...
Click to collapse
thanks man! keep up the good work!
and nice, based on your answer on the first post, we have a new build as of a couple hours ago, anyone running it yet? anyone have a revised bug list? should we discuss that here or in the other thread?

It would appear that the incredible has been removed from the buildbot cycle as of the latest build. A version was built today (check the dates) but looking here: http://buildbot.teamdouche.net/tgrid it's no longer listed

I hit check for update on the rom in Rom Manager, but it didnt say there was new rom. The last one under nightly builds in rom manager still has same time stamp as one i got last night.

killer2239 said:
I hit check for update on the rom in Rom Manager, but it didnt say there was new rom. The last one under nightly builds in rom manager still has same time stamp as one i got last night.
Click to expand...
Click to collapse
if you clear download cache and redownload it should be newer, someone posted the repo and it clearly showed a date and time of today even though the file name still said 7-8 or 7-9 on it the time and date were 7-10 unless it was mirrored then or osmething.

killer2239 said:
I hit check for update on the rom in Rom Manager, but it didnt say there was new rom. The last one under nightly builds in rom manager still has same time stamp as one i got last night.
Click to expand...
Click to collapse
The filename doesn't change. Just clear the download cache in ROM manager and then choose download ROM, reinstall as usual. I guarantee its a different file. Updating OP with what my current build version shows.

Sometimes download of apps in market just stalls.
Some apps fail to install. (android-vnc)
Sometimes screen doesn't register touches until rotated.

jermaine151 said:
The filename doesn't change. Just clear the download cache in ROM manager and then choose download ROM, reinstall as usual. I guarantee its a different file. Updating OP with what my current build version shows.
Click to expand...
Click to collapse
Deleted the CM6 zip file from the sd card, then redownloaded the nightly build. Installed and noticed the rom version now has 7/11 as the date instead of the zip files number. So thats good. I see you crossed out the green light while charging bug. Thats only difference i have noticed thats been fixed.
I really hope they are concentrating on Facebook, Camera, GPS bug the most. Thats the biggest deal breaker for most i know.

Getting the 'Click' to work again.

Yes, I know that the filename is "Effect_Tick.ogg" located in /system/media/audio/ui. I also know that the 'setting' is in "Settings -> Sound and notification -> Other sounds". But for some reason, it just will not play.
Yeah, I like to hear that click when I press things on my phone(s). So much so, that I have kept the old ICS sound around to write it to my other phones since.
I'll try to make this short. I had my old Nexus 6 go into a bootloop about a year ago so I restored it with a factory flash and then re-rooted it and flashed my favorite Rom, Pure Nexus 5.1.1. It (the click) had worked before, but I do not know why it stopped working. There were other problems still on my phone so I finally bought a new one and flashed it to this ROM. I used MyBackupPro to restore my apps as I do not care for some of the newer version of apps that I use. I was also trying to flash the TBO market on my phone as well. When first I flashed my phone, the click was working, but somewhere along the line it stopped. If I use root explorer and go to the file's location and press on it, it will play just fine. So I'm just not sure what's up.
I did get a big hint. I installed "FP Click sound changer". Within that app, when I press on "Effect_Tick.ogg" I get the following message:
"java.lang.NullPointerException: Attempt to invoke virtual method 'void android.media.MediaPlayer.setAudioStreamType(int)' on a null object reference"
This leads me to believe that is is something inside of framework-res.apk or systemui.apk or something like that. I didn't see enough in build.prop to make me think it would be in there. Any ideas?
Thanks in advance.

The error you're getting with FP Click Sound Changer is because the app likely isn't properly initialized. Meaning a change in Android between when the app was last updated and now has broken the app. The error has nothing to do with either of the .APK files you mentioned. If I recall correctly, neither system app deals with media to begin with.
The most obvious question here is whether you have tried a new copy of the audio file, even if it appears to work perfectly. If you have done that and are still having issues, one of your apps that you are using is causing the problem. You're going to have to do some troubleshooting to resolve this, namely starting with a blank slate and reinstalling apps one at a time until you find the one that causes the problem. Before you protest, any answers without you attempting some troubleshooting on your own are merely guesses made off of inadequate data.

Thank you for the reply, however my ROM was 'cooked' up on Sept 2015 and FP Click Sound changer was released/updated on Dec 26 2015, so what you suggest cannot be the cause. Besides, it only throws the error on Effect_Tick.ogg and no other system sound. And yes, I do have fresh copy of the file from ICS days.
But you are correct, if nobody knows which system app would throw that error message, then I know a fresh start is in order.

On this forum, many people have updated their N6 to more up-to-date versions of Android than the version you had. However, I wouldn't have provided that answer had you told us which version of Android you were running in the first place as well as the fact you built it yourself.
In any event, I hope your fresh start works out for you. You may also want to consider building a newer version of AOSP for yourself as well.

Thank you again for the reply, however:
Strephon Alkhalikoi said:
However, I wouldn't have provided that answer had you told us which version of Android you were running in the first place as well as the fact you built it yourself.
Click to expand...
Click to collapse
teddyearp said:
I had my old Nexus 6 go into a bootloop about a year ago so I restored it with a factory flash and then re-rooted it and flashed my favorite Rom, Pure Nexus 5.1.1. <snip>
Click to expand...
Click to collapse
I am trying to do a Google search on the error message itself as well.

I missed that in your post. Oops.

Strephon Alkhalikoi said:
I missed that in your post. Oops.
Click to expand...
Click to collapse
Well, I certainly meant no offence. Some years back, I used to to help folks out with their Android phones/problems and would at times be about the same way as you. Many times the details were not there. However equally so sometimes, the OP did provide the answers but the others that would chime in did not seem to read all of them.
With that said, I was thinking about rewording my question to perhaps ask if anyone knew which system apps on Android 5.1.1 would call for Effect_Tick.ogg so I could try to find where it had been set to 'null', but I stumbled across my solution after all. File permissions. So for any readers:
Yes, using ES Explorer, I copied again my good Effect_Tick.ogg to /system/media/audio/ui and it still didn't work except in music player. So I thought since ES would allow me to see and change file permissions, let me take a look. Sure enough, the file permissions for Effect_Tick.ogg were different than all the other sounds in that location. It was set to rw,rw and group sdcard,s. All the others were rw,r,r and group root. Changed to match the others and problem solved. :highfive:
Thanks very much again for trying to help, at least someone (you) did and that does mean a lot to me on such an old(ish) device since as you said, many have moved on and/or flashed much newer versions of Android to the N6. :good::good:

I'm glad you solved your problem. Even better, you came back to tell us about it.
Too many find the solution and don't say anything.

Strephon Alkhalikoi said:
<snip>Too many find the solution and don't say anything.
Click to expand...
Click to collapse
How well I remember that fact.

Prime Vid - Not Available?

So I have a Fire 7 tab that, at some point a good while back I did a whole debloat and launcher highjack on. I haven't really used this tab in quite some time. Decided to start using it again just today so dusting it off. It's on the 5.6 software now, which I realized is a mistake but I didn't realize the 5.3.6 software update was actually the 5.6.3 update (due to the typo) until I started poking around the forums here again. So ya, not super but things are working just fine still so not a huge deal I guess.
Anyway, I just realized that Prime Video is one of the apps that apparently was disabled (or whatever) when I debloated a while back. In the apps list is says "Not installed for this user". When I click on the app, the screen for it is entirely greyed out (though it does show as taking up 50.16MB on the device).
Is there a way at this point for me to get this app back? I tried installing from the play store and from a downloaded apk to no avail. Any help much appreciated. Thanks!

byproxy said:
So I have a Fire 7 tab that, at some point a good while back I did a whole debloat and launcher highjack on. I haven't really used this tab in quite some time. Decided to start using it again just today so dusting it off. It's on the 5.6 software now, which I realized is a mistake but I didn't realize the 5.3.6 software update was actually the 5.6.3 update (due to the typo) until I started poking around the forums here again. So ya, not super but things are working just fine still so not a huge deal I guess.
Anyway, I just realized that Prime Video is one of the apps that apparently was disabled (or whatever) when I debloated a while back. In the apps list is says "Not installed for this user". When I click on the app, the screen for it is entirely greyed out (though it does show as taking up 50.16MB on the device).
Is there a way at this point for me to get this app back? I tried installing from the play store and from a downloaded apk to no avail. Any help much appreciated. Thanks!
Click to expand...
Click to collapse
You'll need to factory reset or reload/sideload FireOS 5.6.3.x (or any build down to 5.4.0.0). There is no way to restore individual apps that have been 'naturalized' via techniques used in the homegrown debloat scripts.

OnePlus 7, OnePlus 7 Pro Get Android Q Developer Preview 2 Update:

Get the update here: https://forums.oneplus.com/threads/android-q-developer-preview-2-for-oneplus-7-pro-7.1054712/
I'm going to be installing this now, who else will be giving this a try?

diaztradeinc said:
Get the update here: https://forums.oneplus.com/threads/android-q-developer-preview-2-for-oneplus-7-pro-7.1054712/
I'm going to be installing this now, who else will be giving this a try?
Click to expand...
Click to collapse
I want to but One plus isn't even trying...
Last time I installed Q beta on my 6T I was so excited and then so disappointed.
https://youtu.be/x46Zspqb2DM
Hoping that this beta on the one plus 7 pro is better more features.

babyboy8100 said:
I want to but One plus isn't even trying...
Last time I installed Q beta on my 6T I was so excited and then so disappointed.
https://youtu.be/x46Zspqb2DM
Hoping that this beta on the one plus 7 pro is better more features.
Click to expand...
Click to collapse
Installation just finished I will report back what I find and let you know if it's even worth it.

Let us know how it goes...

Had an issue with start up and fingerprint at first, rebooted and was able to get through fingerprint. I go through all the startup steps finally boot and oneplus launcher force closes non stop. Reboot does not fix this issue either, I was lucky to have Nova launcher restored from back up but now navigation gestures do not work. I will try another fresh install and see what happens but so far stay away.

I was able to get through the initial setup but I had to skip network setup because the keyboard wasn't working. The rom seems very buggy.
Things like the QS pulldown animation are very laggy, gestures work but are laggy too and OnePlus launcher can randomly crash when opening app drawer and causes screen to flicker. Location permission seems to freeze the whole app and sometimes the whole phone just goes crazy and the screen flickers and the touchscreen gets unresponsive... and I've only had it installed for like 10 mins. I'd stay away ?

gigatex said:
I was able to get through the initial setup but I had to skip network setup because the keyboard wasn't working. The rom seems very buggy.
Things like the QS pulldown animation are very laggy, gestures work but are laggy too and OnePlus launcher can randomly crash when opening app drawer and causes screen to flicker. Location permission seems to freeze the whole app and sometimes the whole phone just goes crazy and the screen flickers and the touchscreen gets unresponsive... and I've only had it installed for like 10 mins. I'd stay away
Click to expand...
Click to collapse
I had to reinstall the preview version, then after everything I had to uninstall update to launcher, no more force closes and navigation gestures are working. And just as I'm typing this i rebooted device and now stuck in a bootloop. Going back to Pie for now.

Tmobile device converted to International.
SIM locked BL Locked
Installed from 9.5.7 - same errors with the launcher as everyone else. Updated and it smoothed out.
Calls only worked on bluetooth and speaker. (maybe a product of my locked bootloader?) I'm not complaining thought. It's beta software for devs and I understand that.

Why are people downloading this expecting a polished final product? IT'S A DEVELOPER PREVIEW. It's not meant for general users, it's to help developers to prepare their apps before the final version comes out. You're under no obligation to even install it.

djsubterrain said:
Why are people downloading this expecting a polished final product? IT'S A DEVELOPER PREVIEW. It's not meant for general users, it's to help developers to prepare their apps before the final version comes out. You're under no obligation to even install it.
Click to expand...
Click to collapse
Based on the posts above, I don't think anyone, including myself, is expecting a final product. No one appears to be complaining. It's feedback on their experience with the installation and performance of the Beta 2 release. I think we all know it's a work in progress. This is kinda of a heads up for others who may be considering installing it for the purpose of using it (with the occasional hiccup).

djsubterrain said:
Why are people downloading this expecting a polished final product? IT'S A DEVELOPER PREVIEW. It's not meant for general users, it's to help developers to prepare their apps before the final version comes out. You're under no obligation to even install it.
Click to expand...
Click to collapse
Why does every thread has to have some overseer come and tell us what we already know?
First of all everyone here was having a great conversation with good feedback regarding the update. No one said this is for developer's only? OnePlus also mentions "Early Adopters" please don't start with negativity just let the thread be!
On another note thank you guys for installing and reporting back your findings, It helps alot now I don't have to wipe my phone and install Q beta.

babyboy8100 said:
Why does every thread has to have some overseer come and tell us what we already know?
First of all everyone here was having a great conversation with good feedback regarding the update. No one said this is for developer's only? OnePlus also mentions "Early Adopters" please don't start with negativity just let the thread be!
On another note thank you guys for installing and reporting back your findings, It helps alot now I don't have to wipe my phone and install Q beta.
Click to expand...
Click to collapse
Lol I asked for a fingerprint theme where everyone else was requesting a theme and that GUY with the funny mustache the OVERSEER didn't approve.... Usually I get ghetto but I just kept it pushing lol.... Back to lurking because of funny mustache guy lol

Launcher kept crashing. Tried a reboot but stuck in a boot loop. Will get it sorted. Beta is beta. If you don't want issues, stay on stable.

Just a heads up, whoever still wants to give it a try do not reboot. After you play with Q for a few and want to go back to Pie. Go and download the downgrade and install. It's a little tricky because with me I lost recovery as well for some odd reason after a reboot.

diaztradeinc said:
Just a heads up, whoever still wants to give it a try do not reboot. After you play with Q for a few and want to go back to Pie. Go and download the downgrade and install. It's a little tricky because with me I lost recovery as well for some odd reason after a reboot.
Click to expand...
Click to collapse
I had the same experience

diaztradeinc said:
Just a heads up, whoever still wants to give it a try do not reboot. After you play with Q for a few and want to go back to Pie. Go and download the downgrade and install. It's a little tricky because with me I lost recovery as well for some odd reason after a reboot.
Click to expand...
Click to collapse
The recovery partition is part of the rom, that's why.

djsubterrain said:
The recovery partition is part of the rom, that's why.
Click to expand...
Click to collapse
Nope part of the boot image. Not rom.

djsubterrain said:
The recovery partition is part of the rom, that's why.
Click to expand...
Click to collapse
Totally forgot about that, I should have tried pushing twrp as I was able to get it stable enough for daily use. But for now I'll just wait for the public Beta.

diaztradeinc said:
Just a heads up, whoever still wants to give it a try do not reboot. After you play with Q for a few and want to go back to Pie. Go and download the downgrade and install. It's a little tricky because with me I lost recovery as well for some odd reason after a reboot.
Click to expand...
Click to collapse
Agree. My BL is locked but a reboot caused a bootloop. I needed to use MSM to get back up.

Let me take a wild stab at this one...no 7 Pro 5G support?
Sent from my [device_name] using XDA-Developers Legacy app

action pill on bottom isn't disappearing

I have an issue with the action pill on the bottom of the screenshot attached. Absolutely ignoring the context of the The huge contextual pill on top of my search bar, I seem to get those for a lot of the services I trigger which is fine, it's normal. My issue is they stay on the screen for a really really long time.they last several seconds to almost a minute.
Does anyone know how to reduce the time for those or why that may be happening? Has anyone else faced this issue with their pixel devices specifically? I don't seem to have this issue with my Samsung note 10 plus.
If anyone can provide clarity for me on this I really would appreciate it because it's starting to get annoying lol thank you!

https://github.com/samchugit/Immersive_Gestural_Nav_Bar
Use this module or can be found in magisk app.
The pill is there to avoid the accidentally touch navigation gesture.

keaheng said:
https://github.com/samchugit/Immersive_Gestural_Nav_Bar
Use this module or can be found in magisk app.
The pill is there to avoid the accidentally touch navigation gesture.
Click to expand...
Click to collapse
My apologies I should have been more clear I'm not talking about the tiny pill on the very bottom for navigation I meant that big white contextual overlay on top of my search bar with the contextual text.
Why it is there doesn't bother me it's just that it's there for 30 seconds to a minute sometimes I'm wondering if anybody's been able to come across how to fix that.
plus I don't know how to root my device nor I'm able to learn based off I need tutorials that have been posted so rooting is not an option sadly.

thepersona said:
My apologies I should have been more clear I'm not talking about the tiny pill on the very bottom for navigation I meant that big white contextual overlay on top of my search bar with the contextual text.
Why it is there doesn't bother me it's just that it's there for 30 seconds to a minute sometimes I'm wondering if anybody's been able to come across how to fix that.
plus I don't know how to root my device nor I'm able to learn based off I need tutorials that have been posted so rooting is not an option sadly.
Click to expand...
Click to collapse
Roots super easy on these as long as you can OEM unlock.
Assuming so install the magisk app, pull boot.img from your factory image, patch it with magisk (it will end up in your download folder as magisk_patched.img) and flash it. Boom, wham, pow.

madscribblerz said:
Roots super easy on these as long as you can OEM unlock.
Assuming so install the magisk app, pull boot.img from your factory image, patch it with magisk (it will end up in your download folder as magisk_patched.img) and flash it. Boom, wham, pow.
Click to expand...
Click to collapse
Thanks for the simplification, I gotta figure out if my device can oem unlock. It's an unlocked device purchased in Canada.
This is what I was talking about in my original post. Ignoring why it's there, or it's context. I know why those pop up. My complaint is that they are there for 30 sec to a minute in length. Why does my device do that. It's been getting annoying. Cause other devices I own have the same contextual pill but don't stay for as long as they do on my P4xl

thepersona said:
Thanks for the simplification, I gotta figure out if my device can oem unlock. It's an unlocked device purchased in Canada.
This is what I was talking about in my original post. Ignoring why it's there, or it's context. I know why those pop up. My complaint is that they are there for 30 sec to a minute in length. Why does my device do that. It's been getting annoying. Cause other devices I own have the same contextual pill but don't stay for as long as they do on my P4xl
Click to expand...
Click to collapse
That's definitely not normal behaviour. Could be caused by one of your apps hogging resources and slowing down your phone.
But if it's not that, maybe try a Factory Reset?

thepersona said:
Thanks for the simplification, I gotta figure out if my device can oem unlock. It's an unlocked device purchased in Canada.
This is what I was talking about in my original post. Ignoring why it's there, or it's context. I know why those pop up. My complaint is that they are there for 30 sec to a minute in length. Why does my device do that. It's been getting annoying. Cause other devices I own have the same contextual pill but don't stay for as long as they do on my P4xl
Click to expand...
Click to collapse
Fair. I thought I'd help on root, albeit a tangent.
What you're seeing is not normal. Have you tried a third party launcher like Nova?

madscribblerz said:
Fair. I thought I'd help on root, albeit a tangent.
What you're seeing is not normal. Have you tried a third party launcher like Nova?
Click to expand...
Click to collapse
Much appreciated! And yes I explicitly transfered everything fr pixel launcher on to Nova. I am explicitly using nova as it adds much more freedom and customization, as well as integration with sesame.
But that pop up always pops up in Spotify or files or anything giving me context on what I've done wether I've deleted something, updates a playlist, moved a photo, etc. So I know it's supposed to be there whenever it show up.
The issue is that it should not last longer than like 5 seconds max. And on my device it's 20 seconds or even longer especially when moving Giles around in device storage etc, it's a while before it goes away and has become annoying lol.

madscribblerz said:
Fair. I thought I'd help on root, albeit a tangent.
What you're seeing is not normal. Have you tried a third party launcher like Nova?
Click to expand...
Click to collapse
Plus with regard to root I figure I'm better off waiting until my device is no longer supported because if I root now, it's going to be like going through hell and back trying to get monthly updates or feature drops flashing this flashing that.
that whole procedure seems very tedious and filled with a lot of leg work. And not only am I dumb but I'm also lazy LOL so I hope in three years time rooting a device namely p4xl will become foolproof. Lol
But I might have the spine to delve into it once the p4xl isn't supported by Google

thepersona said:
Much appreciated! And yes I explicitly transfered everything fr pixel launcher on to Nova. I am explicitly using nova as it adds much more freedom and customization, as well as integration with sesame.
But that pop up always pops up in Spotify or files or anything giving me context on what I've done wether I've deleted something, updates a playlist, moved a photo, etc. So I know it's supposed to be there whenever it show up.
The issue is that it should not last longer than like 5 seconds max. And on my device it's 20 seconds or even longer especially when moving Giles around in device storage etc, it's a while before it goes away and has become annoying lol.
Click to expand...
Click to collapse
Not an exact answer, given, but that is a toast message that you're dealing with. You may want to look for options on how to modify the default behavior for toast messages. It likely requires root to modify but if you can do so then that's where it'll be. you may want to look in the settings for the apps where it displays to see if there is some kind of toast notification option to disable.
---------- Post added at 07:41 PM ---------- Previous post was at 07:39 PM ----------
thepersona said:
Plus with regard to root I figure I'm better off waiting until my device is no longer supported because if I root now, it's going to be like going through hell and back trying to get monthly updates or feature drops flashing this flashing that.
that whole procedure seems very tedious and filled with a lot of leg work. And not only am I dumb but I'm also lazy LOL so I hope in three years time rooting a device namely p4xl will become foolproof. Lol
But I might have the spine to delve into it once the p4xl isn't supported by Google
Click to expand...
Click to collapse
It is kind of foolproof, but does require a few manual steps each time you update. Do know that Google does not void the warranty for devices that are rooted.
Personal preference I respect, but I wouldn't let technical obstacles overcome your desire to root at some point. It's actually very simple compared to other devices I've had including the earlier pixels, so if all things are equal the Pixel 4 is the easiest to deal with.

madscribblerz said:
Not an exact answer, given, but that is a toast message that you're dealing with. You may want to look for options on how to modify the default behavior for toast messages. It likely requires root to modify but if you can do so then that's where it'll be. you may want to look in the settings for the apps where it displays to see if there is some kind of toast notification option to disable.
I looked into the settings there's nothing on there specifically or explicitly talking about toast notifications. But that is a clearer answer I just can't seem to figure it out I thought it would have been notification dots but it's not that. Ah well lol
---------- Post added at 07:41 PM ---------- Previous post was at 07:39 PM ----------
It is kind of foolproof, but does require a few manual steps each time you update. Do know that Google does not void the warranty for devices that are rooted.
Personal preference I respect, but I wouldn't let technical obstacles overcome your desire to root at some point. It's actually very simple compared to other devices I've had including the earlier pixels, so if all things are equal the Pixel 4 is the easiest to deal with.
Click to expand...
Click to collapse
Yeah I agree with what you're saying and that's interesting I did not know that Google doesn't void the warranty if one decides to root their device. Thanks for the tidbit. Yeah I agree with you having a technical obstacle overcoming the desire right now is pretty high and it stings because if I knew I could do it in a way where I won't break my device or really mess it up that would have helped. I just recently learned about ADB and I haven't fully grasped the concept but I know enough to just get by lol.
If you know of a guaranteed method on how to root the Pixel 4 XL without damage to the device I would appreciate a link to a thread or even a video. Because everything that I've heard has been hit or miss everybody's gotten different results and potentially bricked or messed up their device there has been more mess ups then success and not been one guaranteed solution on how to root the device in a way where it wouldn't mess something up.

thepersona said:
If you know of a guaranteed method on how to root the Pixel 4 XL without damage to the device I would appreciate a link to a thread or even a video. Because everything that I've heard has been hit or miss everybody's gotten different results and potentially bricked or messed up their device there has been more mess ups then success and not been one guaranteed solution on how to root the device in a way where it wouldn't mess something up.
Click to expand...
Click to collapse
Ok,I'll give you a 101.
First unlock flashing. It's the same for all pixels and consists of 2 steps. The first is changing a setting under developer options (to enable developer options click the build number in about several times until you see it enable) and then toggle OEM unlock to enabled.
Step 2 is booting into fastboot mode (vol down while booting) and actually unlocking the phone (fastboot flashing unlock).
There are help files everywhere on that part so find one you like to get you through those steps. Again in this all pixels are equal, so don't stress if you can't find help for the 4 specifically. Note you do not need to unlock critical, and also note doing this will wipe your device. If you've done it right on startup you'll get a yellow warning screen (ignore).
The next part is rooting. Update your device to the latest factory image (boot in fastboot mode and run flash-all from the zip (remove the -w from the bat file if you don't want to wipe the phone).
Boot the phone after and let it run the ROM upgrade app. Install the magisk app and choose install and in the ROM image you downloaded is a boot.img file you will tell magisk to patch. Do so and in download you'll have a magisk_patched.img file. Move that to your computer, reboot into fastboot mode, and fastboot flash boot magisk_patched.img.
Reboot and you're in business.
I'll keep an eye on this thread and if you run into any problems I'll help you quickly. Also note you can't really destroy a pixel. There is a lot to cover to explain why (and I'm sure some creative soul has managed to) but you can always flash the factory ROM with the -w included in flash-all.bat to recover.
It is scary if you haven't done it, but if you're like me once you're rooted it was so easy you'll feel silly.
To update monthly download the ROM, extract boot.img, patch it with magisk, apply the ROM (no -w), reboot and let the ROM finish, reboot to fastboot mode, flash magisk_patched.img (like above), boot and all is good.
Any questions, just ask.

madscribblerz said:
Ok,I'll give you a 101.
First unlock flashing. It's the same for all pixels and consists of 2 steps. The first is changing a setting under developer options (to enable developer options click the build number in about several times until you see it enable) and then toggle OEM unlock to enabled.
Step 2 is booting into fastboot mode (vol down while booting) and actually unlocking the phone (fastboot flashing unlock).
There are help files everywhere on that part so find one you like to get you through those steps. Again in this all pixels are equal, so don't stress if you can't find help for the 4 specifically. Note you do not need to unlock critical, and also note doing this will wipe your device. If you've done it right on startup you'll get a yellow warning screen (ignore).
The next part is rooting. Update your device to the latest factory image (boot in fastboot mode and run flash-all from the zip (remove the -w from the bat file if you don't want to wipe the phone).
Boot the phone after and let it run the ROM upgrade app. Install the magisk app and choose install and in the ROM image you downloaded is a boot.img file you will tell magisk to patch. Do so and in download you'll have a magisk_patched.img file. Move that to your computer, reboot into fastboot mode, and fastboot flash boot magisk_patched.img.
Reboot and you're in business.
I'll keep an eye on this thread and if you run into any problems I'll help you quickly. Also note you can't really destroy a pixel. There is a lot to cover to explain why (and I'm sure some creative soul has managed to) but you can always flash the factory ROM with the -w included in flash-all.bat to recover.
It is scary if you haven't done it, but if you're like me once you're rooted it was so easy you'll feel silly.
To update monthly download the ROM, extract boot.img, patch it with magisk, apply the ROM (no -w), reboot and let the ROM finish, reboot to fastboot mode, flash magisk_patched.img (like above), boot and all is good.
Any questions, just ask.
Click to expand...
Click to collapse
Thanks brother I appreciate the guide and your patience in explains this and willing to help me out with this. The language and terminology I think is the most intimidating lol. I've got a MacBook pro so hopefully I can give this a shot and it will work with that device.
I'll keep you posted.

thepersona said:
Thanks brother I appreciate the guide and your patience in explains this and willing to help me out with this. The language and terminology I think is the most intimidating lol. I've got a MacBook pro so hopefully I can give this a shot and it will work with that device.
I'll keep you posted.
Click to expand...
Click to collapse
No worries
Only change with a Mac is the flash-all.bat I mentioned will be flash-all.sh.

thepersona said:
Much appreciated! And yes I explicitly transfered everything fr pixel launcher on to Nova. I am explicitly using nova as it adds much more freedom and customization, as well as integration with sesame.
Click to expand...
Click to collapse
I briefly tried Nova (but went back to Action Launcher) and I don't remember having that kind of problem. Did you have this problem before you switched to Nova?

fclifton said:
I briefly tried Nova (but went back to Action Launcher) and I don't remember having that kind of problem. Did you have this problem before you switched to Nova?
Click to expand...
Click to collapse
Nope not at all I think it occured after some update probably March.because it's been occurring to the point where I've noticed all throughout March I'm now updating to the April security patch so hopefully that will fix it

madscribblerz said:
No worries
Only change with a Mac is the flash-all.bat I mentioned will be flash-all.sh.
Click to expand...
Click to collapse
Hey man do I need to install any Google drivers onto a Mac apparently when I go to the website it says I don't need to but for rooting do I have to do that?
And do I just Google how to fast boot flash a pixel or something in order to get the zip folders you talked about?
Is this walkthrough in the video below the same as the method youre describing? Cause I can't seem to find any guides on how to do that method.

thepersona said:
Hey man do I need to install any Google drivers onto a Mac apparently when I go to the website it says I don't need to but for rooting do I have to do that?
And do I just Google how to fast boot flash a pixel or something in order to get the zip folders you talked about?
Is this walkthrough in the video below the same as the method youre describing? Cause I can't seem to find any guides on how to do that method.
Click to expand...
Click to collapse
That is a much more detailed guide to the approach that I'm describing. I think following it you'll be able to do it without issue. It's the same approach I've been using for months with no issues. I've even gotten so confident in it I don't even back up my phone before I update monthly. I just know things are going to work.
The zip folder comes from Google just search for Pixel 4 factory image and there will be a page with downloads of the most recent ROM files. April was just released yesterday. That's the file that you want to download and will have the boot.img in it.
I'm not certain on a Mac, but on a PC you have to download the USB drivers and then the platform tools from Google in order to have what you need to make this work. But I think the guide you're referring to will be able to give you that stuff.
---------- Post added at 06:25 PM ---------- Previous post was at 06:01 PM ----------
thepersona said:
Hey man do I need to install any Google drivers onto a Mac apparently when I go to the website it says I don't need to but for rooting do I have to do that?
And do I just Google how to fast boot flash a pixel or something in order to get the zip folders you talked about?
Is this walkthrough in the video below the same as the method youre describing? Cause I can't seem to find any guides on how to do that method.
Click to expand...
Click to collapse
The ROM site is https://developers.google.com/android/images

I figured out my original issue on this post. It was in accessibility, the setting was called time to take action timeout! Now it's fixed. The bloody toast notification is back to default!

thepersona said:
I figured out my original issue on this post. It was in accessibility, the setting was called time to take action timeout! Now it's fixed. The bloody toast notification is back to default!
Click to expand...
Click to collapse
Awesome news. I learned something so win-win. :good: