Ever since last week I got all sensors of the device not working for no apparent reason.
I've reported about this, but then found out it's a very known issue that wasn't solved by Google yet, and that it randomly occurs for Pixel devices of all kinds, starting from Android 10.
Because of this issue, none of these work: auto-rotate, active edge, flip to shhh, proximity, ambient light, double tap to wake...
I tried to do factory reset, I tried to re-flash the firmware, update it to Android R, but none of those helped. I wanted to flash Android 9 somehow, because it says that the issue starts on Android 10, but then noticed there is no Android 9 for Pixel 4.
Then I noticed that some claim they found a fix for it, but on Pixel 3-XL :
Ask someone with working sensors to share the following folder with you: root/mnt/vendor/persist/sensors. Please ensure the device they have is the same as yours (Pixel 3 (blueline) and Pixel 3 XL (crosshatch) are NOT the same devices). They should, ideally, share it as a *.tar file to keep the permissions of subfiles intact.
Instructions to generate this tar file are here: https://forum.xda-developers.com/pix...4/post80833171
On your rooted phone running Android 10, navigate to: root/mnt/vendor/persist/ and first of all, backup your /sensors/ folder. Then, paste the contents of the tar file in there so you have the sensors folder from the working device that was shared with you.
Reboot and report. You should have working sensors now.
Click to expand...
Click to collapse
Can anyone please help me on this?
Would this help for Pixel 4 too?
If so, could anyone please share the file here, so that I could try it ?
Why not just RMA? Yeah, you'll get a refurb but it will work correctly.
bobby janow said:
Why not just RMA? Yeah, you'll get a refurb but it will work correctly.
Click to expand...
Click to collapse
RMA? I'm not in a country that Google provides service. Only some stores even offer to sell the device.
Plus what if it happens again?
AndroidDeveloperLB said:
RMA? I'm not in a country that Google provides service. Only some stores even offer to sell the device.
Plus what if it happens again?
Click to expand...
Click to collapse
Reports are that it doesn't happen on a new or RMA device but that's moot in your case. I don't see many options for you other than waiting.
bobby janow said:
Reports are that it doesn't happen on a new or RMA device but that's moot in your case. I don't see many options for you other than waiting.
Click to expand...
Click to collapse
Waiting for what?
Do you have Pixel 4? Can you please share the exact files that are suggested there?
Maybe it could help?
AndroidDeveloperLB said:
Waiting for what?
Do you have Pixel 4? Can you please share the exact files that are suggested there?
Maybe it could help?
Click to expand...
Click to collapse
Wait for an update that fixes your issue. Some have said the Feb update did it, some say no. Maybe the March update? I don't know but if you can't RMA then either flash another rom or wait for a fix from Google. It's a known issue so hopefully it will be fixed soon.
bobby janow said:
Wait for an update that fixes your issue. Some have said the Feb update did it, some say no. Maybe the March update? I don't know but if you can't RMA then either flash another rom or wait for a fix from Google. It's a known issue so hopefully it will be fixed soon.
Click to expand...
Click to collapse
I had stock ever since I got Pixel 4 (had Pixel 2 before). Maybe a custom rom will fix it. Any that you can recommend? I thought there aren't any custom ROMs for it yet.
I actually don't know how to flash custom ROMs on Pixel 4. TWRP doesn't seem to be a possible solution on it yet, no?
I only succeeded rooting it with Magisk, by patching the boot file. Tried to do it on Android R (was worth it if it worked), but it didn't work, sadly.
On Pixel 2 I could use TWRP. For some reason I failed to let it stay, so I had to flash it each time via the PC just to run it. On Pixel 4 I couldn't even find TWRP. Maybe now it's available.
AndroidDeveloperLB said:
I had stock ever since I got Pixel 4 (had Pixel 2 before). Maybe a custom rom will fix it. Any that you can recommend? I thought there aren't any custom ROMs for it yet.
I actually don't know how to flash custom ROMs on Pixel 4. TWRP doesn't seem to be a possible solution on it yet, no?
I only succeeded rooting it with Magisk, by patching the boot file. Tried to do it on Android R (was worth it if it worked), but it didn't work, sadly.
On Pixel 2 I could use TWRP. For some reason I failed to let it stay, so I had to flash it each time via the PC just to run it. On Pixel 4 I couldn't even find TWRP. Maybe now it's available.
Click to expand...
Click to collapse
Hopefully, someone will jump in here and help you with a custom rom suggestion. I haven't bl unlocked since midway through my 5X so I'm not the one to ask. From what I understand TWRP is basically on hold but I could be wrong.
damn, after almost 3 years i come here with the same issue, seems like nobody linked the persist.img or fixed the issue here
Related
This morning, my Note received a rather large software update that installed without many problems. Most likely certain security updates, but I was surprised to receive it as we are not really "accustomed" to any attention from Samsung for this tablet. Any further comments from anybody else?
I got the same.
Sent from my HTC 10 using XDA-Developers Legacy app
many problems? like what i have it to and i hate updating. anything broke? IR blaster still work? Please and thanks.
Mispelling
nanofoxx said:
many problems? like what i have it to and i hate updating. anything broke? IR blaster still work? Please and thanks.
Click to expand...
Click to collapse
Sorry for the misspelling. I meant to say "without any problems" not "without many problems". In fact, the whole update process was smooth and fast. Everything works fine. I understand, however, that everyone's setup is different and my experience should not be the absolute rule.
Nothing here on my device. Although it might be because I'm in Sweden.
Did anyone see any changes? I dont see/feel anything other than the version number change even the security patch level date remained the same. Is there a changelog somewhere
dingnecros said:
Did anyone see any changes? I dont see/feel anything other than the version number change even the security patch level date remained the same. Is there a changelog somewhere
Click to expand...
Click to collapse
I don't see any difference after the update, either. I wonder what it was supposed to have updated?
Maris_ said:
I don't see any difference after the update, either. I wonder what it was supposed to have updated?
Click to expand...
Click to collapse
There's a whole new Lollipop firmware on the San mobile firmware site.
Yes...problems
My tablet updated and now the OS boots super slow and then does a soft shutdown and reboots a second time. It takes more than 60 secs to get to the home screen. Anyone know how to uninstall this update?
ADRz said:
This morning, my Note received a rather large software update that installed without many problems. Most likely certain security updates, but I was surprised to receive it as we are not really "accustomed" to any attention from Samsung for this tablet. Any further comments from anybody else?
Click to expand...
Click to collapse
I've seen this post for a few days but not had time to respond till now.
I've got an SM-P605v. Haven't seen, or been able to download the update you've mentioned. This may be because I don't use Verizon as my connectivity partner, or it may be that my particular tablet's OS doesn't need the security updates that yours did.
Kingsman1 said:
I've seen this post for a few days but not had time to respond till now.
I've got an SM-P605v. Haven't seen, or been able to download the update you've mentioned. This may be because I don't use Verizon as my connectivity partner, or it may be that my particular tablet's OS doesn't need the security updates that yours did.
Click to expand...
Click to collapse
I also have a SM-P605V but have Verizon as my carrier. I got the notification to update today. I don't see anything on VZW site about it nor under the specific SKU on SamMobile (still has 10/15/15 as the last official update). When looking at the SM-P605 model, there are some in the list (even today's date), though they are for non-USA countries.
Even so, it looks like they are still all Android 5.1.1, so it's likely just some minor tweaks. To my understanding, you would need to pop in an activated Verizon SIM to get the update for your specific tablet, as Verizon is the one that issues it. You can also wait until it's posted on SamMobile and manually do it. https://www.sammobile.com/firmwares/database/SM-P605V/
---------- Post added at 12:02 PM ---------- Previous post was at 11:33 AM ----------
I think I found the official from Verizon: https://www.verizonwireless.com/support/samsung-galaxy-note-10-2014-update/
Software Version: LMY47X.P605VVRSDPL1
The current software update gives you the most up to date Android™ security patch on your device.
Click to expand...
Click to collapse
(I called VZW and she confirmed that it was an Android Security patch, no MM, darnit!)
Kingsman1 said:
I've seen this post for a few days but not had time to respond till now.
I've got an SM-P605v. Haven't seen, or been able to download the update you've mentioned. This may be because I don't use Verizon as my connectivity partner, or it may be that my particular tablet's OS doesn't need the security updates that yours did.
Click to expand...
Click to collapse
You should be able to flash this now that Sammobile posted it... https://www.sammobile.com/firmwares/database/SM-P605V/
I got this a couple of days ago - managed to odin flash after I put the wrong file and got the boot loader triangle a day before.
Its extremely stable and the tablets working like a dream - the only issue is no root.
Edit: I noticed a great improvement in battery management and it will charge to 100% from 30% in 4 hours before I flashed the 5.1.1 rom it took nearly 8 hours with a new(second hand) USB Flex connector and nearly 20 hours with the old usb flex connector to go from 30% to 100%.
I really like this tablet - it reminds me so much of my SM-N910F note 4.
You can root the latest firmware and also install twrp. I have a 600.
louvass said:
You can root the latest firmware and also install twrp. I have a 600.
Click to expand...
Click to collapse
did it actually do anything? or is it not worth it
graffix31 said:
did it actually do anything? or is it not worth it
Click to expand...
Click to collapse
Probably just a security update
Please excuse my silly question but I have P600 with 5.1.1 and never rooted. Do I need to install twrp before I update or it doesn't matter? Updates always make me uneasy with locking bootloader or needing new root methods.
If you just want to update then flash with Odin and the appropriate file. Try looking at sammobile.com for the appropriate rom file.
If you want root then you will need to install a custom recovery using CF auto or Twerp - the latter will NOT work on the SM-605v version as the bootloader is locked and will result in the yellow triangle and stating that the tablet has a strange recovery and that you should see a verizon technician. By installing the recovery you can then update the system or even try out new roms created by the people of this wonderful community.
Rooting will potentially stop business application with built in security from working - i.e. HSBC application, Virgin Media app and Sky Movies apps will not work on rooted phones to name a few.
I updated and rooted and everything is working ok. I had trouble with 64gb Sandisk microsd with "sd card unexpectedly removed" error. Then it mount itself back. Sometime it shows empty and asks to format and sometime it works. Also the lockscreen flicker and that usually when the card error happened. I suspect they are related and it happens only when waking up the device. The card works fine with all my other devices including my note 4 on stock 5.1.1. I'm not sure what caused it because I just used this sd card with the note 10.1 and then updated and rooted all in the same day.
Anyway, I removed the Sandisk and now I'm using 32gb Samsung and it only happened once for maybe 12 hours (could have been 100 times with Sandisk). Also, I don't notice the lockscreen flickering anymore. I will see if this problem comes back or it just that Sandisk doesn't play well my note. I have seen many people here reported similar problem with other Samsung devices for too many reasons. I don't believe file format is the issue but I'm using exFAT.
I just noticed December's images are up for og pixel xl and pixel
Zehlek said:
I just noticed December's images are up for og pixel xl and pixel
Click to expand...
Click to collapse
Eh Zehlek, I am trying to update from the August Pie build. Do you think just flashing the system.img and vendor.img would work (like it was in the Nexus days)? I can't really be bothered going through the re-rooting .
Thanks.
Anyone who has updated,,,have you noticed anything with the Dec update? Or just another security patch?
Archangel said:
Anyone who has updated,,,have you noticed anything with the Dec update? Or just another security patch?
Click to expand...
Click to collapse
Just the new search bar with the Google Assistant link and drawing program hidden in the Easter Egg.
jaytv said:
Just the new search bar with the Google Assistant link and drawing program hidden in the Easter Egg.
Click to expand...
Click to collapse
I heard for other devices (Pixel 2) the UI (At least on the home screen) has been much more fluid with the updated Pixel launcher. I would agree with this on the Pixel XL too now...I have far less stutters using navigation gestures and swiping right to go to the Discover feed. Good update!
This is really random, but after updating anyone else having an issue with the screen turning off when a right to far left of the screen is performed? Noticed it when I was swiping a word from far right of the screen to far left, and it turns the screen off. Does the same thing outside of the app. Checked the Gestures settings and couldn't find anything relevant. (Wiped data on upgrade) Any suggestions are appreciated!
chinesecooler said:
Eh Zehlek, I am trying to update from the August Pie build. Do you think just flashing the system.img and vendor.img would work (like it was in the Nexus days)? I can't really be bothered going through the re-rooting .
Thanks.
Click to expand...
Click to collapse
I'm not 100% sure I would ask @razorloves he is the expert on this one
chinesecooler said:
Eh Zehlek, I am trying to update from the August Pie build. Do you think just flashing the system.img and vendor.img would work (like it was in the Nexus days)? I can't really be bothered going through the re-rooting .
Thanks.
Click to expand...
Click to collapse
doubt it. you need the kernel too (boot.img). then you'd need to reflash twrp and magisk.
you also need new radio & bootloader img's.
what's so hard about re-rooting? you just have to flash twrp and magisk, right?
razorloves said:
doubt it. you need the kernel too (boot.img). then you'd need to reflash twrp and magisk.
you also need new radio & bootloader img's.
what's so hard about re-rooting? you just have to flash twrp and magisk, right?
Click to expand...
Click to collapse
Yeah figured that out. Initially I just flashed the two and it boot looped. Had to do the lot and reroot. :/
Archangel said:
Anyone who has updated,,,have you noticed anything with the Dec update? Or just another security patch?
Click to expand...
Click to collapse
Before the update, I had to manually enter my apn, but After December update, all my apn automatically work. I noticed better signal reception too. I don't know if it's the update related.
I liked it,
Rebooted after initial setup and fastbooted into twrp...
Installed king kernel 3.16
Installed magisk.
Perfection, battery lasts forever now. 5.5h sot is an daily thing, 3.5-4h if streaming pandora
So basically I've tried every method shown in YouTube or XDA on how to get the update but I still haven't received it. Should I worry about this or am I just a little impatient.
Important information:
After receiving the November 1st update my phone entered in a bootloop without any reason, I suspect it was due to the Google Cam app that I had installed while on 7.1 however I made it to 8.1 without having any issue so I doubt it. Anyway, after this bootloop I had no other option than to make a factory reset (loosing Gcam in the process). I was so pleased with the improvements the Google Cam made that I felt the necessity of installing it again. However, if used the same method that I did for the first time it would end in a factory reset since it had to unlock the bootloader. I found a solution on a thread which mentioned that this factory reset could be avoided if you press the volume down button while unlocking the bootloader. This worked fine. So what I did was unlock the bootloader, momentarily install Magisk, enable Camera2Api by flashing a module, uninstall Magisk and then lock the bootloader again. A restart later I had my phone working with Google Cam again (and still having to this day).
So my question is:
Could this affect in any way my OTA updates and be the reason why I'm not getting Android P?
Sorry for the long post but I had to make sure all this details were cleared.
I'll wait for a response :fingers-crossed:
You have seen all threads (both here and at miui.com) about broken networks?
The update was buggy, the phone should support LTE band 1, 3, 5, 7, 8, 20, 38, 40.
After Pie update it only supports 1, 3, 5, 40, 41.
Click to expand...
Click to collapse
Among few other reported bugs...
And You still want it that badly?
JockeSve said:
You have seen all threads (both here and at miui.com) about broken networks?
Among few other reported bugs...
And You still want it that badly?
Click to expand...
Click to collapse
For example I don't care about 4G, so maybe OP is on the same boat..[emoji846]
_mysiak_ said:
For example I don't care about 4G, so maybe OP is on the same boat..[emoji846]
Click to expand...
Click to collapse
That could be the reason of course...
But quite many of people complaining that they haven't received the update don't read the warnings about this (and previous version) beta release. - AFAIK it's not globally released as release yet...
I still haven´t received Android Q. Can somebody help me, please?
JockeSve said:
You have seen all threads (both here and at miui.com) about broken networks?
Among few other reported bugs...
And You still want it that badly?
Click to expand...
Click to collapse
I was a little aware about those issues but it looked like it wasn't a big deal. But now that you talk about it feels like maybe I was wrong ??*. Guess I'll just wait and see what happens.
Thanks for the info.
PS: what I'm more interested in knowing now is if the process I followed could have affected the OTA's in any way
fmorgado1987 said:
I still haven´t received Android Q. Can somebody help me, please?
Click to expand...
Click to collapse
Yeah, maybe I am a little impatient
_mysiak_ said:
For example I don't care about 4G, so maybe OP is on the same boat..[emoji846]
Click to expand...
Click to collapse
Actually I do care about 4G and wouldn't like loosing it
Update
Thanks for the replys.
I didn't want to sound desperate about the issue and if the update is having problems or bugs I don't know if I'm still very interested. I only created this thread to gather some information about the update since I can't really find any reputable source talking about it and didn't know if it is rolling live world wide o was just a beta leak like many people say.
Update 2
I have finally received the update via OTA without VPN method or anything. What should I do? I want to preserve 4G connection but I'm not really sure if the modem used in Android Pie has compatibility with my country's networks (I'm from Argentina)
i accidentally erase my backup rom in my phone..and now my phone dont have os..and i download rom online..but i couldn't flash it..always an error is flash..REMOTE PARTITION DOESN'T EXIST..what will i do?? do ineed to root my phone??
Got the Pie update notice today along with January security patch. My question is for those who, like me, waited until the official notification to update.
With so many here experiencing problems with the previous update(s), it's hard to distinguish which threads are for it, custom, or for the latest Xiaomi update. Did you update to Pie in January? Are there any issues you've noticed with the update? Should I pull the trigger on the update or wait?
Any info is appreciated, as always.
Regards,
KB
I just directly installed January update, migrated from Oreo. Didn't face any issues as of yet.
By the way how do you guys turn on FM Radio?
No data since update.
I did the update earlier today and haven't been able to get mobile data since. Can anybody help me?
Barneyjp18 said:
I did the update earlier today and haven't been able to get mobile data since. Can anybody help me?
Click to expand...
Click to collapse
I downloaded my update with the mobile data and used it since right after. No problem. Wifi seems ok too.
Barneyjp18 said:
I did the update earlier today and haven't been able to get mobile data since. Can anybody help me?
Click to expand...
Click to collapse
That sounds like a serious issue, and one that makes me think I might just wait a bit on this update. Thanks for the feedback, and I hope you get the issue resolved. Where are you located?
KB_Thailand said:
That sounds like a serious issue, and one that makes me think I might just wait a bit on this update. Thanks for the feedback, and I hope you get the issue resolved. Where are you located?
Click to expand...
Click to collapse
I'm am located in Japan. Did the update while connected to wifi on WiFi. I never even questioned it as never had a problem in the 14months I have owned the phone.
Barneyjp18 said:
I'm am located in Japan. Did the update while connected to wifi on WiFi. I never even questioned it as never had a problem in the 14months I have owned the phone.
Click to expand...
Click to collapse
I understand. I've not experienced many of the issues some have with the updates, though the battery issues a few updates ago were driving me crazy. Those seem to be resolved now and I can easily get 2 to 3 days out of a charge. The only reason I hesitated was I read some of the threads from the initial update Xiaomi put out, and was trying to be sure this one was less troublesome before allowing it. I saw a couple of folks complain about the loss of WiFi and Data on the first update, so perhaps all of the initial bugs haven't been squashed. I'm in Thailand, so need it to be as clean as possible.
Again, hope you get the issue resolved. Let us know if you do.
I am from Czech Republic and I can say I don't have any LTE issues, battery is great. No issues with Pie at all.
@KB_Thailand
If you are a big fan of gcam.. Then dont update, else do it.
For me everything is working fine, except gcam focus issue.
Stock camera works though.
ShaikhSiddiky said:
I just directly installed January update, migrated from Oreo. Didn't face any issues as of yet.
By the way how do you guys turn on FM Radio?
Click to expand...
Click to collapse
You need to connect a wired headphone in the 3.5 mm jack, then you will get FM.
Regards
Eshwar123 said:
@KB_Thailand
If you are a big fan of gcam.. Then dont update, else do it.
For me everything is working fine, except gcam focus issue.
Stock camera works though.
Click to expand...
Click to collapse
It's not working even flashing the magisk patch module?
ccalixtro said:
It's not working even flashing the magisk patch module?
Click to expand...
Click to collapse
I don't know about this, coz I'm a non rooted user.
If it works, please share,
Eshwar123 said:
I don't know about this, coz I'm a non rooted user.
If it works, please share,
Click to expand...
Click to collapse
Well it works for me. Just unlock the bootloader, put the phone in fastboot mode, boot twrp cosmicdans from adb, flash magisk and when it boots open magisk and download camera patch for pie. It's really easy but i think when you unlock the bootloader you lose your data so think about it.
KB_Thailand said:
Got the Pie update notice today along with January security patch. My question is for those who, like me, waited until the official notification to update.
Click to expand...
Click to collapse
If you are stock 100% do it, if not hang out a while, no big issues now for stock, very few people on stock have had an issue with the latest Pie, those that do have very simple easily fixed things.
Barneyjp18 said:
I did the update earlier today and haven't been able to get mobile data since. Can anybody help me?
Click to expand...
Click to collapse
Try the last page here, changing the IPv4/IPv6 setting, it fixed it for others who had a problem.
https://forum.xda-developers.com/mi-a1/help
I have also lost my data connection since the update.
Does anyone have any idea on how to fix this problem?
EDIT : It seems that the update deleted the apn configuration. Re-entering it solved the issue.
Based on the positive responses I went ahead and did the update since my A1 is stock. So far so good with no issues I've noticed. Both data and wifi seem to be working properly.
Thanks for the responses!
After updating to pie many of the users including myself face an issue where the mic volume has reduced a lot. Other people can't hear me properly on normal voice calls
ccalixtro said:
Well it works for me. Just unlock the bootloader, put the phone in fastboot mode, boot twrp cosmicdans from adb, flash magisk and when it boots open magisk and download camera patch for pie. It's really easy but i think when you unlock the bootloader you lose your data so think about it.
Click to expand...
Click to collapse
Thank you for confirming that,
After rooting, and installing the magisk patch, can I completely unroot and lock the bootloader, and will the patch still work?
Will unlocking the bootloader also wipe data?
(i thought only locking bootloader will wipe, we can use the vol button trick)
Thanks in advance.
Eshwar123 said:
Thank you for confirming that,
After rooting, and installing the magisk patch, can I completely unroot and lock the bootloader, and will the patch still work?
Will unlocking the bootloader also wipe data?
(i thought only locking bootloader will wipe, we can use the vol button trick)
Thanks in advance.
Click to expand...
Click to collapse
1. Unlocking bootloader wipes data
2. Does your phone contain nuclear weapon key? If no, then i don't see any reason you dont want a unlocked bootloader. (Manufacturer denying warranty for unlocked bootloader is thing of past, MI has no problem with it. Also you can lock phone just before giving it to MI store in any case)
3. As long as you install apps from playstore, i also dont see any problem with a rooted phone either.
.:Addicted:. said:
1. Unlocking bootloader wipes data
2. Does your phone contain nuclear weapon key? If no, then i don't see any reason you dont want a unlocked bootloader. (Manufacturer denying warranty for unlocked bootloader is thing of past, MI has no problem with it. Also you can lock phone just before giving it to MI store in any case)
3. As long as you install apps from playstore, i also dont see any problem with a rooted phone either.
Click to expand...
Click to collapse
I just want to stay stock and receive official updates and with gcam working as like on oreo. That's it Bro.,
That's why i wanted to unroot and keep the BL locked.
Will the vol down key avoid wipe for unlocking BL as well?
And will the patch work after unroot?
Thanks
The 4th beta is available publicly today and the Pixel 3a models are officially supported again. This means they should show up in "your available devices" and updates will automatically be pushed out to your device. This is certainly easier than having to manually flash them.
https://www.google.com/android/beta
Is this only for unlocked pixel 3a or will it work with carrier locked ones also, such as TMobile.
synaethe said:
Is this only for unlocked pixel 3a or will it work with carrier locked ones also, such as TMobile.
Click to expand...
Click to collapse
That is a good question, and honestly I don't know the answer for sure (my phone is bootloader unlocked).
That being said, the Q beta will come across like a normal update would. So I would think it is available to locked devices. Even if you want to quit the beta and go back to Android P, I think that comes across as an update as well (although it will do a factory reset of your device and you will have to download all apps and data again). This is the advantage to participating in the actual official beta vs. manually flashing the beta.
It's an over the air update. One of the points of getting pixel is to be on the bleeding edge with the OS. regardless of carrier. It's available whether you're locked or not. Downloading mine now and I'm still locked on T-Mobile.
Yeah confirmed downloading now. on EE network UK. Also seems fine updating from beta 3 which I was on.
sic0048 said:
That is a good question, and honestly I don't know the answer for sure (my phone is bootloader unlocked).
That being said, the Q beta will come across like a normal update would. So I would think it is available to locked devices. Even if you want to quit the beta and go back to Android P, I think that comes across as an update as well (although it will do a factory reset of your device and you will have to download all apps and data again). This is the advantage to participating in the actual official beta vs. manually flashing the beta.
Click to expand...
Click to collapse
Thanks looks like it will work, it started downloading as OTA once I opted in on the beta. Hopefully it's stable enough for basic use. Thanks!
Having a problem after updating to Q beta 4
Some apps will no longer start, and others leave a screen echo when going to home screen.
How do I re-wipe cache?
If that doesn't work I'll try a factory reset (which makes sense for switching from P to Q anyway)
Just updated to Q Beta 4. So far so good, all apps are running - let's see how this goes !
Sent from my Pixel 3a XL using Tapatalk
Matrioux said:
Having a problem after updating to Q beta 4
Some apps will no longer start, and others leave a screen echo when going to home screen.
How do I re-wipe cache?
If that doesn't work I'll try a factory reset (which makes sense for switching from P to Q anyway)
Click to expand...
Click to collapse
Ok, it seems to be a Nova launcher issue. pixel launcher works fine.
Sent from my Pixel 3a using Tapatalk
Matrioux said:
Ok, it seems to be a Nova launcher issue. pixel launcher works fine.
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
I find the Pixel launcher much smoother in the beta version. Using it as my default for the time being - was using Nova previously
Sent from my Pixel 3a XL using Tapatalk
Do bubble notifications work for anyone? I would like to try it out on beta 4.
apologies for the noob question but i'm on rooted stock, i understand i'll lose root installing Q but is there anything else i need to do to avoid getting myself into trouble? uninstall magisk?
edit: i'll tell you what not to do. don't uninstall magisk and reboot. this seemed innocuous enough but now i have the "No command" screen and android Q is the least of my concerns....
c_tho said:
apologies for the noob question but i'm on rooted stock, i understand i'll lose root installing Q but is there anything else i need to do to avoid getting myself into trouble? uninstall magisk?
edit: i'll tell you what not to do. don't uninstall magisk and reboot. this seemed innocuous enough but now i have the "No command" screen and android Q is the least of my concerns....
Click to expand...
Click to collapse
Take a breath. It's ok. If your bootloader is unlocked all you have to do is flash factory images with the -w and you should be up and running again in no time. It happens to everyone who plays with root at some point.
Sent from my Pixel 3a using Tapatalk
jmtjr278 said:
Take a breath. It's ok. If your bootloader is unlocked all you have to do is flash factory images with the -w and you should be up and running again in no time. It happens to everyone who plays with root at some point.
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
god thanks so much for this. appears that just flashing the magisk-patched boot image has the phone booting again but i guess that puts me back at square one (sans data)? assuming to get to Q the best approach is to flash the factory image (currently downloading), go through setup and then get the OTA?
c_tho said:
god thanks so much for this. appears that just flashing the magisk-patched boot image has the phone booting again but i guess that puts me back at square one (sans data)? assuming to get to Q the best approach is to flash the factory image (currently downloading), go through setup and then get the OTA?
Click to expand...
Click to collapse
Yes, flash stock boot.img, then OTA will work. But before doing so, join the beta program so that you'll receive beta 4.
syckman said:
Yes, flash stock boot.img, then OTA will work. But before doing so, join the beta program so that you'll receive beta 4.
Click to expand...
Click to collapse
all sorted now, on Qb4. thanks for the help folks. it's looking great.
Does beta 4 enables volte on non supported carriers?
Some people on their pixel 3 with beta 3 enables volte with other carriers. Can anyone confirm please
This has been my battery stats in BETA 4 since i flashed it.
I keep getting the notification to update on my Sprint locked Pixel 3a. I don't want to though because I'm really hoping to root this phone in the near future and I don't want to not be able to because I updated.
So I'm really just asking if the Q Beta 4 would affect being able to root?
Just an FYI guys, Beta 4 was pulled this morning due to a bootloop issue. If you're on the beta and get the problem, you'll have to roll back to P, if you're looking to upgrade to Q, id say wait and make sure the issue is fixed.