Currently on Nitrogen OS.. I've been having an issue where I will hold the home button down to pull up search, tap on the search bar to bring up the keyboard, and within a few seconds the search bar clears itself and closes the keyboard. I made a screen recording to show you the issue in action. The first instance I don't type anything, just wait, and it closes itself. The second time I started typing and it happens again. So basically every time I open search I have to tap the search bar, wait for the keyboard to close, then tap the search bar again, then it works... until i need to search something else.
Here is the recording of the issue in action
I've posted this issue in multiple places and nobody knows the answer. Some people have said they've experienced this issue while on stock and with other mods installed. No idea how to figure out what exactly is causing this.
did you wipe cache and data of the google app, and reboot?
did you allow all permission of the google app and reboot?
thats what I would try
This same thing is happening on Moto Z Force (Verizon). I was running Android M when this started happening. I downgraded the Google app to the stock version and it fixed the issue.
I just updated to 7.0 and it's back. I tried downgrading the Google app, but this time it was just uninstalled.
I saw your post on stack exchange but can't reply (rep).
I, too, had Nova installed, as a reply assumed. It said to switch, so I uninstalled Nova, used the stock launcher, rebooted, cleared my cache partition, and the issue persists.
I reviewed your log and I think it has something to do with the assistant; maybe screen polling. My search bar closes after either 8 or 12 seconds (that's not a range, one or the other). I noted your screen recording was 8 seconds.
I'd really like to get this sorted, too. I'm happy to help in any way I can.
No news on this? I'm surprised it's not a bigger issue. Nothing I do helps. The problem seems independent of cash, system resource, or run time.
I sorted it, at least on my phone. I had to downgrade the Google app, downgrade Google Play services, disable both, reboot into recovery, flush my cache partition, reboot, enable play services, upgrade, enable Google, upgrade, and now the issue is gone.
---------- Post added at 06:05 PM ---------- Previous post was at 06:04 PM ----------
citenx said:
I sorted it, at least on my phone. I had to downgrade the Google app, downgrade Google Play services, disable both, reboot into recovery, flush my cache partition, reboot, enable play services, upgrade, enable Google, upgrade, and now the issue is gone.
Click to expand...
Click to collapse
Forgot to mention if you follow this procedure on the Moto Z then you will have to deal with a notification every second saying Motorola voice has stopped working. You just have to muscle through it.
Well, I was wrong.
It definitely worked for a while. Now the issue is back. I'll try to find some time to isolate the issue.
---------- Post added at 07:50 PM ---------- Previous post was at 07:49 PM ----------
BTW, this is the stack exchange thread I meantime above: http://android.stackexchange.com/questions/163620/google-search-not-working-properly-logcat-included
You do know about a simple tool that will tell you just what is going wrong right? Its called a logcat and it is troubleshooting 101. There are tons of tuts on the site on how to pull and read one. Just stating that it is closing on your device really means nothing and is not worth the time it takes to type out a post unless you add a logcat file with it.
zelendel said:
You do know about a simple tool that will tell you just what is going wrong right? Its called a logcat and it is troubleshooting 101. There are tons of tuts on the site on how to pull and read one. Just stating that it is closing on your device really means nothing and is not worth the time it takes to type out a post unless you add a logcat file with it.
Click to expand...
Click to collapse
This.
Plus you didn't even list which gapps version you used which would also be relevant to troubleshooting.
Related
I have Cyanogen's 4.2.3.1 installed with the 2.0 Maps application and Navigation works correctly for me.
Since I installed Navigation I am getting a huge "Double tap to answer" button that pops up on my screen when a call comes in.
A) It seems to have shortened the amount of time my phone rings before sending to voicemail
B) The double tap is flaky
C) It looks like ****
I have searched Google and the forums to see if this was an issue people had but can only find people talking about the in-call unlock screen.
Does anyone know why this is happening and how to stop it?
Is your navigation actually on while this is happening? If you have the little triangle above in your task bar then it is.
If you are fully exited from maps this shouldn't come up. At least it doesn't on my phone.
This happens all the time now. Even with GPS off and the Maps app not even loaded. Persists through reboots.
Odd. This happens while I have maps loaded, but not when its not loaded.
How did you install navigation?
push back our old build.prop
Will pushing back my old build.prop disable navigation?
No navigation only needs it for the install. I thought that might be the problem. Push your old prop files back and good luck!
this happend to me aswell, but i actually liked the double click - box look
that would also happen when my phone was just sitting here, no nav on, it would just light up, and have the double click box lit up.
i was on 4.2.3.1.
all that ended when i flashed cyan 4.2.4
i didnt wipe.. or fix permissions.
i installed navs from other thread [basically just the update.zip and clear data]
and everythingg works just fine. thanks to all!
I didn't know 4.2.4 was out yet but thought a Cyanogen Mod update would probably fix that issue. Reverting to my previous *.props has fixed all the issues.
You should've posted this in the Q&A section or an existing related thread.
Anyways.. To get rid of the double tap box, you need to push back the original build.props. If you do that however, you'll lose navigation in a few hours, like 6 or 7 hours.
There's already a thread about this that's named something like "unlocked features from new build.prop".
tee aiy emm said:
You should've posted this in the Q&A section or an existing related thread.
Anyways.. To get rid of the double tap box, you need to push back the original build.props. If you do that however, you'll lose navigation in a few hours, like 6 or 7 hours.
There's already a thread about this that's named something like "unlocked features from new build.prop".
Click to expand...
Click to collapse
I will remember that next time. After being on here for almost 3 years I forget that the newbie youngsters like to change how we have done things here. Like one thread per issue. Thank you for the helpful link to the thread you thought I should have posted it in, great to see that XDA hasn't gone all to hell with newbie senior members who just throw out dictates and then can't even do a decent job of helping people.
use this if you are running cyanogen http://forum.xda-developers.com/showthread.php?t=583684
Heres the thread for updated features from build.prop
http://forum.xda-developers.com/showthread.php?t=583030
I just did the install with the newest cyanogen and then tried calling myself and I dont have any issues.
Also, navigation works fine.
I have a G1 with CM 4.2.4, and I'm not having the issue either. I tested incoming calls with the NAV and in maps.
I finally got Navigation -and- paid apps in Market to show, but, I am experiencing the same problem as the OP mentioned.
I don't want to lose Navigation but this is a little annoying. Someone mentioned if I put the original build.prop and build.trout.prop back, Navigation will not show up. How can we get the best of both worlds?
[delete - repeat post]
Proxin said:
I finally got Navigation -and- paid apps in Market to show, but, I am experiencing the same problem as the OP mentioned.
I don't want to lose Navigation but this is a little annoying. Someone mentioned if I put the original build.prop and build.trout.prop back, Navigation will not show up. How can we get the best of both worlds?
Click to expand...
Click to collapse
i swear i feel like people just post without reading anything. i posted a link to a thread that will fix your problem. look up a few posts. another member here had an update.zip that will install the maps without breaking the market, without making the weird floating box, and without any other weird problems. if you are running cyanogen it will work perfect.
the .props need to me modified to allow navigation to remain longer than a few hours. just apply the update-navigation.zip from recovery mode and it will fix your issue.
Babaki said:
look up a few posts. another member here had an update.zip that will install the maps without breaking the market, without making the weird floating box, and without any other weird problems. if you are running cyanogen it will work perfect.
Click to expand...
Click to collapse
Actually I am having this same issue WITH using that .zip but for me it is no big deal. We are lucky to have Nav, I will take it with whatever problems (temporary of course) it comes with!
i had the double tap issue after i manually installed nav on wednesday. today i ran that .zip and the box is gone. i dont get why it would work for some people and not others.
the zip was actually updated 3 or 4 times. so if you applied it when it was first dropped, maybe you have an old version
I've noticed that quite often some apps fail to appear on my recent apps list (the one that appears when you long press the home button). For example I am running Opera Mobile, I long press home, I switch to another app for a few seconds to look at something, then I long press home again but Open Mobile is missing form the list! This can be fixed by immediately pressing back to close the recent apps list and then reopening it by long pressing home. The second time all apps are properly there.
This problem is not limited to S3 mini. A friend running 4.1 on some other Samsung phone (the one with the curved screen, I don't remember the model) also encounters this problem.
Anyone else here affected? I see no references to this problem on the web. Any way to solve this? Or perhaps any news about s3 getting 4.2 hopefully fixing this?
It's quite annoying considering it happens a few times per day to me.
Tritonio_GR said:
I've noticed that quite often some apps fail to appear on my recent apps list (the one that appears when you long press the home button). For example I am running Opera Mobile, I long press home, I switch to another app for a few seconds to look at something, then I long press home again but Open Mobile is missing form the list! This can be fixed by immediately pressing back to close the recent apps list and then reopening it by long pressing home. The second time all apps are properly there.
This problem is not limited to S3 mini. A friend running 4.1 on some other Samsung phone (the one with the curved screen, I don't remember the model) also encounters this problem.
Anyone else here affected? I see no references to this problem on the web. Any way to solve this? Or perhaps any news about s3 getting 4.2 hopefully fixing this?
It's quite annoying considering it happens a few times per day to me.
Click to expand...
Click to collapse
Never happened...maybe it's related to the specific app (in your case Opera Mobile). It also happens with other apps?
dariofreud said:
Never happened...maybe it's related to the specific app (in your case Opera Mobile). It also happens with other apps?
Click to expand...
Click to collapse
I'm pretty sure it happens with many apps. I'll keep a closer eye on it and if it only happens with Opera I'll reply again. But I'm pretty sure I would have noticed if only Opera was causing it.
Tritonio_GR said:
I'm pretty sure it happens with many apps. I'll keep a closer eye on it and if it only happens with Opera I'll reply again. But I'm pretty sure I would have noticed if only Opera was causing it.
Click to expand...
Click to collapse
Ok let know if it's only opera or some else. Just to give a feedback i'll download and see if it also happens to me.
So i'll let you know in a while
---------- Post added at 04:03 PM ---------- Previous post was at 03:54 PM ----------
dariofreud said:
Ok let know if it's only opera or some else. Just to give a feedback i'll download and see if it also happens to me.
So i'll let you know in a while
Click to expand...
Click to collapse
Nope, for me it remains. Tried to switch and remain on another app, spending some time on it but opera remains in memory as usual...
Don't know what to say, maybe some process in the rom..
Do you have root privileges? Maybe you can try some mod rom if you want...
Hope someone else can give you more help, good luck :good:
You're not the only one experiencing this problem It happens every time you switch to another app for few seconds (5-6). I guess this happens because the SystemUI process doesn't have enough time to refresh the index of the apps running in background and generate new thumbnails for them ^^
dariolob said:
You're not the only one experiencing this problem It happens every time you switch to another app for few seconds (5-6). I guess this happens because the SystemUI process doesn't have enough time to refresh the index of the apps running in background and generate new thumbnails for them ^^
Click to expand...
Click to collapse
That's exactly my, wild, guess. Not enough time to generate a thumbnail or something. So it's an android bug and there's nothing to do about it? And why all the lack of information on this bug on the internet?
Hmm
Tritonio_GR said:
That's exactly my, wild, guess. Not enough time to generate a thumbnail or something. So it's an android bug and there's nothing to do about it? And why all the lack of information on this bug on the internet?
Click to expand...
Click to collapse
Over a year later and I run into this problem on an S4 running 4.4.2. This thread is literally the only info I can find on this problem. Such a pain, I rely on the recent apps list a lot and half the time either the list order does not update, or an app I last opened or two is missing. Did you manage to resolve this?
This bugs the crap out of me. Google is so lazy and they never fix stuff they just let it go on forever and ever
Hey all,
As I'm sure you all know Snapchat recently rolled out an update that included the now very popular Geofilters. However, they do not show up for me on my HTC one. I got the State ones that were present for the Holiday season, but now that those are gone I am left with the basic filters. No cool location based ones now. No one else I know is having any problems with it on their Android or iOS devices, and after much searching I have not found a reason why I am not getting them too. Have any of you experienced the same issue or know of any solutions?
Thanks
blu_rush said:
Hey all,
As I'm sure you all know Snapchat recently rolled out an update that included the now very popular Geofilters. However, they do not show up for me on my HTC one. I got the State ones that were present for the Holiday season, but now that those are gone I am left with the basic filters. No cool location based ones now. No one else I know is having any problems with it on their Android or iOS devices, and after much searching I have not found a reason why I am not getting them too. Have any of you experienced the same issue or know of any solutions?
Thanks
Click to expand...
Click to collapse
I thought these filters were only unlocked/available when you are at a very specific location. Maybe this is the problem, you are not located where there are filters available... Anyway you would probably have a better answer by asking them directly on their support page. Unless location services are disabled on your M7, this is probably a problem with the app, not with your phone...
alray said:
I thought these filters were only unlocked/available when you are at a very specific location. Maybe this is the problem, you are not located where there are filters available... Anyway you would probably have a better answer by asking them directly on their support page. Unless location services are disabled on your M7, this is probably a problem with the app, not with your phone...
Click to expand...
Click to collapse
I'm having the same issue (but I'm not sure if it's a phone problem or a snapchat problem). My GPS/location services are on and I am definitely in an area that has geofilters (my roommate gets them on his phone). I've tried re-installing the app and I still don't get them. I'm also on Snapchat beta, but I don't think that has anything to do with it. If anyone knows a fix for this, let me know!
Thank you for the information in your blog, I would like to recommend FineFilterz.com -MK
This is an amazing site try it
---------- Post added at 12:25 PM ---------- Previous post was at 12:10 PM ----------
Try finefilterz website it is an amazing site
I'm on chroma anyone have this issue? I go to the google search app and go to images once I scroll a image or two it pauses then goes back to the home screen. It does not say force close or anything and when I check the recents list its not on there. Anyone have this issue?
Yes! I have this too and it's driving me crazy. Have you figured out a fix? I even switched to another ROM and it's still happening.
Yes, always happens to me.. I'm using slim gapps. Not sure, but may be a Google bug. I keep meaning to get logs but I always forget.
---------- Post added at 02:44 PM ---------- Previous post was at 02:43 PM ----------
Actually Facebook does the same when I use the built in Facebook viewer to read an article / watch a video.
Checking in with the same problem. I'm on hoppySlim with the Slim gApps mini 5.0.build.0.x-20150508. It happens a lot with normal searches but Google Image Search almost guarantees a crash.
It is extremely annoying. It seems to be aosp related because doesn't happen on cleanrom.... I like chroma a lot but with this annoying crash I can't handle it!
Had the same problem. This helped.
https://play.google.com/store/apps/details?id=com.google.android.webview
sully112277 said:
Had the same problem. This helped.
https://play.google.com/store/apps/details?id=com.google.android.webview
Click to expand...
Click to collapse
Do any of you wanna try this? I just finished putting everything back on clean ROM >_>
kurofox23? said:
Do any of you wanna try this? I just finished putting everything back on clean ROM >_>
Click to expand...
Click to collapse
I'm on a clean rom too. I'll try it.
Edit.. Haha. First image search closed as soon as untouched the screen.
rootSU said:
Haha. First image search closed as soon as untouched the screen.
Click to expand...
Click to collapse
Just tried it out on a fresh flash. First image search closed for me, too.
I also went back and even went as far as wiping internal storage... Still closing as well...back to cleanrom
kurofox23? said:
I also went back and even went as far as wiping internal storage... Still closing as well...back to cleanrom
Click to expand...
Click to collapse
I just image search on chrome. I have to open the image in chrome anyway to download it.
rootSU said:
I just image search on chrome. I have to open the image in chrome anyway to download it.
Click to expand...
Click to collapse
Google search is always faster. I just tap search in nova and I'm off. Or I'll voice command it. With chrome you have to open new tab or get rid of what you were doing and erase whatever text is in search box. AKA I'm lazy Lol.
But in all honesty I prefer the google search.
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: